May 2018 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3022) The build should build the (deprecated) lra-annotations module

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-3022?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3022: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > The build should build the (deprecated) lra-annotations module > -------------------------------------------------------------- > > Key: JBTM-3022 > URL: https://issues.jboss.org/browse/JBTM-3022 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.8.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > the lra parent pom should include a build of the lra-annotations module: > <module>lra-annotations</module> -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3022) The build should build the (deprecated) lra-annotations module

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-3022?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Michael Musgrove created pull request #1315 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > The build should build the (deprecated) lra-annotations module > -------------------------------------------------------------- > > Key: JBTM-3022 > URL: https://issues.jboss.org/browse/JBTM-3022 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.8.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > the lra parent pom should include a build of the lra-annotations module: > <module>lra-annotations</module> -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3022) The build should build the (deprecated) lra-annotations module

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-3022: -------------------------------------- Summary: The build should build the (deprecated) lra-annotations module Key: JBTM-3022 URL: https://issues.jboss.org/browse/JBTM-3022 Project: JBoss Transaction Manager Issue Type: Bug Components: LRA Affects Versions: 5.8.1.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next the lra parent pom should include a build of the lra-annotations module: <module>lra-annotations</module> -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3016) NoSuchFieldException throws when setting the pool properties

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-3016?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-3016: ---------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > NoSuchFieldException throws when setting the pool properties > ------------------------------------------------------------ > > Key: JBTM-3016 > URL: https://issues.jboss.org/browse/JBTM-3016 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tomcat > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > > I think there are only "maxTotal", "maxIdle" and "minIdle" in the GenericObjectPoolConfig, the others are in its parent class BaseObjectPoolConfig. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3021) Running afterCompletion from reaper thread can get ConcurrentModificationException

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-3021?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-3021: -------------------------------- Component/s: JTA > Running afterCompletion from reaper thread can get ConcurrentModificationException > ---------------------------------------------------------------------------------- > > Key: JBTM-3021 > URL: https://issues.jboss.org/browse/JBTM-3021 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Amos Feng > Assignee: Tom Jenkinson > > The way the locking works _syncLock and _synchs are used at different times and so it can be that _syncs is not locked and the .iterator() .next() might get CoModEx -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3021) Running afterCompletion from reaper thread can get ConcurrentModificationException

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-3021?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-3021: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Running afterCompletion from reaper thread can get ConcurrentModificationException > ---------------------------------------------------------------------------------- > > Key: JBTM-3021 > URL: https://issues.jboss.org/browse/JBTM-3021 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Amos Feng > Assignee: Tom Jenkinson > > The way the locking works _syncLock and _synchs are used at different times and so it can be that _syncs is not locked and the .iterator() .next() might get CoModEx -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3020) Add ability for resources to indicate XA_RDONLY on end

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-3020?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-3020: -------------------------------- Forum Reference: https://developer.jboss.org/message/982097, https://javaee.groups.io/g/jta-spec/topic/suggestion_for_a_2pc/18102512 (was: https://developer.jboss.org/message/982097) > Add ability for resources to indicate XA_RDONLY on end > ------------------------------------------------------ > > Key: JBTM-3020 > URL: https://issues.jboss.org/browse/JBTM-3020 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: David Lloyd > Assignee: Ondra Chaloupka > Fix For: 5.next > > > As discussed in WFLY-10258 and https://developer.jboss.org/message/982097, this request is to add the ability for an XAResource to indicate (on end) that it has no committable work, which would act as a hint to order that XAResource at an earlier point of prepare processing, which will in turn increase the chances of a 1PC optimization occurring. > As expressed in the forum thread, the mechanism should not interfere with compatibility. One possible way to do this would be to introduce an enhanced subinterface of XAResource which includes a method like this: > {code:java} > int endWithResult(Xid xid, int flags) throws XAException; > {code} > The method behaves semantically identically to {{XAResource#end}} , except it would be allowed to return {{XA_RDONLY}} or {{XA_OK}}. A value of {{XA_RDONLY}} would indicate that the resource expects to return {{XA_RDONLY}} in response to a {{prepare}} call, whereas a value of {{XA_OK}} indicates that the resource's future {{prepare}} result cannot yet be decided or will be {{XA_OK}}. An invalid result should probably behave equivalently to an {{XAException}} being thrown by the {{end}} method. {{XAER_RMERR}} seems like a reasonable error code for this case. An alternative strategy would be to treat an invalid return value as being equivalent to {{XA_OK}}. > Since it's a subinterface of {{XAResource}}, it could also define the following default method: > {code:java} > default void end(Xid xid, int flags) throws XAException { > endWithResult(xid, flags); > } > {code} > This method would not need to be called by the TM, but would correctly satisfy the {{XAResource}} contract without requiring the user to implement the redundant method. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3021) Running afterCompletion from reaper thread can get ConcurrentModificationException

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-3021?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Tom Jenkinson created pull request #1313 in GitHub -------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Running afterCompletion from reaper thread can get ConcurrentModificationException > ---------------------------------------------------------------------------------- > > Key: JBTM-3021 > URL: https://issues.jboss.org/browse/JBTM-3021 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Amos Feng > Assignee: Tom Jenkinson > > The way the locking works _syncLock and _synchs are used at different times and so it can be that _syncs is not locked and the .iterator() .next() might get CoModEx -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3021) Running afterCompletion from reaper thread can get ConcurrentModificationException

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-3021?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-3021: -------------------------------- Reporter: Amos Feng (was: Tom Jenkinson) > Running afterCompletion from reaper thread can get ConcurrentModificationException > ---------------------------------------------------------------------------------- > > Key: JBTM-3021 > URL: https://issues.jboss.org/browse/JBTM-3021 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Amos Feng > Assignee: Tom Jenkinson > > The way the locking works _syncLock and _synchs are used at different times and so it can be that _syncs is not locked and the .iterator() .next() might get CoModEx -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3021) Running afterCompletion from reaper thread can get ConcurrentModificationException

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-3021: ----------------------------------- Summary: Running afterCompletion from reaper thread can get ConcurrentModificationException Key: JBTM-3021 URL: https://issues.jboss.org/browse/JBTM-3021 Project: JBoss Transaction Manager Issue Type: Bug Reporter: Tom Jenkinson Assignee: Tom Jenkinson The way the locking works _syncLock and _synchs are used at different times and so it can be that _syncs is not locked and the .iterator() .next() might get CoModEx -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues May 2018