Jboss启动错误
在现有应用程序上，我尝试启动 JBOSS 服务器，但出现以下错误。
不幸的是，我还不清楚，这个 jboss 上已经配置了什么并且正在使用什么。目前;我想尽快解决这个错误。
如果查看堆栈跟踪，您可以建议缺少哪种配置或者我应该查看什么来解决此问题；那么我将非常感激。
任何帮助表示赞赏。
------------------在下面Skaffman的帮助下；我能够将堆栈跟踪减少到这个------------------
07:36:36,971 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
--- MBeans waiting for other MBeans ---
ObjectName: xyz.management:service=Queue,name=managementQueue
State: CONFIGURED
I Depend On:
jboss.messaging:service=ServerPeer
ObjectName: xyz.management:service=Queue,name=indexQueue
State: CONFIGURED
I Depend On:
jboss.messaging:service=ServerPeer
ObjectName: xyz.management:service=Queue,name=adaptiveLearningQueue
State: CONFIGURED
I Depend On:
jboss.messaging:service=ServerPeer
ObjectName: xyz.management:service=Queue,name=xyzErrorQueue
State: CONFIGURED
I Depend On:
jboss.messaging:service=ServerPeer
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.messaging:service=ServerPeer
State: NOTYETINSTALLED
Depends On Me:
xyz.management:service=Queue,name=managementQueue
xyz.management:service=Queue,name=indexQueue
xyz.management:service=Queue,name=adaptiveLearningQueue
xyz.management:service=Queue,name=xyzErrorQueue
javax.naming.NameNotFoundException: XAConnectionFactory not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
at org.jnp.server.NamingServer.lookup(NamingServer.java:296)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:589)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:182)
at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:188)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerStartDelivery(JMSContainerInvoker.java:665)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl$ExceptionListenerRunnable.run(JMSContainerInvoker.java:1594)
at java.lang.Thread.run(Thread.java:619)
On an existing application I am trying to startup the JBOSS server and I get following error.
Unfortunately I do not know clearly as yet, what all has been configured and is being used on this jboss. For now; I quickly want to get the error sorted out.
If looking at the stack trace, you can suggest what kind of configuration is missing or what I should be looking at to fix this problem; then I'll be really grateful.
any help is appreciated.
------------------After Skaffman's help below; I was able to reduce the stacktrace to this------------------
07:36:36,971 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
--- MBeans waiting for other MBeans ---
ObjectName: xyz.management:service=Queue,name=managementQueue
State: CONFIGURED
I Depend On:
jboss.messaging:service=ServerPeer
ObjectName: xyz.management:service=Queue,name=indexQueue
State: CONFIGURED
I Depend On:
jboss.messaging:service=ServerPeer
ObjectName: xyz.management:service=Queue,name=adaptiveLearningQueue
State: CONFIGURED
I Depend On:
jboss.messaging:service=ServerPeer
ObjectName: xyz.management:service=Queue,name=xyzErrorQueue
State: CONFIGURED
I Depend On:
jboss.messaging:service=ServerPeer
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.messaging:service=ServerPeer
State: NOTYETINSTALLED
Depends On Me:
xyz.management:service=Queue,name=managementQueue
xyz.management:service=Queue,name=indexQueue
xyz.management:service=Queue,name=adaptiveLearningQueue
xyz.management:service=Queue,name=xyzErrorQueue
javax.naming.NameNotFoundException: XAConnectionFactory not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
at org.jnp.server.NamingServer.lookup(NamingServer.java:296)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:589)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:182)
at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:188)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerStartDelivery(JMSContainerInvoker.java:665)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl$ExceptionListenerRunnable.run(JMSContainerInvoker.java:1594)
at java.lang.Thread.run(Thread.java:619)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我认为你这里有多个问题。
JBoss 正在尝试部署在
deploy目录中找到的文件velocity.log。这显然不是您想要的，但请注意，任何放入deploy目录中的文件，JBoss 都会尝试部署。您需要找出正在执行的操作，然后停止它。第二个问题是您的应用程序中某处有一堆 JMS 部署（例如 MDB），但该服务器上不存在 JMS（或尚未正确配置）。
I think you have multiple issues here.
JBoss is trying to deploy the file
velocity.logwhich it has found in itsdeploydirectory. This is clearly not what you intended, but realise that any files that get dropped into thedeploydirectory , JBoss will try and deploy. You need to find out what's doing that, and stop it.The second problem is that you have a bunch of JMS deployments (e.g. MDBs) somewhere in your application, but JMS is not present (or has not been configured correctly) on this server.