August 2016 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2714) Remove deprecated Reasteasy API from RTS

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2714?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2714: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Remove deprecated Reasteasy API from RTS > ---------------------------------------- > > Key: JBTM-2714 > URL: https://issues.jboss.org/browse/JBTM-2714 > Project: JBoss Transaction Manager > Issue Type: Task > Components: REST > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Fix For: 5.next > > > Deprecated Resteasy 2 APIs are being removed by 3.1.0. We need to upgrade the version and update our code to use new APIs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2724) Blacktie should not override maven-assembly-plugin version from parent

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2724: -------------------------------------- Summary: Blacktie should not override maven-assembly-plugin version from parent Key: JBTM-2724 URL: https://issues.jboss.org/browse/JBTM-2724 Project: JBoss Transaction Manager Issue Type: Bug Components: BlackTie Affects Versions: 5.3.3.Final Environment: windows (http://albany.eng.hst.ams2.redhat.com/job/btny-pulls-narayana-catelyn/1089) Reporter: Michael Musgrove Assignee: Amos Feng One of our PRs (http://albany.eng.hst.ams2.redhat.com/job/btny-pulls-narayana-catelyn/1089) ran on windows and failed due to a version issue with the maven-assembly-plugin. The blacktie/blacktie/pom.xml overrides the version set in the parent: {quote}  <version>2.4</version> {quote} We should either retest without the version override or try to find another solution if the latest version of the plugin still has the same issue ([~zhfeng] are you aware of any alternative?). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2723) Upgrade the apr to 1.5

by Amos Feng (JIRA)

Amos Feng created JBTM-2723: ------------------------------- Summary: Upgrade the apr to 1.5 Key: JBTM-2723 URL: https://issues.jboss.org/browse/JBTM-2723 Project: JBoss Transaction Manager Issue Type: Task Components: BlackTie Reporter: Amos Feng Assignee: Amos Feng Fix For: 5.next -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2722) AtomicTransaction equals method is incorrect

by Tomasz Adamski (JIRA)

[ https://issues.jboss.org/browse/JBTM-2722?page=com.atlassian.jira.plugin.... ] Tomasz Adamski updated JBTM-2722: --------------------------------- Description: Method returns false even for equal objects. > AtomicTransaction equals method is incorrect > -------------------------------------------- > > Key: JBTM-2722 > URL: https://issues.jboss.org/browse/JBTM-2722 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.3.3.Final > Reporter: Tomasz Adamski > Assignee: Tomasz Adamski > > Method returns false even for equal objects. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2722) AtomicTransaction equals method is incorrect

by Tomasz Adamski (JIRA)

Tomasz Adamski created JBTM-2722: ------------------------------------ Summary: AtomicTransaction equals method is incorrect Key: JBTM-2722 URL: https://issues.jboss.org/browse/JBTM-2722 Project: JBoss Transaction Manager Issue Type: Bug Components: JTS Affects Versions: 5.3.3.Final Reporter: Tomasz Adamski Assignee: Tomasz Adamski -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2721) Downgrade the version of WildFly to last released version

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2721?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2721: ------------------------------------- Occasionally we do need to use the SNAPSHOT if there is something fundamentally altered in WildFly unfortunately. > Downgrade the version of WildFly to last released version > --------------------------------------------------------- > > Key: JBTM-2721 > URL: https://issues.jboss.org/browse/JBTM-2721 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie, Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > This would be useful in cases like https://developer.jboss.org/message/961052#961052 where the snapshot is not in nexus. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2721) Downgrade the version of WildFly to last released version

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2721: ----------------------------------- Summary: Downgrade the version of WildFly to last released version Key: JBTM-2721 URL: https://issues.jboss.org/browse/JBTM-2721 Project: JBoss Transaction Manager Issue Type: Task Components: BlackTie, Build System Reporter: Tom Jenkinson Assignee: Tom Jenkinson Priority: Minor Fix For: 5.next This would be useful in cases like https://developer.jboss.org/message/961052#961052 where the snapshot is not in nexus. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2720) Allow the setting of an initial delay in PeriodRecovery

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2720?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Tom Jenkinson created pull request #39 in GitHub ------------------------------------------------------------------------------------------ Status: Pull Request Sent (was: Open) > Allow the setting of an initial delay in PeriodRecovery > ------------------------------------------------------- > > Key: JBTM-2720 > URL: https://issues.jboss.org/browse/JBTM-2720 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Recovery > Reporter: Matthew Robson > Assignee: Tom Jenkinson > > Currently Periodic Recovery kicks off at the same interval on every server. As a domain mode cluster grows in size, this leads to significant contention in the DB, especially for RAC implementations. Completion time goes from milliseconds with 1 server to 20+ seconds with 20+ servers. > In an effort to avoid this, an offset the initial start of Periodic Recovery could be provided for the nodes in the cluster. > Periodic Recovery currently leverages 2 properties: > <system-properties> > <property name="RecoveryEnvironmentBean.periodicRecoveryPeriod" value="120"/> > <property name="RecoveryEnvironmentBean.recoveryBackoffPeriod" value="10"/> > </system-properties> > The proposal would be to add a 3rd property, 'RecoveryEnvironmentBean.periodicRecoveryInitilizationOffset' which, when set, would be used for each node. If not set, it would default to current behavior. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2720) Allow the setting of an initial delay in PeriodRecovery

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2720?page=com.atlassian.jira.plugin.... ] Tom Jenkinson moved JBEAP-5577 to JBTM-2720: -------------------------------------------- Project: JBoss Transaction Manager (was: JBoss Enterprise Application Platform) Key: JBTM-2720 (was: JBEAP-5577) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Recovery (was: Transactions) Affects Version/s: (was: 7.backlog.GA) > Allow the setting of an initial delay in PeriodRecovery > ------------------------------------------------------- > > Key: JBTM-2720 > URL: https://issues.jboss.org/browse/JBTM-2720 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Recovery > Reporter: Matthew Robson > Assignee: Tom Jenkinson > > Currently Periodic Recovery kicks off at the same interval on every server. As a domain mode cluster grows in size, this leads to significant contention in the DB, especially for RAC implementations. Completion time goes from milliseconds with 1 server to 20+ seconds with 20+ servers. > In an effort to avoid this, an offset the initial start of Periodic Recovery could be provided for the nodes in the cluster. > Periodic Recovery currently leverages 2 properties: > <system-properties> > <property name="RecoveryEnvironmentBean.periodicRecoveryPeriod" value="120"/> > <property name="RecoveryEnvironmentBean.recoveryBackoffPeriod" value="10"/> > </system-properties> > The proposal would be to add a 3rd property, 'RecoveryEnvironmentBean.periodicRecoveryInitilizationOffset' which, when set, would be used for each node. If not set, it would default to current behavior. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2719) tpcall get three seconds delay in the fooapp quickstart

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2719?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Amos Feng created pull request #1045 in GitHub ---------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > 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

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues August 2016