Weblogic 8.1 managed server unable to contact Admin server

Question

I have a strange issue here.
I have admin server on Linux Machine A
Managed server on Linux Machine B.
When i try to start managed server on Machine B, i get the following error.
The WebLogic Server did not start up properly.
Exception raised: 'weblogic.management.configuration.ConfigurationException: [Configuration Management:150001]An error occurred while connecting to the admin server to bootstrap through URL: http://MachineA:7100/wl_management_internal2/Bootstrap, user: system
java.io.EOFException
at java.io.ObjectInputStream$BlockDataInputStream.readFully(ObjectInputStream.java:2571)
at java.io.ObjectInputStream$GetFieldImpl.readFields(ObjectInputStream.java:1990)
The error suggests that managed server on machine B, is unable to contact Admin server on Machine A.
But i know for sure that Admin server is running on that port 7100 for sure.
It has been for the last 3 years.
To see if Machine B and Machine A have network issues, i did telnet.
From Machine B: i typed the following
telnet MachineA 7100
Connected to MachineA.
Escape character is '^]'
The above telnet command tells us that no network issues exist.
After a few tries, the managed server contacts to admin server and comes up.
This is not a one time thing.
I saw this behavior many times.
How should i resolve this?
Edited by: gvamsius on Feb 12, 2009 1:23 PM

Answer 1

Every thing is configured fine.
Nothing wrong with Configuration.
This domain has been running for the past 3 years.
Recently, i found something interesting in admin server logs, when i try to start the managed servers.
I realized there will be some amount of hand shake that happens during managed server startup, when it tries to communicate with admin server.
Here is the log snippet when managed server A contacts Admin server and starts up successfully.
####<Mar 10, 2009 12:11:42 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150023> <Bootstrap servlet invoked with action isrunning from managed server Managed Server A.>
####<Mar 10, 2009 12:11:42 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150030> <The bootstrap servlet has acknowledged that the admin server is running to the booting managed server Managed Server A.>
####<Mar 10, 2009 12:11:42 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150023> <Bootstrap servlet invoked with action bootstrap from managed server Managed Server A.>
####<Mar 10, 2009 12:11:46 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150031> <*The bootstrap servlet has finished sending the configuration to Managed Server A*.>
Here is the log snippet when managed server B contacts Admin server and does not start.
####<Mar 10, 2009 12:07:07 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <ExecuteThread: '14' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150023> <Bootstrap servlet invoked with action isrunning from managed server Managed Server B.>
####<Mar 10, 2009 12:07:07 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <ExecuteThread: '14' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150030> <The bootstrap servlet has acknowledged that the admin server is running to the booting managed server Managed Server B.>
####<Mar 10, 2009 12:07:08 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <ExecuteThread: '14' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150023> <Bootstrap servlet invoked with action bootstrap from managed server Managed Server B.>
The difference as you can see here is that managed server starts up only when Admin Server does the following
<*The bootstrap servlet has finished sending the configuration to Managed Server A*.>
Does any one knows why Admin server would not send the above bootstrap configuation all the times for the managed servers?