Are you sure there is no exception further up?
Try setting the logging threshold
to DEBUG of the file appender in
You will get extra information in
Thanks again warjort. This exception was in server.log
server.log:2003-04-24 15:34:35,973 ERROR [org.jboss.ejb.EntityContainer] Initialization failed
server.log:2003-04-24 15:35:01,760 ERROR [org.jboss.deployment.scanner.URLDeploymentScanner] MBeanException: Exception in MBean operation 'checkIncompleteDeployments()'
I forgot to mention that I'm using JBoss-3.2.0RC1
I doubt the entity bean is the problem
although it obviously needs resolving.
You need to get the debug logging to find out
why your MBean didn't start when queues
Thanks once again.
to log4j.xml in server/all/conf/
But, the server.log still shows the same level of output as
before. I'm running JBoss with the shell ./run.sh -c all
Here is another oddity. In my mbean declaration I commented out
all but one of the dependencies. So the declaration now looks like
this: <!-- EPPOS Service Configuration -->
With this declaration. My mbean is started. But, Of course there are other
exceptions which I fully expected due to the other two JMS components
having not been started. The work around that I am going to use. Is
to get the RMI adaptor on the client side and use it to invoke a "startListening" method
on the mbean. That works. But, It does'nt solve the mystery of why
this problem is occuring.
Thanks in advance.
I assumed this was a typo before
Shouldn't that be
Yup. That's a typo. What is did a copyNPaste. I missed the j
I have attached debug output that you may find helpful.
Andrian, this was a typo in the config file as well. I changed the
boss to jboss and all worked as expected. My bad.