覆盖Jboss/Server/Default/lib中的Jar后重启,提示没有更新

最新推荐文章于 2021-01-19 02:07:51 发布
最新推荐文章于 2021-01-19 02:07:51 发布
阅读量190 收藏
点赞数
分类专栏： JBoss 文章标签： java
本文解决了一个关于JBoss服务器更新JAR包后出现的TLD属性识别问题。作者更新了JAR包但未同步更新TLD文件导致应用启动时遇到属性识别错误。最终通过将TLD文件放置于WEB-INF目录并重启JBoss解决了该问题。

摘要生成于 C知道 ，由 DeepSeek-R1 满血版支持， 前往体验 >

我原来项目的Jboss/Server/Default/lib中的jar版本需要更新
于是我拷贝新版本的jar覆盖掉其中的相应jar，结果重启后提示错误如下：
其中的toolBarPosition 是在新版本的jar中才定义的attibute，不知道怎么回事儿，希望各位帮忙
2007-12-10 10:40:51,125 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/ERP.[jsp]] Servlet.service() for servlet jsp threw exception
org.apache.jasper.JasperException: /hr/employeeInfo.jsp(88,7) Attribute toolBarPosition invalid for tag dataGrid according to TLD
at org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40)
at org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:407)
at org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:236)
at org.apache.jasper.compiler.Validator$ValidateVisitor.checkXmlAttributes(Validator.java:1198)
at org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:819)
at org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507)
at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
at org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)
at org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:838)
at org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507)
at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
at org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)
at org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:838)
at org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507)
at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
at org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)
at org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:838)
at org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507)
at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
at org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)
at org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:838)
at org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507)
at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
at org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)
at org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:838)
at org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507)
at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
at org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)
at org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2392)
at org.apache.jasper.compiler.Node$Root.accept(Node.java:489)
at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
at org.apache.jasper.compiler.Validator.validate(Validator.java:1737)
at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:178)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:306)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:286)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:273)
at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:566)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:311)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:687)
at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:469)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:403)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)
at org.operamasks.faces.context.ServletExternalContext.dispatch(ServletExternalContext.java:73)
at org.operamasks.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:286)
at org.jboss.seam.jsf.SeamViewHandler.renderView(SeamViewHandler.java:87)
at org.operamasks.faces.lifecycle.LifecycleImpl$RenderResponse.execute(LifecycleImpl.java:299)
at org.operamasks.faces.lifecycle.LifecycleImpl.doPhase(LifecycleImpl.java:118)
at org.operamasks.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:91)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:245)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:68)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:85)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:44)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:595)

自己回答吧，由于没有更新AOM组件的tld造成Attribute无法识别，将Tld文件复制到WEB-INF/下重启JBoss就Ok了！其实很简单的错误往往都在提示信息中，嗨，没注意，白浪费了几天时间。
Missing classpath entry D:\jboss-4.0.5.GA \server\default\lib\mail.jar
huang870615 专栏
07-26 772
尝试新版本Eclipse3.7 indigo 加载jboss4.2 服务，出现 Missing classpath entry D:\jboss-4.0.5.GA \server\default\lib\mail.jar 错误        我的jboss4.2 server下面只有一个messaging服务,没有default服务，如果default服务存在就不会产生   这样的问题...
jboss之启动加载过程详解(-)
kingwolfs的博客
05-18 1296
今天看了看jboss的boot.log和server.log日志，结合自己的理解和其他的资料，现对jboss的启动和加载过程做出如下总结； 本文以 JBoss Application Server 4.2.1 GA（以下简称JBoss）为例，介绍它在Windows平台上的启动过程。为了方便叙述，对平台环境做以下假定：Java运行时的安装路径为 C:/Java，JBoss的安装路径为C:/JB...
Jboss基础入门配置
独行者的专栏
11-05 4465
一、设置控制台登录窗口 安装好jboss并启动jboss后，在浏览器窗口的地址栏里键入                                                                                                                                                         
jboss mysql 连接池_项目经验——jboss 配置数据库连接池
weixin_33646989的博客
01-19 261
数据库的连接和关闭是非常消耗系统资源的，在多层结构的应用环境中，这种资源消耗又直接的反映到系统性能上来。在项目实际应用中，最常用的解决方案便是建立数据库连接池。一、数据库连接池基本原理当程序启动时，系统主动建立出足够的数据库连接，并将这些连接组成一个连接池。每次应用程序请求数据库连接时，无需重新建立，直接从链接池中获取已建立连接。使用完毕后，无需关闭，直接归还给数据库连接池，以备其他程序调用。通过...
jboss问题总结
10-25
二、JBoss部署应用程序时，数据库驱动放在应用程序的web-inf/lib下时，首次连接数据库是无法建立连接， 原因可能是jboss启动时，初始化数据源没有找到数据库驱动，而首次是连接是找不到数据源，但是开始初始化数据源，所以在连接是数据库连接正常， 解决办法：将数据库驱动程序放在%jboss_home%\server\default\lib文件夹下
我使用的openacs是openacs-bin-0.5.0.3，它里面是一个acs.ear文件然后把这个文件复制到了Jboss的/server/default/deploy/目录下
03-26
- **部署失败**：检查JBoss日志中的`ClassNotFoundException`或数据库连接错误，确保驱动包（如`postgresql-*.jar`）已放入`/server/default/lib`目录。 - **清理缓存**：若修改未生效，执行 **Project → Clean**...
jboss打包不起作用，替换jar即可
11-29
常见的日志路径是`JBOSS_HOME/server/default/log/server.log`。 5. **社区支持**： 如果以上方法都无法解决问题，不要忘记利用社区资源。JBoss有一个活跃的用户社区，可以在官方论坛或Stack Overflow等平台寻找...
jboss6 sqlserver 2000 数据库连接配置
03-29
3. **配置JNDI数据源**：在`JBOSS_HOME/server/default/deploy/jboss-service.xml`或应用特定的配置文件（如`META-INF/jboss-service.xml`）中，定义JNDI数据源。例如： ```xml <jndi-name>java:jboss/data...
16:51:33,561 ERROR [URLDeploymentScanner] Incomplete Deployment listing: --- Incompletely deployed packages --- org.jboss.deployment.DeploymentInfo@ebb24ee4 { url=file:/opt/jboss-4.2.2.GA/server/default/deploy/acs.ear } deployer: org.jboss.deployment.EARDeployer@225b1b status: Deployment FAILED reason: URL file:/opt/jboss-4.2.2.GA/server/default/tmp/deploy/tmp3003181215135402123acs.ear-contents/acs-war-exp.war/ deployment failed state: FAILED watch: file:/opt/jboss-4.2.2.GA/server/default/deploy/acs.ear altDD: null lastDeployed: 1742892691824 lastModified: 1742892691617 mbeans: --- MBeans waiting for other MBeans --- ObjectName: jboss.j2ee:service=EjbModule,module=acs-ejb.jar State: FAILED Reason: org.jboss.deployment.DeploymentException: Error while fixing table name; - nested throwable: (org.jboss.util.NestedSQLException: Could not create connection; - nested throwable: (org.jboss.resource.JBossResourceException: Failed to register driver for: com.mysql.jdbc.Driver; - nested throwable: (java.lang.ClassNotFoundException: No ClassLoaders found for: com.mysql.jdbc.Driver)); - nested throwable: (org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (org.jboss.resource.JBossResourceException: Failed to register driver for: com.mysql.jdbc.Driver; - nested throwable: (java.lang.ClassNotFoundException: No ClassLoaders found for: com.mysql.jdbc.Driver)))) ObjectName: jboss.web.deployment:war=acs-war.war,id=225351972 State: FAILED Reason: org.jboss.deployment.DeploymentException: URL file:/opt/jboss-4.2.2.GA/server/default/tmp/deploy/tmp3003181215135402123acs.ear-contents/acs-war-exp.war/ deployment failed --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- ObjectName: jboss.j2ee:service=EjbModule,module=acs-ejb.jar State: FAILED Reason: org.jboss.deployment.DeploymentException: Error while fixing table name; - nested throwable: (org.jboss.util.NestedSQLException: Could not create connection; - nested t
最新发布
03-26
- **服务器级**：`JBOSS_HOME/server/default/lib/`目录中 $$ \text{驱动文件路径} = \begin{cases} \text{应用级} & \text{仅当前应用可用} \\ \text{服务器级} & \text{全局可用} \end{cases} $$ 2. **...
jboss: Server/default/Deploy（部署Jboss用用程序的目录）
KingQzhang的专栏
08-07 919
 jboss:  Server/default/Deploy（部署Jboss用用程序的目录）whirlybird ，jet，vehicle.aircraft.constructing.suspend.prority. lib（default服务器启动时回被加载的jar文件）work（工作目录）   Conf（default服务器的配置文件）log（存放default服务器的日志文件）
jboss之各deployment共享各class的证据
wangxiangjunpxp
12-28 277
2006-12-14 15:17:36,858 INFO  [WXJ] 这次共查到：0 个记录! 2006-12-14 15:17:47,584 INFO  [org.apache.catalina.core.StandardContext] Reloading this Context has started 2006-12-14 15:17:55,520 INFO  [WXJ] ucl3...
jboss eap6.1 (7)(tld文件解决)
zhanglu5116的专栏
11-29 2335
16:00:30,019 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/asset].[jsp]] (http-/0.0.0.0:8080-5) JBWEB000236: Servlet.service() for servlet jsp threw exception: org.apache.
jboss配置入门
logal的专栏
12-06 1297
jboss配置入门(1)2007-11-01 10:442.0 FOR NEW USER2.0.1 JBOSS 的一点说明$JBOSS-HOME/server/下有3个目录，all/default/minimal，它们是表示3种配置，全部的配置、默认配置、最小配置，我们在启动JBOSS服务时，可以指定run –c all 表示是启动all配置(将会加载所有服务)；run 表示是以默认配置启动;
JBoss将common下的lib放入classspath
netliving的专栏
12-25 168
这几天在进行jboss下的开发，那的最小的容器本来想一点一点的添加功能，结果发现真的很麻烦啊。 默认的common下的lib没有加入到classpath中，需要修改配置文件 &lt;domain&gt;/conf/jboss-service.xml，添加   &lt;classpath codebase="${jboss.common.lib.url}" archives="*"/&gt;...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值