September 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1610) Typo in method names of SerializableXAResourceDeserializer interface

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1610?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reopened JBTM-1610: --------------------------------- > Typo in method names of SerializableXAResourceDeserializer interface > -------------------------------------------------------------------- > > Key: JBTM-1610 > URL: https://issues.jboss.org/browse/JBTM-1610 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Recovery > Affects Versions: 4.17.3, 5.0.0.M2 > Reporter: jaikiran pai > Assignee: Tom Jenkinson > Priority: Optional > > The 2 methods in SerializableXAResourceDeserializer are named these: > {code} > ... > public boolean canDeserialze(String className); > ... > public XAResource deserialze(ObjectInputStream ois) throws IOException, ClassNotFoundException; > {code} > Notice the typo - a missing "i" in deserialize. > I guess it's too late or a bit too much to change those methods now since that interface might already be in use, in different projects. Hence, marking this JIRA as "Optional" -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1610) Typo in method names of SerializableXAResourceDeserializer interface

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1610?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-1610. --------------------------------- Resolution: Won't Fix > Typo in method names of SerializableXAResourceDeserializer interface > -------------------------------------------------------------------- > > Key: JBTM-1610 > URL: https://issues.jboss.org/browse/JBTM-1610 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Recovery > Affects Versions: 4.17.3, 5.0.0.M2 > Reporter: jaikiran pai > Assignee: Tom Jenkinson > Priority: Optional > > The 2 methods in SerializableXAResourceDeserializer are named these: > {code} > ... > public boolean canDeserialze(String className); > ... > public XAResource deserialze(ObjectInputStream ois) throws IOException, ClassNotFoundException; > {code} > Notice the typo - a missing "i" in deserialize. > I guess it's too late or a bit too much to change those methods now since that interface might already be in use, in different projects. Hence, marking this JIRA as "Optional" -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1927) Pull request checker on Windows always reports BlackTie tests as failing

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1927?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-1927. --------------------------------- Resolution: Won't Fix This is a jenkins issue > Pull request checker on Windows always reports BlackTie tests as failing > ------------------------------------------------------------------------ > > Key: JBTM-1927 > URL: https://issues.jboss.org/browse/JBTM-1927 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Critical > > Pull: https://github.com/jbosstm/narayana/pull/429 > Build failed "http://172.17.131.2/job/btny-pulls-narayana-windows2008/293/" > If you look at the report, it is blue with "BUILD SUCCESSFUL" reported: > http://172.17.131.2/job/btny-pulls-narayana-windows2008/293/console -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1923) JTA quick start guide link on website incorrect

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1923?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1923: -------------------------------- Fix Version/s: 5.0.0.M5 > JTA quick start guide link on website incorrect > ----------------------------------------------- > > Key: JBTM-1923 > URL: https://issues.jboss.org/browse/JBTM-1923 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Documentation > Reporter: Ondřej Chaloupka > Assignee: Tom Jenkinson > Fix For: 5.0.0.M5 > > > on http://www.jboss.org/jbosstm/documentation/5_0_0_M4 > for jta quick start guide the link, instead of quick_start_guide is only quick_start -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1923) JTA quick start guide link on website incorrect

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1923?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-1923. --------------------------------- Resolution: Done Fixed on the site for M4 and bc9b14e923710ceb5e9e0b263eb3a09a252c4852 for master > JTA quick start guide link on website incorrect > ----------------------------------------------- > > Key: JBTM-1923 > URL: https://issues.jboss.org/browse/JBTM-1923 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Documentation > Reporter: Ondřej Chaloupka > Assignee: Tom Jenkinson > Fix For: 5.0.0.M5 > > > on http://www.jboss.org/jbosstm/documentation/5_0_0_M4 > for jta quick start guide the link, instead of quick_start_guide is only quick_start -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1774) STM artifactId name potentially ambiguous?

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1774?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1774: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/467 > STM artifactId name potentially ambiguous? > ------------------------------------------ > > Key: JBTM-1774 > URL: https://issues.jboss.org/browse/JBTM-1774 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Build System, STM > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Optional > Fix For: 5.0.0.M5 > > > Most modules that a user is expected to build and use (e.g. XTS, ArjunaCore, the JTA/JTS uber jars) use an aggregate nominative part of the group plus a module-centric name to differentiate them. > The problem such that it is, can be seen cleanest in JBTM-1769 (https://github.com/jbosstm/narayana/commit/8ec2ab2375e3efb67489e7702f20c4...). Here the user is suggested to build :core to build STM which is ambiguous in context with the rest of the project in particular ArjunaCore. > Can the artifactId be changed to stm-core? or just stm? -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1774) STM artifactId name potentially ambiguous?

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1774?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1774: -------------------------------- Fix Version/s: 5.0.0.M5 > STM artifactId name potentially ambiguous? > ------------------------------------------ > > Key: JBTM-1774 > URL: https://issues.jboss.org/browse/JBTM-1774 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Build System, STM > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Optional > Fix For: 5.0.0.M5 > > > Most modules that a user is expected to build and use (e.g. XTS, ArjunaCore, the JTA/JTS uber jars) use an aggregate nominative part of the group plus a module-centric name to differentiate them. > The problem such that it is, can be seen cleanest in JBTM-1769 (https://github.com/jbosstm/narayana/commit/8ec2ab2375e3efb67489e7702f20c4...). Here the user is suggested to build :core to build STM which is ambiguous in context with the rest of the project in particular ArjunaCore. > Can the artifactId be changed to stm-core? or just stm? -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1945) BlackTie can drop a message when multiple threads send a tpcall at the same time

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1945?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-1945. --------------------------------- Resolution: Done > BlackTie can drop a message when multiple threads send a tpcall at the same time > -------------------------------------------------------------------------------- > > Key: JBTM-1945 > URL: https://issues.jboss.org/browse/JBTM-1945 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.0.M5 > > > Test failed: test_215(org.jboss.narayana.blacktie.jatmibroker.xatmi.CSTest) > Intermittent failure seems to have been triggered by: https://github.com/jbosstm/narayana/commit/e0e5d7ab58e377ad6eb43e1737baa7... > Nothing obvious in the commit so setting up a repeating job > It seems that calling receive on a JMS session while the connection is stopped, then in a different thread call start a few seconds later means that hornetq may not restart delivery of messages. If you have a timed receive at the end of the wait period the message is available for delivery. > I will raise a HQ issue but for ourselves I am changing the algorithm so that we do not call connection.start after the receive. -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1944) Merge blacktie and narayana scripts

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1944?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1944: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Merge blacktie and narayana scripts > ----------------------------------- > > Key: JBTM-1944 > URL: https://issues.jboss.org/browse/JBTM-1944 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.0.0.M5 > > > There are still two sets of scripts for building narayana and blacktie > build.* > blacktie/build.* > scripts/hudson/narayana.* > blacktie/scripts/hudson/blacktie-* > Merge them to simplify -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1925) Enable remote debugger in JBossAS/WildFly for all tests

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1925?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1925: -------------------------------- Issue Type: Task (was: Enhancement) > Enable remote debugger in JBossAS/WildFly for all tests > ------------------------------------------------------- > > Key: JBTM-1925 > URL: https://issues.jboss.org/browse/JBTM-1925 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 4.17.11, 5.0.0.M5 > > > This allows us to attach to hung AS instances and see what they are doing. > Adding this to narayana.sh should do the trick: > {code} > echo JAVA_OPTS='"$JAVA_OPTS -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n"' >> ./bin/standalone.conf > {code} -- 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

12 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues September 2013