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
Back to discussions
Expand all | Collapse all

Unable to stop/start server

  • 1.  Unable to stop/start server

    Posted Mon November 28, 2011 05:04 AM
    Hi All,

    Please help me, Its urgent.

    i am unable stop/start server, its hanging . I am  killing the process.

    Nodeagent is satrting fine. When i execute startServer or from console. Its taking time.

    It's not staring , Please help me.

    warnigs:

    [11/28/11 14:09:27:691 GMT+05:30] 00000010 RLSHAGroupCal
    W   CWRLS0030W: Waiting for HAManager to activate recovery processing for local WebSphere server
    [11/28/11 14:10:27:696 GMT+05:30] 0000000e RLSHAGroupCal
    W   CWRLS0030W:Waiting for HAManager to activate recovery processing for local WebSphere server
    [11/28/11 14:11:27:703 GMT+05:30] 00000011 RLSHAGroupCal
    W   CWRLS0030W: Waiting for HAManager to activate recovery processing for local WebSphere server
    [11/28/11 14:12:27:708 GMT+05:30] 00000011 RLSHAGroupCal
    W   CWRLS0030W: Waiting for HAManager to activate recovery processing for local WebSphere server
    [11/28/11 14:13:27:714 GMT+05:30] 00000010 RLSHAGroupCal
    W   CWRLS0030W: Waiting for HAManager to activate recovery processing for local WebSphere server


    Thanks,
    Chinna


  • 2.  Unable to stop/start server

    Posted Mon November 28, 2011 06:38 AM

    Cluster member startup does not complete due to "Waiting for HAManager" error


    ISSUE AT THE TIME OF:

    When attempting to start a cluster member, the startup process appears to be
    suspended and does not complete, and theSystemOut.logfile displays the
    following error:

    ERROR CODE

    CWRLS0030W: Waiting for HAManager to activate recovery
    processing for local WebSphere server

      Reason:

    The high availability manager for WebSphere Application Serveris unable to establish communication due to a port conflict on the DCS_UNICAST_ADDRESS port used by the cluster member.
    Note: There are other instances where you may receive this same error message such as the cluster member is the only member started in the core group with HAManager enabled.




    Solution:    Complete the following steps to correct this problem:

    1. Log in to the deployment manager's administrative console.

    2. Click Servers > Application Servers, and select the server that corresponds to the cluster member that is failing to start.

    3. Click Ports, and then click DCS_UNICAST_ADDRESS.

    4. Modify the port number to a unique port number.

    5. Click Apply, and save your configuration changes.

    6. Restart the cluster member.



    Also Go Throgh below Link from IBM before Gohead with above.

    publib.boulder.ibm.com/infocenter/wpdoc/...


  • 3.  Unable to stop/start server

    Posted Mon November 28, 2011 09:33 AM
    Hi Rajkumar,

    Thanks for your repaly..


    After stop/ starting Dmgr,  i am able start/stop servers through console or commands.

    Its resolved now.

    Thanks,
    Chinna.


  • 4.  Unable to stop/start server

    Posted Tue November 29, 2011 02:13 PM
    The reason for this situation is.... one of the members of the HA group is in undefined state. check for DCS messages while the server start and it should report which member has issue for connections. Then restart that server. 

    As per IBM support site, this fix has been included in the fixpack29 or up.


  • 5.  Unable to stop/start server

    Posted Tue December 06, 2011 03:17 AM
    Hi All,

    In my environment, WAS level is 6.1.0.37.

    After applying 29 or above fix pack this problem will not come right, because this fix already  included into above 29 fix packs releases.


    Please clarify.

    Thanks,
    Chinna.


  • 6.  Unable to stop/start server

    Posted Wed December 07, 2011 02:45 PM
    correct... i too have seen this happening on FP39 

    Create a PMR 


  • 7.  Unable to stop/start server

    Posted Wed December 07, 2011 03:04 PM

    We have the same problem from time to time and we are patched to 6.1.0.39 in the process of going to 6.1.0.41. This problem started when we went from a 32 bit platform to a 64 bit platform. We have a PMR that has been closed and we were told that a fix would be in a future version or to move to V 7 or 8 but as a temporary fix when this happens IBM directed us to clear the items from the following directories on the JVM that you are unable to start and its working for us although a pain.


    Websphere\profiles\”profile name”\wstemp


    Websphere\profiles\”profile name”\temp



  • 8.  Unable to stop/start server

    Posted Wed December 07, 2011 05:43 PM
    Yes... that alternative will work since we are forcing it to get the new status from core group. 
    Thanks for writing the alternative here
     


  • 9.  Unable to stop/start server

    Posted Sun September 09, 2012 10:09 PM
    Hi,

    Alternate way - Disable Core group services

    Regards,
    L.Ganesh


  • 10.  Unable to stop/start server

    Posted Wed February 13, 2013 11:35 AM
    Hai friends,
         I am new to was can anyone tell what is HAmanager in was?what is use of it?
    how to enable in WAS? 


Related Content