Re: making the XARessource serializable
От | teknokrat |
---|---|
Тема | Re: making the XARessource serializable |
Дата | |
Msg-id | fcltmc$56s$1@sea.gmane.org обсуждение исходный текст |
Ответ на | Re: making the XARessource serializable ("Heikki Linnakangas" <heikki@enterprisedb.com>) |
Список | pgsql-jdbc |
Heikki Linnakangas wrote: > teknokrat wrote: >> From what i have managed to make out, Arjuna has a xa recovery module >> that can recover resources if the XAResource is serializable. Things get >> more complicated if its not. I've recompiled the jdbc drivers, making >> PGXAConnection serializable and it worked. > > What exactly did you do to "make PGXAConnection serializable"? If you > just add "implements Serializable", you'll get an > NotSerializableException when you actually try to serialize it. > belive or not, thats exactly what i did. I thought that the BaseConnection instance would stuff things up but it hasn't. No idea why. >> This is a link illustrating >> the behaviour we were getting >> http://wiki.jboss.org/wiki/Wiki.jsp?page=TxNonSerializableXAResource > > According to that, you need to provide an implementation of > com.arjuna.ats.jta.recovery.XAResourceRecovery. Apparently there's a > simple implementation that looks up the XADataSource implementation with > JNDI. See JBoss Transaction API Programmers Guide, chapter 4, title > "Shipped XAResourceRecovery implementations". yeah, the JDBCXARecovery module. I guess I'll have to llok into that. The problem for us being that our password can't be in plaintext. > I'm surprised Arjuna/JBoss doesn't just connect to every database listed > in JNDI, or at least all those that were used in the transactions that > need recovery. That's what other app servers do, I believe. > that would be good.
В списке pgsql-jdbc по дате отправления: