December 2012 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1037) RCN: Nullcheck of value previously dereferenced (RCN_REDUNDANT_NULLCHECK_WOULD_HAVE_BEEN_A_NPE)

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1037?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1037: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/171 > RCN: Nullcheck of value previously dereferenced (RCN_REDUNDANT_NULLCHECK_WOULD_HAVE_BEEN_A_NPE) > ----------------------------------------------------------------------------------------------- > > Key: JBTM-1037 > URL: https://issues.jboss.org/browse/JBTM-1037 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Amos Feng > Assignee: Tom Jenkinson > Fix For: 5.0.0.M2 > > > 1.ArjunaCore/txoj > com.arjuna.ats.internal.txoj.abstractrecords.CadaverLockRecord Line 68 > Nullcheck of lm at line 79 of value previously dereferenced in new com.arjuna.ats.internal.txoj.abstractrecords.CadaverLockRecord(LockStore, LockManager, BasicAction) -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1044) ML: Synchronization on field in futile attempt to guard that field (ML_SYNC_ON_FIELD_TO_GUARD_CHANGING_THAT_FIELD)

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1044?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-1044. --------------------------------- Resolution: Rejected Looking at the code, we are using _theStatus to guard on _theAction. I can see that _theStatus changes in this block but I think it is safe as we are guarding _theAction rather than _theStatus > ML: Synchronization on field in futile attempt to guard that field (ML_SYNC_ON_FIELD_TO_GUARD_CHANGING_THAT_FIELD) > ------------------------------------------------------------------------------------------------------------------ > > Key: JBTM-1044 > URL: https://issues.jboss.org/browse/JBTM-1044 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Amos Feng > Assignee: Tom Jenkinson > > 1.ArjunaJTS/jts > com.arjuna.ats.jts.extensions.AtomicTransaction Line 667 > Synchronization on AtomicTransaction._theStatus in futile attempt to guard it -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1036) NP: Possible null pointer dereference (NP_NULL_ON_SOME_PATH)

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1036?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1036: -------------------------------- Fix Version/s: 5.0.0.Final > NP: Possible null pointer dereference (NP_NULL_ON_SOME_PATH) > ------------------------------------------------------------ > > Key: JBTM-1036 > URL: https://issues.jboss.org/browse/JBTM-1036 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Amos Feng > Assignee: Tom Jenkinson > Fix For: 5.0.0.Final > > > 1.ArjunaJTA/jdbc > Possible null pointer dereference of conn in com.arjuna.ats.internal.jdbc.recovery.BasicXARecovery.getXAResource() Line 169 > 2.ArjunaCore/arjuna > com.arjuna.ats.arjuna.StateManager Line 1234 > Possible null pointer dereference of action in com.arjuna.ats.arjuna.StateManager.forgetAction(BasicAction, boolean, int) > 3.ArjunaCore/arjuna > com.arjuna.ats.internal.arjuna.objectstore.HashedStore Line 131 > Possible null pointer dereference of aUid in com.arjuna.ats.internal.arjuna.objectstore.HashedStore.allObjUids(String, InputObjectState, int) > 4.ArjunaJTS/jtax > com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.coordinator.ServerTransaction Line 108 > Possible null pointer dereference of ServerTransaction._theXid in com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.coordinator.ServerTransaction.save_state(OutputObjectState, int) > 5.ArjunaJTS/jts > com.arjuna.ats.internal.jts.context.ContextManager Line 553 > Possible null pointer dereference of action in com.arjuna.ats.internal.jts.context.ContextManager.pushAction(ControlWrapper) > 6.ArjunaJTS/jts > com.arjuna.ats.jts.extensions.AtomicTransaction Line 617 > Possible null pointer dereference of AtomicTransaction._theAction in com.arjuna.ats.jts.extensions.AtomicTransaction.equals(Object) -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1043) IL: An apparent infinite loop (IL_INFINITE_LOOP)

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1043?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-1043. --------------------------------- Resolution: Rejected Haven't evaluated the code it appears this check although it could be written differently would not be able to result in an infinite loop (even if FindBugs thinks it would) > IL: An apparent infinite loop (IL_INFINITE_LOOP) > ------------------------------------------------ > > Key: JBTM-1043 > URL: https://issues.jboss.org/browse/JBTM-1043 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Amos Feng > Assignee: Tom Jenkinson > > 1.ArjunaJTS/jts > com.arjuna.ats.internal.jts.context.ContextManager Line 291 > There is an apparent infinite loop in com.arjuna.ats.internal.jts.context.ContextManager.purgeActions(String) -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1040) IL: An apparent infinite recursive loop (IL_INFINITE_RECURSIVE_LOOP)

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1040?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1040: -------------------------------- Description: 1.XTS/WSAS com.arjuna.mw.wsas.completionstatus.Unknown Line 52 There is an apparent infinite recursive loop in com.arjuna.mw.wsas.completionstatus.Unknown.equals(Object) was: 1.XTS/WSAS com.arjuna.mw.wsas.completionstatus.Unknown Line 52 There is an apparent infinite recursive loop in com.arjuna.mw.wsas.completionstatus.Unknown.equals(Object) 2.ArjunaJTS/orbportability com.arjuna.orbportability.common.ant.IDLCompiler Line 376 There is an apparent infinite recursive loop in com.arjuna.orbportability.common.ant.IDLCompiler.processIDL(IDLCompiler$IDLCompilerDetails, String, String, String) > IL: An apparent infinite recursive loop (IL_INFINITE_RECURSIVE_LOOP) > -------------------------------------------------------------------- > > Key: JBTM-1040 > URL: https://issues.jboss.org/browse/JBTM-1040 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Amos Feng > Assignee: Tom Jenkinson > > 1.XTS/WSAS > com.arjuna.mw.wsas.completionstatus.Unknown Line 52 > There is an apparent infinite recursive loop in com.arjuna.mw.wsas.completionstatus.Unknown.equals(Object) -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1040) IL: An apparent infinite recursive loop (IL_INFINITE_RECURSIVE_LOOP)

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1040?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1040: -------------------------------- Assignee: Paul Robinson (was: Tom Jenkinson) > IL: An apparent infinite recursive loop (IL_INFINITE_RECURSIVE_LOOP) > -------------------------------------------------------------------- > > Key: JBTM-1040 > URL: https://issues.jboss.org/browse/JBTM-1040 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Amos Feng > Assignee: Paul Robinson > > 1.XTS/WSAS > com.arjuna.mw.wsas.completionstatus.Unknown Line 52 > There is an apparent infinite recursive loop in com.arjuna.mw.wsas.completionstatus.Unknown.equals(Object) -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1040) IL: An apparent infinite recursive loop (IL_INFINITE_RECURSIVE_LOOP)

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1040?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1040: ------------------------------------- Fixed: 2.ArjunaJTS/orbportability com.arjuna.orbportability.common.ant.IDLCompiler Line 376 There is an apparent infinite recursive loop in com.arjuna.orbportability.common.ant.IDLCompiler.processIDL(IDLCompiler$IDLCompilerDetails, String, String, String) > IL: An apparent infinite recursive loop (IL_INFINITE_RECURSIVE_LOOP) > -------------------------------------------------------------------- > > Key: JBTM-1040 > URL: https://issues.jboss.org/browse/JBTM-1040 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Amos Feng > Assignee: Tom Jenkinson > > 1.XTS/WSAS > com.arjuna.mw.wsas.completionstatus.Unknown Line 52 > There is an apparent infinite recursive loop in com.arjuna.mw.wsas.completionstatus.Unknown.equals(Object) -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1386) ATBridgeTest hangs during Deployment

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1386?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1386: -------------------------------- Environment: Job 124: Linux tenafly.buildnet.ncl.jboss.com 2.6.32-279.14.1.el6.i686 #1 SMP Tue Nov 6 21:05:14 UTC 2012 i686 i686 i386 GNU/Linux CentOS release 6.3 (Final) java version "1.6.0_37" Java(TM) SE Runtime Environment (build 1.6.0_37-b06) Java HotSpot(TM) Client VM (build 20.12-b01, mixed mode, sharing) AS7 master on 10/12/2012 was: Job 124: Linux tenafly.buildnet.ncl.jboss.com 2.6.32-279.14.1.el6.i686 #1 SMP Tue Nov 6 21:05:14 UTC 2012 i686 i686 i386 GNU/Linux CentOS release 6.3 (Final) java version "1.6.0_37" Java(TM) SE Runtime Environment (build 1.6.0_37-b06) Java HotSpot(TM) Client VM (build 20.12-b01, mixed mode, sharing) > ATBridgeTest hangs during Deployment > ------------------------------------ > > Key: JBTM-1386 > URL: https://issues.jboss.org/browse/JBTM-1386 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Testing, TXFramework > Environment: Job 124: > Linux tenafly.buildnet.ncl.jboss.com 2.6.32-279.14.1.el6.i686 #1 SMP Tue Nov 6 21:05:14 UTC 2012 i686 i686 i386 GNU/Linux > CentOS release 6.3 (Final) > java version "1.6.0_37" > Java(TM) SE Runtime Environment (build 1.6.0_37-b06) > Java HotSpot(TM) Client VM (build 20.12-b01, mixed mode, sharing) > AS7 master on 10/12/2012 > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M2 > > Attachments: jboss.stacktrace, org.jboss.narayana.txframework.functional.ATBridgeTest-output.txt > > > http://172.17.131.2/job/jbossts-narayana-java6/121/ > http://172.17.131.2/job/jbossts-narayana-java6/124/ > Notice the following in the stack dump which looks very similar to [AS7-5946]: > {code} > "management-handler-thread - 3" prio=10 tid=0xa0661800 nid=0x282b in Object.wait() [0x9c669000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0xa626ae88> (a org.jboss.as.controller.ContainerStateMonitor) > at java.lang.Object.wait(Object.java:485) > at org.jboss.as.controller.ContainerStateMonitor.awaitContainerStateChangeReport(ContainerStateMonitor.java:158) > - locked <0xa626ae88> (a org.jboss.as.controller.ContainerStateMonitor) > at org.jboss.as.controller.ModelControllerImpl.awaitContainerStateChangeReport(ModelControllerImpl.java:452) > at org.jboss.as.controller.OperationContextImpl.awaitModelControllerContainerMonitor(OperationContextImpl.java:147) > {code} > Also, notice the last line of the server log: > {code} > [0m[0m16:08:52,111 INFO [org.jboss.as.arquillian] (MSC service thread 1-1) Arquillian deployment detected: ArquillianConfig[service=jboss.arquillian.config."test.jar",unit=test.jar,tests=[org.jboss.narayana.txframework.functional.ATStatefullTest, org.jboss.narayana.txframework.functional.ATBridgeTest, org.jboss.narayana.txframework.functional.rest.at.simpleEJB > {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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1386) ATBridgeTest hangs during Deployment

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1386?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1386: -------------------------------- Description: http://172.17.131.2/job/jbossts-narayana-java6/121/ http://172.17.131.2/job/jbossts-narayana-java6/124/ Notice the following in the stack dump which looks very similar to [AS7-5946]: {code} "management-handler-thread - 3" prio=10 tid=0xa0661800 nid=0x282b in Object.wait() [0x9c669000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0xa626ae88> (a org.jboss.as.controller.ContainerStateMonitor) at java.lang.Object.wait(Object.java:485) at org.jboss.as.controller.ContainerStateMonitor.awaitContainerStateChangeReport(ContainerStateMonitor.java:158) - locked <0xa626ae88> (a org.jboss.as.controller.ContainerStateMonitor) at org.jboss.as.controller.ModelControllerImpl.awaitContainerStateChangeReport(ModelControllerImpl.java:452) at org.jboss.as.controller.OperationContextImpl.awaitModelControllerContainerMonitor(OperationContextImpl.java:147) {code} Also, notice the last line of the server log: {code} [0m[0m16:08:52,111 INFO [org.jboss.as.arquillian] (MSC service thread 1-1) Arquillian deployment detected: ArquillianConfig[service=jboss.arquillian.config."test.jar",unit=test.jar,tests=[org.jboss.narayana.txframework.functional.ATStatefullTest, org.jboss.narayana.txframework.functional.ATBridgeTest, org.jboss.narayana.txframework.functional.rest.at.simpleEJB {code} was: http://172.17.131.2/job/jbossts-narayana-java6/121/ http://172.17.131.2/job/jbossts-narayana-java6/124/ > ATBridgeTest hangs during Deployment > ------------------------------------ > > Key: JBTM-1386 > URL: https://issues.jboss.org/browse/JBTM-1386 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Testing, TXFramework > Environment: Job 124: > Linux tenafly.buildnet.ncl.jboss.com 2.6.32-279.14.1.el6.i686 #1 SMP Tue Nov 6 21:05:14 UTC 2012 i686 i686 i386 GNU/Linux > CentOS release 6.3 (Final) > java version "1.6.0_37" > Java(TM) SE Runtime Environment (build 1.6.0_37-b06) > Java HotSpot(TM) Client VM (build 20.12-b01, mixed mode, sharing) > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M2 > > Attachments: jboss.stacktrace, org.jboss.narayana.txframework.functional.ATBridgeTest-output.txt > > > http://172.17.131.2/job/jbossts-narayana-java6/121/ > http://172.17.131.2/job/jbossts-narayana-java6/124/ > Notice the following in the stack dump which looks very similar to [AS7-5946]: > {code} > "management-handler-thread - 3" prio=10 tid=0xa0661800 nid=0x282b in Object.wait() [0x9c669000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0xa626ae88> (a org.jboss.as.controller.ContainerStateMonitor) > at java.lang.Object.wait(Object.java:485) > at org.jboss.as.controller.ContainerStateMonitor.awaitContainerStateChangeReport(ContainerStateMonitor.java:158) > - locked <0xa626ae88> (a org.jboss.as.controller.ContainerStateMonitor) > at org.jboss.as.controller.ModelControllerImpl.awaitContainerStateChangeReport(ModelControllerImpl.java:452) > at org.jboss.as.controller.OperationContextImpl.awaitModelControllerContainerMonitor(OperationContextImpl.java:147) > {code} > Also, notice the last line of the server log: > {code} > [0m[0m16:08:52,111 INFO [org.jboss.as.arquillian] (MSC service thread 1-1) Arquillian deployment detected: ArquillianConfig[service=jboss.arquillian.config."test.jar",unit=test.jar,tests=[org.jboss.narayana.txframework.functional.ATStatefullTest, org.jboss.narayana.txframework.functional.ATBridgeTest, org.jboss.narayana.txframework.functional.rest.at.simpleEJB > {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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1386) ATBridgeTest hangs during Deployment

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1386?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1386: -------------------------------- Environment: Job 124: Linux tenafly.buildnet.ncl.jboss.com 2.6.32-279.14.1.el6.i686 #1 SMP Tue Nov 6 21:05:14 UTC 2012 i686 i686 i386 GNU/Linux CentOS release 6.3 (Final) java version "1.6.0_37" Java(TM) SE Runtime Environment (build 1.6.0_37-b06) Java HotSpot(TM) Client VM (build 20.12-b01, mixed mode, sharing) > ATBridgeTest hangs during Deployment > ------------------------------------ > > Key: JBTM-1386 > URL: https://issues.jboss.org/browse/JBTM-1386 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Testing, TXFramework > Environment: Job 124: > Linux tenafly.buildnet.ncl.jboss.com 2.6.32-279.14.1.el6.i686 #1 SMP Tue Nov 6 21:05:14 UTC 2012 i686 i686 i386 GNU/Linux > CentOS release 6.3 (Final) > java version "1.6.0_37" > Java(TM) SE Runtime Environment (build 1.6.0_37-b06) > Java HotSpot(TM) Client VM (build 20.12-b01, mixed mode, sharing) > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M2 > > Attachments: jboss.stacktrace, org.jboss.narayana.txframework.functional.ATBridgeTest-output.txt > > > http://172.17.131.2/job/jbossts-narayana-java6/121/ > http://172.17.131.2/job/jbossts-narayana-java6/124/ -- 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

11 years, 11 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 December 2012