|
Problem(Abstract) |
After enabling global security in a federated environment
nodeagent failed to start with following exceptions in SystemOut.log file
:
[3/31/06 13:30:55:282 EST] 18346a3 ContainerImpl E WSVR0501E: Error
creating component null [class com.ibm.ws.runtime.component.ORBImpl]
org.omg.CORBA.INTERNAL: CREATE_LISTENER_FAILED_4 vmcid: 0x49421000 minor
code: 56 completed: No
[3/31/06 13:30:55:355 EST] 18346a3 ContainerImpl E WSVR0501E: Error
creating component null [class com.ibm.ws.naming.bootstrap.NameServerImpl]
java.lang.NullPointerException
at
com.ibm.ws.naming.distcos.ServantManagerImpl.<init>(ServantManagerImpl.java:132)
[3/31/06 13:30:56:414 EST] 18346a3 WsnInitCtxFac W NMSV0602E: Naming
Service unavailable. A communications error occurred.
[3/31/06 13:30:56:428 EST] 18346a3 SecurityServe E SECJ0283E: Error
binding User Registry. The exception is
javax.naming.CommunicationException: Could not obtain an initial context
due to a communication failure. Since no provider URL was specified, the
default provider URL of "corbaloc:iiop:1.0@agsos119:2809/NameService" was
used. Make sure that any bootstrap address information in the URL is
correct and that the target name server is running. Possible causes other
than an incorrect bootstrap address or unavailable name server include the
network environment and workstation network configuration. [Root exception
is org.omg.CORBA.COMM_FAILURE: WRITE_ERROR_SEND_1 vmcid: 0x49421000 minor
code: 50 completed: No]
|
|
|
|
Cause |
Port conflict for "CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS"
endPoint for this nodeagent process . |
|
|
Resolving the
problem |
Make sure the following 3 endPoints does not have any port
conflict issue for this nodeagent process:
endPointName="SAS_SSL_SERVERAUTH_LISTENER_ADDRESS">
endPointName="CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS">
endPointName="CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS">
You can verify whether the port is in use by some other service on the
machine using "netstat" command .
If you are required to change the port number for one of these endPoints
pls do following :
1) Log on to dmgr console-->system
administration-->nodeagents-->click on nodeagent -->select
"endpoints" under Additional Properties section--> change the port
number here-->Apply-->save .
2)Since nodeagent is down you need to run syncNode.sh command from the
base node configuration which will synchronizes the configuration between
deployment manager and the base node.
Now you should be able to start the nodeagent process successfully . |
|
|