We are using WL 9.2 mp2 on Sol 10. We get exception when are using the
application and the application becomes unavailable. We cannot shut down the
server using stopWebLogic.sh script. We have to kill the server.
[b]This is the exception :
<Apr 28, 2008 3:33:33 PM CDT> <Critical> <Server>
<BEA-002616> <Failed to listen on channel "Default" on
90.168.56.120:7056, failure count: 1, failing for 0 seconds, java.ne
t.SocketException: Invalid argument>
<Apr 28, 2008 3:33:34 PM CDT> <Critical> <Server>
<BEA-002616> <Failed to listen on channel "Default" on
90.168.56.120:7056, failure count: 2, failing for 1 seconds, java.ne
t.SocketException: Invalid argument>
<Apr 28, 2008 3:33:36 PM CDT> <Critical> <Server>
<BEA-002616> <Failed to listen on channel "Default" on
90.168.56.120:7056, failure count: 3, failing for 3 seconds, java.ne
t.SocketException: Invalid argument>
<Apr 28, 2008 3:33:39 PM CDT> <Notice> <Server>
<BEA-002615> <After having failed to listen, the server is now
listening on channel "Default" on 90.168.56.120:7056.>
<Apr 28, 2008 4:11:31 PM CDT> <Critical> <Server>
<BEA-002616> <Failed to listen on channel "Default" on
90.168.56.120:7056, failure count: 1, failing for 0 seconds, java.ne
t.SocketException: Invalid argument>
<Apr 28, 2008 4:11:32 PM CDT> <Critical> <Server>
<BEA-002616> <Failed to listen on channel "Default" on
90.168.56.120:7056, failure count: 2, failing for 1 seconds, java.ne
t.SocketException: Invalid argument>
<Apr 28, 2008 4:11:34 PM CDT> <Critical> <Server>
<BEA-002616> <Failed to listen on channel "Default" on
90.168.56.120:7056, failure count: 3, failing for 3 seconds, java.ne
t.SocketException: Invalid argument>
<Apr 28, 2008 4:11:37 PM CDT> <Critical> <Server>
<BEA-002616> <Failed to listen on channel "Default" on
90.168.56.120:7056, failure count: 4, failing for 6 seconds, java.ne
t.SocketException: Invalid argument>
<Apr 28, 2008 4:11:41 PM CDT> <Critical> <Server>
<BEA-002616> <Failed to listen on channel "Default" on
90.168.56.120:7056, failure count: 5, failing for 10 seconds, java.n
et.SocketException: Invalid argument>
<Apr 28, 2008 4:11:46 PM CDT> <Critical> <Server>
<BEA-002616> <Failed to listen on channel "Default" on
90.168.56.120:7056, failure count: 6, failing for 15 seconds, java.n
et.SocketException: Invalid argument>
<Apr 28, 2008 4:11:52 PM CDT> <Critical> <Server>
<BEA-002616> <Failed to listen on channel "Default" on
90.168.56.120:7056, failure count: 7, failing for 21 seconds, java.n
et.SocketException: Invalid argument>
<Apr 28, 2008 4:11:59 PM CDT> <Critical> <Server>
<BEA-002616> <Failed to listen on channel "Default" on
90.168.56.120:7056, failure count: 8, failing for 28 seconds, java.n
et.SocketException: Invalid argument>
<Apr 28, 2008 4:12:07 PM CDT> <Critical> <Server>
<BEA-002616> <Failed to listen on channel "Default" on
90.168.56.120:7056, failure count: 9, failing for 36 seconds, java.n
et.SocketException: Invalid argument>
<Apr 28, 2008 4:12:16 PM CDT> <Critical> <Server>
<BEA-002616> <Failed to listen on channel "Default" on
90.168.56.120:7056, failure count: 10, failing for 45 seconds, java.
net.SocketException: Invalid argument>
<Apr 28, 2008 4:12:16 PM CDT> <Critical> <Server>
<BEA-002617> <Attempting to close and reopen the server socket on on
channel "Default" on 90.168.56.120:7056.>
<Apr 28, 2008 4:12:26 PM CDT> <Notice> <Server>
<BEA-002614> <Reopening channel "Default" on
90.168.56.120:7056.>
<Apr 28, 2008 4:12:26 PM CDT> <Notice> <Server>
<BEA-002615> <After having failed to listen, the server is now
listening on channel "Default" on 90.168.56.120:7056.>
<Apr 28, 2008 4:12:26 PM CDT> <Notice> <Server>
<BEA-002623> <Connection rejected, the server is in the RUNNING
state.^M
Starting service
weblogic.application.internal.BackgroundDeploymentService$WaitForBackgroundCompl
etion, 110 of 112.^M
Last service weblogic.deploy.service.internal.adminserver.HeartbeatService took
4ms.>
<Apr 28, 2008 4:12:26 PM CDT> <Notice> <Server>
<BEA-002623> <Connection rejected, the server is in the RUNNING
state.^M
Starting service
weblogic.application.internal.BackgroundDeploymentService$WaitForBackgroundCompl
etion, 110 of 112.^M
Last service weblogic.deploy.service.internal.adminserver.HeartbeatService took
4ms.>
<Apr 28, 2008 4:12:26 PM CDT> <Notice> <Server>
<BEA-002623> <Connection rejected, the server is in the RUNNING
state.^M
Starting service
weblogic.application.internal.BackgroundDeploymentService$WaitForBackgroundCompl
etion, 110 of 112.^M
Last service weblogic.deploy.service.internal.adminserver.HeartbeatService took
4ms.>[/b]
Why will this occur ?
|