November 2014 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2284) XID.toString broken: indexing mistake in array

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2284?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2284: -------------------------------- Fix Version/s: 4.17.24 > XID.toString broken: indexing mistake in array > ---------------------------------------------- > > Key: JBTM-2284 > URL: https://issues.jboss.org/browse/JBTM-2284 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 4.17.15 > Environment: EAP 6.2.4 with JBoss JTS module in version 4.17.15 > Reporter: Christian von Kutzleben > Assignee: Tom Jenkinson > Fix For: 4.17.24 > > > com.arjuna.ats.internal.jta.xa.XID > > public String toString () > { > //... > stringBuilder.append(", "); > for (int i = 0; i < bqual_length; i++) { > stringBuilder.append(gtrid_length+data[i]); > } > //... > } > > correct: stringBuilder.append(data[i+gtrid_length]); > The result is, that the Xid instances logged in log files are corrupted and multiple different Xid share the same String representation, which makes the logging information unusable -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2284) XID.toString broken: indexing mistake in array

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2284?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2284: ------------------------------------- My apologies, it looks like we forgot to backport the fix for this useful bugfix. I have done that now. Fix on master: https://github.com/jbosstm/narayana/commit/6e8435a3175f6bc583b3af71c58def... Fix on 4.17: https://github.com/jbosstm/narayana/commit/23a72786efacd3ee0a5889c7f25f51... > XID.toString broken: indexing mistake in array > ---------------------------------------------- > > Key: JBTM-2284 > URL: https://issues.jboss.org/browse/JBTM-2284 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 4.17.15 > Environment: EAP 6.2.4 with JBoss JTS module in version 4.17.15 > Reporter: Christian von Kutzleben > Assignee: Tom Jenkinson > Fix For: 4.17.24 > > > com.arjuna.ats.internal.jta.xa.XID > > public String toString () > { > //... > stringBuilder.append(", "); > for (int i = 0; i < bqual_length; i++) { > stringBuilder.append(gtrid_length+data[i]); > } > //... > } > > correct: stringBuilder.append(data[i+gtrid_length]); > The result is, that the Xid instances logged in log files are corrupted and multiple different Xid share the same String representation, which makes the logging information unusable -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2284) XID.toString broken: indexing mistake in array

by Christian von Kutzleben (JIRA)

