Bug 1253597

Summary:	[GSS](6.4.x) Exceptions of lifecycle methods for session beans are suppresses without any message
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	wfink
Component:	CDI/Weld, EJB	Assignee:	wfink
Status:	CLOSED DUPLICATE	QA Contact:	Matous Jobanek <mjobanek>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.2.0	CC:	jharting, maschmid, pmuir, rsmeral, sdouglas
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-14 08:34:59 UTC	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:

Description wfink 2015-08-14 08:23:58 UTC

Description of problem:
If a lifecycle method of EJB's throw an Exception it is expected that this will be logged and the invocation fail.
This works correct if there is no CDI involved in this deployment.
If a beans.xml is added the Exception is swallowed and the instance might work not correct.



How reproducible:
----- Class ----
@Singleton
@Startup
public class StartupSingletonBean {
  private static final Logger log = Logger.getLogger(StartupSingletonBean.class);

  @PostConstruct
  private void postConstruct() {
    log.info("StartupSingleton is started. Resource 'myString' is '" + myString + "'");
    throw new RuntimeException("THIS IS A TEST");
  }
}



Steps to Reproduce:
1. If the application does not contain a beans.xml the Exception is logged and the Bean is not created.
2. If the application contains a beans.xml the weld deployment is activated and the Exception is swallowed.

Comment 1 wfink 2015-08-14 08:34:59 UTC


*** This bug has been marked as a duplicate of bug 1207240 ***