from error log, I guess you config a xa datasource for JMS perstance.
look into "YOUR_JBOSS_HOME/server/YOUR_PROFILE/deploy/messaging/XXX-persistence-service", where there are two attribute "DataSource", find out the datasource name and check corresponding datascource if it's XA datasource.
Apologies for the late reply, but I'm still trying to deal with this issue.
I looked into the datasource defined in the path you gave, which turned out to be a file called "hsqldb-persistence-service.xml". From what I've read, this refers to the default Hypersonic database that JBoss ships with. I'm not sure why I'm seeing a continuous error from something that is included in the default JBoss configuration. Do I have to configure Hypersonic somehow to prevent this error from occurring? Should I modify the hsqldb-persistence-service.xml file to ensure that this datasource is treated as an XA Datasource by JBoss?
I'm kind of at a loss with this one, so any help that anyone can offer is much appreciated. This exception is spamming itself in our log files about every five minutes or so.
Did you ever figure this out. I recently ran across this and figured I would at least post one possible solution.
If you are not using clustering then there are a few fields in the oracle-persistance-service.xml file that need to be commented out.
You should have already done steps 1 - 3 but I added them just in case.
- cd /.../jbossas/server/xxx/deploy/messaging/
- rm hsqldb-persistence-service.xml
- cp /.../jbossas/docs/examples/jms/oracle-persistance-service.xml .
- vim oracle-persistence-service.xml
- / Channel (that is find for 'Channel' in vim)
- comment out the 4 lines below the Note that tell you to comment out the lines, like so.