[JBoss JIRA] (JBTM-2719) tpcall get three seconds delay in the fooapp quickstart
by Amos Feng (JIRA)
Amos Feng created JBTM-2719:
-------------------------------
Summary: tpcall get three seconds delay in the fooapp quickstart
Key: JBTM-2719
URL: https://issues.jboss.org/browse/JBTM-2719
Project: JBoss Transaction Manager
Issue Type: Bug
Components: BlackTie, Demonstrator
Reporter: Amos Feng
Assignee: Amos Feng
Fix For: 5.next
The apr_pollset_poll in HybridSocketEndpointQueue.cxx Line 392 is blocking and timing out after 3 second. It is the root cause for the tpcall delaying.
So it should try to wake up the polling in non-conversation session while disconnect
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 8 months
[JBoss JIRA] (JBTM-2718) Make CompensatableActionImpl.WorkInfo class static
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-2718?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris updated JBTM-2718:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Make CompensatableActionImpl.WorkInfo class static
> --------------------------------------------------
>
> Key: JBTM-2718
> URL: https://issues.jboss.org/browse/JBTM-2718
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: Compensations
> Reporter: Gytis Trikleris
> Assignee: Gytis Trikleris
> Priority: Trivial
> Fix For: 5.next
>
>
> If inner class does not require access to an enclosing instance there should be preffered to use inner static class.
> (21902 SIC: Inner class could be made static
> This class is an inner class, but does not use its embedded reference to the object which created it.)
> As reference I would mention Joshua Bloch: Effective Java, item 22.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 8 months
[JBoss JIRA] (JBTM-1853) RESTAT does not expose recovery URIs after a crash
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-1853?page=com.atlassian.jira.plugin.... ]
Michael Musgrove commented on JBTM-1853:
----------------------------------------
Upgraded to priority Major since the fix for JBTM-2714 relies on this functionality.
> RESTAT does not expose recovery URIs after a crash
> --------------------------------------------------
>
> Key: JBTM-1853
> URL: https://issues.jboss.org/browse/JBTM-1853
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: REST
> Affects Versions: 5.0.0.M3
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Fix For: 5.later
>
> Original Estimate: 6 hours
> Remaining Estimate: 6 hours
>
> The RESTAT coordinator creates a participant-recovery URI during participant enlistment. This URI should exist for as long as the participant participates in the transaction including during recovery time. After a coordinator crash GET requests return 404 instead of returning the participant resource URI
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 8 months
[JBoss JIRA] (JBTM-1853) RESTAT does not expose recovery URIs after a crash
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-1853?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-1853:
-----------------------------------
Priority: Major (was: Minor)
> RESTAT does not expose recovery URIs after a crash
> --------------------------------------------------
>
> Key: JBTM-1853
> URL: https://issues.jboss.org/browse/JBTM-1853
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: REST
> Affects Versions: 5.0.0.M3
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Fix For: 5.later
>
> Original Estimate: 6 hours
> Remaining Estimate: 6 hours
>
> The RESTAT coordinator creates a participant-recovery URI during participant enlistment. This URI should exist for as long as the participant participates in the transaction including during recovery time. After a coordinator crash GET requests return 404 instead of returning the participant resource URI
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 8 months
[JBoss JIRA] (JBTM-2667) JDBC Connection leak with Postgres
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2667?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2667:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> JDBC Connection leak with Postgres
> ----------------------------------
>
> Key: JBTM-2667
> URL: https://issues.jboss.org/browse/JBTM-2667
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: JTA
> Affects Versions: 5.3.2.Final
> Reporter: Alexis Hassler
> Assignee: Tom Jenkinson
> Fix For: 5.next
>
>
> When using Narayana's JDBC TransactionalDriver with a Postgres XA datasource, the connections are never closed.
> The problem can be workarounded by adding a modifier :
> {code:java}
> ModifierFactory.putModifier ("postgresql native driver", -1, -1, PsqlConnectionModifier.class.getName());
> {code}
> With a modifier, the close method is called on the XAConnection object, with no modifier it's called on the Connection object.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 8 months