Shiva.
We recently upgraded our WebLogic platform to 6.0 SP2 with all the rolliing paches,
JDK 1.3.1 and solaris 6. When we deployed this config in production, we started
to see the following exceptions which seem to indicate that the server is stopping
every now and then for a few seconds. Actually, this happens very frequently and
I've been working with BEA on this issue the last 3 weeks but no resolution so
far. Looks like you guys have already seen this error in your envt...any ideas
how we can fix this one??
Given below is the exception I see in the logs .. Please help ...
####<Dec 5, 2001 5:53:50 PM PST> <Critical> <WebLogicServer> <jaws.andale.com>
<myserver> <ListenThread> <system> <> <000204> <Faile d to listen on port 80,
failure count: 1, failing for 1,007,603,630 seconds, java.net.SocketException:
Software caused connection ab ort> ####<Dec 5, 2001 5:53:51 PM PST> <Notice> <WebLogicServer>
<jaws.andale.com> <myserver> <ListenThread> <system> <> <000205> <After h aving
failed to listen, the server is now listening on port 80>
I am having the same problem. I have the trial version of "WLS 6.2 SP2" and using the bundled JVM [1.3.1_01] on Solaris 2.7. I have downloaded the latest version of LWS 6.2 [so it should have all the patches].
I also get the "java.net.SocketException:
Software caused connection abort" message !
Please help as I am stumped.
Thanks,
Annu