Topic
  • 7 replies
  • Latest Post - ‏2011-05-04T10:14:22Z by SridharSanthanakrishnan
SridharSanthanakrishnan
6 Posts

Pinned topic wsadmin did not working for Websphere_portal

‏2011-05-03T06:49:28Z |
I am using the folloing command to create dump file
open startserver.bat add the set IBM_HEAPDUMP=true
then startserver Websphere_portal
wsadmin
set jvm $AdminControl completeObjectName type=JVM,process=Websphere_portal,*
$AdminControl invoke $jvm dumpThreads

Actually my WAS server has server1 with admin console.But portal server Websphere_portal did not have admin console.When i try wsadmin command ,it is connecting only to server1 but not Websphere_portal.
So i could not excute dump file commands for Websphere_portal

Anyone could help me on this ?
I get the folloing message when i try use wsadmin

5/2/11 16:28:35:617 IST 0000000a AbstractShell A WASX7093I: Issuing message: "WASX7023E: Error creating "SOAP" connection to host "localhost"; exception information: com.ibm.websphere.management.exception.ConnectorNotAvailableException: com.ibm.websphere.management.exception.ConnectorNotAvailableException: ADMC0016E: The system cannot create a SOAP connector to connect to host localhost at port 10005."
5/2/11 16:28:35:617 IST 0000000a AbstractShell E WASX7120E: Diagnostic information from exception with text "com.ibm.websphere.management.exception.ConnectorException
java.lang.reflect.InvocationTargetException: java.lang.reflect.InvocationTargetException
" follows:

com.ibm.websphere.management.exception.ConnectorException: ADMC0016E: The system cannot create a SOAP connector to connect to host localhost at port 10005.
at com.ibm.websphere.management.AdminClientFactory.createAdminClient(AdminClientFactory.java:498)
at com.ibm.ws.scripting.CommonScriptingObject.connectToAdminService(CommonScriptingObject.java:120)
at com.ibm.ws.scripting.CommonScriptingObject.<init>(CommonScriptingObject.java:101)
at com.ibm.ws.scripting.AdminControlClient.<init>(AdminControlClient.java:165)
at com.ibm.ws.scripting.AbstractShell.createControlClient(AbstractShell.java:1081)
at com.ibm.ws.scripting.AbstractShell.run(AbstractShell.java:1960)
at com.ibm.ws.scripting.WasxShell.main(WasxShell.java:1025)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at com.ibm.wsspi.bootstrap.WSLauncher.launchMain(WSLauncher.java:183)
at com.ibm.wsspi.bootstrap.WSLauncher.main(WSLauncher.java:90)
at com.ibm.wsspi.bootstrap.WSLauncher.run(WSLauncher.java:72)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
at org.eclipse.core.launcher.Main.run(Main.java:977)
at com.ibm.wsspi.bootstrap.WSPreLauncher.launchEclipse(WSPreLauncher.java:329)
at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:92)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:67)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:522)
at com.ibm.websphere.management.AdminClientFactory.createAdminClient(AdminClientFactory.java:350)
... 27 more
Caused by: com.ibm.websphere.management.exception.ConnectorNotAvailableException: com.ibm.websphere.management.exception.ConnectorNotAvailableException: ADMC0016E: The system cannot create a SOAP connector to connect to host localhost at port 10005.
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.reconnect(SOAPConnectorClient.java:351)
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.<init>(SOAPConnectorClient.java:181)
... 32 more
Caused by: com.ibm.websphere.management.exception.ConnectorNotAvailableException: ADMC0016E: The system cannot create a SOAP connector to connect to host localhost at port 10005.
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.getUrl(SOAPConnectorClient.java:1123)
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.access$300(SOAPConnectorClient.java:113)
at com.ibm.ws.management.connector.soap.SOAPConnectorClient$4.run(SOAPConnectorClient.java:316)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.reconnect(SOAPConnectorClient.java:309)
... 33 more
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:391)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:252)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:239)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:389)
at java.net.Socket.connect(Socket.java:556)
at java.net.Socket.connect(Socket.java:504)
at java.net.Socket.<init>(Socket.java:412)
at java.net.Socket.<init>(Socket.java:255)
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.getUrl(SOAPConnectorClient.java:1103)
... 37 more

