Bug 1252583

Summary: [GSS](6.4.z) Naming store is null before CDI lifecycle BeforeShutdown event fires
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Ger-Jan te Dorsthorst <gtedorst>
Component: CDI/WeldAssignee: Ryan Emerson <remerson>
Status: CLOSED CURRENTRELEASE QA Contact: Matej Novotny <manovotn>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.2.4CC: amelicha, bmaxwell, bspyrkos, cdewolf, gtedorst, jason.greene, jawilson, jharting, manovotn, maschmid, pmuir, remerson, rpelisse, sdouglas, vtunka
Target Milestone: CR1   
Target Release: EAP 6.4.5   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1235745, 1281618    

Description Ger-Jan te Dorsthorst 2015-08-11 19:34:19 UTC
Description of problem:

A CDI extension has a BeforeShutdown event handler that looks up the UserTransaction and performs a clean-up operation. If the application is undeployed, all works as expected, but EAP is shut down (gracefully), the lookup fails.

It looks like EAP is stopping the subsystems before firing the CDI event.

Version-Release number of selected component (if applicable):

6.2.4

How reproducible:

The issue is reproducible with the reproducer attached to Red Hat support case 01487736.

Steps to Reproduce:

Comment #16 in the associated support case.

Actual results:

Lookup fails in BeforeShutdown handler because NamingStore is null.

Expected results:

NamingStory should not be null.

Additional info:

Comment 1 Ger-Jan te Dorsthorst 2015-08-11 19:35:12 UTC
Possibly fixed upstream in https://issues.jboss.org/browse/WFLY-1886.

Comment 29 Matej Novotny 2015-11-05 07:20:26 UTC
Setting status to verified.
Reproduced with provided reproducer, then verified it's gone with 6.4.5.CP.CR1.

Comment 32 Petr Penicka 2017-01-17 11:42:39 UTC
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.

Comment 33 Petr Penicka 2017-01-17 11:42:59 UTC
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.