[JBoss JIRA] (JBFORUMS-298) xception in thread "main" javax.xml.stream.FactoryConfigurationError: Provider com.bea.xml.stream.EventFactory not found
by chandrasheker b (JIRA)
chandrasheker b created JBFORUMS-298:
----------------------------------------
Summary: xception in thread "main" javax.xml.stream.FactoryConfigurationError: Provider com.bea.xml.stream.EventFactory not found
Key: JBFORUMS-298
URL: https://issues.jboss.org/browse/JBFORUMS-298
Project: JBoss Forums
Issue Type: Feature Request
Reporter: chandrasheker b
Assignee: Luca Stancapiano
C:\Program Files\jboss-eap-6.0\bin>standalone.bat
Calling "C:\Program Files\jboss-eap-6.0\bin\standalone.conf.bat"
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: C:\Program Files\jboss-eap-6.0
JAVA: C:\Java\jdk1.6.0_26\bin\java
JAVA_OPTS: -client -Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djboss.server.default.config=standalone.xml
===============================================================================
Exception in thread "main" javax.xml.stream.FactoryConfigurationError: Provider com.bea.xml.stream.EventFactory not found
at javax.xml.stream.FactoryFinder.newInstance(FactoryFinder.java:72)
at javax.xml.stream.FactoryFinder.find(FactoryFinder.java:176)
at javax.xml.stream.FactoryFinder.find(FactoryFinder.java:92)
at javax.xml.stream.XMLEventFactory.newInstance(XMLEventFactory.java:30)
at __redirected.__XMLEventFactory.<clinit>(__XMLEventFactory.java:73)
at __redirected.__JAXPRedirected.initAll(__JAXPRedirected.java:81)
at org.jboss.modules.Module$1.run(Module.java:126)
at org.jboss.modules.Module$1.run(Module.java:113)
at java.security.AccessController.doPrivileged(Native Method)
at org.jboss.modules.Module.<clinit>(Module.java:113)
at org.jboss.modules.Main.main(Main.java:255)
Press any key to continue . . .
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (JBRULES-3587) Declarations from "declare" sections don't apply to sub-classes if those live in a different package
by Jörg Henne (JIRA)
Jörg Henne created JBRULES-3587:
-----------------------------------
Summary: Declarations from "declare" sections don't apply to sub-classes if those live in a different package
Key: JBRULES-3587
URL: https://issues.jboss.org/browse/JBRULES-3587
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-compiler
Affects Versions: 5.4.0.Final
Reporter: Jörg Henne
Assignee: Mark Proctor
Declarations (like {{@role(event)}}) in a {{declare}}-Section should apply to sub-classes of the declared class, too, but don't if the sub-class resides in a different package than the base class.
Attached you'll find an example which demonstrates the issue. The class {{ButtonEvent}} derives from {{VSCPEvent}} which is declared with{{@role(event)}}. Running {{com.levigo.overlord.DroolsTest}} yields a {{java.lang.ClassCastException: org.drools.common.DefaultFactHandle}} which is caused by the ButtonEvent not being recognized as an event instead of a fact.
The Problem goes away if {{ButtonEvent}} is declared as an event (uncomment the section in {{overlord.drl}} or {{ButtonEvent}} is moved to the same package as {{VSCPEvent}}.
For more information see the referenced forum thread.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] Created: (JBRULES-3033) java.lang.ClassCastException when change rule condition and declarative facts/events are used
by Federico Weisse (JIRA)
java.lang.ClassCastException when change rule condition and declarative facts/events are used
---------------------------------------------------------------------------------------------
Key: JBRULES-3033
URL: https://issues.jboss.org/browse/JBRULES-3033
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core
Affects Versions: 5.1.1.FINAL
Reporter: Federico Weisse
Assignee: Mark Proctor
We have drl files where we declare events. we use declarative events (there is no java class AlertaPosManual)
(like this)
declare AlertaPosManual
@role (event)
@expires(10s)
idTerminal : java.lang.String
end
We use a StatefullSession for fusion cep and we need that changes in rules refresh the kBase in runtime. But when a rule condition changes this exception in throw
Exception in thread "Thread-2" java.lang.ClassCastException: com.sample.ConsumoPostManual cannot be cast to com.sample.ConsumoPostManual
at org.drools.base.com.sample.ConsumoPostManual17710704$getIdTerminal.getValue(Unknown Source)
at org.drools.base.extractors.BaseObjectClassFieldReader.getHashCode(BaseObjectClassFieldReader.java:192)
at org.drools.base.ClassFieldReader.getHashCode(ClassFieldReader.java:193)
at org.drools.core.util.AbstractHashTable$SingleIndex.hashCodeOf(AbstractHashTable.java:582)
at org.drools.core.util.RightTupleIndexHashTable.getOrCreate(RightTupleIndexHashTable.java:360)
at org.drools.core.util.RightTupleIndexHashTable.add(RightTupleIndexHashTable.java:243)
at org.drools.reteoo.AccumulateNode.assertObject(AccumulateNode.java:246)
at org.drools.reteoo.ObjectTypeNode.updateSink(ObjectTypeNode.java:276)
at org.drools.reteoo.PropagationQueuingNode.updateSink(PropagationQueuingNode.java:111)
at org.drools.reteoo.BetaNode.attach(BetaNode.java:214)
at org.drools.reteoo.builder.BuildUtils.attachNode(BuildUtils.java:151)
at org.drools.reteoo.builder.CollectBuilder.build(CollectBuilder.java:114)
at org.drools.reteoo.builder.PatternBuilder.attachPattern(PatternBuilder.java:111)
at org.drools.reteoo.builder.PatternBuilder.build(PatternBuilder.java:72)
at org.drools.reteoo.builder.GroupElementBuilder$AndBuilder.build(GroupElementBuilder.java:132)
at org.drools.reteoo.builder.GroupElementBuilder.build(GroupElementBuilder.java:78)
at org.drools.reteoo.builder.ReteooRuleBuilder.addSubRule(ReteooRuleBuilder.java:155)
at org.drools.reteoo.builder.ReteooRuleBuilder.addRule(ReteooRuleBuilder.java:128)
at org.drools.reteoo.ReteooBuilder.addRule(ReteooBuilder.java:117)
at org.drools.reteoo.ReteooRuleBase.addRule(ReteooRuleBase.java:428)
at org.drools.common.AbstractRuleBase.addRule(AbstractRuleBase.java:721)
at org.drools.common.AbstractRuleBase.addPackages(AbstractRuleBase.java:545)
at org.drools.reteoo.ReteooRuleBase.addPackages(ReteooRuleBase.java:445)
at org.drools.reteoo.ReteooRuleBase.addPackage(ReteooRuleBase.java:452)
at org.drools.agent.impl.KnowledgeAgentImpl.addResourcesToKnowledgeBase(KnowledgeAgentImpl.java:937)
at org.drools.agent.impl.KnowledgeAgentImpl.incrementalBuildResources(KnowledgeAgentImpl.java:821)
at org.drools.agent.impl.KnowledgeAgentImpl.buildKnowledgeBase(KnowledgeAgentImpl.java:586)
at org.drools.agent.impl.KnowledgeAgentImpl.applyChangeSet(KnowledgeAgentImpl.java:185)
at org.drools.agent.impl.KnowledgeAgentImpl$ChangeSetNotificationDetector.run(KnowledgeAgentImpl.java:1106)
at java.lang.Thread.run(Thread.java:619)
I think that's because the statefullSession has an instance of
com.sample.ConsumoPostManual (loaded with the classLoader
org.drools.rule.JavaDialectRuntimeData$PackageClassLoader@1218b25) But when
the kBase is regenerated and the class com.sample.ConsumoPostManual to, the
classLoader org.drools.rule.JavaDialectRuntimeData is recreated so there
are two versions of the class com.sample.ConsumoPostManual in differents
classLoader (one in the statefullSession and the other in the kBase)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] Created: (JBRULES-2962) Knowledge Agent rebuilding KnowledgeBase with scanner/notifier does not work with declared facts
by Ross Hall (JIRA)
Knowledge Agent rebuilding KnowledgeBase with scanner/notifier does not work with declared facts
------------------------------------------------------------------------------------------------
Key: JBRULES-2962
URL: https://issues.jboss.org/browse/JBRULES-2962
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core
Affects Versions: 5.2.0.M1, 5.1.1.FINAL
Reporter: Ross Hall
Assignee: Mark Proctor
When reloading rules in a KnowledgeAgent declared facts will cause ClassCastExceptions when new-instance is set to false. When new-instance is set to true, the KnowledgeBase is rebuilt, however declared facts are not recognized and associated rules will not fire. Rules not using declared facts will fire normally. Using POJOs works fine.
In both cases the KnowledgeAgent will build the rule base the first time, the issue only seems to occur when the changeset resources are modified and are detected by the resource notifier and scanner.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (JBRULES-3597) KnowledgeAgent can't incrementally load resources with equivalent declared types
by Davide Sottara (JIRA)
Davide Sottara created JBRULES-3597:
---------------------------------------
Summary: KnowledgeAgent can't incrementally load resources with equivalent declared types
Key: JBRULES-3597
URL: https://issues.jboss.org/browse/JBRULES-3597
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core
Affects Versions: 5.4.0.Final
Reporter: Davide Sottara
Assignee: Davide Sottara
Priority: Blocker
Fix For: 5.5.0.Beta1
Assume a KA is created and configured to load its KB incrementally.
Assume the KA will load two resources in two different steps.
If the two DRL resources contain the same type definition, two typeDeclarations will be created.
The first will be "novel" and used to compile the first DRL.
The second will simply refer the already loaded class.
(Notice that the PackageBuilder will not allow the two definitions to
be different)
The rulebase, however, can't merge the two compiled packages because
the "novel" attribute is different and apparently incompatible.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] Created: (AS7-1613) NPE in TranslatingSuspendableChannel.scheduleReadTask
by Ondrej Zizka (JIRA)
NPE in TranslatingSuspendableChannel.scheduleReadTask
-----------------------------------------------------
Key: AS7-1613
URL: https://issues.jboss.org/browse/AS7-1613
Project: Application Server 7
Issue Type: Bug
Components: CLI
Affects Versions: 7.0.1.Final
Reporter: Ondrej Zizka
Assignee: Alexey Loubyansky
Happened after a while of inactivity (if that matters).
[standalone@localhost:9999 interface=public] cd ..
[standalone@localhost:9999 /] cd ..
[standalone@localhost:9999 /] ls
extension core-service path subsystem system-property deployment interface socket-binding-group
[standalone@localhost:9999 /] Exception in thread "pool-1-thread-21" java.lang.NullPointerException
at org.xnio.channels.TranslatingSuspendableChannel.scheduleReadTask(TranslatingSuspendableChannel.java:253)
at org.xnio.channels.TranslatingSuspendableChannel.resumeReads(TranslatingSuspendableChannel.java:233)
at org.jboss.remoting3.remote.ClientConnectionOpenListener$Authentication$2.run(ClientConnectionOpenListener.java:498)
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:662)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months