We use the last version of JBoss with EJB3. We need to start a TCP/IP ServerSocket in our JBoss application, listening all the time the app is running. Is there a problem to do this in JBoss? Is it allowed, and is there a danger JBoss to decide to influence the thread(s) I start?
By the way, the EJB specification (for both 2 and 3) states that: anonymous wrote : The enterprise bean must not attempt to manage threads. The enterprise bean must not attempt | to start, stop, suspend, or resume a thread; or to change a thread?s priority or name. The enterprise | bean must not attempt to manage thread groups. Well, they say "The enterprise bean must not attempt to manage threads". But does it mean that this restriction is not related to other classes deployed in the EJB container? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3922499#3922499 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3922499 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
