Ticket #40 (closed defect: fixed)

Opened 19 months ago

Last modified 18 months ago

Over 30 possibilities for NPE's when Transaction/SubTransaction of Availability is null

Reported by: T.Doenz Owned by: M.Barisits
Priority: critical Milestone:
Component: CAPI3-Native Version: 2.0
Keywords: Cc:

Description

All over the native implementation of CAPI-3, EntryLockedExceptions are thrown when containers or entries are locked. Usually an instance of Availability is used to get the ID's of the Transaction and SubTransaction that holds the lock and pass them to the exception constructor. As the tx and stx field of Availability can be null, an NPE is thrown when the ID's are accessed like in the following typical example:

throw new EntryLockedException(availability.getTx().getId(), availability.getSubTx().getId());

Change History

comment:1 Changed 19 months ago by T.Doenz

see ticket #33 which describes several examples where such an NPE occurred

comment:2 Changed 18 months ago by T.Doenz

  • Status changed from new to closed
  • Resolution set to fixed

The bug included, in addition to EntryLockedException and Availability objects, also ContainerLockedExceptions and LockResult objects.

Note: See TracTickets for help on using tickets.