Bug 781068 (SOA-3556)

Summary: "Unable to save node riftsaw .Transport implementation not yet initialised" - seen on server riftboot
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Len DiMaggio <ldimaggi>
Component: riftsawAssignee: Gary Brown <gbrown>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: urgent Docs Contact:
Priority: urgent    
Version: 5.2.0.ER6   
Target Milestone: ---   
Target Release: 5.2.0.CR1   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-3556
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
5.2.0.ER6
Last Closed: 2011-11-10 10:16:43 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.log.gz none

Description Len DiMaggio 2011-11-04 03:14:36 UTC 
project_key: SOA

This is seen booting an otherwise idle server - clean install - no archives deployed:

2011-11-03 22:53:21,845 ERROR [org.apache.juddi.v3.client.config.UDDIClerk] (Thread-28) 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:636)
2011-11-03 22:53:21,849 ERROR [org.apache.juddi.v3.client.config.UDDIClerk] (Thread-28) 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:636)
Comment 1 Len DiMaggio 2011-11-04 03:16:10 UTC 
Attachment: Added: server.log.gz
Comment 2 Douglas Palmer 2011-11-04 09:54:05 UTC 
Changing the order of ant task in the installer should fix this. The target deploy.esb.uddi.config needs to be called after deploy-clustering.
Comment 3 Gary Brown 2011-11-04 09:56:33 UTC 
Installation script changed to apply esb config change (to uncomment dependency on juddi) until after clustering config changes - thanks Doug for diagnosing the problem.
Comment 4 Douglas Palmer 2011-11-04 15:03:21 UTC 
Link: Added: This issue is related to SOA-3392
Comment 5 David Le Sage 2011-11-09 02:54:08 UTC 
Release Notes Docs Status: Added: Not Required
Writer: Added: dlesage
Comment 6 Ivo Bek 2011-11-10 10:16:43 UTC 
Verified in SOA-P 5.2.0.CR1.