views:

56

answers:

3

wsadmin is taking about 10 minutes to connect to the WebSphere Application Server 7.0

i tried this:

C:\WAS_HOME\profiles\PROFILE_NAME\bin>wsadmin -lang jython -user -password -javaoption -Djava.net.preferIPv4Stack=true

but very disappointed to wait to get a session within the shell, for example:

wsadmin>

http://groups.google.com/group/ibm.software.websphere.application-server/browse_thread/thread/2f94111985009e39 http://www-01.ibm.com/support/docview.wss?rs=0&uid=swg21174765

===========

thank you for your feedback Rick!

i tried to get the port number and hostname by using AdminControl.getHost() and AdminControl.getPort() and I was eventually connected to the server despite some delay.

I noticed that I was connected to the server much faster when the hostname and port number were provided in the list of arguments.

Then i tried -conntype none and I was connected to the server almost immediately. do you have any idea why this happens? is there a log file i can take a look to understand the configurations?

=============

A: 

Perhaps you can try to specify the host and port when you invoke wsadmin to remove any problems that may come in due to resolving host names?

wsadmin.bat -host xyx -port soap_port

Another debug option is to specify -conntype none. This launches wsadmin without connecting to the DMGR. If that also takes a long time, you have some other problems.

wsadmin.bat -conntype none

Rick
<pre>thank you for your feedback Rick!i tried to get the port number and hostname by using AdminControl.getHost() and AdminControl.getPort() and I was eventually connected to the server despite some delay. I noticed that I was connected to the server much faster when the hostname and port number were provided in the list of arguments.Then i tried -conntype none and I was connected to the server almost immediately. do you have any idea why this happens? is there a log file i can take a look to understand the configurations?</pre>
Nicholas Key
When you specify -conntype none it doesn't actually connect to the server. When running in that mode you'll notice that some of the normal options aren't available. I don't have WAS installed on my machine, but it seems like AdminControl doesn't work when running this way. Not really sure. Since providing the host and port made things work better, I'm going to assume hostname resolution is taking a bulk of the time.
Rick
A: 

would it be advisable to use -Djava.net.preferIPv4Stack=true as the value in the argument?

for example

wsadmin -lang jython -user USERNAME - password PASSWORD -host LOCALHOST -port 9999 -javaoption -Djava.net.preferIPv4Stack=true

it still took me quite some time to connect to the applications server

Nicholas Key
A: 

Is your DMGR running fine, do a restart of your dmgr or nodeagent and see if the connection is faster.

Gautam