Christian von Kutzleben created JBTM-2284: --------------------------------------------- Summary: XID.toString broken: indexing mistake in array Key: JBTM-2284 URL: https://issues.jboss.org/browse/JBTM-2284 Project: JBoss Transaction Manager Issue Type: Bug Affects Versions: 4.17.15 Environment: EAP 6.2.4 with JBoss JTS module in version 4.17.15 Reporter: Christian von Kutzleben Assignee: Tom Jenkinson com.arjuna.ats.internal.jta.xa.XID public String toString () { //... stringBuilder.append(", "); for (int i = 0; i < bqual_length; i++) { stringBuilder.append(gtrid_length+data[i]); } //... } correct: stringBuilder.append(data[i+gtrid_length]); The result is, that the Xid instances logged in log files are corrupted and multiple different Xid share the same String representation, which makes the logging information unusable -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2277) GC Overhead issue when building WildFly Full Feature Pack

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2277?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2277: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > GC Overhead issue when building WildFly Full Feature Pack > --------------------------------------------------------- > > Key: JBTM-2277 > URL: https://issues.jboss.org/browse/JBTM-2277 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Blocker > Fix For: 5.0.4 > > > http://172.17.131.2/view/Status/job/narayana-AS800/628/ > {code} > [ERROR] GC overhead limit exceeded -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/OutOfMemoryError > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2279) Provide a way to allow overriding of a set CheckedActionFactory

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-2279?page=com.atlassian.jira.plugin.... ] Mark Little edited comment on JBTM-2279 at 11/11/14 8:14 AM: ------------------------------------------------------------- Wouldn't it have been easier/better/less invasive to have hidden this within a call to something like getCheckedActionFactory()? _checkedAction = _checkedActionFactory.getCheckedAction(get_uid(), type()); + _checkedAction = allowCheckedActionFactoryToBeOverriden ? arjPropertyManager + .getCoordinatorEnvironmentBean().getCheckedActionFactory() + .getCheckedAction(get_uid(), type()) + : defaultCheckedActionFactory.getCheckedAction(get_uid(), + type()); was (Author: marklittle): Wouldn't it have been easier/better/less invasive to have hidden this within the call to getCheckedAction? _checkedAction = _checkedActionFactory.getCheckedAction(get_uid(), type()); + _checkedAction = allowCheckedActionFactoryToBeOverriden ? arjPropertyManager + .getCoordinatorEnvironmentBean().getCheckedActionFactory() + .getCheckedAction(get_uid(), type()) + : defaultCheckedActionFactory.getCheckedAction(get_uid(), + type()); > Provide a way to allow overriding of a set CheckedActionFactory > --------------------------------------------------------------- > > Key: JBTM-2279 > URL: https://issues.jboss.org/browse/JBTM-2279 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.4 > > > Out of the box the BasicAction caches the reference to the checkedactionfactory and so if a users classpath is not available to narayana there is no way for a user to provide a CAF to Narayana. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2279) Provide a way to allow overriding of a set CheckedActionFactory

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-2279?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-2279: ----------------------------------- Wouldn't it have been easier/better/less invasive to have hidden this within the call to getCheckedAction? _checkedAction = _checkedActionFactory.getCheckedAction(get_uid(), type()); + _checkedAction = allowCheckedActionFactoryToBeOverriden ? arjPropertyManager + .getCoordinatorEnvironmentBean().getCheckedActionFactory() + .getCheckedAction(get_uid(), type()) + : defaultCheckedActionFactory.getCheckedAction(get_uid(), + type()); > Provide a way to allow overriding of a set CheckedActionFactory > --------------------------------------------------------------- > > Key: JBTM-2279 > URL: https://issues.jboss.org/browse/JBTM-2279 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.4 > > > Out of the box the BasicAction caches the reference to the checkedactionfactory and so if a users classpath is not available to narayana there is no way for a user to provide a CAF to Narayana. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2279) Provide a way to allow overriding of a set CheckedActionFactory

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2279?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2279: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Provide a way to allow overriding of a set CheckedActionFactory > --------------------------------------------------------------- > > Key: JBTM-2279 > URL: https://issues.jboss.org/browse/JBTM-2279 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.4 > > > Out of the box the BasicAction caches the reference to the checkedactionfactory and so if a users classpath is not available to narayana there is no way for a user to provide a CAF to Narayana. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2277) GC Overhead issue when building WildFly Full Feature Pack

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2277?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2277: ----------------------------------- Git Pull Request: https://github.com/jbosstm/jboss-as/pull/35, https://github.com/jbosstm/narayana/pull/760 (was: https://github.com/jbosstm/jboss-as/pull/35) > GC Overhead issue when building WildFly Full Feature Pack > --------------------------------------------------------- > > Key: JBTM-2277 > URL: https://issues.jboss.org/browse/JBTM-2277 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Blocker > Fix For: 5.0.4 > > > http://172.17.131.2/view/Status/job/narayana-AS800/628/ > {code} > [ERROR] GC overhead limit exceeded -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/OutOfMemoryError > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2277) GC Overhead issue when building WildFly Full Feature Pack

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2277?page=com.atlassian.jira.plugin.... ] Michael Musgrove reassigned JBTM-2277: -------------------------------------- Assignee: Michael Musgrove (was: Tom Jenkinson) > GC Overhead issue when building WildFly Full Feature Pack > --------------------------------------------------------- > > Key: JBTM-2277 > URL: https://issues.jboss.org/browse/JBTM-2277 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Blocker > Fix For: 5.0.4 > > > http://172.17.131.2/view/Status/job/narayana-AS800/628/ > {code} > [ERROR] GC overhead limit exceeded -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/OutOfMemoryError > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2277) GC Overhead issue when building WildFly Full Feature Pack

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2277?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-2277: ---------------------------------------- The oracle tuning guide (http://www.oracle.com/technetwork/java/javase/gc-tuning-6-140523.html) says: {quote} The parallel collector will throw an OutOfMemoryError if too much time is being spent in garbage collection: if more than 98% of the total time is spent in garbage collection and less than 2% of the heap is recovered, an OutOfMemoryError will be thrown {/quote} and then goes on to discuss the parallel garbage collector. Adding the following setting to the build resolves the issue: MAVEN_OPTS="-XX:+UseConcMarkSweepGC" > GC Overhead issue when building WildFly Full Feature Pack > --------------------------------------------------------- > > Key: JBTM-2277 > URL: https://issues.jboss.org/browse/JBTM-2277 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Blocker > Fix For: 5.0.4 > > > http://172.17.131.2/view/Status/job/narayana-AS800/628/ > {code} > [ERROR] GC overhead limit exceeded -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/OutOfMemoryError > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues November 2014