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

Tom Jenkinson (JIRA) jira-events at lists.jboss.org
Thu Sep 19 10:20:03 EDT 2013

    [ https://issues.jboss.org/browse/JBTM-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805830#comment-12805830 ] 

Tom Jenkinson commented on JBTM-1036:

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)
removed null check as action cannot be null

com.arjuna.ats.jts.extensions.AtomicTransaction Line 617
Possible null pointer dereference of AtomicTransaction._theAction in com.arjuna.ats.jts.extensions.AtomicTransaction.equals(Object)
There was an assumption that both ControlWrappers are null or neither, although the statemachine today guarantees that it is possible that in the future the code may use the .equals in an unpredicted manner.
> 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) 
>          Components: JTA, JTS, Transaction Core
>            Reporter: Amos Feng
>            Assignee: Tom Jenkinson
>            Priority: Minor
>             Fix For: 5.0.0.M5
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
> 1.ArjunaJTA/jdbc
> Possible null pointer dereference of conn in com.arjuna.ats.internal.jdbc.recovery.BasicXARecovery.getXAResource() Line 169
> 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)

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

More information about the jbossts-issues mailing list