3 Replies Latest reply on Jan 8, 2008 2:14 PM by Mark Little

    TxNonSerializableXAResource

    Morten Hauch Newbie

      From time to time we are seeing the message described in
      http://wiki.jboss.org/wiki/Wiki.jsp?page=TxNonSerializableXAResource
      in our server.log.

      The only resources involved in the failing transaction is a database and jms (based on JBossMQ).
      Are any of these known potentialy not to be serializable - and is there a way to verify/correct this?

      As I read the wiki entry, this problem can be solved in one of two ways:
      1. Making the resource serializable
      2. Providing an instance of a XAResourceRecovery Implementation.

      Unfortunately it is not at all clear to me how to perform any of these solutions.

      Since I do not use any "homemade" XAResources, I would expect it to be a matter of configuration. Is that correct - and how should it be configured?

      This problem was introduced when we upgraded from 4.0.5 to 4.2.0.

      I am aware of that this description is not very clear - unfortunately it is due to our lack of understanding of this issue.
      Hope you never the less can give us a hint of what to do in order to solve this.