-
1. Re: Does it matter with the warning
manik Jan 4, 2008 8:54 AM (in response to scotthkao)Hi
I can't say I've ever seen this before - it may well have to do with the fact that JBoss Cache is not an XA resource and hence doesn't go through the steps to register itself as an XA resource with an XA compliant TM.
This should not impact any functionality though, except XA recovery, but in a cache's case this would typically be to flush the cache.
Anyway, I have created a JIRA issue to investigate the WARN message: JBCACHE-1254
Could you please confirm - on the JIRA - the versions of JBoss Cache and JBoss TS, as well as the environment (i.e., within an app server, etc)?
Cheers,
Manik -
2. Re: Does it matter with the warning
scotthkao Jan 9, 2008 11:40 AM (in response to scotthkao)"manik.surtani@jboss.com" wrote:
Hi
Anyway, I have created a JIRA issue to investigate the WARN message: <a href="http://jira.jboss.org/jira/browse/JBCACHE-1254">JBCACHE-1254</a>
Could you please confirm - on the JIRA - the versions of JBoss Cache and JBoss TS, as well as the environment (i.e., within an app server, etc)?
I have no idea how to put the related versions on the JIRA.
I now place the version info here.
JBossCache: 2.0.0.GA
JBossTS: 4.2.3.GA
Environment: standalone Java application
Thansk,
Scott -
3. Re: Does it matter with the warning
manik Apr 4, 2008 8:47 AM (in response to scotthkao)Not a bug in JBC. Rejecting the JIRA.
From the JBossTS guys:
that looks like misconfiguration - that value should be in the default config file. Either they have edited it out the file or the file is not being found. ensure jbossts etc dir is on the classpath (yes the dir itself, not the files in it). then check the file etc/jbossjta-properties.xml file has com.arjuna.ats.arjuna.xa.nodeIdentifier specified in it. -
4. Re: Does it matter with the warning
mreasy Jun 19, 2008 6:03 AM (in response to scotthkao)Hi,
I get the same warning, but due to jboss.server.data.dir pointing to a custom directory. jbossjta-properties.xml has com.arjuna.ats.arjuna.xa.nodeIdentifier specified.
The default layout
jboss
- server
-- default
---- data
works, but my layout:
root
- data
- jboss
-- configname
results in Name of XA node not defined.
Already tried to add root/data and root/data/tx-object-store to the CP, which did not help.
Could you exlain what was meant with "jbossts etc dir"?
Thanks