January 2007 - jboss-dev-forums - Jboss List Archives

[Design of JCA on JBoss] - Re: JBossTS/JCA Recovery work for JBoss 4.2

by timfox

Also, not everyone that wants recovery will be using JCA. I guess I'm still missing something, but I don't really see why recovery is being viewed as the responsibility of JCA. They seem orthogonal to me. Have I totally misunderstood this thread? :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4005959#4005959 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4005959

19 years, 2 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: JBossTS/JCA Recovery work for JBoss 4.2

by timfox

"weston.price(a)jboss.com" wrote : You are outlining the case for JBM. The JMS/JCA adapter had to account for multiple foreign providers, not just JBM. Not really. JBoss TS recovery works that way for any XAResource - whether it's from JBM, a database, or whatever. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4005952#4005952 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4005952

19 years, 2 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: JBossTS/JCA Recovery work for JBoss 4.2

by weston.price＠jboss.com

Sorry, I should have been more clear. You are outlining the case for JBM. The JMS/JCA adapter had to account for multiple foreign providers, not just JBM. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4005951#4005951 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4005951

19 years, 2 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: JBossTS/JCA Recovery work for JBoss 4.2

by timfox

"weston.price(a)jboss.com" wrote : | For JCA inflow, it has to be through JCA as I am the one initiating the transaction calling XASession.getXAResource() so I am not sure how your recovery stuff would come into play. Also, for outbound connections (ie JDBC) this has to be done to properly register recoverables with JBossTS. Why does it matter who initiated the tx? For recovery with JBoss TS, as long as you have provided an XAResourceRecovery instance, the recovery manager will call upon that to get an XAresource then call recover() on that to get the list of xids from the resource manager. (You can also make the XAresource serializable but that is another story) The recovery manager will then call commit or rollback on them as it deems appropriate. I don't see what relevance it has who started the transaction. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4005948#4005948 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4005948

19 years, 2 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: JBossTS/JCA Recovery work for JBoss 4.2

by bill.burke＠jboss.com

anonymous wrote : 2)Provide a serializable wrapper to support XA resource recovery using JBossTS. | | It was my plan to use this wrapper both on the inbound and outbound for JCA. From my understanding, this would enable JBossTS to reconsruct the XAResource and call recover as the XAResource (in this case the wrapper) would be written to the transaction log enabling JBossTS to do it's thing. | One issue with this is that the user that executed the original transaction may not have permission to perform a recovery. For instance, only a DBA may have the permission to perform recovery on the database. Also, because the XA spec is a bit ambiguous, different XAResources of different vendors may have different requirements on what flags you pass into XAResource.recover(). There's also the general problem that some XAResources require Xid padding and others don't. I'm guessing that JBoss TS solves the latter two problems in very very hacky ways that are easy to break as there is no defined integration contract between JBoss, JBoss JCA, and Arjuna. I do not know how or if they solve the permission problem. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4005943#4005943 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4005943

19 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Failing tests

by scott.stark＠jboss.org

I'll fix this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4005940#4005940 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4005940

19 years, 2 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: JBossTS/JCA Recovery work for JBoss 4.2

by weston.price＠jboss.com

anonymous wrote : | I'm probably misunderstanding what you're doing here, but for JMS the recovery manager interfaces with the jms provider via an XAResourceRecovery instance - i.e. there's no JCA involved. | For JCA inflow, it has to be through JCA as I am the one initiating the transaction calling XASession.getXAResource() so I am not sure how your recovery stuff would come into play. Also, for outbound connections (ie JDBC) this has to be done to properly register recoverables with JBossTS. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4005927#4005927 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4005927

19 years, 2 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: JBossTS/JCA Recovery work for JBoss 4.2

by timfox

I'm probably misunderstanding what you're doing here, but for JMS the recovery manager interfaces with the jms provider via an XAResourceRecovery instance - i.e. there's no JCA involved. Are you suggesting that all XA recovery is driven via the JCA adapter? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4005914#4005914 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4005914

19 years, 2 months

1
0
0 / 0

[Design of JCA on JBoss] - JBossTS/JCA Recovery work for JBoss 4.2

by weston.price＠jboss.com

Currently in the 4.2 branch the | org.jboss.resource.connectionmanager.xa.JcaXAResourceWrapper | has been provided for two reasons: 1) We needed a way to override the isSameRM method to address a well known WebSphereMQ bug where mutliple XAResouces could not be enlisted in the same transaction from the same RM. Basically this simply amounted to moving the isSameRM stuff that was originally done for Oracle to be more generic. 2)Provide a serializable wrapper to support XA resource recovery using JBossTS. It was my plan to use this wrapper both on the inbound and outbound for JCA. From my understanding, this would enable JBossTS to reconsruct the XAResource and call recover as the XAResource (in this case the wrapper) would be written to the transaction log enabling JBossTS to do it's thing. I wanted to throw this out in the forum just be sure I am not missing anything and to solicit advice as to if this is the appropriate approach to take. The alternative approach would be to implement the | com.arjuna.ats.jta.recovery.XAResourceRecovery | interface and do things in the same manner as the JMS recovery work. Thoughts? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4005906#4005906 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4005906

19 years, 2 months

1
0
0 / 0

[Design of POJO Server] - Re: JAXBDeployer

by jason.greene＠jboss.com

"adrian(a)jboss.org" wrote : | I'd also need to do a lot more testing before I was convinced it actually works. | | e.g. I recently filed a bug which shows Sun's impl doesn't inheritance properly. | | I've been assigned a bug number, but it hasn't appeared on the website yet | - who knows when it will get fixed, hopefully not 4 years like the classloader | problems :-) | | http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6516905 | It works great for me. What's the inheritence problem? Also, bugs for it are supposed to be opened here: https://jaxb.dev.java.net/servlets/ProjectIssues -Jason View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4005880#4005880 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4005880

19 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums January 2007