1 Reply Latest reply on Jan 9, 2004 12:45 PM by mandar

    Questions about JBoss on Linux

    mandar Newbie

       

      "mandarm" wrote:
      "mandarm" wrote:
      Hi,
      We are using Jboss 3.2.1 on Linux
      JDK version 1.4.1_02

      1) On starting jboss server, we see about 70 threads created even without any requests coming in.
      Is this expected or something is wrong in our configuration ?

      2) Whenever an application exception is thrown, the server waits for about 3 minutes and 10 seconds before it does the next step (calling next line of code)
      The same ejb code works fine on JBoss 3.2.1 on Windows 2000 machine. All the ejbs have transaction setting as "NotSupported".

      Why can this happen ?

      What is the default transaction level settings for EJBs in Jboss ?

      I have also enabled the level "TRACE" for TxInterceptorCMT and BeanLock categories in log4j. I do not see any entries being written to the log file. So I assume that there are no transactions created by Jboss.

      Thanks for your help.

      Regards
      Mandar


        • 1. Re: Questions about JBoss on Linux
          mandar Newbie

           

          "mandarm" wrote:
          "mandarm" wrote:
          Hi,
          Here is the trace from TxInterceptorCMT when jboss hangs on linux for about 3 minutes and 10 seconds

          Tx setting for first bean Supports
          Tx setting for seond bean (called by first bean) NotSupported

          -------------------------------------------------

          2004-01-09 13:45:40,279 TRACE [org.jboss.ejb.plugins.TxInterceptorCMT] [RMI TCP Connection(21)-10.2.25.10] Current transaction in MI is null
          2004-01-09 13:45:40,279 TRACE [org.jboss.ejb.plugins.TxInterceptorCMT] [RMI TCP Connection(21)-10.2.25.10] TX_SUPPORTS for create
          2004-01-09 13:45:40,280 TRACE [org.jboss.ejb.plugins.TxInterceptorCMT] [RMI TCP Connection(21)-10.2.25.10] Thread came in with tx null
          2004-01-09 13:45:40,721 TRACE [org.jboss.ejb.plugins.TxInterceptorCMT] [RMI TCP Connection(21)-10.2.25.10] Current transaction in MI is null
          2004-01-09 13:45:40,721 TRACE [org.jboss.ejb.plugins.TxInterceptorCMT] [RMI TCP Connection(21)-10.2.25.10] TX_SUPPORTS for process
          2004-01-09 13:45:40,722 TRACE [org.jboss.ejb.plugins.TxInterceptorCMT] [RMI TCP Connection(21)-10.2.25.10] Thread came in with tx null
          2004-01-09 13:45:40,755 TRACE [org.jboss.ejb.plugins.TxInterceptorCMT] [RMI TCP Connection(21)-10.2.25.10] Current transaction in MI is null
          2004-01-09 13:45:40,756 TRACE [org.jboss.ejb.plugins.TxInterceptorCMT] [RMI TCP Connection(21)-10.2.25.10] TX_NOT_SUPPORTED for create
          2004-01-09 13:45:40,756 TRACE [org.jboss.ejb.plugins.TxInterceptorCMT] [RMI TCP Connection(21)-10.2.25.10] Thread came in with tx null
          2004-01-09 13:45:40,758 TRACE [org.jboss.ejb.plugins.TxInterceptorCMT] [RMI TCP Connection(21)-10.2.25.10] Current transaction in MI is null
          2004-01-09 13:45:40,759 TRACE [org.jboss.ejb.plugins.TxInterceptorCMT] [RMI TCP Connection(21)-10.2.25.10] TX_NOT_SUPPORTED for process
          2004-01-09 13:45:40,759 TRACE [org.jboss.ejb.plugins.TxInterceptorCMT] [RMI TCP Connection(21)-10.2.25.10] Thread came in with tx null

          -------------------------------------------------

          Hope that this will give some hint about what I need to change to handle application exception better.

          Thanks
          Mandar