Topic
  • 3 replies
  • Latest Post - ‏2011-04-08T17:55:57Z by StevenSchader
tzhao
tzhao
15 Posts

Pinned topic Please help, addnode failed for newly created custom profile

‏2011-04-08T17:17:39Z |
It failed to create a new custom profile. The log file indicated the failure from addnode call. So I executed the addnode command from the command line window. It still failed.

Here is command line output, I also attached the addNode.log here for your reference.

Thanks!

+++++++++++++++++++++++++++++++++++++
C:\IBM\WebSphere\AppServer\profiles\Custom02\bin>addnode localhost 8879 -trace -
username wasadmin -password wasadmin
ADMU0116I: Tool information is being logged in file
C:\IBM\WebSphere\AppServer\profiles\Custom02\logs\addNode.log
CWPKI0309I: All signers from remote keystore already exist in local keystore.
ADMU0001I: Begin federation of node VEW03SEFNode02 with Deployment Manager at
localhost:8879.
ADMU0009I: Successfully connected to Deployment Manager Server: localhost:8879
ADMU0507I: No servers found in configuration under:
C:\IBM\WebSphere\AppServer\profiles\Custom02\config/cells/VEW03SEFNod
e01Cell/nodes/VEW03SEFNode02/servers
ADMU2010I: Stopping all server processes for node VEW03SEFNode02
ADMU0024I: Deleting the old backup directory.
ADMU0015I: Backing up the original cell repository.
ADMU0012I: Creating Node Agent configuration for node: VEW03SEFNode02
ADMU0014I: Adding node VEW03SEFNode02 configuration to cell: VEW03SEFCell01
ADMU0027E: An error occurred during federation Read timed out; rolling back to
original configuration.
ADMU0211I: Error details may be seen in the file:
C:\IBM\WebSphere\AppServer\profiles\Custom02\logs\addNode.log
ADMU0026I: An error occurred during federation; rolling back to original
configuration.
ADMU0113E: Program exiting with error:
com.ibm.websphere.management.exception.AdminException:
com.ibm.websphere.management.exception.ConnectorException:
ADMC0009E: The system failed to make the SOAP RPC call: invoke,
resulting from: [SOAPException: faultCode=SOAP-ENV:Client; msg=Read
timed out; targetException=java.net.SocketTimeoutException: Read
timed out]
ADMU0211I: Error details may be seen in the file:
C:\IBM\WebSphere\AppServer\profiles\Custom02\logs\addNode.log

C:\IBM\WebSphere\AppServer\profiles\Custom02\bin>
Updated on 2011-04-08T17:55:57Z at 2011-04-08T17:55:57Z by StevenSchader
  • StevenSchader
    StevenSchader
    12 Posts

    Re: Please help, addnode failed for newly created custom profile

    ‏2011-04-08T17:22:57Z  
    Hi,

    Try increasing the soap timeout found in C:\IBM\WebSphere\AppServer\profiles\Custom02\propertiessoap.client.props

    from:
    com.ibm.SOAP.requestTimeout=180

    to:
    com.ibm.SOAP.requestTimeout=900
  • tzhao
    tzhao
    15 Posts

    Re: Please help, addnode failed for newly created custom profile

    ‏2011-04-08T17:53:01Z  
    Hi,

    Try increasing the soap timeout found in C:\IBM\WebSphere\AppServer\profiles\Custom02\propertiessoap.client.props

    from:
    com.ibm.SOAP.requestTimeout=180

    to:
    com.ibm.SOAP.requestTimeout=900
    Thanks, it works!
  • StevenSchader
    StevenSchader
    12 Posts

    Re: Please help, addnode failed for newly created custom profile

    ‏2011-04-08T17:55:57Z  
    • tzhao
    • ‏2011-04-08T17:53:01Z
    Thanks, it works!
    Excellent!

    Also see -> http://publib.boulder.ibm.com/infocenter/wasinfo/fep/index.jsp?topic=/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/rtrb_admincomp.html&resultof="com.ibm.SOAP.requestTimeout"

    Steven.