WAS 5.1 unable to stop node and also wsadmin not working.. - Websphere

This is a discussion on WAS 5.1 unable to stop node and also wsadmin not working.. - Websphere ; Dear WAS friends, I am having below issue with WAS 5.1 ND application server. We are unable to stop the node and wsadmin command giving below error:- wsadmin.sh :- [11/16/09 15:34:23:978 GMT+01:00] 251c7b52 AbstractShell A WASX7093I: Issuing message: "WASX7023E: Error ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: WAS 5.1 unable to stop node and also wsadmin not working..

  1. WAS 5.1 unable to stop node and also wsadmin not working..

    Dear WAS friends,

    I am having below issue with WAS 5.1 ND application server. We are unable to stop the node and wsadmin command giving below error:-

    wsadmin.sh :-

    [11/16/09 15:34:23:978 GMT+01:00] 251c7b52 AbstractShell A WASX7093I: Issuing message: "WASX7023E: Error creating "SOAP" connection
    to host "xxxxxxx"; exception information: com.ibm.websphere.management.exception.ConnectorNo tAvailableException"
    [11/16/09 15:34:23:979 GMT+01:00] 251c7b52 AdminControlC W WASX7072E: The control service is not available.
    [11/16/09 15:34:24:023 GMT+01:00] 251c7b52 AdminConfigCl W WASX7198W: The configuration service is not running. Configuration comman
    ds will not run.
    [11/16/09 15:34:24:101 GMT+01:00] 251c7b52 AdminConfigCl A WASX7208I: Validation settings in effect now: Level=HIGHEST, Cross-valida
    tion=true, Output file=/usr/WebSphere/AppServer/logs/wsadmin.valout
    [11/16/09 15:34:24:164 GMT+01:00] 251c7b52 AdminAppClien W WASX7072E: The control service is not available.
    [11/16/09 15:34:24:165 GMT+01:00] 251c7b52 AdminAppClien W WASX7206W: The application management service is not running. Application
    management commands will not run.
    [11/16/09 15:34:33:564 GMT+01:00] 251c7b52 WasxShell A WASX7331I: Unexpected exception received when querying for changes in thi
    s session: com.ibm.ws.scripting.ScriptingException: WASX7070E: The configuration service is not available.

    When we stop the node using stopNode.sh we see below error;;-

    [11/16/09 10:31:59:422 GMT+01:00] 26d0565a AdminTool A ADMU3100I: Reading configuration for server: nodeagent
    [11/16/09 10:32:07:219 GMT+01:00] 26d0565a WsServerStop E ADMU3002E: Exception attempting to process server nodeagent
    [11/16/09 10:32:07:219 GMT+01:00] 26d0565a WsServerStop E ADMU3007E: Exception com.ibm.websphere.management.exception.ConnectorEx ce
    ption: ADMC0053E: Could not create SOAP Connector to connect to host xxxxxx at port 9999 with SOAP Connector security enabled.
    [11/16/09 10:32:07:219 GMT+01:00] 26d0565a WsServerStop A ADMU3007E: Exception com.ibm.websphere.management.exception.ConnectorEx ce
    ption: ADMC0053E: Could not create SOAP Connector to connect to host xxxxxx at port 9999 with SOAP Connector security enabled.
    at com.ibm.websphere.management.AdminClientFactory.cr eateAdminClient(AdminClientFactory.java:359)
    at com.ibm.ws.management.tools.LaunchUtils.getAdminCl ient(LaunchUtils.java:347)
    at com.ibm.ws.management.tools.LaunchUtils.getAdminCl ient(LaunchUtils.java:287)
    at com.ibm.ws.management.tools.WsServerStop.runTool(W sServerStop.java:196)
    at com.ibm.ws.management.tools.AdminTool.executeUtili ty(AdminTool.java:192)
    at com.ibm.ws.management.tools.WsServerStop.main(WsSe rverStop.java:86)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:85)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:58)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:60)
    at java.lang.reflect.Method.invoke(Method.java:391)
    at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.jav a:204)
    at java.lang.Thread.run(Thread.java:567)
    Caused by: java.lang.reflect.InvocationTargetException
    at sun.reflect.NativeConstructorAccessorImpl.newInsta nce0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInsta nce(NativeConstructorAccessorImpl.java:80)
    at sun.reflect.DelegatingConstructorAccessorImpl.newI nstance(DelegatingConstructorAccessorImpl.java:44)
    at java.lang.reflect.Constructor.newInstance(Construc tor.java:315)
    at com.ibm.websphere.management.AdminClientFactory.cr eateAdminClient(AdminClientFactory.java:300)
    ... 12 more
    Caused by: com.ibm.websphere.management.exception.ConnectorNo tAvailableException
    at com.ibm.ws.management.connector.soap.SOAPConnector Client.reconnect(SOAPConnectorClient.java:253)
    at com.ibm.ws.management.connector.soap.SOAPConnector Client. (SOAPConnectorClient.java:186)
    ... 17 more
    Caused by: [SOAPException: faultCode=SOAP-ENV:Client; msg=Error opening socket: javax.net.ssl.SSLHandshakeException: certificate exp
    ired; targetException=java.lang.IllegalArgumentException : Error opening socket: javax.net.ssl.SSLHandshakeException: certificate exp
    ired]
    at org.apache.soap.transport.http.SOAPHTTPConnection. send(Unknown Source)
    at org.apache.soap.rpc.Call.invoke(Unknown Source)
    at com.ibm.ws.management.connector.soap.SOAPConnector Client$2.run(SOAPConnectorClient.java:236)
    at com.ibm.ws.security.util.AccessController.doPrivil eged(AccessController.java:111)
    at com.ibm.ws.management.connector.soap.SOAPConnector Client.reconnect(SOAPConnectorClient.java:233)
    ... 18 more
    ---- Begin backtrace for nested exception
    java.lang.reflect.InvocationTargetException
    at sun.reflect.NativeConstructorAccessorImpl.newInsta nce0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInsta nce(NativeConstructorAccessorImpl.java:80)
    at sun.reflect.DelegatingConstructorAccessorImpl.newI nstance(DelegatingConstructorAccessorImpl.java:44)
    at java.lang.reflect.Constructor.newInstance(Construc tor.java:315)
    at com.ibm.websphere.management.AdminClientFactory.cr eateAdminClient(AdminClientFactory.java:300)
    at com.ibm.ws.management.tools.LaunchUtils.getAdminCl ient(LaunchUtils.java:347)
    at com.ibm.ws.management.tools.LaunchUtils.getAdminCl ient(LaunchUtils.java:287)
    at com.ibm.ws.management.tools.WsServerStop.runTool(W sServerStop.java:196)
    at com.ibm.ws.management.tools.AdminTool.executeUtili ty(AdminTool.java:192)
    at com.ibm.ws.management.tools.WsServerStop.main(WsSe rverStop.java:86)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:85)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:58)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:60)
    at java.lang.reflect.Method.invoke(Method.java:391)
    at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.jav a:204)
    at java.lang.Thread.run(Thread.java:567)
    Caused by: com.ibm.websphere.management.exception.ConnectorNo tAvailableException
    at com.ibm.ws.management.connector.soap.SOAPConnector Client.reconnect(SOAPConnectorClient.java:253)
    at com.ibm.ws.management.connector.soap.SOAPConnector Client.(SOAPConnectorClient.java:186)
    ... 17 more
    Caused by: [SOAPException: faultCode=SOAP-ENV:Client; msg=Error opening socket: javax.net.ssl.SSLHandshakeException: certificate exp
    ired; targetException=java.lang.IllegalArgumentException : Error opening socket: javax.net.ssl.SSLHandshakeException: certificate exp
    ired]
    at org.apache.soap.transport.http.SOAPHTTPConnection. send(Unknown Source)
    at org.apache.soap.rpc.Call.invoke(Unknown Source)
    at com.ibm.ws.management.connector.soap.SOAPConnector Client$2.run(SOAPConnectorClient.java:236)
    at com.ibm.ws.security.util.AccessController.doPrivil eged(AccessController.java:111)
    at com.ibm.ws.management.connector.soap.SOAPConnector Client.reconnect(SOAPConnectorClient.java:233)
    ... 18 more

    [11/16/09 10:32:07:248 GMT+01:00] 26d0565a AdminTool A ADMU0509I: The server "nodeagent" cannot be reached. It appears to be sto
    pped.

    Please help, I tried several things and didn't work. We tried to create new certificates, new LTPA tokens.. no luck.. Also the port is listening on the server, when we use netstat -an we can see. So please shed some light.

    Thanks for your help.

  2. Re: WAS 5.1 unable to stop node and also wsadmin not working..


+ Reply to Thread