Jaroslav Pullmann created JBRULES-3680: ------------------------------------------ Summary: OSGI Drools initialization failure: ExecutorProviderImpl not found Key: JBRULES-3680 URL: https://issues.jboss.org/browse/JBRULES-3680 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-api, drools-core Affects Versions: 5.5.0.CR1, 5.4.0.Final Environment: Linux, Java SE 6., Apache Felix 4 Reporter: Jaroslav Pullmann Assignee: Mark Proctor Drools can't resolve implementation of org.drools.concurrent.ExecutorProvider interface as part of its initialization within an OSGi runtime. The error has been already reported along with full stack trace here: http://lists.jboss.org/pipermail/rules-users/2012-May/026839.html https://community.jboss.org/message/758994#758994 Appropriate bundles are loaded: 14|Active | 5|Drools :: Compiler (5.5.0.CR1) 17|Active | 5|Drools :: Core (5.5.0.CR1) 18|Active | 5|Knowledge API (5.5.0.CR1) 19|Active | 5|Knowledge Internal API (5.5.0.CR1) The package "org.drools.concurrent" is exported twice: inspect c *package org.drools.core [17] provides: ------------------------------ osgi.wiring.package; org.drools.concurrent 5.5.0.CR1 [UNUSED] org.drools.api [18] provides: ----------------------------- osgi.wiring.package; org.drools.concurrent 5.5.0.CR1 [UNUSED] Adding a bundle dependency on Drools Core to Knowledge API bundle helped to overcome this split package issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira