Bug 780286 (SOA-2689)

Summary: juddi error with 5.1 ER5
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Aleksandar Kostadinov <akostadinov>
Component: jUDDI - within SOAAssignee: Kevin Conner <kevin.conner>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.1.0.ER5CC: akostadinov, kevin.conner, pmacik
Target Milestone: ---   
Target Release: 5.1.0 GA, 5.1.0.ER7   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-2689
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
RHEL4/5 and windows, Sun java 16, server default/production/all
Last Closed: 2011-02-04 05:43:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
server_default.log none

Description Aleksandar Kostadinov 2010-12-16 11:53:39 UTC
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'

Comment 1 Aleksandar Kostadinov 2010-12-16 11:53:40 UTC
Link: Added: This issue Cloned from SOA-2346


Comment 2 Aleksandar Kostadinov 2010-12-16 11:58:54 UTC
Link: Removed: This issue Cloned from SOA-2346 


Comment 3 Kevin Conner 2010-12-16 16:02:42 UTC
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.

Comment 4 Kevin Conner 2010-12-16 16:27:42 UTC
I have a workaround for this if the cause can be verified.

Comment 5 Aleksandar Kostadinov 2010-12-16 16:57:19 UTC
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.

Comment 6 Aleksandar Kostadinov 2010-12-16 17:07:22 UTC
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

Comment 7 Aleksandar Kostadinov 2010-12-16 17:24:51 UTC
another FYI https://hudson.qa.jboss.com/hudson/view/SOA-Release/job/soa-win-scripts/324 see server production log. This is on windows.


Comment 8 Kevin Conner 2010-12-17 16:16:03 UTC
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.


Comment 9 Kevin Conner 2010-12-17 20:04:46 UTC
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.

Comment 10 Kevin Conner 2010-12-17 20:07:27 UTC
Link: Added: This issue depends JBESB-3549


Comment 11 Kevin Conner 2010-12-17 20:13:43 UTC
There is a workaround in the ESB, will be in the next release.

Comment 12 Aleksandar Kostadinov 2010-12-31 10:24:58 UTC
I'm seeing the exception with ER6 also - http://hudson.qa.jboss.com/hudson/job/soa-unix-scripts/210

Comment 14 Kevin Conner 2011-01-04 09:25:06 UTC
It should be present in ER6 as the tag cut-off predates this fix.  It will be in the next release.

Comment 15 Dana Mison 2011-01-05 00:14:44 UTC
Writer: Added: dlesage


Comment 16 Aleksandar Kostadinov 2011-01-24 09:48:45 UTC
reopening to change fix version

Comment 17 Aleksandar Kostadinov 2011-01-24 09:50:02 UTC
Release Notes Text: Added: I don't see the error any more, thank you!


Comment 18 Dana Mison 2011-02-03 08:27:30 UTC
Release Notes Text: Removed: I don't see the error any more, thank you! 


Comment 19 David Le Sage 2011-02-04 05:39:40 UTC
Temporarily reopening to update release note info.

Comment 20 David Le Sage 2011-02-04 05:42:59 UTC
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.