Oracle Weblogic Server (MOSC)

MOSC Banner

Unknown 10.3.4 work manager constraints

edited Dec 9, 2011 2:02AM in Oracle Weblogic Server (MOSC) 7 commentsAnswered
Hello, I observed a change of behavior after a migration from 10.3.2 to 10.3.4
I have set a maximum constraint on a JMS queue to 32.
The queue itself is based on a No store JMSServer as we have to set a JMSServer even if we want only a memory queue.

When i have launched a stressing test, i got the following message:
managed1_yyyy_MM_dd_HH_mm.log:####<Jul 1, 2011 1:51:36 PM CEST> <Info> <WorkManager> <vgerndvud260> <managed1> <weblogic.timers.TimerThread> <<WLS Kernel>> <> <> <1309521096408> <WL-002936> <maximum thread constraint weblogic.jms.JMSServer1NoStore.Limited is reached>

So i have discovered that a constraint has been automatically created on the JMSServer in 10.3.4.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center