April 2016 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2658) Implement JMS integration classes for MessageListener

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2658?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2658. ------------------------------- Resolution: Migrated to another ITS > Implement JMS integration classes for MessageListener > ----------------------------------------------------- > > Key: JBTM-2658 > URL: https://issues.jboss.org/browse/JBTM-2658 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA > Affects Versions: 5.3.2.Final > Reporter: Alexis Hassler > Priority: Minor > > The new JMS integration classes are working fine with a Publisher or a simple Consumer, but not with MessageListener. It would be nice to be able to implement something like a MDB without JavaEE. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2658) Implement JMS integration classes for MessageListener

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2658?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2658: ------------------------------------- Hi Alexis, I think you might be in the wrong place, this is the transaction manager component not the JMS component? Maybe you could talk to the Artemis team? Unless I misunderstood but in which case I recommend a discussion here first: https://developer.jboss.org/en/jbosstm/content?filterID=contentstatus%5bp... > Implement JMS integration classes for MessageListener > ----------------------------------------------------- > > Key: JBTM-2658 > URL: https://issues.jboss.org/browse/JBTM-2658 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA > Affects Versions: 5.3.2.Final > Reporter: Alexis Hassler > Priority: Minor > > The new JMS integration classes are working fine with a Publisher or a simple Consumer, but not with MessageListener. It would be nice to be able to implement something like a MDB without JavaEE. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2658) Implement JMS integration classes for MessageListener

by Alexis Hassler (JIRA)

Alexis Hassler created JBTM-2658: ------------------------------------ Summary: Implement JMS integration classes for MessageListener Key: JBTM-2658 URL: https://issues.jboss.org/browse/JBTM-2658 Project: JBoss Transaction Manager Issue Type: Feature Request Components: JTA Affects Versions: 5.3.2.Final Reporter: Alexis Hassler Priority: Minor The new JMS integration classes are working fine with a Publisher or a simple Consumer, but not with MessageListener. It would be nice to be able to implement something like a MDB without JavaEE. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2579) Throw XAException in XATerminator::commit if a wrapped resource fails transiently

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2579?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2579: ----------------------------------------------- Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1325726|https://bugzilla.redhat.com/show_bug.cgi?id=1325726] from MODIFIED to ON_QA > Throw XAException in XATerminator::commit if a wrapped resource fails transiently > --------------------------------------------------------------------------------- > > Key: JBTM-2579 > URL: https://issues.jboss.org/browse/JBTM-2579 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Critical > Fix For: 4.17.31, 5.2.9.Final > > > It is possible for a resource that we are wrapping to return say XA_RETRY or XA_RMFAIL and therefore end up in the BasicAction failed list. However there is no error returned from commit in this circumstance as the recovery manager should ensure a consistent outcome. > The reason this becomes a problem for JTA and XATerminator in particular is that as no error is returned a parent coordinator will assume the branch completed successfully. In the future when it calls XATerminator::recover though this branch will be returned and detected as an orphan. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2575) When checking for orphaned subordinate transactions in the middle of a tree branches that are eligible for orphan detection will be rolled back

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2575?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2575: ----------------------------------------------- Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1289386|https://bugzilla.redhat.com/show_bug.cgi?id=1289386] from MODIFIED to ON_QA > When checking for orphaned subordinate transactions in the middle of a tree branches that are eligible for orphan detection will be rolled back > ----------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2575 > URL: https://issues.jboss.org/browse/JBTM-2575 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 4.17.31, 5.2.9.Final > > > There is a check in the subordinate orphan detection that not only checks for matching gtrid but also for matching subordinate name. This will not match correctly for an intermediary node. E.g. > a->b b->c > When b scans c the xid it gets back will have subordinate name of c, b will look in its object store and match the subordinate on gtrid but the subordinate node ID in b subordinateatomicaction will be "b". > This check is actually superfluous anyway. We already know that the Xid returned from c was for b because of transport level checks. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2120) Add a deferred exceptions to the rollback exception if the first resource throws a heuristic rollback

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2120?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2120: ----------------------------------------------- Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1316270|https://bugzilla.redhat.com/show_bug.cgi?id=1316270] from MODIFIED to ON_QA > Add a deferred exceptions to the rollback exception if the first resource throws a heuristic rollback > ----------------------------------------------------------------------------------------------------- > > Key: JBTM-2120 > URL: https://issues.jboss.org/browse/JBTM-2120 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.2.6.Final > > > Pull https://github.com/jbosstm/narayana/pull/598 added deferred throwables in case the XAR::end fails during commit. It doesn't handle the case of the HEURISTIC_ROLLBACK of a first resource where Narayana rolls back the remaining participants and then clears the failed/heuristic lists (and marks the txn as rolled back). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2636) Backport deferred exceptions

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2636?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2636: ----------------------------------------------- Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1316270|https://bugzilla.redhat.com/show_bug.cgi?id=1316270] from MODIFIED to ON_QA > Backport deferred exceptions > ---------------------------- > > Key: JBTM-2636 > URL: https://issues.jboss.org/browse/JBTM-2636 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.32 > > > Includes > * JBTM-2120 > * https://github.com/jbosstm/narayana/pull/598/commits -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2657) Missing narayana-osgi-jta artifact with the release profile

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2657?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Amos Feng created pull request #1002 in GitHub ---------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Missing narayana-osgi-jta artifact with the release profile > ----------------------------------------------------------- > > Key: JBTM-2657 > URL: https://issues.jboss.org/browse/JBTM-2657 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Amos Feng > Assignee: Amos Feng > Labels: JTA, OSGI > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2657) Missing narayana-osgi-jta artifact with the release profile

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2657?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-2657: ---------------------------- Fix Version/s: 5.next > Missing narayana-osgi-jta artifact with the release profile > ----------------------------------------------------------- > > Key: JBTM-2657 > URL: https://issues.jboss.org/browse/JBTM-2657 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Amos Feng > Assignee: Amos Feng > Labels: JTA, OSGI > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2657) Missing narayana-osgi-jta artifact with the release profile

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2657?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-2657: ---------------------------- Labels: JTA OSGI (was: ) > Missing narayana-osgi-jta artifact with the release profile > ----------------------------------------------------------- > > Key: JBTM-2657 > URL: https://issues.jboss.org/browse/JBTM-2657 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Amos Feng > Assignee: Amos Feng > Labels: JTA, OSGI > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues April 2016