2 Replies Latest reply on Mar 28, 2011 2:08 AM by yong deng

    A question on NPE thrown by com.arjuna.ats.arjuna.recovery.ActionStatusService.doWork

    yong deng Newbie

      My environment:

          JBossTS 4.2.3 SP6
      Issue description:
          I am running my J2EE application longevity testing. During the long run, I once met following NPE:
      2010-05-18 19:25:45,336 WARN  [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.recovery.ActionStatusService_2] - Other Exception: java.lang.NullPointerException
      2010-05-18 19:25:45,476 ERROR [STDERR] java.lang.NullPointerException
      2010-05-18 19:25:45,476 ERROR [STDERR]           at com.arjuna.ats.arjuna.recovery.ActionStatusService.doWork(ActionStatusService.java:123)
      2010-05-18 19:25:45,476 ERROR [STDERR]           at com.arjuna.ats.internal.arjuna.recovery.Connection.run(Connection.java:83)
          I investigate the arjuna codes. I found com.arjuna.ats.arjuna.recovery.TransactionStatusManager will setup a server socket. It listens there to wait for client and will start new thread to server client's request. The NPE is thrown by the working thread which servers client's request.
          I am happy it will only impact one time client request.
      My questions here are:
          1. Will the NPE impact transaction recvoery function to work properly later on?
          2. Is this a bug and fixed in later release?