[jbossts-issues] [JBoss JIRA] (JBTM-2713) Investigate why a null FileLock is declared but not used
Tom Jenkinson (JIRA)
issues at jboss.org
Fri Aug 26 05:57:00 EDT 2016
[ https://issues.jboss.org/browse/JBTM-2713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom Jenkinson updated JBTM-2713:
--------------------------------
Description:
It is not assigned but later on it is checked for null and if not then released:
https://github.com/jbosstm/narayana/blob/29270942f17cc553ad1497a41f60fce12e784fb6/ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/LogStore.java#L734
was:
It certainly isn't referenced:
https://github.com/jbosstm/narayana/blob/29270942f17cc553ad1497a41f60fce12e784fb6/ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/LogStore.java#L734
> 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 is not assigned but later on it is checked for null and if not then released:
> https://github.com/jbosstm/narayana/blob/29270942f17cc553ad1497a41f60fce12e784fb6/ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/LogStore.java#L734
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jbossts-issues
mailing list