• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Accessing wsadmin.bat and doing a thread dump on Websphere

 
Andres Delrotti
Ranch Hand
Posts: 172
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello guys.

I was trying to do a manual thread dump on Websphere so I accessed wsadmin.bat. I get the error:

WASX7023E: Error creating “SOAP” connection to host “localhost” ... ....

- I dont have any deployment manager installed.
- I already checked wsadmin.properties and the host and port matches the soap host and port set in my was admin console. (soap host=localhost,soap port =8880)
- I already included -conntype -host -user and -password in accessing wsadmin. ( >>wsadmin.bat -conntype SOAP -host localhost -user MyUser -password MyPassword )
- I already checked localhost in the host file under etc/drivers
- I did a telnet to localhost 8880 and it was able to connect

None of them fixed it.

What seems to be the problem? I'm doing this for 3 days now and I cant move forward. This is Websphere 5 by the way...

Thanks,
 
Mikalai Zaikin
Ranch Hand
Posts: 3330
10
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Andres Delrotti wrote:Hello guys.

I was trying to do a manual thread dump on Websphere so I accessed wsadmin.bat. I get the error:

WASX7023E: Error creating “SOAP” connection to host “localhost” ... ....

- I dont have any deployment manager installed.
- I already checked wsadmin.properties and the host and port matches the soap host and port set in my was admin console. (soap host=localhost,soap port =8880)
- I already included -conntype -host -user and -password in accessing wsadmin. ( >>wsadmin.bat -conntype SOAP -host localhost -user MyUser -password MyPassword )
- I already checked localhost in the host file under etc/drivers
- I did a telnet to localhost 8880 and it was able to connect

None of them fixed it.

What seems to be the problem? I'm doing this for 3 days now and I cant move forward. This is Websphere 5 by the way...

Thanks,


1) Small chance, but maybe you have some firewall (Like Kerio, or Symantec Personal Firewall) running on your Windows workstation? try to disable it.

2) Did you try -conntype NONE (if you have all locally installed)? Or maybe try via RMI ?

3) Maybe install some firewall software on Windows machine, which will listen outgoing connections, and will show you real port number which is attempted to reach, when you try wsadmin ? (e.g. it's attempting not to 8880, but some other...)

HTH,
MZ
 
Andres Delrotti
Ranch Hand
Posts: 172
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
^^

Already tried -conntype NONE but when I start to execute the $AdminControl command it says its not available.

Already did a netstat -a on port 8880 and it says its listening

There's a semantec on the machine but I couldn't disable it though.....but the firewall is set to off

Could it be that ssl has something to do with this?
 
Mikalai Zaikin
Ranch Hand
Posts: 3330
10
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Andres Delrotti wrote:

Could it be that ssl has something to do with this?


It could be, but it can be said for sure by inspecting WAS logs. Too few inputs.
 
Andres Delrotti
Ranch Hand
Posts: 172
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Mikalai Zaikin wrote:
Andres Delrotti wrote:

Could it be that ssl has something to do with this?


It could be, but it can be said for sure by inspecting WAS logs. Too few inputs.


These are the errors shown in the wsadmin log


The startup trace state is *=all=disabled.
Loaded properties file "/C:/WebSphere/AppServer51/properties/wsadmin.properties"
Issuing message: "WASX7023E: Error creating "SOAP" connection to host "localhost"; exception information: com.ibm.websphere.management.exception.ConnectorNotAvailableException"
WASX7213I: The scripting client is not connected to a server process
The configuration service is not running. Configuration commands will not run.
Validation settings in effect now: Level=HIGHEST, Cross-validation=true, Output file=C:\WebSphere\AppServer51\logs\wsadmin.valout
WASX7072E: The control service is not available.
WASX7206W: The application management service is not running. Application management commands will not run.
 
Mikalai Zaikin
Ranch Hand
Posts: 3330
10
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Andres Delrotti wrote:
These are the errors shown in the wsadmin log


The startup trace state is *=all=disabled.
Loaded properties file "/C:/WebSphere/AppServer51/properties/wsadmin.properties"
Issuing message: "WASX7023E: Error creating "SOAP" connection to host "localhost"; exception information: com.ibm.websphere.management.exception.ConnectorNotAvailableException"
WASX7213I: The scripting client is not connected to a server process
The configuration service is not running. Configuration commands will not run.
Validation settings in effect now: Level=HIGHEST, Cross-validation=true, Output file=C:\WebSphere\AppServer51\logs\wsadmin.valout
WASX7072E: The control service is not available.
WASX7206W: The application management service is not running. Application management commands will not run.


There could be 2 problems:
1) server is not running
2) wsadmin trying to connect to wrong port

 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic