Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1098072

Summary:	[GSS](one-off) EAP 6.2.2. apply WELD-1550 to weld-core-1.1.17.Final-redhat-1.jar - Interceptor creation fails
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Shaun Appleton <sappleto>
Component:	CDI/Weld	Assignee:	Martin Kouba <mkouba>
Status:	CLOSED NOTABUG	QA Contact:	Ron Šmeral <rsmeral>
Severity:	unspecified	Docs Contact:	Russell Dickenson <rdickens>
Priority:	unspecified
Version:	6.2.2	CC:	amelicha, jharting, pmuir
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://c.na7.visual.force.com/apex/Case_View?id=500A000000J6sK4
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-06-19 09:01:18 UTC	Type:	Support Patch
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Shaun Appleton 2014-05-15 08:28:24 UTC

Description of problem:
Customer cannot deploy services on 6.2.0 or 6.2.2.
Whereas the same ear gets deployed without any problem in EAP 6.1.1

It throws the following exception and deployment fails


12:48:31,661 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."sample-ear-1.0.1-SNAPSHOT.ear".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."sample-ear-1.0.1-SNAPSHOT.ear".WeldStartService: Failed to start service
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_04]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_04]
	at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_04]
Caused by: org.jboss.weld.exceptions.DeploymentException: Exception List with 1 exceptions:
Exception 0 :
org.jboss.weld.exceptions.WeldException: WELD-000830 Unable to load the cache value for the key Extension [class com.sample.extension.SampleExtension] with qualifiers [@Default]; sample-ear-1.0.1-SNAPSHOT.ear
	at org.jboss.weld.util.cache.LoadingCacheUtils.getCacheValue(LoadingCacheUtils.java:73)
	at org.jboss.weld.util.cache.LoadingCacheUtils.getCastCacheValue(LoadingCacheUtils.java:112)
	at org.jboss.weld.util.cache.LoadingCacheUtils.getCastCacheValue(LoadingCacheUtils.java:93)
	at org.jboss.weld.bean.proxy.ClientProxyProvider.getClientProxy(ClientProxyProvider.java:102)
	at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:607)
	at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:232)
	at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:213)
	at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:75)
	at org.jboss.weld.bootstrap.events.AbstractDeploymentContainerEvent.fire(AbstractDeploymentContainerEvent.java:46)
	at org.jboss.weld.bootstrap.events.AfterDeploymentValidationImpl.fire(AfterDeploymentValidationImpl.java:31)
	at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:382)
	at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:64)
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
	at java.lang.Thread.run(Thread.java:722)
Caused by: com.google.common.util.concurrent.UncheckedExecutionException: org.jboss.weld.exceptions.WeldException: by java.lang.IllegalAccessError: class com.sample.extension.SampleExtension$Proxy$_$$_WeldClientProxy cannot access its superinterface com.sample.SuperInterface



This has been reproduced by support and suspect it is due to https://issues.jboss.org/browse/WELD-1550

Comment 1 Shaun Appleton 2014-05-15 13:36:07 UTC

there is a commit for this at https://github.com/mkouba/core/commit/171ff573952fa51da35ff9968f4d3fa537719afd

Comment 2 Shaun Appleton 2014-05-21 11:28:25 UTC

This did not resolve the issue.

Comment 3 Shaun Appleton 2014-06-19 09:01:18 UTC

closing as this does not fix the issue