Jan 5th, 2012, 03:35 AM
Spring JMS running on Tomcat using CommonJ
We have ported our application that uses the Spring Framework and Spring JMS from Websphere and JBoss to Tomcat. As we utilize work managers, we are using CommonJ which seems to be one solution for handling the thread pools. However, if we try and declare a work manager with greater then 100 max threads, we receive an error when Tomcat starts up:
javax.naming.NamingException: Value maxThreads out of range [0..100]
The error is being trigerred from the de.myfoo.commonj.util.AbstractFactory class within CommonJ. Does anyone know if this is a limit imposed by CommonJ as I can't find it documented anywhere? Does anyone have a solution to declare a work manager with more then 100 threads?
Mar 17th, 2012, 04:11 AM
Are you able to successfully port this application on tomcat? We are also in planning to port our application from Websphere to tomcat. We have used Spring, JMS and WorkManager(Async bean feature) of Websphere. We are planning to use commonJ , But not sure about the reliability of this open source framework. Is your application successfully running with commonJ ? Your response will be helpful.
Tags for this Thread