[ http://issues.apache.org/jira/browse/DERBY-757?page=all ]
Mike Matrigali resolved DERBY-757:
----------------------------------
Fix Version: 10.2.0.0
10.1.2.2
Resolution: Fixed
svn 371085 is the merge of the fix from trunk to 10.1.
> java.lang.NullPointerException can occur while scanning for global id in
> the transaction table under heavey load.
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-757
> URL: http://issues.apache.org/jira/browse/DERBY-757
> Project: Derby
> Type: Bug
> Components: Store
> Versions: 10.2.0.0, 10.1.3.0, 10.1.2.2, 10.0.2.2
> Reporter: Suresh Thalamati
> Assignee: Mike Matrigali
> Fix For: 10.2.0.0, 10.1.2.2
>
> TransactonTable.java:
> public ContextManager findTransactionContextByGlobalId(
> ....
> if (entry.getGid() != null &&
> entry.getGid().equals(global_id))
> ---
> }
> In the above code gid in the entry can get set to null , if the
> transaction the entry referes to is committed.
> So second part of the above condition can get a NPE.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