5/2/11 16:28:35:617 IST 0000000a AdminControlC W WASX7072E: The control service is not available.
5/2/11 16:28:35:648 IST 0000000a AdminConfigCl W WASX7198W: The configuration service is not running. Configuration commands will not run.
5/2/11 16:28:35:664 IST 0000000a AdminConfigCl A WASX7208I: Validation settings in effect now: Level=HIGHEST, Cross-validation=true, Output file=C:/IBM/WebSphere61/PortalServer/wp_profile/logs/wsadmin.valout
5/2/11 16:28:35:695 IST 0000000a AdminAppClien W WASX7072E: The control service is not available.
5/2/11 16:28:36:039 IST 0000000a AdminAppClien W WASX7206W: The application management service is not running. Application management commands will not run.
5/2/11 16:28:36:054 IST 0000000a AdminCmdClien W WASX7198W: The configuration service is not running. Configuration commands will not run.
5/2/11 16:28:36:054 IST 0000000a CommandMgr E commandframework failed to initialize in client mode
5/2/11 16:28:36:101 IST 0000000a AdminCmdClien W WASX7198W: The configuration service is not running. Configuration commands will not run.
5/2/11 16:28:36:101 IST 0000000a AdminCmdClien W WASX8011W: AdminTask object is not available.
5/2/11 16:59:22:773 IST 0000000a WasxShell A WASX7331I: Unexpected exception received when querying for changes in this session: com.ibm.ws.scripting.ScriptingException: WASX7070E: The configuration service is not available.
Updated on 2011-05-04T10:14:22Z at 2011-05-04T10:14:22Z by SridharSanthanakrishnan
  • SystemAdmin
    SystemAdmin
    37421 Posts

    Re: wsadmin did not working for Websphere_portal

    ‏2011-05-03T07:14:59Z  
    Hi,

    You can connect using wsadmin to app server itself and websphere portal is an application hosted on your app server so you can manage portal through app server itself, does this answer your question?

    //Ahmed
  • gas
    gas
    942 Posts

    Re: wsadmin did not working for Websphere_portal

    ‏2011-05-03T09:12:03Z  
    Check the SOAP port of the WebSphere_portal server via console and then issue wsadmin wiht the following command:

    wsadmin.sh -conntype SOAP -host localhost -port port_number

    you should be connected to the WebSphere_Portal server instead of server1
  • SridharSanthanakrishnan
    6 Posts

    Re: wsadmin did not working for Websphere_portal

    ‏2011-05-03T11:41:39Z  
    • gas
    • ‏2011-05-03T09:12:03Z
    Check the SOAP port of the WebSphere_portal server via console and then issue wsadmin wiht the following command:

    wsadmin.sh -conntype SOAP -host localhost -port port_number

    you should be connected to the WebSphere_Portal server instead of server1
    I am not sure about above commands.It is not working for me.

    I see the below issue when I execute the below under wsadmin

    wsadmin>$AdminControl invoke $jvm dumpThreads
    WASX7015E: Exception running command: "$AdminControl invoke $jvm dumpThreads"; e
    xception information:com.ibm.ws.scripting.ScriptingException: WASX7025E: Error found in String ""; c
    annot create ObjectName.
  • SridharSanthanakrishnan
    6 Posts

    Re: wsadmin did not working for Websphere_portal

    ‏2011-05-03T12:02:10Z  
    Hi,

    You can connect using wsadmin to app server itself and websphere portal is an application hosted on your app server so you can manage portal through app server itself, does this answer your question?

    //Ahmed
    when i install the application in app server and when try start app, i see the below error

    "AAAA.ear"can not be started because it is installed on a different server.

    Can you please explian how to manage portal app in WAS server instead of portal server

    Thanks
    Sridhar
  • gas
    gas
    942 Posts

    Re: wsadmin did not working for Websphere_portal

    ‏2011-05-03T13:08:11Z  
    when i install the application in app server and when try start app, i see the below error

    "AAAA.ear"can not be started because it is installed on a different server.

    Can you please explian how to manage portal app in WAS server instead of portal server

    Thanks
    Sridhar
    Use admin console from WebSphere_Portal server.
    Since was 6.1 admin console is available on every app server.
    So if it is Portal 6.1 (or deployed on WAS 6.1 or higher) you will have admin console on websphere_portal also.
    I don't remember wheter it is on default_host or admin_host, so check both ports.
    It has the same uri as on server1 but different port - http://host:port/ibm/console, as port test either WC_adminhost or WC_defaulthost (you will be redirected to https if security is enabled).
  • SystemAdmin
    SystemAdmin
    37421 Posts

    Re: wsadmin did not working for Websphere_portal

    ‏2011-05-04T07:04:50Z  
    when i install the application in app server and when try start app, i see the below error

    "AAAA.ear"can not be started because it is installed on a different server.

    Can you please explian how to manage portal app in WAS server instead of portal server

    Thanks
    Sridhar
    Hi,

    Default ports for WebSphere Administrative Console for WebSphere Portal:

    server1, use http://<hostname>:10001/admin
    WebSphere_Portal, use http://<hostname>:10027/admin
    //Ahmed
  • SridharSanthanakrishnan
    6 Posts

    Re: wsadmin did not working for Websphere_portal

    ‏2011-05-04T10:14:22Z  
    Hi,

    Default ports for WebSphere Administrative Console for WebSphere Portal:

    server1, use http://<hostname>:10001/admin
    WebSphere_Portal, use http://<hostname>:10027/admin
    //Ahmed
    Thanks.