Oracle Weblogic Server (MOSC)

MOSC Banner

Effect of message "MaxThreadContraint reached m times for last n seconds"

edited Feb 16, 2018 4:00AM in Oracle Weblogic Server (MOSC) 2 commentsAnswered

Hello Experts ,

We have production domain with 12 managed servers on Weblogic 10.3.6 and OSB 11.1.1.7.0 verion . There is one proxy service which is entry point for several clients sending request to this domain .

In order to avoid thread starvation we have configured several work managers and there is a major WM for entry Proxy service.

Configuration for this WM is MinThreadsConstraint=20, CapacityConstraint=500 and MaxThreadConstraint=200 .

Earlier MaxThreadConstraint was 150 and we kept on increasing and now its 200.

Problem is there is always this message in server log files :

"<Info> <WorkManager> <host> <osb01_m1> <[ACTIVE] ExecuteThread: '80' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1517938507198> <BEA-002939> <maximum thread constraint MaxThreadsConstraint-SOAFacade is reached 36 times for last 196 seconds>"

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

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center