Win a copy of The Java Performance Companion this week in the Performance forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Root deployment has missing dependencies; continuing Incomplete Deployment

 
Mona Sharma
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello all,

When i tried to start the JBoss Server using jdk-1_5_0_16 and JBoss_4_2_1_GA, i get the following error. I am not aware of this error.
if any body has some clues then this will be very helpful.

2008-10-14 10:49:34,734 ERROR | (org.jboss.system.server.Server:486) - Root deployment has missing
dependencies; continuing
Incomplete Deployment listing:

--- MBeans waiting for other MBeans ---
ObjectName: jboss.security:name=XMLLoginConfig
State: FAILED
Reason: java.lang.AbstractMethodError: org.jboss.security.auth.login.XMLLoginConfig.jbossInterna
lLifecycle(Ljava/lang/String V

ObjectName: jboss.mq:service=DestinationManager
State: FAILED
Reason: java.lang.NoClassDefFoundError: org/jboss/util/jmx/MBeanProxy
I Depend On:
jboss.mq:service=PersistenceManager
jboss.mq:service=StateManager
Depends On Me:
jboss.mq.destination:service=Queue,name=Notifier
jboss.mq:service=SecurityManager
jboss.mq.destination:service=Queue,name=DLQ

--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.mq:service=DestinationManager
State: FAILED
Reason: java.lang.NoClassDefFoundError: org/jboss/util/jmx/MBeanProxy
I Depend On:
jboss.mq:service=PersistenceManager
jboss.mq:service=StateManager
Depends On Me:
jboss.mq.destination:service=Queue,name=Notifier
jboss.mq:service=SecurityManager
jboss.mq.destination:service=Queue,name=DLQ

ObjectName: jboss.security:name=XMLLoginConfig
State: FAILED
Reason: java.lang.AbstractMethodError: org.jboss.security.auth.login.XMLLoginConfig.jbossInterna
lLifecycle(Ljava/lang/String V

at org.jboss.deployment.MainDeployer.checkIncompleteDeployments(MainDeployer.java:1385)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:785)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:508)
at java.lang.Thread.run(Thread.java:595)
2008-10-14 10:49:34,781 INFO | (org.jboss.system.server.Server:504) - JBoss (MX MicroKernel) [4.2
.1.GA (build: SVNTag=JBoss_4_2_1_GA date=200707131605)] Started in 6s:391ms

Thanks in advance.

Regards,
Monadear
 
Peter Johnson
author
Bartender
Posts: 5852
7
Android Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
There is no such class, org.jboss.util.jmx.MBeanProxy, in 4.2.1. In fact, the MBeanProxy class is located in package org.jboss.mx.util. So it appears that you have supplied custom code or a custom configuration and that code or configuration is incorrect.
 
Jaikiran Pai
Marshal
Pie
Posts: 10447
227
IntelliJ IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
"Monadear java"

Please check your email for a message from JavaRanch.
 
Mona Sharma
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Jaikiran Pai:
"Monadear java"

Please check your email for a message from JavaRanch.


ok
[ October 16, 2008: Message edited by: Mona Sharma ]
 
Mona Sharma
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Peter Johnson:
There is no such class, org.jboss.util.jmx.MBeanProxy, in 4.2.1. In fact, the MBeanProxy class is located in package org.jboss.mx.util. So it appears that you have supplied custom code or a custom configuration and that code or configuration is incorrect.


I did some modifications in a Jboss-service.xml file and the code moves forward but there is an error. Here below you can find the new error description. Please tell me where a new change i have to do for this error.

2008-10-16 11:42:07,937 ERROR | (org.jboss.system.server.Server:486) - Root deployment has missing dependencies; continuing
Incomplete Deployment listing:

--- MBeans waiting for other MBeans ---
ObjectName: aes.rrm:service=RRMDownloader
State: CONFIGURED
I Depend On:
aes.na:service=NAClientNotifier

ObjectName: aes.na:service=NAClientNotifier
State: CONFIGURED
I Depend On:
jboss.mq.destination:service=Queue,name=Notifier
jboss.mq:service=InvocationLayer,type=OIL
jboss:service=Mail
aes.sh:service=SignatureHandler
Depends On Me:
aes.rrm:service=RRMDownloader

--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.mq.destination:service=Queue,name=Notifier
State: NOTYETINSTALLED
Depends On Me:
aes.na:service=NAClientNotifier


at org.jboss.deployment.MainDeployer.checkIncompleteDeployments(MainDeployer.java:1385)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:785)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:508)
at java.lang.Thread.run(Thread.java:595)
2008-10-16 11:42:08,000 INFO | (org.jboss.system.server.Server:504) - JBoss (MX MicroKernel) [4.2
.1.GA (build: SVNTag=JBoss_4_2_1_GA date=200707131605)] Started in 2s:375ms

The error generated is somewhere here
jboss.mq.destination:service

But i am not able to find the cause.

Thanks,
Mona
 
Jaikiran Pai
Marshal
Pie
Posts: 10447
227
IntelliJ IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
What exact changes have you done to the clean installation of JBoss?
 
Mona Sharma
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
What does this part of code mean:-

--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.mq.destination:service=Queue,name=Notifier
State: NOTYETINSTALLED
Depends On Me:
aes.na:service=NAClientNotifier

I think the error is generated here.
 
Mona Sharma
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Jaikiran Pai:
What exact changes have you done to the clean installation of JBoss?


Sorry i didn't understand you. I didn't clean any installation in JBoss
 
Jaikiran Pai
Marshal
Pie
Posts: 10447
227
IntelliJ IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Mona Sharma:
What does this part of code mean:-

--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.mq.destination:service=Queue,name=Notifier
State: NOTYETINSTALLED
Depends On Me:
aes.na:service=NAClientNotifier



This error indicates that the queue named Notifier is not deployed.

Originally posted by Mona Sharma:
Sorry i didn't understand you. I didn't clean any installation in JBoss


I actually meant what are the changes you did to any files in JBoss after downloading a fresh JBoss A fresh downloaded JBoss does not run into this issue, so i guess there are some changes that were done which is causing this error.
 
Peter Johnson
author
Bartender
Posts: 5852
7
Android Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Also, what you are posting is the deployer summary report printed after the deployer is finished. That report is usually useless for determining root causes. Earlier in the console log there should be exception stack traces showing what the errors are. You need to find and post the first exception stack trace. You might have to increase the buffer size for the console, or redirect the output to a file, to get this information.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic