I'm having hard time to understand follosing issue, so mayby someone could clear things out.
Recently I have been profiling JBoss AS with JProfiler and noticed that JMS SessionsPool Worker threads are blocked for about 6-10 seconds after they are created. This happens atleast with our software and with JBoss 4.0.4.
Does anyone know internal reason for blocking these threads? Having hardtime to understand why they have to be blocked... :)
I am also getting the same behavior in JProfiler. I am using JBoss 4.2.2 GA. I am having the snapshot of the JProfiler, according to the JProfiler "JMS SessionPool Worker" thread blocked since 117 seconds and still in blocked state. Monitor class it is showing is "org.jboss.mq.server.ReceiversImpl"
|Retrieving data ...|