We do have full recovery now.
Mark.
Dimitris Andreadis wrote:
I suppose after Arjuna's integration the Transaction Recovery task and
subtasks are obsolete now?
http://jira.jboss.com/jira/browse/JBAS-1402
---
Using Tomcat but need to do
Replied on the forum.
Mark.
Emmanuel Bernard wrote:
A Seam use reported an isssue in the way Hibernate register a sync
with JBossTM (the old one at least).
I've described the issue in JIRA
http://jira.jboss.com/jira/browse/EJBTHREE-540
Please provide feedbacks on this one. We must fix that
Adrian Brock wrote:
I've closed the JTA issue:
http://jira.jboss.com/jira/browse/JBAS-3155
AFAIK, this originally comes from the OTS spec.
Synchronizations were standardised first in the OTS. Prior to that
everyone did it in a vendor-specific manner.
I guess the only way an OTS
Not sure what you mean. That reference is purely about registering a
subordinate synchronization with the original transaction coordinator.
JBossTS does this already because it's an optional part of the OTS
specification. You create and enlist the sub-synchronization with the
root
No, there's no guaranteed order (it can be different between transaction
instances and between commit phases). None of the standards provide for
it (going back beyond X/Open), and in fact that's one of the reasons
synchronizations were introduced as a separate protocol (to guarantee
ordering).
, 5, 6, 1,
2, 3.
I guess this doesn't matter since the JMS message order guarantee
doesn't apply after rollback anyway, but good to know.
I guess some users (wrongly) might expect messages to go back in the
queue in the order they were consumed.
Mark Little wrote:
No, there's no guaranteed
without
anyone actually testing the integration.
Beyond that, is this going to be integrated into the installer? If it
is, then we also need an integration test in the jbossas testsuite.
-Original Message-
From: Mark Little [mailto:[EMAIL PROTECTED]
Sent: Saturday, February 25, 2006
Yes, we're still on target for a 4.0.4 plug-in for end of March.
Mark.
Scott M Stark wrote:
The new jta code is not fully cleaned and in a public repository. Need
to check with Mark/Kevin to see if this is still on target for a 4.0.4
release next month.
-Original Message-
From:
Yes. The intention is for 2 plugins for 4.0.4: one to cover the purely
local JTA implementation (which becomes the default in 5.0) and one to
cover JTS/WS-T (which will remain as a separate plugin in 5.0).
Mark.
Andy Miller wrote:
JBoss Transactions should stay an optional plug-in for the
So it depends what you expect to see.
http://jira.jboss.com/jira/browse/JBTM-2 is one example of the tasks
left. You need to remember that the main integration effort was done
months ago in Arjuna, who've been selling the integrated components for
a few years. What we're doing here is a
As part of our ongoing standards activities, I've set up a series of
product/standard matrixes linked off
http://wiki.jboss.org/wiki/Wiki.jsp?page=ADescriptionOfWhatStandardsAreSupported
If you want to update, please do so, or send me the relevant information:
(i) standards body
(ii) name of
Oleg, as someone pointed out the other day, check out www.arjuna.com, where
you'll find an OTS transaction manager (the ex-HP transaction service) that's
been integrated with JBoss. We're also a partnet of JBoss.
Let me know if you've any problems/questions.
Mark.
= Original Message From
From what I heard at JavaOne from a couple of people (e.g., Macromedia use a
cut of it in their app. server), it's dead.
Mark.
- Original Message -
From: Bill Burke [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, June 26, 2003 4:54 PM
Subject: RE: [JBoss-dev] Tyrex transaction
13 matches
Mail list logo
