• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 612
  • Last Modified:

Websphere application server toolkit cannot start server

Hello,

When I am working remotely and I try to start the server on my local device, I get the following exception:
javax.naming.NameNotFoundException: Name "RMIConnector" not found in context "".

It causes my server to be stuck in "Starting" mode even though I also get the "Server server1 open for e-business" message.  When I am in the office, I do not have this issue.
0
KMBrochu
Asked:
KMBrochu
  • 11
  • 7
10 Solutions
 
HonorGodCommented:
> When I am working remotely...
   How are you connecting remotely?

What kind of operating system is being used?


0
 
KMBrochuAuthor Commented:
I use Aventail as a VPN into my work.  I am using Windows XP as my OS.
0
 
HonorGodCommented:
So the application server toolkit (AST) is not seeing the successful start of the AppServer, but only when remotely connected to the host?
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
KMBrochuAuthor Commented:
Pretty much.  The host is local (my laptop).  The problem only happens when I am remote, rather than at work.  So I have my laptop at home rather than having my laptop at work.
0
 
HonorGodCommented:
It might be due to the fact that when you are remote, your IP address changes.
the AST may be trying to start the AppServer using the work hostname rather than something fixed like "localhost"
0
 
KMBrochuAuthor Commented:
Okay.  Where would I check that.  In my server window, the server indicates that it is Websphere v6.1 Server @ localhost.
0
 
HonorGodCommented:
Good question.  It may not be an AST setting.

Are you able to execute the startServer command outside of AST (when you are not at work) and have the Application Server start successfully?

I think so, based upon the fact that you are seeing the "open for e-business" message.
0
 
KMBrochuAuthor Commented:
Yes, I am able to start the server ourside of AST using startserver.bat.  I get the same exception message though when I look at the logs.
0
 
HonorGodCommented:
Please locate the logs directory, then

- stop the AppServer
- Clear the logs directory (rename the files if you need to keep them)
- Issue the startServer outside of AST
- Rename the StartServer.log file
- stop the server
- Try to start the server using AST
- Attach the two different startServer.log file here for us to review.

Thanks for your help with this.

0
 
KMBrochuAuthor Commented:
Thank you for looking into this!

The log from using startserver.bat is OutsideASTstartServer.log OutsideASTstartServer.log
The log from using AST is InsideASTstartServer.log InsideASTstartServer.log
0
 
HonorGodCommented:
wow, if I remove the timestamp and process id differences, the files are basically identical...

I'm going to have to give this a little thought...
0
 
HonorGodCommented:
I wonder if the AST has some kind of timeout for how long it is willing to wait for the AppServer to start before giving up and complaining...
0
 
KMBrochuAuthor Commented:
I was thinking the same thing, but do not know where I would set that.
0
 
HonorGodCommented:
Let me see I can find something...
0
 
KMBrochuAuthor Commented:
I double clicked on my server and found that the "Optimize server for testing and developing" checkbox was clicked.  I unclicked it and tried to start the server with the same result.

I also noticed that there is an entry called "Update server status internal (in milliseconds)".  I tried increasing that number and had no success.  All produce the same result.

Very frustrating.
0
 
HonorGodCommented:
One other thing came to mind that might be different for the home vs. work environment was the fact that the AppServer start time may be longer because of TCP/IP lookups for hostnames that aren't available when you are at home.

Unfortunately, looking at the log files you provided, the time required to start the AppServer is 2 minutes or less, so this would seem to indicate that you aren't running into a timeout issue, at least during the start of the AppServer.

I agree, quite frustrating.
0
 
HonorGodCommented:
Thanks for the grade & points.

Good luck & have a great day.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 11
  • 7
Tackle projects and never again get stuck behind a technical roadblock.
Join Now