aspose file tools*
The moose likes JBoss/WildFly and the fly likes Clustering Warning Messages Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » JBoss/WildFly
Bookmark "Clustering Warning Messages" Watch "Clustering Warning Messages" New topic
Author

Clustering Warning Messages

Borgward Coupe
Greenhorn

Joined: Apr 07, 2004
Posts: 1
Hi
What do I have to do to get rid of those warnings (see below). I thought I have to create a InitialContext by using the HA-JNDI port (in my case it is the default port: 1100 ) but I still get the warning message.
Is there anything else I need to know
Cheers
Rolf

Waring Message
07:21:39,070 WARN [TxConnectionManager] Prepare called on a local tx. Use of local transactions on a jta transaction wi
th more than one branch may result in inconsistent data in some cases of failure.

My way of getting the initial context (HA-JNDI)
private Context getInitialContext() throws NamingException {
Hashtable environment = new Hashtable();
environment.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
environment.put(Context.URL_PKG_PREFIXES, "org.jboss.naming rg.jnp.interfaces");
environment.put(Context.PROVIDER_URL, TARGETHOST + ":1100");
return new InitialContext(environment);
}
Konstantin Avdeyev
Greenhorn

Joined: Jan 14, 2002
Posts: 1
you need to use XA datasource instead of local datasource. With more than one branch inside transaction transaction manager wants to do two-phase commit which is only possible with XA datasource.
 
 
subject: Clustering Warning Messages