| Summary: | RiftSaw/uddi error on startup when clustered | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Douglas Palmer <dpalmer> |
| Component: | unspecified | Assignee: | Kurt Stam <kurt.stam> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.2.0.ER4 | CC: | kevin.conner |
| Target Milestone: | --- | ||
| Target Release: | 5.2.0 GA, 5.2.0.CR1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-3392 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-11-10 10:16:02 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: | |
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. This was set in the non clustered profile but was missing from the clustered profile. Fix is in the RiftSaw branch now. Release Notes Docs Status: Added: Not Required Writer: Added: dlesage This issue is not fixed in soa-p 5.2.0.ER5 even in ER6. I think the issue SOA-3556 duplicate this issue. Link: Added: This issue relates to SOA-3556 Verified in SOA-P 5.2.0.CR1. |
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)