[JBoss JIRA] (JBRULES-3680) OSGI Drools initialization failure: ExecutorProviderImpl not found
by Jaroslav Pullmann (JIRA)
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
13 years, 8 months
[JBoss JIRA] (AS7-5541) [7.1] OSGi bootstrap may exhaust threads and deadlock
by Thomas Diesler (JIRA)
Thomas Diesler created AS7-5541:
-----------------------------------
Summary: [7.1] OSGi bootstrap may exhaust threads and deadlock
Key: AS7-5541
URL: https://issues.jboss.org/browse/AS7-5541
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Affects Versions: 7.1.1.Final
Reporter: David Bosschaert
Assignee: Thomas Diesler
Priority: Critical
Fix For: 7.2.0.Alpha1
Reported on the Forum:
{code}org.jboss.msc.service.fail JB${bisas.pid} MSC service thread 1-16 ERROR MSC00001: Failed to start service jbosgi.AutoInstallProvider.COMPLETE: org.jboss.msc.service.StartException in service jbosgi.AutoInstallProvider.COMPLETE: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767)
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: java.lang.IllegalStateException: Cannot load module: deployment.osgi.enterprise:4.2.0.201003190513
at org.jboss.osgi.framework.internal.ResolverPlugin.loadModules(ResolverPlugin.java:261)
at org.jboss.osgi.framework.internal.ResolverPlugin.applyResolverResults(ResolverPlugin.java:229)
at org.jboss.osgi.framework.internal.ResolverPlugin.resolveAll(ResolverPlugin.java:209)
at org.jboss.osgi.framework.internal.PackageAdminPlugin.resolveBundles(PackageAdminPlugin.java:385)
at org.jboss.as.osgi.service.AutoInstallIntegration$1.start(AutoInstallIntegration.java:176)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
... 3 more
Caused by: org.jboss.modules.ModuleLoadException: Timeout waiting for module service: deployment.osgi.enterprise:4.2.0.201003190513
at org.jboss.as.server.moduleservice.ServiceModuleLoader$ModuleSpecLoadListener.getModuleSpec(ServiceModuleLoader.java:133)
at org.jboss.as.server.moduleservice.ServiceModuleLoader.findModule(ServiceModuleLoader.java:174)
at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:275)
at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:222)
at org.jboss.as.server.moduleservice.ServiceModuleLoader.preloadModule(ServiceModuleLoader.java:158)
at org.jboss.modules.ModuleLoader.preloadExportedModule(ModuleLoader.java:233)
at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:246)
at org.jboss.as.osgi.service.ModuleLoaderIntegration.preloadModule(ModuleLoaderIntegration.java:191)
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:204)
at org.jboss.osgi.framework.internal.ModuleManagerPlugin.loadModule(ModuleManagerPlugin.java:556)
at org.jboss.osgi.framework.internal.ResolverPlugin.loadModules(ResolverPlugin.java:259)
... 9 more{code}
--
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
13 years, 8 months
[JBoss JIRA] (AS7-5517) NullPointerException if an expression is in the jboss-app.xml file
by Francois MESSIAEN (JIRA)
Francois MESSIAEN created AS7-5517:
--------------------------------------
Summary: NullPointerException if an expression is in the jboss-app.xml file
Key: AS7-5517
URL: https://issues.jboss.org/browse/AS7-5517
Project: Application Server 7
Issue Type: Bug
Components: EE
Affects Versions: 7.1.3.Final (EAP)
Environment: JBoss AS 7.1.3 SNAPSHOT of the 9/06/12
Windows 7 pro
Reporter: Francois MESSIAEN
Assignee: David Lloyd
A NullPointerException is thrown when the JBoss AS 7.1.3 tries to replace an expression in the "jboss-app.xml" file.
--
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
13 years, 8 months
[JBoss JIRA] (JBRULES-3657) Eval bytecode not correctly generated
by Mario Fusco (JIRA)
Mario Fusco created JBRULES-3657:
------------------------------------
Summary: Eval bytecode not correctly generated
Key: JBRULES-3657
URL: https://issues.jboss.org/browse/JBRULES-3657
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 5.3.1.Final
Reporter: Mario Fusco
Assignee: Mario Fusco
Fix For: 5.3.2.Final
When a declaration does a double dereferencing, with the value of the method returned by the second dereferencing being a primitive type, the bytecode of the eval class using it is not correctly generated and causes, when instanced, an Exception like the following:
Exception in thread "main" java.lang.VerifyError: (class: gov/ssa/asa/rules/Rule_vhrGroupingByLocationEval0Invoker, method: evaluate signature: (Lorg/drools/spi/Tuple;[Lorg/drools/rule/Declaration;Lorg/drools/WorkingMemory;Ljava/lang/Object;)Z) Expecting to find integer on stack
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389)
at java.lang.Class.getConstructor0(Class.java:2699)
at java.lang.Class.newInstance0(Class.java:326)
at java.lang.Class.newInstance(Class.java:308)
at org.drools.rule.JavaDialectRuntimeData.wire(JavaDialectRuntimeData.java:413)
--
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
13 years, 8 months