Using WL6.0 JMS to post ticker information. On the other end, I have a Message Driven Bean listeneing to this topic. During busy times, the bean(s) can't keep up. I've changed initial beans in pool and max bean in pool with no luck. Number of consumers is always one. So I changed from a topic to a queue, set initial beans to 5. Now the number of consumers is 5, keeps up just fine. It looks like WL is not creating beans when it needs them. Does anyone know what'g going on / what I'm missing?
Are you using service pack 1? Don't know if it will help, but check out the release notes: http://e-docs.bea.com/wls/docs60/notes/bugfixes2.html This issue resolved with service pack 1 sounds promising... Change Request Number: 040066 Description: The setting max-beans-in-free-pool now determines the maximum number of concurrent instances that can be created to service messages. It is bound by the number of ExecuteThreads.
Joined: Oct 13, 2000
Thanks for the info, looking at that link and know problems, not really sure to upgrade to SP1 or not. SP1 known problems include Apache plug-in may fail for high loads (100+ users). 100 is high, sheesh...