Bug 1281537

Summary:	[GSS](6.4.z) PersistenceRefProcessor.getPersistenceUnitBindingSource can throw NullPointerException
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Mike <mike>
Component:	JPA	Assignee:	jboss-set
Status:	CLOSED CURRENTRELEASE	QA Contact:	Martin Simka <msimka>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.4.4	CC:	bmaxwell, dereed, dtikhomi, jbilek, jtruhlar, msochure, scott.marlow, smarlow, vtunka
Target Milestone:	CR1
Target Release:	EAP 6.4.11
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-01-17 13:13:23 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:
Bug Depends On:
Bug Blocks:	1361648

Description Mike 2015-11-12 17:09:18 UTC

In PersistenceRefProcessor the getPersistenceUnitBindingSource method calls PersistenceUnitSearch.resolvePersistenceUnitSupplier to retrieve a  PersistenceUnitMetadata object. It then without checking for null, dereferences that object to get the scoped persistent unit name.

However, resolvePersistenceUnitSupplier through its call to findPersistenceUnitSupplier can return a null value.

When this happens NullPointerException is thrown rather than DeploymentUnitProcessingException as would be expected.

Comment 1 Scott Marlow 2015-11-12 18:17:52 UTC

This is fixed upstream at https://github.com/wildfly/wildfly/blob/master/jpa/subsystem/src/main/java/org/jboss/as/jpa/processor/PersistenceRefProcessor.java#L211 (also see WFLY-1994).

Comment 5 Mike McCune 2016-03-28 22:32:18 UTC

This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 7 Jiří Bílek 2016-10-07 11:00:05 UTC

Verified with EAP 6.4.11.CP.CR1

Comment 8 Petr Penicka 2017-01-17 13:13:23 UTC

Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.

Comment 9 Petr Penicka 2017-01-17 13:15:10 UTC

Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.