[JBoss JIRA] (JBTM-1566) Expose timed delivery feature of hornetq in btenqueue
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1566?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1566:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
thanks for the contribution
> Expose timed delivery feature of hornetq in btenqueue
> -----------------------------------------------------
>
> Key: JBTM-1566
> URL: https://issues.jboss.org/browse/JBTM-1566
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: BlackTie
> Affects Versions: 5.0.0.M2
> Reporter: Crispin Boylan
> Assignee: Crispin Boylan
> Fix For: 5.0.0.Final
>
>
> It would be good to be able to specify a delivery time for the message (either relative or absolute) in the btenqueue.
> on #jbossts it was discussed and apparently HornetQ does support this so it just needs to be exposed to the blacktie interface.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months
[JBoss JIRA] (JBTM-1566) Expose timed delivery feature of hornetq in btenqueue
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1566?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1566:
--------------------------------
Assignee: Crispin Boylan (was: Amos Feng)
> Expose timed delivery feature of hornetq in btenqueue
> -----------------------------------------------------
>
> Key: JBTM-1566
> URL: https://issues.jboss.org/browse/JBTM-1566
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: BlackTie
> Affects Versions: 5.0.0.M2
> Reporter: Crispin Boylan
> Assignee: Crispin Boylan
> Fix For: 5.0.0.Final
>
>
> It would be good to be able to specify a delivery time for the message (either relative or absolute) in the btenqueue.
> on #jbossts it was discussed and apparently HornetQ does support this so it just needs to be exposed to the blacktie interface.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months
[JBoss JIRA] (JBTM-1171) improve XAResource preparefailed logging
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBTM-1171?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on JBTM-1171:
-----------------------------------------------
Ondrej Chaloupka <ochaloup(a)redhat.com> changed the Status of [bug 959462|https://bugzilla.redhat.com/show_bug.cgi?id=959462] from ON_QA to VERIFIED
> improve XAResource preparefailed logging
> ----------------------------------------
>
> Key: JBTM-1171
> URL: https://issues.jboss.org/browse/JBTM-1171
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: JTA
> Affects Versions: 4.6.1.CP12
> Reporter: Jonathan Halliday
> Assignee: Michael Musgrove
> Fix For: 4.6.1.CP13, 4.17.5, 5.0.0.M4
>
>
> com.arjuna.ats.internal.jta.resources.arjunacore.preparefailed does not log the underlying XA exception. In cases where e.g. db constraints are deferred to tx commit time, such errors can contain useful information.
> Note that non-deferred constraints are covered by JBTM-575 as the problem manifests at the earlier beforeCompletion (i.e. sql flush) stage.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months
[JBoss JIRA] (JBTM-1171) improve XAResource preparefailed logging
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBTM-1171?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on JBTM-1171:
-----------------------------------------------
Ondrej Chaloupka <ochaloup(a)redhat.com> made a comment on [bug 959462|https://bugzilla.redhat.com/show_bug.cgi?id=959462]
Verified for EAP 6.1.1.ER3.
For info - there was needed to do small changes in reproducer and deferred constraints has to be set on TEST table (thanks akovari for help).
E.g. add unique constraint on the TEST table. You can run test first time and it passes and then alter table like this:
ALTER TABLE TEST ADD
CONSTRAINT key_is_unique UNIQUE (KEY)
DEFERRABLE INITIALLY DEFERRED;
The second run shows the exception.
The second change was to use jboss-as-arquillian-container-managed instead of jboss-as-arquillian-container-remote.
> improve XAResource preparefailed logging
> ----------------------------------------
>
> Key: JBTM-1171
> URL: https://issues.jboss.org/browse/JBTM-1171
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: JTA
> Affects Versions: 4.6.1.CP12
> Reporter: Jonathan Halliday
> Assignee: Michael Musgrove
> Fix For: 4.6.1.CP13, 4.17.5, 5.0.0.M4
>
>
> com.arjuna.ats.internal.jta.resources.arjunacore.preparefailed does not log the underlying XA exception. In cases where e.g. db constraints are deferred to tx commit time, such errors can contain useful information.
> Note that non-deferred constraints are covered by JBTM-575 as the problem manifests at the earlier beforeCompletion (i.e. sql flush) stage.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months
[JBoss JIRA] (JBTM-1863) RESTAT Integration API does not allow participants to leave a transaction early
by Michael Musgrove (JIRA)
Michael Musgrove created JBTM-1863:
--------------------------------------
Summary: RESTAT Integration API does not allow participants to leave a transaction early
Key: JBTM-1863
URL: https://issues.jboss.org/browse/JBTM-1863
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: REST
Affects Versions: 5.0.0.M3
Reporter: Michael Musgrove
Assignee: Gytis Trikleris
Priority: Minor
The restat integration API class org.jboss. narayana.rest.integration.api.ParticipantsManager interface does not allow participants to leave the transaction early (in the spec a participant can DELETE the participant-recovery URI to notify the coordinator that it is leaving the transaction early).
Question: The reportHeuristic method allows participants to leave the transaction after the termination protocol has started. To keep the interface simple would it be sensible to replace reportHeuristic with something that covered leaving a transaction at any time or would that be confusing normal operations with error conditions? If so then maybe just the converse of enlist?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months