Bug #1013 (closed)
Opened 11 years ago
Closed 11 years ago
StatefulService.close() can still throw an exception
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | minor | Cc: | |
| Sprint: | n.a. | ||
| Total Remaining Time: | n.a. |
Description
See ticket:883.
It's unclear under what circumstances, but the Hibernate session exception thrown still appears. It is harmless, in that the close() method performs no actions and so the action need not be active, but regardless, the exception should not be thrown.
Change History (2)
comment:1 Changed 11 years ago by jmoore
comment:2 Changed 11 years ago by jmoore
- Resolution set to fixed
- Status changed from new to closed
Closing. No further issues seen during testing.
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
r2677 finally has a solution for this which seems to work. This allows the transaction handler time to commit the transaction before disconnecting from and closing the hibernate session. Since no logic is currently supported in our StatefulServiceInterface.close() methods, this should be fine.