Bug #173 (closed)
Stateful session beans are throwing exceptions on passivation.
Reported by: | jamoore | Owned by: | jamoore |
---|---|---|---|
Priority: | minor | Cc: | ejb3 |
Sprint: | n.a. | ||
Total Remaining Time: | n.a. |
Description
The presence of non-transient / non-null fields in the RenderingBean causes passivation errors.
Change History (3)
comment:1 Changed 18 years ago by jmoore
- Status changed from new to assigned
comment:2 Changed 18 years ago by jmoore
- Resolution set to fixed
- Status changed from assigned to closed
r731 cleans up all bean fields. No passivation errors should occur.
comment:3 Changed 18 years ago by jmoore
Looks like the same chapter of the spec also suggests not relying on transient. In @PrePassivate? we should set to null.
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
4.2.1 of the ejbcore spec details what values are allowed for a non-transient field on passiviation. A simplified list includes:
Care must be taken in the @PrePassivate method to guarantee one of these values.