Win a copy of The Java Performance Companion this week in the Performance forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

weblogic.utils.UnsyncCircularQueue$FullQueueException

 
lolita ling
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi all!
I use weblogic9.2 on Suse linux. when weblogic runs for sometime,I get the exception as follows:
[root@wapapp2 logs3]# tail -200 /data/bea/user_projects/domains/base_domain/servers/server36/logs/server36.log
####<May 28, 2009 10:40:34 AM CST> <Critical> <WorkManager> <wapapp2> <server36> <weblogic.timers.TimerThread> <<WLS Kernel>> <> <> <1243478434939> <BEA-002911> <WorkManager weblogic.jms.jmsserver36.Limited failed to schedule a request due to weblogic.utils.UnsyncCircularQueue$FullQueueException: Queue exceed maximum capacity of: '65536' elements
weblogic.utils.UnsyncCircularQueue$FullQueueException: Queue exceed maximum capacity of: '65536' elements
at weblogic.utils.UnsyncCircularQueue.expandQueue(UnsyncCircularQueue.java:72)
at weblogic.utils.UnsyncCircularQueue.put(UnsyncCircularQueue.java:94)
at weblogic.work.MinThreadsConstraint.add(MinThreadsConstraint.java:85)
at weblogic.work.RequestManager.enqueueOnReachingMaxConstraint(RequestManager.java:170)
at weblogic.work.RequestManager.executeIt(RequestManager.java:212)
at weblogic.work.ServerWorkManagerImpl.schedule(ServerWorkManagerImpl.java:140)
at weblogic.timers.internal.TimerManagerImpl.execute(TimerManagerImpl.java:631)
at weblogic.timers.internal.TimerThread$Thread.run(TimerThread.java:270)

can anybody give me some advice on how to avoid this?
any help is greatly appreciated!
>
 
Ajish Thomas
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Seems to be a BUG raise one case with Oracle
 
walid taraf
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Seen same error for us on WL10.3. Need a patch in the form a jar file that needs to be first on classpath ahead of the other installed server jars like webserviceclient.jar, com.bea.core.utils jars etc. Needs to be highest in classloader so it does not collide with the same classes down below.

Worked for us once applied.
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic