JMS/JTA issue is case of a server crash

Question

          Hi All
          I am having some JMS/JTA related issue in case of a server crash. This is there
          for both 6.1 and 7.0. Its like this - an MDB is getting data from a Queue and
          its CMT [ie JTA]. Now when the MDB has the onMessage call back that time a usertransaction
          has been opened by the JMS framework of WLS 7.0/6.1. Now when the onMessage block
          is executing if the server crashes - before the TX has been rolled back/commited
          then next time when that server is restarted that message does mot appear on the
          Queue for 4-5 minutes and the Queue shows the message in "Bytes Pending". So the
          user has to wait for 4-5 minutes before getting back the message. In this time
          period whatever u try - like use QueueBrowser /QueueReceiver to find the message
          shows no result. This is something to do with JTA/JMS combination.
          Is there anyway to control this "invisible time" of the message? This is causing
          a lot of problem in our user base.
          thanks
          Anamitra
          

Answer 1

I don't think there are any issues. You might get more info from the
          transaction newsgroup and/or customer support.
          Tom
          Anamitra wrote:
          > Hi Tom
          > thats good - but this brings another question. If that was to be reduced are there
          > any side effects that I should be aware of?
          > thanks
          > Anamitra
          >
          > Tom Barnes <[email protected]> wrote:
          >
          >>This is a FAQ, but is not in the FAQ.
          >>
          >>1) As an enhancement, the transaction recovery delay has been reduced,
          >>
          >>or even eliminated in 8.1.
          >>
          >>2) There are plans to back-port this reduction to 7.0 - I think the
          >>back-port is already available. Contact customer support.
          >>
          >>3) Meanwhile, there is somewhat of a work-around. You can reduce the
          >>
          >>recovery delay to as little as 60 seconds by setting
          >> RecoveryThresholdMillis="60000"
          >>in the "JTA" section of your config.xml, programmatically via JMX on
          >>the
          >>"JTAMBean".
          >>
          >>Tom
          >>
          >>Anamitra wrote:
          >>
          >>>Hi All
          >>>I am having some JMS/JTA related issue in case of a server crash. This
          >>
          >>is there
          >>
          >>>for both 6.1 and 7.0. Its like this - an MDB is getting data from a
          >>
          >>Queue and
          >>
          >>>its CMT [ie JTA]. Now when the MDB has the onMessage call back that
          >>
          >>time a usertransaction
          >>
          >>>has been opened by the JMS framework of WLS 7.0/6.1. Now when the onMessage
          >>
          >>block
          >>
          >>>is executing if the server crashes - before the TX has been rolled
          >>
          >>back/commited
          >>
          >>>then next time when that server is restarted that message does mot
          >>
          >>appear on the
          >>
          >>>Queue for 4-5 minutes and the Queue shows the message in "Bytes Pending".
          >>
          >>So the
          >>
          >>>user has to wait for 4-5 minutes before getting back the message. In
          >>
          >>this time
          >>
          >>>period whatever u try - like use QueueBrowser /QueueReceiver to find
          >>
          >>the message
          >>
          >>>shows no result. This is something to do with JTA/JMS combination.
          >>
          >>>Is there anyway to control this "invisible time" of the message? This
          >>
          >>is causing
          >>
          >>>a lot of problem in our user base.
          >>>
          >>>thanks
          >>>Anamitra
          >>
          >