Bug 780927 (SOA-3392) - RiftSaw/uddi error on startup when clustered
Summary: RiftSaw/uddi error on startup when clustered
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-3392
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: unspecified
Version: 5.2.0.ER4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.2.0 GA,5.2.0.CR1
Assignee: Kurt Stam
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-20 14:49 UTC by Douglas Palmer
Modified: 2011-11-10 10:16 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-10 10:16:02 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 781068 0 urgent CLOSED "Unable to save node riftsaw .Transport implementation not yet initialised" - seen on server riftboot 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-3392 0 None None None Never

Internal Links: 781068

Description Douglas Palmer 2011-09-20 14:49:17 UTC 
project_key: SOA

2011-09-20 10:15:32,193 ERROR [org.apache.juddi.v3.client.config.UDDIClerk] (Thread-29) Unable to save node riftsaw .Transport implementation not yet initialised
org.apache.juddi.v3.client.transport.TransportException: Transport implementation not yet initialised
        at org.jboss.internal.soa.esb.registry.client.JuddiInVMTransport.getImplementation(JuddiInVMTransport.java:143)
        at org.jboss.internal.soa.esb.registry.client.JuddiInVMTransport.getUDDISecurityService(JuddiInVMTransport.java:116)
        at org.apache.juddi.v3.client.config.UDDIClerk.getAuthToken(UDDIClerk.java:572)
        at org.apache.juddi.v3.client.config.UDDIClerk.saveNode(UDDIClerk.java:582)
        at org.apache.juddi.v3.client.config.UDDIClerkManager.saveClerkAndNodeInfo(UDDIClerkManager.java:156)
        at org.apache.juddi.v3.client.config.BackGroundRegistration.run(BackGroundRegistration.java:37)
        at java.lang.Thread.run(Thread.java:680)
2011-09-20 10:15:32,213 ERROR [org.apache.juddi.v3.client.config.UDDIClerk] (Thread-29) Unable to save clerk BPELClerk .Transport implementation not yet initialised
org.apache.juddi.v3.client.transport.TransportException: Transport implementation not yet initialised
        at org.jboss.internal.soa.esb.registry.client.JuddiInVMTransport.getImplementation(JuddiInVMTransport.java:143)
        at org.jboss.internal.soa.esb.registry.client.JuddiInVMTransport.getUDDISecurityService(JuddiInVMTransport.java:116)
        at org.apache.juddi.v3.client.config.UDDIClerk.getAuthToken(UDDIClerk.java:572)
        at org.apache.juddi.v3.client.config.UDDIClerk.saveClerk(UDDIClerk.java:600)
        at org.apache.juddi.v3.client.config.UDDIClerkManager.saveClerkAndNodeInfo(UDDIClerkManager.java:160)
        at org.apache.juddi.v3.client.config.BackGroundRegistration.run(BackGroundRegistration.java:37)
        at java.lang.Thread.run(Thread.java:680)
Comment 1 Kevin Conner 2011-09-20 15:06:53 UTC 
I'm not sure what is kicking off this background thread but whatever it is needs to wait until the service transport is initialised.  It needs to include a dependency on jboss.esb:service=JuddiRMI.
Comment 2 Douglas Palmer 2011-09-20 15:57:54 UTC 
This was set in the non clustered profile but was missing from the clustered profile. Fix is in the RiftSaw branch now.
Comment 3 David Le Sage 2011-09-21 03:11:43 UTC 
Release Notes Docs Status: Added: Not Required
Writer: Added: dlesage
Comment 4 Ivo Bek 2011-11-04 14:59:09 UTC 
This issue is not fixed in soa-p 5.2.0.ER5 even in ER6. I think the issue SOA-3556 duplicate this issue.
Comment 5 Douglas Palmer 2011-11-04 15:03:21 UTC 
Link: Added: This issue relates to SOA-3556
Comment 6 Ivo Bek 2011-11-10 10:16:02 UTC 
Verified in SOA-P 5.2.0.CR1.
Note You need to log in before you can comment on or make changes to this bug.