August 2016 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2712) Karaf build failing

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2712?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2712. ------------------------------- Resolution: Out of Date > Karaf build failing > ------------------- > > Key: JBTM-2712 > URL: https://issues.jboss.org/browse/JBTM-2712 > Project: JBoss Transaction Manager > Issue Type: Task > Components: OSGi > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Blocker > > The build of Karaf has started failing. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2713) Investigate why a null FileLock is declared but not used

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2713?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2713: -------------------------------- Summary: Investigate why a null FileLock is declared but not used (was: Remove FileLock cruft from LogStore file) > Investigate why a null FileLock is declared but not used > -------------------------------------------------------- > > Key: JBTM-2713 > URL: https://issues.jboss.org/browse/JBTM-2713 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > It certainly isn't referenced: > https://github.com/jbosstm/narayana/blob/29270942f17cc553ad1497a41f60fce1... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

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

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2722?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2722: -------------------------------- Forum Reference: https://developer.jboss.org/message/956793#956793 > 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 > Fix For: 5.3.4.Final > > > Method returns false even for equal objects. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

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

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2722?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reopened JBTM-2722: --------------------------------- > 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 > Fix For: 5.3.4.Final > > > Method returns false even for equal objects. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

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

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2722?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2722. ------------------------------- Resolution: Done > 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 > Fix For: 5.3.4.Final > > > Method returns false even for equal objects. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

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

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2723?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2723: -------------------------------- Description: This is to provide the basis of JBTM-2719. APR now provides a method to wakeup waiting pools which should be useful. > 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 is to provide the basis of JBTM-2719. APR now provides a method to wakeup waiting pools which should be useful. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2729) Upgrade the zip to 3.0 in the CI el5 servers

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2729?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2729: ------------------------------------- This is just an upload on the CI servers - ancillary to main project. > Upgrade the zip to 3.0 in the CI el5 servers > -------------------------------------------- > > Key: JBTM-2729 > URL: https://issues.jboss.org/browse/JBTM-2729 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie > Reporter: Amos Feng > Assignee: Amos Feng > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2730) Moving txn datastore to machine with different default encoding can cause in-doubt participants not being recovered

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2730?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2730: -------------------------------- Fix Version/s: 5.next > Moving txn datastore to machine with different default encoding can cause in-doubt participants not being recovered > ------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2730 > URL: https://issues.jboss.org/browse/JBTM-2730 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.3.3.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Fix For: 5.next > > > Narayana uses system default encoding when encode and decode data for object store. This could be a trouble if user uses non-ASCII characters for node identifier and object store is meanwhile moved between machines with different default encodings. > I've currently revealed two cases which could cause a trouble: > * node id set as {{...}} _(there is needed to use some characters which are encoded in UTF-8 as more bytes characters)_ will let container being started for encoding ISO-8859-1 and won't be started for encoding UTF-8. That's when configuration moved from ISO-8859-1 machine to UTF-8 machine when the another machine will be expected to finish recovery of some failed txn the second machine fails to start. (sure, workaround is to set jvm default encoding via parameter {{-Dfile.encoding}}) > * node id set to {{kulaťoučký}}, whole eap installation moved from one machine with ISO-8859-1 to machine with default encoding set to UTF-8. Txn object store is copied too for second machine finishing in-doubt transaction by recovery. The second machine won't finish transactions which depends on node identifer check (bottom-up recovery) as node id will be decoded differently than it was understood at the first machine. > This issue was found by using static code analysis and reacts to report message > {code} > 21994 Dm: Dubious method used In org.jboss.narayana.osgi.jta.internal.ObjStoreBrowserImpl.ObjStoreBrowserImpl (com.arjuna.ats.arjuna.tools.osb.mbean.ObjStoreBrowser): Found a call to a method which will perform a byte to String (or String to byte) conversion, and will assume that the default platform encoding is suitable) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2732) pre-release.sh does not allow tagging to proceed when error does not exist

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2732?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2732: ------------------------------------- The issue was in the script that we use for release. This is ancillary to the main project. > pre-release.sh does not allow tagging to proceed when error does not exist > -------------------------------------------------------------------------- > > Key: JBTM-2732 > URL: https://issues.jboss.org/browse/JBTM-2732 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.3.4.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2717) XAResourceRecoveryHelper removed in a wrong state

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2717?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2717: ------------------------------------- Also note that the test failed on slow (coverage) run > XAResourceRecoveryHelper removed in a wrong state > ------------------------------------------------- > > Key: JBTM-2717 > URL: https://issues.jboss.org/browse/JBTM-2717 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Priority: Minor > > {code} > Failed tests: > XARecoveryModuleHelpersUnitTest.testTimelyXAResourceRecoveryHelperRemoval1:55->testTimelyXAResourceRecoveryHelperRemoval:208 helper removed in wrong state expected:<2> but was:<0> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 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