joesnmp does not have any special integration with the jboss thread pools. When in "agent" mode, if configured to use a thread pool by setting the agent NumberOfThreads attribute, it creates it's own thread pool to serve incoming get/set requests. AFAIK, when joesnmp is used to do outgoing get/set requests, it creates one or two threads for processing them, again, nothing to do with jboss threads. Maybe it is better for you to abstract all joesnmp functionality within an mbean called by your EJBs. This doesn't improve integration of threads with jboss thread pools, but it at least will give you more control over managing snmp "sessions". View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092923#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...