Hide Forgot
Steps to Reproduce: just start server all project_key: SOA Exception detected by:`org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: Unexpected error during registration for epr JMSEpr [ PortReference < <wsa:Address jms:10.16.94.138:1099#queue/DeadMessageQueue/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 10.16.94.138:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:destination-name : queue/DeadMessageQueue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/> > ] at org.jboss.soa.esb.listeners.message.MessageAwareListene' Exception detected by:`Caused by: org.jboss.soa.esb.services.registry.RegistryException: org.apache.ws.scout.transport.TransportException: java.lang.Exception: Cannot locate configuration source META-INF/uddi.xml at org.jboss.internal.soa.esb.service' Exception detected by:`Caused by: javax.xml.registry.JAXRException: org.apache.ws.scout.transport.TransportException: java.lang.Exception: Cannot locate configuration source META-INF/uddi.xml at org.apache.ws.scout.registry.BusinessQueryManagerV3Imp' Exception detected by:` Deployment "jboss.esb.vfsfile:/qa/hudson_ws/workspace/soa-unix-scripts/jbosssoa-standalone/jboss-esb/server/default/deploy/jbossesb.esb/" is in error due to the following reason(s): javax.xml.registry.JAXRException: org.apache.ws.scout.transport.TransportException: java.lang.Exception: Cannot locate configuration source META-INF/uddi.xml Deployment "<UNKNOWN jboss.esb.vf'
Link: Added: This issue Cloned from SOA-2346
Link: Removed: This issue Cloned from SOA-2346
The only explanation I can see for this is a concurrency bug in UDDIClientContainer, I need to get hold of a MP machine to verify.
I have a workaround for this if the cause can be verified.
As we chatter on IRC, if I'm not available please ask somebody from QE (vjuranek, Len, Martin, Jirka, Prabhat, whoever in #jbossqa) to reserve soa4 (linux), or soa7 (windows) for you when you can look at that. If there is some long running task on the machines at the time, you could kill it.
FYI https://hudson.qa.jboss.com/hudson/job/soa-unix-scripts/209 Issue happened with the standalone server - see standalone server debug log - https://hudson.qa.jboss.com/hudson/job/soa-unix-scripts/209/artifact/jbosssoa-standalone/jboss-esb/server/default/log/server.log
another FYI https://hudson.qa.jboss.com/hudson/view/SOA-Release/job/soa-win-scripts/324 see server production log. This is on windows.
I have seen this occur on a windows box (soa7) but have been unsuccessful at debugging as it alters the timings. I have managed to verify that there are concurrent modifications to the UDDIClientContainer, supporting the theory, and will try to create a byteman test to replicate it.
I have a convoluted test case that exhibits this issue, definitely a bug in juddi. The issue can be worked around through a very simple change in ESB.
Link: Added: This issue depends JBESB-3549
There is a workaround in the ESB, will be in the next release.
I'm seeing the exception with ER6 also - http://hudson.qa.jboss.com/hudson/job/soa-unix-scripts/210
It should be present in ER6 as the tag cut-off predates this fix. It will be in the next release.
Writer: Added: dlesage
reopening to change fix version
Release Notes Text: Added: I don't see the error any more, thank you!
Release Notes Text: Removed: I don't see the error any more, thank you!
Temporarily reopening to update release note info.
Release Notes Docs Status: Added: Documented as Resolved Issue Release Notes Text: Added: https://issues.jboss.org/browse/JBESB-3549 A registry exception occurred when the server was started. This was caused by a concurrecy bug in JUDDI. A code fix has been applied. As a result, this exception no longer occurs.