[JBoss JIRA] Created: (JBRULES-506) Exception thrown when retract, reassert and retract again
by Leo Liang (JIRA)
Exception thrown when retract, reassert and retract again
---------------------------------------------------------
Key: JBRULES-506
URL: http://jira.jboss.com/jira/browse/JBRULES-506
Project: JBoss Rules
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.0.4, 3.0.1
Reporter: Leo Liang
Assigned To: Mark Proctor
Attachments: Fact.java, test.drl, TestDriver.java
In one rule retract the object and re-assert it, then retract the object again in the following activated rule. A null pointer exception will occur at this time.
java.lang.NullPointerException
at org.drools.reteoo.TerminalNode.retractTuple(TerminalNode.java:216)
at org.drools.reteoo.LeftInputAdapterNode.retractObject(LeftInputAdapterNode.java:207)
at org.drools.reteoo.ObjectSource.propagateRetractObject(ObjectSource.java:141)
at org.drools.reteoo.ObjectTypeNode.retractObject(ObjectTypeNode.java:180)
at org.drools.reteoo.Rete.retractObject(Rete.java:150)
at org.drools.reteoo.ReteooRuleBase.retractObject(ReteooRuleBase.java:207)
at org.drools.reteoo.ReteooWorkingMemory.doRetract(ReteooWorkingMemory.java:77)
at org.drools.common.AbstractWorkingMemory.retractObject(AbstractWorkingMemory.java:668)
at org.drools.base.DefaultKnowledgeHelper.retractObject(DefaultKnowledgeHelper.java:86)
at com.ericsson.ruletest.debug.Rule_test2_0.consequence(Rule_test2_0.java:8)
at com.ericsson.ruletest.debug.Rule_test2_0ConsequenceInvoker.evaluate(Rule_test2_0ConsequenceInvoker.java:22)
at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:437)
at org.drools.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:407)
at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:269)
at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:256)
at com.ericsson.ruletest.TestDriver.main(TestDriver.java:26)
The given test case is the the simplified from my production code.
--------------- test.drl ------------------------
package com.ericsson.ruletest.debug
import com.ericsson.ruletest.Fact;
rule "test1"
salience 10
no-loop true
when
input:Fact();
then
retract(input);
assert(input);
end;
rule "test2"
salience 0
no-loop true
when
input:Fact();
then
retract(input);
end;
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 7 months
[JBoss JIRA] Created: (JBMESSAGING-601) Place Messaging artifacts in the repository
by Richard Achmatowicz (JIRA)
Place Messaging artifacts in the repository
-------------------------------------------
Key: JBMESSAGING-601
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-601
Project: JBoss Messaging
Issue Type: Task
Components: Tests and Performance
Reporter: Richard Achmatowicz
Assigned To: Ovidiu Feodorov
Priority: Critical
Fix For: 1.2.0.Beta1
In order to test Messaging within the AS testsuite, we need a scoped deployment of Messaging (as Messaging currently uses modified versions of Remoting and other jars). We also want to use release-admin.xml to create the Messaging configuration for the application server. (NOTE: All of this assumes a JMX-based deployment and testing context, as discussed in our recent conversion concerning JMX vs MC based-deployments.)
I need to get these artifacts (jboss-messagings-coped.sar, release-admin.xml) somehow, for each release of Messaging which is to be tested. This means placing copies in repository.jboss.com.
As for the contents of the scoped sar, I need a version which includes the following:
(i) all the Messaging classes
(ii) the modified jars for remoting etc. and a service descriptor to turn on scoping
(iii) service descriptors for deployment of the Messaging MBeans via JMX
The contents reflect the fact that this sar will be used together with release-admin,xml to create a Messaging configuration which can be used to start the AS with and run integration tests against Messaging.
This sar need not contain any test-related deployments, as the testsuite can manage those separately.
Because we may want to test differing versions of Messaging, such a sar (e.g. named jboss-messaging-scoped.sar) and a copy of release-admin.xml should be available for each version in the repository. At present, the repository supports two versions of Messaging: 1.0.1.CR4, and snapshot.
I suppose these could be placed in a resources subdirectory on the repository.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 7 months
[JBoss JIRA] Created: (JBESB-170) ObjectToCVSString needs to inform invoker of errors
by Mark Little (JIRA)
ObjectToCVSString needs to inform invoker of errors
---------------------------------------------------
Key: JBESB-170
URL: http://jira.jboss.com/jira/browse/JBESB-170
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: ESB Core
Reporter: Mark Little
Assigned To: Tom Fennelly
Priority: Minor
Fix For: 4.0
[junit] 14:12:30,626 ERROR ObjectToCSVString:113 - Bean method: getId not found/accessible on message object org.jboss.soa.esb.actions.converters.ObjectToCSVStringUnitTest$TestBean
[junit] java.lang.NoSuchMethodException: org.jboss.soa.esb.actions.converters.ObjectToCSVStringUnitTest$TestBean.getId()
[junit] at java.lang.Class.getMethod(Class.java:1581)
is thrown if a method signature is not available. Should be configurable whether or not the processor continues to operate. Also, if it does then it would be good if it flagged in the output that the signature was invalid.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 7 months