5 Replies Latest reply on Jun 18, 2014 8:59 AM by tomjenkinson

    Issues wiht Jboss EAP 5.0.1

    dchavarria

      Hello,

       

      First of all I want you to know I'm a completely jboss newbie, I'm running with a lot of issues with a productive server we have at work and I really need some help of someone expert on jboss to understand some errors.

       

      We are using jBoss Enterprise Application Platform 5.0.1 and the application running over that is SAVVION Business Process Manager, I've already ask for help with SAVVION's support but they told me to ask with jBoss Support so here I am.

       

      Lately we are getting messages like this on jboss log:

       

      2013-11-06 23:50:04,877 WARN  [com.arjuna.ats.jta.logging.loggerI18N] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] Could not find new XAResource to use for recovering non-serializable XAResource < 131075, 30, 28, 4945102481024849100101589997565558535051535250985358531025249511021024810248491001015899975655585350515352509853585310252495249 >

      2013-11-06 23:52:14,905 WARN  [com.arjuna.ats.jta.logging.loggerI18N] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] Could not find new XAResource to use for recovering non-serializable XAResource < 131075, 30, 28, 4945102481024849100101589997565558535051535250985358531025249511021024810248491001015899975655585350515352509853585310252495249 >

      2013-11-06 23:54:24,930 WARN  [com.arjuna.ats.jta.logging.loggerI18N] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] Could not find new XAResource to use for recovering non-serializable XAResource < 131075, 30, 28, 4945102481024849100101589997565558535051535250985358531025249511021024810248491001015899975655585350515352509853585310252495249 >

      2013-11-06 23:56:34,962 WARN  [com.arjuna.ats.jta.logging.loggerI18N] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] Could not find new XAResource to use for recovering non-serializable XAResource < 131075, 30, 28, 4945102481024849100101589997565558535051535250985358531025249511021024810248491001015899975655585350515352509853585310252495249 >

      2013-11-06 23:58:44,989 WARN  [com.arjuna.ats.jta.logging.loggerI18N] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] Could not find new XAResource to use for recovering non-serializable XAResource < 131075, 30, 28, 4945102481024849100101589997565558535051535250985358531025249511021024810248491001015899975655585350515352509853585310252495249 >


      This message's are alway's showing on log files and they are appearing a lot of times.


      I don't undestand completely this messages, for what I understand they have to do with some transactions that where never recorded on our database, am I right? or am I wrong?


      Do you now how can I get rid of this messages?


      Any help will be really appreciated.


      Thanks in Advance.


        • 1. Re: Issues wiht Jboss EAP 5.0.1
          wdfink

          Hi David,

          welcome to the forum.

          The EAP forum is only for EAP6 issues as this EAP version is available/free for all developers.

          This is more related to transactions so I'll move it.

           

          If you are looking for JBoss support you use the Red Hat customer support portal, you need a subscription for that.

          • 2. Re: Issues wiht Jboss EAP 5.0.1
            wdfink

            The message is because the transaction was aborted and the TxManager is looking for a connection to complete it.

            This might be not possible for some reasons (i.e. incomplete implementation). If you want to get rid of this messages you can stop the Instance and delete the TxManager file store in the server/<profile>/data directory.

            • 3. Re: Issues wiht Jboss EAP 5.0.1
              dchavarria

              Thank you very much for your help, If I stop the Instance and delete the TxManager file store it will have any other effect beside of getting rid of those messages? I'm asking this since this is a productive instance and I'm afraid that if I delete the TxManager file store some other data will be lost.

               

              Again Thank You.

              • 4. Re: Issues wiht Jboss EAP 5.0.1
                wdfink

                You should think about the Tx behaviour.

                In normal cases the database will rollback the transactions if the connections are lost or the behviour is inconsistent.

                If you drop this files and the transactions are still rolled back you have a consistent state.

                With some DB's (i.e. Oracle) you might have hanging, suspect transactions, here the DB admin can manually clean them up.

                • 5. Re: Issues wiht Jboss EAP 5.0.1
                  tomjenkinson

                  Just in case you are still looking into this (we normally get TX questions over here: Narayana) then I do not recommend deleting the transaction log folder. The issue you have is due to configuration and the fact your resource manager has not been registered with the application server. By deleting the object store you more than likely will be creating undetectable heuristic outcomes on transactions where some resources committed and some are rolled back as orphans.