Scenario: Consider a b2b commerce application hosted on a WebLogic cluster with JMS
messages being received, processed, and forwarded to external servers. The server log indicates
a potential stuck thread problem where threads are continually getting stuck and JMX monitoring
indicates a continuous backlog of pending messages that could be due to any of the in-flight
messages, delayed messages, or messages being inhibited from delivery. The recommended
approach for setting the number of execute threads would be:
A.
Set the default thread pool max value to match load expectations
B.
Use an iterative approach to set the max thread count value
C.
Set this value the same as the max connections value set on database connections
D.
Leave this setting to be handled by the Work Manager by configuring MaxThreadsConstraint