[GLASSFISH-20437] SFSB PreDestroy never commits during undeploy Created: 30/Apr/13  Updated: 20/Dec/16  Resolved: 30/Apr/13

Status: Resolved
Project: glassfish
Component/s: ejb_container
Affects Version/s: 4.0_dev
Fix Version/s: 4.0_dev

Type: Bug Priority: Critical
Reporter: marina vatkina Assignee: marina vatkina
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: 4_0-approved


SFSB container calls PreDestroy during undeploy, but ContainerSynchronization prevents transaction completion.

  • What is the impact on the customer of the bug?
    PreDestroy behavior is not as described in the EJB spec
  • How likely is it that a customer will see the bug and how serious is the bug?
    If the code expects to flush data to the database, the data will be lost
  • Is it a regression?
    It's a missing part in the new functionality
  • Does it meet other bug fix criteria (security, performance, etc.)?
  • What CTS failures are caused by this bug?
  • What is the cost/risk of fixing the bug?
  • How risky is the fix? How much work is the fix? Is the fix complicated?
  • Is there an impact on documentation or message strings?
  • Which tests should QA (re)run to verify the fix did not destabilize GlassFish?
  • Which is the targeted build of 4.0 for this fix?
  • If this an integration of a new version of a component from another project,
    what are the changes that are being brought in? This might be list of
    Jira issues from that project or a list of revision messages.

Comment by marina vatkina [ 30/Apr/13 ]

Fixed by accounting for SFSB PreDestroy called in a transaction.
Sending src/main/java/com/sun/ejb/containers/ContainerSynchronization.java
Transmitting file data .
Committed revision 61740.

Generated at Thu Apr 27 14:02:59 UTC 2017 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.