[jboss-user] [JBoss Messaging] - Incrementing thread counter using MDB's ?

JBoss 4.2.1/ JBM 1.3 GA We use MDBs running as endpoints for JMS messages. Running a load test on our code, here is a sample of logs that i see on the JBoss AS. com/favicon.ico|resolved:true|recommended:true|lastupdatedtime:0 | 16:11:36,079 DEBUG [WorkManager(2)-1675]: org.jboss.jms.server.endpoint.ServerConnectionEndpoint - Connection 2736 stopped | 16:11:36,079 DEBUG [WorkManager(2)-1675]: org.jboss.jms.server.endpoint.ServerConnectionEndpoint - Connection 2736 stopped | 16:11:36,091 INFO [WorkManager(2)-1676]: com.getmedium.services.urivalidation.ejbs.UriMDB - JMS URL::http://wwwapps.ups.com/WebTracking/track | 16:11:36,092 INFO [WorkManager(2)-1676]: com.getmedium.services.urivalidation.ejbs.UriValidator - UriValidator::http://wwwapps.ups.com/WebTracking/track | 16:11:36,092 INFO [WorkManager(2)-1676]: com.getmedium.services.urivalidation.ejbs.UriValidator - Running HTML parser | 16:11:36,093 DEBUG [WorkManager(2)-1676]: com.getmedium.services.urivalidation.HtmlParser - resolving {}http://wwwapps.ups.com/WebTracking/track | 16:11:36,108 INFO [WorkManager(2)-1674]: com.getmedium.services.urivalidation.HtmlParser - Resolving URL::http://www.datingnetwork.com | 16:11:36,109 INFO [WorkManager(2)-1674]: com.getmedium.services.urivalidation.HtmlParser - URL isResolved::true | 16:11:36,109 INFO [WorkManager(2)-1674]: com.getmedium.services.urivalidation.HtmlParser - Found a title Token | 16:11:36,301 INFO [WorkManager(2)-1676]: com.getmedium.services.urivalidation.HtmlParser - Resolving URL::http://wwwapps.ups.com/WebTracking/track | 16:11:36,301 INFO [WorkManager(2)-1676]: com.getmedium.services.urivalidation.HtmlParser - URL isResolved::true | 16:11:36,305 INFO [WorkManager(2)-1676]: com.getmedium.se The section of the log with this expression : [WorkManager(2)-1676] bothers me. the number you see 1676 started from 0. This number keeps incrementing as the load test progresses. The log messages are coming from the MDB. My reading of this display is that this log line is generated by the Thread#1676 in Thread group WorkManager(2). Is this right ? Should the thread count continue to increment ?If pooling ...i would expect to see these numbers being re-used. Is this number increment symptomatic of misconfiguration on my part ? I have not profiled the server yet. The server has not crashed . Yet :)) Here is my Log4J pattern : log4j.appender.stdout.layout.ConversionPattern = %d{ABSOLUTE} %p %x [%t]: %c - %m%n View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086365#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...