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

WeSphere 8.5.5.x wsadmin script AdminControl.invoke hangs

  • 1.  WeSphere 8.5.5.x wsadmin script AdminControl.invoke hangs

    Posted 11/12/20 11:28 PM

    We have WebSphere 8.5.5.x installed and we are running into issue with some wsadmin tool command when attempting to run our application. Our script hangs. Our application runs fine when we execute it from the web console but if we try to run it using admin commands we get an error. Below is an example of the command we are running:

    AdminControl.invoke(appManager,'startApplication','%s' % Appname)’

    Error:

    wsadmin>AdminControl.invoke(appManager,'startApplication','%s' % Appname)

    WASX7015E: Exception running command: "AdminControl.invoke(appManager,'startApplication','%s' % Appname)"; exception information:

    com.ibm.websphere.management.exception.ConnectorNotAvailableException

    javax.naming.ServiceUnavailableException: javax.naming.ServiceUnavailableException: A communication failure occurred while attempting to obtain an initial context with the provider URL: "corbaloc:iiop:localhost:2809/WsnAdminNameService". Make sure that any bootstrap address information in the URL is correct and that the target name server is running. A bootstrap address with no port specification defaults to port 2809. 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.TRANSIENT: java.net.ConnectException: Connection refused:host=cimbnrcs-app,port=2809 vmcid: IBM minor code: E02 completed: No]

    We know its not a bootstrap issue - we do have the port set at 2809. We also checked the appManager variable to ensure it wasn’t empty.

    Any suggestions that could be causing this?



    #Support
    #SupportMigration
    #WebSphereApplicationServer(WAS)


  • 2.  RE: WeSphere 8.5.5.x wsadmin script AdminControl.invoke hangs
    Best Answer

    Posted 11/12/20 11:31 PM

    A couple of things can cause the wsadmin

    scripts to hang. Consider the following:

    - Corrupted profile – Recommend creating

    a new profile and retrying the test

    - Sometimes memory or Java is an issue

    and its a good idea to start

    wsadmin with java memory specs to avoid a hang..

    example:

    wsadmin" -lang jython -javaoption -Xmx1024m -f %1

    Reference the following page for

    known issues encountered when using wsadmin tool:

    https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.multiplatform.doc/ae/rtrb_wsadminprobs.html#rtrb_wsadminprobs__%20wasx7015e



    #Support
    #SupportMigration
    #WebSphereApplicationServer(WAS)


Related Content