Hide Forgot
project_key: SOA Running the business_rules_service quickstart raises this exception: 2011-07-27 14:29:33,231 WARN [org.jboss.detailed.classloader.ClassLoaderManager] (pool-38-thread-1) Unexpected error during load of:org.drools.spi.CompiledInvoker java.lang.SecurityException: class "org.drools.spi.CompiledInvoker"'s signer information does not match signer information of other classes in the same package
Affects Testing: Added: [Blocks Testing] Blocked Tests: Added: Rules based services
Attachment: Added: server.log
Assigning to David to incorporate review comments.
Release Notes Docs Status: Added: Not Required Writer: Added: dlesage
This is still an issue with my ER2 builds.
The issue occurs when the org.drools.util.CompositeClassLoader first attempts to load a class from the 'org.drools.spi' package as it results in the attempt being made without any signing information. Previous classes within that package have been loaded through the normal classloader mechanism and have the correct signer information attached. Still investigating.
It looks like this is a bug in the CertificateReaderInputStream, inherited from EAP. Drools seems to be triggering this issue through their EclipseJavaCompiler class. I think I have enough information to create a test case, will handle this tomorrow.
Raised JBVFS-176 to cover this issue. I have compiled my suggested fix and installed it into SOA, this addresses the drools classloading issue.
Link: Added: This issue depends JBPAPP-6983
Link: Added: This issue is a dependency of SOA-3258
Patch jar integrated into SOA-P for ER2.
Verified fixed in the ER3 build.