Bug 779241 (SOA-1634)

Summary: spring_aop QS does not work with signed JARs
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Jiri Pechanec <jpechane>
Component: ExamplesAssignee: Kevin Conner <kevin.conner>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.0.2, 5.0.0 ER4   
Target Milestone: ---   
Target Release: FUTURE   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-1634
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-08 20:02:17 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:

Description Jiri Pechanec 2009-11-23 06:44:10 UTC 
Affects: Release Notes
Date of First Response: 2009-11-23 05:41:25
project_key: SOA

An exception is thrown during deployment

07:42:18,930 WARN  [HDScanner] Failed to process changes
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

DEPLOYMENTS IN ERROR:
  Deployment "jboss.esb.vfszip:/home/jpechane/releases/50ER4AS/jboss-as/server/default/deploy/Quickstart_spring_aop.esb/" is in error due to the following reason(s): java.lang.SecurityException: class "org.jboss.soa.esb.samples.quickstart.spring_aop.SaySomething$$EnhancerByCGLIB$$a0e8df19"'s signer information does not match signer information of other classes in the same package

	at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:994)
	at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:940)
	at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:873)
	at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128)
	at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:378)
	at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:256)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
	at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:619)
Comment 1 Kevin Conner 2009-11-23 10:41:25 UTC 
Jirka, can you add more details about what you have done here?
Comment 2 Jiri Pechanec 2009-11-23 11:11:36 UTC 
Just run ant deploy for spring_aop QS
Comment 3 Kevin Conner 2009-12-07 11:09:17 UTC 
Link: Added: This issue depends JBESB-3038
Comment 4 Kevin Conner 2010-01-19 13:10:54 UTC 
The only way around this appears to be replacing the cglib jars with the unsigned versions, it does not look like cglib functions correctly when signed.

This also appears to be an issue for the EAP platform, see Tom's comments in the ESB issue.
Comment 5 tcunning 2010-01-19 13:32:06 UTC 
Link: Added: This issue depends JBPAPP-3000
Comment 6 Anne-Louise Tangring 2010-01-22 17:57:09 UTC 
Affects: Added: [Release Notes]
Comment 7 David Le Sage 2010-02-10 03:30:52 UTC 
I have documented this issue for the Release Notes.  Here is the draft text:


https://jira.jboss.org/jira/browse/SOA-1634

    Currently, the spring_aop quick start does not work with signed
    JARs. If you try to run ant deploy for this quick start, an
    org.jboss.deployers.client.spi.IncompleteDeploymentException will be thrown.

    To work around this issue, replace the cglib JARs with unsigned versions.