> Is the downloaded version of JBossTS is compatible with JBoss 4.2.1 GA
The JTA component is, the JTS is not.
> If not what should we do, any work around will be appreciated.
Wait for AS 5.0 or download the source code and start hacking.
>The JTA component is, the JTS is not.
Thanks buddy, I already knew that, thats why I asked the question.
>Wait for AS 5.0 or download the source code and start hacking.
Well there must be some work around for that, besides your idea of hacking, nor I can wait for AS 5.0
Currently I am trying out some tests, but if some one has already did that or has work around please reply.
Syed Saulat Rizvi
Working around the ORB version incompatibility is possible if you don't mind breaking things. You can put the ORB used by the JTS into the AS, but you'll break various IIOP interop cases. If you have JBossAS on both ends that's fine. If you need to communicate to other app servers e.g. glassfish, it's probably not.
That won't help if your business logic is in EJBs. The pluggable JTS transaction handling for EJBs is broken in AS 4.2 and will need API changes to fix. If you are not using EJBs you may be in with a chance.
Don't even get me started on the tx branch lock sharing issues in Microsoft DTS.
Thank you jhalliday for your feedback.
I have managed to integrate JBoss 4.0.5 with JBossTs 4.2.3 along with patched version of Jacorb. Things are fine uptill now. If the installation document that comes along JBossTs 4.2.3 is updated so that it contains the following two points, will help the developers to integrate JBossTs 4.2.3 easily.
1) You have to change the Object Store Directory in jbossjts-properties so that both the JTS and the JBoss should point to the same directory. Its better to use absolute path rather using relative path.
2) You have to change the environment variable JACORB_HOME to the jacorb installation directory in setup-env.bat file in <jacorb installation>\bin directory
I have found all of these points from your posts in this forum.
Syed Saulat Rizvi
> Things are fine uptill now.
Actually distributed transactions with EJBs are broken in 4.0 too. Transaction context inflow does not behave correctly. EJB3 may be ok, I've not tried that combination.
This is my environment
SQL Server 2005
I have gone through the examples trail_map, and all ran fine.
I have not tried the distributed transactions up till now. Can you tell me with these combinations, Distributed transaction will be able to complete with proper transaction context prorogation????
If not then should I consider alternatives like JOTM for stand alone JTA rather looking something embedded with JBoss (like JBossts)
I really appreciate your feedbacks and helps.
Which trail map are you referring to? The one in JBossTS is concerned with use of the TS outside of the app server, so it's not bothered by the bug in the AS.
If you needs transaction propagation on EJB calls between different JVMs then JOTM won't help you, at least not without some major hacking of the app server. If you don't need that, why are you looking at JBossTS JTS?
Also jtds does not do XA properly on SQLServer 2005. Even on SQL Server 2000 the support for XA is only experimental. Use the Microsoft drivers.
>If you needs transaction propagation on EJB calls between different JVMs
the answer is yes
Ok I will use the Microsoft drivers, can
Can you tell me the exact document or link to implement distributed transactions using JBoss 4.0.5 (along with Jbossts 4.2.3) because there is too much information spread in different documents and I am suffering from information overflow :-) I just have to garbage collect my brain. The documents I read were more towards JTA and I need some code examples to undersdand JTS, How to use JbossTs with JBoss so that transaction propagation on EJB calls between different JVMs can be achieved.
I again thank you for you help (considering you are answering me on this free forum)
> Can you tell me the exact document or link to implement distributed transactions using JBoss 4.0.5 (along with Jbossts 4.2.3)
The INSTALL file in the JBossTS distribution has most of what you need to get started. The only real issue is that the AS JTS transaction handling is buggy, so transaction inflow currently won't work even if you follow the instructions correctly.
I have followed the INSTALL file and done with the configurations.
>>The only real issue is that the AS JTS transaction handling is buggy, so transaction inflow currently won't work even if you follow the instructions correctly.
So what do you suggests me (except for waiting for JBoss 5 and hacking ;) )
> So what do you suggests me (except for waiting for JBoss 5 and hacking ;) )
You could try giving me a big pile of cash :-)
Seriously though, if I had any better solution I would have given it about half a dozen messages back and saved us both some time. There is a slim chance we'll do a 4.2 release with the fix, but since it would mean taking resources away from 5.0 it's not likely.
Finally I found here the reason why my distributed transaction doesn't work :-((
How big must be the pile of cash?
And how long would it take to fix the distributed transactions for ejb 3.0 bug?
I think it could take several months until the 5.0 release.
The only alternative I see at the moment is: switch to glassfish.
But I like to avoid this.
There won't be any official support for JTS in JBossAS 4.2.1. Can you go back to JBossAS 4.0.5?
> How big must be the pile of cash?
The contractors are coming round to quote for my new kitchen later this week. I'll let you know...
> And how long would it take to fix the distributed transactions for ejb 3.0 bug?
Fixing it should not be hard. Getting the AS test suite adapted for the JTS transaction manager and doing all the rest of the release engineering will take a lot longer.
> I think it could take several months until the 5.0 release.
yep. It will take even longer if we stop working on it and do the JTS for AS 4.2 work instead. That's generally considered a Bad Thing since there are more people waiting for 5.0.
> Can you go back to JBossAS 4.0.5?
...which BTW has the same JTS bug, but at least it will give you something to do whilst waiting for 5.0 :-)