WebSphere Application Server & Liberty

WebSphere Application Server & Liberty

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
  • 1.  Node Federation error

    Posted 08/11/10 10:36 AM
    Node Federation error

    --------------------------------

    While adding a node to a cell on a standalone server.. following error has been encountered
    I have then removed sample applications from server1..but still the problem remains the same..

    I have tried all these commands but the error persists.

    addNode MYPC-PCNode01 8879

    addNode MYPC-PCNode01 8879 -trace

    addNode MYPC-PCNode01 8879 -includeapps

    even -trace option does not create a addNode.log


    ---------------------------------------


    ADMU0116I: Tool information is being logged in file C://Program
    Files//IBM//WebSphere//AppServer//profiles//AppSrv01//logs//addNode.log
    ADMU0128I: Starting tool with the AppSrv01 profile
    ADMU0001I: Begin federation of node MYPC-PCNode01 with Deployment Manager at
    MYPC-PC:8879.
    ADMU0009I: Successfully connected to Deployment Manager Server: MYPC-PC:8879
    ADMU0505I: Servers found in configuration:
    ADMU0506I: Server name: server1
    ADMU2010I: Stopping all server processes for node MYPC-PCNode01
    ADMU7702I: Because server1 is registered to run as a Windows Service, the
    request to stop this server will be completed by stopping the
    associated Windows Service.
    ADMU0024I: Deleting the old backup directory.
    ADMU0015I: Backing up the original cell repository.
    ADMU0012I: Creating Node Agent configuration for node: MYPC-PCNode01
    ADMU0014I: Adding node MYPC-PCNode01 configuration to cell: MYPC-PCCell01
    ADMU0026I: An error occurred during federation; rolling back to original
    configuration.
    ADMU2028E: Exception
    com.ibm.etools.j2ee.commonarchivecore.exception.SaveFailureException:

    collectionform.js caught in expanding ear at C://Program
    Files//IBM//WebSphere//AppServer/profiles/AppSrv01//config/cells/MYPC-P
    CNode01Cell/applications/PlantsByWebSphere.ear/PlantsByWebSphere.ear
    to C://Program
    Files//IBM//WebSphere//AppServer/profiles/AppSrv01/installedApps/MYPC-
    PCNode01Cell/PlantsByWebSphere.ear
    ADMU2028E: Exception
    com.ibm.etools.j2ee.commonarchivecore.exception.SaveFailureException:

    scripts/browserStyle.js caught in expanding ear at C://Program
    Files//IBM//WebSphere//AppServer/profiles/AppSrv01//config/cells/MYPC-P
    CNode01Cell/applications/SamplesGallery.ear/SamplesGallery.ear
    to C://Program
    Files//IBM//WebSphere//AppServer/profiles/AppSrv01/installedApps/MYPC-
    PCNode01Cell/SamplesGallery.ear
    ADMU0113E: Program exiting with error:
    com.ibm.websphere.management.exception.AdminException: doMergeConfig
    failed, resulting from:
    com.ibm.wsspi.configarchive.ConfigArchiveException: importNode
    command failed

    --------------------------------

    Posted By: Abhinav at Mar 4 2009 7:01PM


  • 2.  Node Federation error

    Posted 08/11/10 10:44 AM
    Federation

    --------------------------------

    addNode.bat hostname 8879 -profileName profilename -includeapps

    It will definetely work.

    Regards,
    R.Thiru

    --------------------------------

    Posted By: rt.venkat@gmail at Mar 9 2009 11:24AM


  • 3.  Node Federation error

    Posted 08/11/10 10:49 AM
    Federation of Node to Dmgr failed

    --------------------------------

    Hi,

    If you are using WAS6.1, try the above command giving 'profileName' option.

    Also try giving -conntype SOAP (if the port 8879 is SOAP).

    Check whether you have any port conflicts.

    --------------------------------

    Posted By: texaco at Mar 10 2009 8:40PM


  • 4.  Node Federation error

    Posted 08/11/10 10:50 AM
    Node federation failed

    --------------------------------

    Hi,

    I found something else too:

    ADMU2028E: Exception {0} caught in expanding ear at {1} to {2}
    Explanation: EAR file could not be expanded to the destination.
    User Response: Run EARExpander tool to expand the ear file to its appropriate locations.

    Take a backup of your node configuration (backupConfig.bat/sh). Then run the command - addNode.bat -conntype SOAP

    Do not add -includeApps option.

    Try it and let us know if this works.

    --------------------------------

    Posted By: texaco at Mar 10 2009 8:44PM