September 2014 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2242) Misbehaving XAResources may delay deployments

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2242?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2242: ----------------------------------------------- Hayk Hovsepyan <hhovsepy(a)redhat.com> changed the Status of [bug 1143956|https://bugzilla.redhat.com/show_bug.cgi?id=1143956] from ON_QA to VERIFIED > Misbehaving XAResources may delay deployments > --------------------------------------------- > > Key: JBTM-2242 > URL: https://issues.jboss.org/browse/JBTM-2242 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Application Server Integration > Affects Versions: 4.17.22, 5.0.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.23, 5.0.4 > > > Recovery scans can delay subsystem deployments because of contention on the lock XARecoveryModule#_xaResourceRecoveryHelpers: > XARecoveryModule#resourceInitiatedRecoveryForRecoveryHelpers takes the lock and then makes calls to the resource which can potentially hang transiently. Meanwhile, deployments which register recovery helpers are delayed whilst waiting for the lock to be released (in XARecoveryModule#addXAResourceRecoveryHelper). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2241) Removal of RecoveryHelpers fails silently if no scan is in progress

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2241?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2241: ----------------------------------------------- Hayk Hovsepyan <hhovsepy(a)redhat.com> changed the Status of [bug 1143956|https://bugzilla.redhat.com/show_bug.cgi?id=1143956] from ON_QA to VERIFIED > Removal of RecoveryHelpers fails silently if no scan is in progress > ------------------------------------------------------------------- > > Key: JBTM-2241 > URL: https://issues.jboss.org/browse/JBTM-2241 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 4.17.22, 5.0.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.23, 5.0.3 > > > There is some code in XARecoveryModule#removeXAResourceRecoveryHelper that defers removal of recovery helpers if a scan is in progress but skips the removal otherwise. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2253) Brandon CI node misconfiguration

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2253?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-2253. --------------------------------- Resolution: Done Jonathan has worked some magic on the node and it should be OK now (at least my standalone test works now) so resolving. > Brandon CI node misconfiguration > --------------------------------- > > Key: JBTM-2253 > URL: https://issues.jboss.org/browse/JBTM-2253 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Testing > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.0.4 > > > http://172.17.131.2/view/Status/job/narayana/639/PROFILE=BLACKTIE,jdk=jdk... > {code} > [0m[31m12:39:56,830 ERROR [org.codehaus.stomp.jms.ProtocolConverter] (StompConnect Transport: tcp:///127.0.0.1:44813) Connection is closed: org.codehaus.stomp.jms.ProtocolConverter@10c10e8 > [0m[31m12:39:56,831 ERROR [org.codehaus.stomp.tcp.TcpTransport] (StompConnect Transport: tcp:///127.0.0.1:44813) Caught an exception: Broken pipe: java.net.SocketException: Broken pipe > at java.net.SocketOutputStream.socketWrite0(Native Method) [rt.jar:1.7.0_51] > at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:113) [rt.jar:1.7.0_51] > at java.net.SocketOutputStream.write(SocketOutputStream.java:159) [rt.jar:1.7.0_51] > at java.io.DataOutputStream.write(DataOutputStream.java:107) [rt.jar:1.7.0_51] > at java.io.FilterOutputStream.write(FilterOutputStream.java:97) [rt.jar:1.7.0_51] > at org.codehaus.stomp.StompMarshaller.marshal(StompMarshaller.java:83) [wildfly-blacktie-5.0.4.Final-SNAPSHOT.jar:5.0.4.Final-SNAPSHOT] > at org.codehaus.stomp.tcp.TcpTransport.onStompFrame(TcpTransport.java:80) [wildfly-blacktie-5.0.4.Final-SNAPSHOT.jar:5.0.4.Final-SNAPSHOT] > at org.codehaus.stomp.jms.ProtocolConverter.sendToStomp(ProtocolConverter.java:498) [wildfly-blacktie-5.0.4.Final-SNAPSHOT.jar:5.0.4.Final-SNAPSHOT] > at org.codehaus.stomp.jms.ProtocolConverter.onStompFrame(ProtocolConverter.java:209) [wildfly-blacktie-5.0.4.Final-SNAPSHOT.jar:5.0.4.Final-SNAPSHOT] > at org.codehaus.stomp.tcp.TcpTransport.run(TcpTransport.java:101) [wildfly-blacktie-5.0.4.Final-SNAPSHOT.jar:5.0.4.Final-SNAPSHOT] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] > [0mTests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 110.88 sec > Running org.jboss.narayana.blacktie.jatmibroker.xatmi.TestTopic > Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.162 sec > Running org.jboss.narayana.blacktie.jatmibroker.xatmi.server.BlackTieServerTestCase > Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.248 sec > Results : > Tests in error: > AtmiBrokerEnvXMLTest.testEnv:53 » UnknownHost brandon.buildnet.ncl.jboss.com: ... > TestConnection.setUp:29 » Configuration Could not create the orb management fu... > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2241) Removal of RecoveryHelpers fails silently if no scan is in progress

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2241?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2241: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1143956|https://bugzilla.redhat.com/show_bug.cgi?id=1143956] from MODIFIED to ON_QA > Removal of RecoveryHelpers fails silently if no scan is in progress > ------------------------------------------------------------------- > > Key: JBTM-2241 > URL: https://issues.jboss.org/browse/JBTM-2241 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 4.17.22, 5.0.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.23, 5.0.3 > > > There is some code in XARecoveryModule#removeXAResourceRecoveryHelper that defers removal of recovery helpers if a scan is in progress but skips the removal otherwise. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2242) Misbehaving XAResources may delay deployments

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2242?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2242: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1143956|https://bugzilla.redhat.com/show_bug.cgi?id=1143956] from MODIFIED to ON_QA > Misbehaving XAResources may delay deployments > --------------------------------------------- > > Key: JBTM-2242 > URL: https://issues.jboss.org/browse/JBTM-2242 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Application Server Integration > Affects Versions: 4.17.22, 5.0.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.23, 5.0.4 > > > Recovery scans can delay subsystem deployments because of contention on the lock XARecoveryModule#_xaResourceRecoveryHelpers: > XARecoveryModule#resourceInitiatedRecoveryForRecoveryHelpers takes the lock and then makes calls to the resource which can potentially hang transiently. Meanwhile, deployments which register recovery helpers are delayed whilst waiting for the lock to be released (in XARecoveryModule#addXAResourceRecoveryHelper). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2242) Misbehaving XAResources may delay deployments

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2242?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2242: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1143956|https://bugzilla.redhat.com/show_bug.cgi?id=1143956] from POST to MODIFIED > Misbehaving XAResources may delay deployments > --------------------------------------------- > > Key: JBTM-2242 > URL: https://issues.jboss.org/browse/JBTM-2242 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Application Server Integration > Affects Versions: 4.17.22, 5.0.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.23, 5.0.4 > > > Recovery scans can delay subsystem deployments because of contention on the lock XARecoveryModule#_xaResourceRecoveryHelpers: > XARecoveryModule#resourceInitiatedRecoveryForRecoveryHelpers takes the lock and then makes calls to the resource which can potentially hang transiently. Meanwhile, deployments which register recovery helpers are delayed whilst waiting for the lock to be released (in XARecoveryModule#addXAResourceRecoveryHelper). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2241) Removal of RecoveryHelpers fails silently if no scan is in progress

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2241?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2241: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1143956|https://bugzilla.redhat.com/show_bug.cgi?id=1143956] from POST to MODIFIED > Removal of RecoveryHelpers fails silently if no scan is in progress > ------------------------------------------------------------------- > > Key: JBTM-2241 > URL: https://issues.jboss.org/browse/JBTM-2241 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 4.17.22, 5.0.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.23, 5.0.3 > > > There is some code in XARecoveryModule#removeXAResourceRecoveryHelper that defers removal of recovery helpers if a scan is in progress but skips the removal otherwise. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2258) Update the build process to build a binary distribution of Narayana during normal install phase

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2258?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2258: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Update the build process to build a binary distribution of Narayana during normal install phase > ----------------------------------------------------------------------------------------------- > > Key: JBTM-2258 > URL: https://issues.jboss.org/browse/JBTM-2258 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.4 > > > ./build.sh install (or just ./build.sh - install is the default) should build the release zip. > We have removed the JavaDocs from the dist as these are available online (including previous versions) and this is consistent with not including the docs either. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2250) RecoveryManagerStartStopTest hang waiting for byteman rendezvous

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2250?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2250: -------------------------------- Assignee: Michael Musgrove (was: Tom Jenkinson) > RecoveryManagerStartStopTest hang waiting for byteman rendezvous > ---------------------------------------------------------------- > > Key: JBTM-2250 > URL: https://issues.jboss.org/browse/JBTM-2250 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 6.0.0 > > Attachments: jstack.1125 > > > The test hung running CI job narayana-jdbcobjectstore (jstack output attached). Buiid config details are: > {quote} > Started by upstream project "narayana-jdbcobjectstore" build number 99 > originally caused by: > Started by user anonymous > Building remotely on brandon in workspace /home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk7.latest/slave/linux > Checkout:linux / /home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk7.latest/slave/linux - hudson.remoting.Channel@64cff684:brandon > Using strategy: Default > Last Built Revision: Revision c37dd7bad1eb75837d79f0356baf35d9fae60a81 (origin/master) > Wiping out workspace first. > Cloning the remote Git repository > Cloning repository git://github.com/jbosstm/narayana.git > git --version > git version 1.7.1 > Fetching upstream changes from origin > Commencing build of Revision cda46e475c3ce62243cf7c63e68310923cb1930b (origin/master > {quote} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2250) RecoveryManagerStartStopTest hang waiting for byteman rendezvous

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2250?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on JBTM-2250: --------------------------------------- http://172.17.131.2/view/Status/job/narayana/PROFILE=MAIN,jdk=jdk7.latest... > RecoveryManagerStartStopTest hang waiting for byteman rendezvous > ---------------------------------------------------------------- > > Key: JBTM-2250 > URL: https://issues.jboss.org/browse/JBTM-2250 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 6.0.0 > > Attachments: jstack.1125 > > > The test hung running CI job narayana-jdbcobjectstore (jstack output attached). Buiid config details are: > {quote} > Started by upstream project "narayana-jdbcobjectstore" build number 99 > originally caused by: > Started by user anonymous > Building remotely on brandon in workspace /home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk7.latest/slave/linux > Checkout:linux / /home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk7.latest/slave/linux - hudson.remoting.Channel@64cff684:brandon > Using strategy: Default > Last Built Revision: Revision c37dd7bad1eb75837d79f0356baf35d9fae60a81 (origin/master) > Wiping out workspace first. > Cloning the remote Git repository > Cloning repository git://github.com/jbosstm/narayana.git > git --version > git version 1.7.1 > Fetching upstream changes from origin > Commencing build of Revision cda46e475c3ce62243cf7c63e68310923cb1930b (origin/master > {quote} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 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 September 2014