5 Replies Latest reply on Aug 5, 2008 12:49 PM by jonathanztaub

    Annoying log warning:

    jonathanztaub Newbie

      I'm getting the following logging message quite often in my application which makes heavy JMS usage (persists messages to the database):

      17:38:46,640 WARN [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, 29, 27, 1--3f57febc:10fd:48901126:17f-3f57febc:10fd:48901126:182
      


      I've browsed the forums and internet and couldn't find exactly what this message is about. My questions are:
      * What exactly is the problem?
      * What is the root cause of it?

        • 1. Re: Annoying log warning:
          jaikiran pai Master

          I don't know what the problem is, but a search brought up this thread http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4093035

          • 2. Re: Annoying log warning:
            jonathanztaub Newbie

            Hmmmmmmmm......
            Thanks for pointing this out. Perhaps I did something funky with the search.
            In any event, that thread doesn't really explain what the problem is, in "plain English" (other than not so useful stack trace message).

            • 3. More info....
              jonathanztaub Newbie

              As part of my development, I drop/create the database a lot of times, this means that I'm getting rid of JBoss' JMS related tables as well. If there was bad data in there, for whatever reason (dead message queue perhaps), it would have been gone. However, I still see the log messages.

              This caused me to think that maybe there is something on the local file system that JBoss creates and perhaps the problem stems from bad/corrupt data that happened while doing initial development and testing.
              So I deleted the entire %JBOSS_HOME%\server\default directory and unzipped it from the distribution zip again - the warning message is gone now.
              This could just be a coincidence, but I'll know in the upcoming days, depending on whether I see the message or not.

              Unfortunately, I zapped the entire directory for good and cannot differentiate it with the current "clean" copy that I have.

              • 4. Re: Annoying log warning:
                jaikiran pai Master

                 

                This caused me to think that maybe there is something on the local file system that JBoss creates and perhaps the problem stems from bad/corrupt data that happened while doing initial development and testing.


                By default, JBoss uses HSQLDB to store JMS related data. The data will be stored in %JBOSS_HOME%\server\< serverName>\data folder. If at all you want to delete the JMS related data (and if it solves your original issue), then you can delete this "data" folder instead of deleting the entire profile.

                • 5. Re: Annoying log warning:
                  jonathanztaub Newbie

                  I was able to reproduce this - it basically happens when I rollback a transaction. There are some files created under %JBOSS_HOME%\server\default\data\tx-object-store. I'm not sure whether this is JMS related at all.

                  However, I still don't quite understand what the problem is and the logs are quite annoying. I searched elsewhere on the internet, and found other people running into this logging statement, but none had any pointers as to what the problem is.

                  Perhaps, and correct me if I'm wrong, XA has to do with 2pc, and having a JMS transaction resource with a database (JDBC) causes some issues. I'll try creating a database insert failure and a rollback inside another bean, which is outside the scope of JMS, and see whether the problem manifests itself there as well.