4 Replies Latest reply on Feb 10, 2006 9:01 AM by atodorov

    JBoss and user threads and sockets

    atodorov

      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:

      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?