jeu. mars 08 17:07:16 GMT+01:00 2001:<E> <WebLogicServer> Exception
invoking weblogic.time.server.ScheduledTrigger@2ef54ad4
java.lang.RuntimeException: <UTIL> UnsyncCircularQueue was full!
at
weblogic.utils.UnsyncCircularQueue.expandQueue(UnsyncCircularQueue.java:43)
at
weblogic.utils.UnsyncCircularQueue.put(UnsyncCircularQueue.java:63)
at
weblogic.kernel.ExecuteThreadManager.execute(ExecuteThreadManager.java:227)
at weblogic.kernel.Kernel.execute(Kernel.java:507)
at
weblogic.time.common.internal.ScheduledTrigger.private_execute(ScheduledTrigger.java:184)
at
weblogic.time.server.ScheduledTrigger.private_execute(ScheduledTrigger.java:55)
at
weblogic.time.common.internal.TimeTable.execute(TimeTable.java:222)
at
weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:140)
at java.lang.Thread.run(Thread.java:479)
jeu. mars 08 17:07:16 GMT+01:00 2001:<E> <WebLogicServer> Exception
invoking weblogic.time.server.ScheduledTrigger@b9714ad4
java.lang.RuntimeException: <UTIL> UnsyncCircularQueue was full!
at
weblogic.utils.UnsyncCircularQueue.expandQueue(UnsyncCircularQueue.java:43)
at
weblogic.utils.UnsyncCircularQueue.put(UnsyncCircularQueue.java:63)
at
weblogic.kernel.ExecuteThreadManager.execute(ExecuteThreadManager.java:227)
at weblogic.kernel.Kernel.execute(Kernel.java:507)
at
weblogic.time.common.internal.ScheduledTrigger.private_execute(ScheduledTrigger.java:184)
at
weblogic.time.server.ScheduledTrigger.private_execute(ScheduledTrigger.java:55)
at
weblogic.time.common.internal.TimeTable.execute(TimeTable.java:222)
at
weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:140)
at java.lang.Thread.run(Thread.java:479)
jeu. mars 08 17:08:44 GMT+01:00 2001:<A> <SSLListenThread>
ListenThread.run() failed:
java.lang.RuntimeException: <UTIL> UnsyncCircularQueue was full!
at
weblogic.utils.UnsyncCircularQueue.expandQueue(UnsyncCircularQueue.java:43)
at
weblogic.utils.UnsyncCircularQueue.put(UnsyncCircularQueue.java:63)
at
weblogic.kernel.ExecuteThreadManager.execute(ExecuteThreadManager.java:227)
at weblogic.kernel.Kernel.execute(Kernel.java:507)
at weblogic.t3.srvr.ListenThread.run(ListenThread.java:338)
jeu. mars 08 17:08:44 GMT+01:00 2001:<!> <SSLListenThread> **** The
WebLogic Server is no longer listening for connections.
jeu. mars 08 17:08:44 GMT+01:00 2001:<!> <SSLListenThread> **** You
should probably restart it.
jeu. mars 08 17:08:44 GMT+01:00 2001:<I> <WebLogicServer> Server
shutdown by system
jeu. mars 08 17:08:44 GMT+01:00 2001:<I> <WebLogicServer> Server
shutdown commencing NOW
jeu. mars 08 17:08:45 GMT+01:00 2001:<I> <HTTP> Destroying servlets in
default servlet context.
jeu. mars 08 17:08:45 GMT+01:00 2001:<I> <ServletContext-General> *.jsp:
destroy
jeu. mars 08 17:08:45 GMT+01:00 2001:<I> <ServletContext-General> file:
destroy
jeu. mars 08 17:08:45 GMT+01:00 2001:<I> <WebLogicServer> Requesting
thread shutdown
jeu. mars 08 17:08:45 GMT+01:00 2001:<E> <WebLogicServer> Failed to
submit shutdown command:
java.lang.RuntimeException: <UTIL> UnsyncCircularQueue was full!
at
weblogic.utils.UnsyncCircularQueue.expandQueue(UnsyncCircularQueue.java:43)
at
weblogic.utils.UnsyncCircularQueue.put(UnsyncCircularQueue.java:63)
at
weblogic.kernel.ExecuteThreadManager.execute(ExecuteThreadManager.java:227)
at weblogic.kernel.Kernel.execute(Kernel.java:507)
at
weblogic.event.server.EventMessage.enqueueRequest(EventMessage.java:247)
at
weblogic.event.server.EventRegistration.private_submit(EventRegistration.java:712)
at
weblogic.event.server.EventTopic.deliverToRegistrations(EventTopic.java:266)
at weblogic.event.server.EventTopic.submit(EventTopic.java:342)
at weblogic.event.server.EventTopic.submit(EventTopic.java:337)
[...]
thanks for any help
--
Maxime Kurkdjian
Oxalide - Consultant
http://www.oxalide.com
yes, you were right. After a little bit of tunning, the bug wasn't
reproduced.
I change the heap size of the JVM, the cpu load of the computer drop
from 60% to 15%. I think that the JVM was wasting time in kind of swap
in/out object due to a lack of memory.
thank you for your help.