[JBoss JIRA] (JBRULES-3517) Combining custom operators with OR results in compile error
by Stathis Rouvas (JIRA)
Stathis Rouvas created JBRULES-3517:
---------------------------------------
Summary: Combining custom operators with OR results in compile error
Key: JBRULES-3517
URL: https://issues.jboss.org/browse/JBRULES-3517
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-compiler (expert)
Affects Versions: 5.4.0.Final
Environment: Drools.5.4.0
Java.1.6
Linux
Reporter: Stathis Rouvas
Assignee: Mark Proctor
I recently migrated from Drools.5.0.1 to Drools.5.4.0 and I am having issues when combining constraints with OR when custom operators are involved.
For example, the following rule:
rule "r548695.1"
no-loop true
dialect "mvel"
when
gnId : GN()
la : t547147( )
v1717 : Tra48( gnId.gNo==gNo , name F_str[startsWith] la.c547148 || postCode F_str[contains] la.c547149 )
then
System.out.println("Rule r548695.1 fired");
end
results in the following exception:
Unable to Analyse Expression gnId.gNo == gNo && ( F_str0.evaluate( name, la.c547148 ) || F_str1.evaluate( postCode, la.c547149 ) ):
[Error: unable to resolve method using strict-mode: my.package.rulez.Tra48.F_str0()]
[Near : {... gNo == gNo && ( F_str0.evaluate( name, la.c54 ....}]
^ : [Rule name='r548695.1']
Please note, that the same rule using AND (&&) between the custom operators compiles OK.
The above rule had not problem whatsoever in Drools.5.0.1.
--
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
13 years, 9 months
[JBoss JIRA] (AS7-3016) Lazy enlistment of JMS Session does not work - UserTransaction implementation does not support it
by Jiri Pechanec (Created) (JIRA)
Lazy enlistment of JMS Session does not work - UserTransaction implementation does not support it
-------------------------------------------------------------------------------------------------
Key: AS7-3016
URL: https://issues.jboss.org/browse/AS7-3016
Project: Application Server 7
Issue Type: Bug
Components: Transactions
Affects Versions: 7.1.0.Beta1b
Reporter: Jiri Pechanec
Assignee: Jonathan Halliday
Priority: Critical
This test case was identified in TCK6. There is a MDB with CMT configured - com/sun/ts/tests/jms/ee/mdb/xa
The testsuite sends a message to MDB
MDB
1) creates a QueueSession
2) Start UT
3) Send a message
4) Rollback UT
5) Start UT
6) Send a message
7) commit UT
Unfortunately the semantics is broken as QueueSession is not enlisted into transactions.
The enlistment is done when UserTransaction emits a notification org/jboss/tm/usertx/UserTransactionRegistry. The enlistment is done by JCA component which receives the notification and enlists all active XAResources.
Unfortunately the notification is emitted by org/jboss/tm/usertx/client/ServerVMClientUserTransaction. Unfortunately org/jboss/as/txn/service/ArjunaTransactionManagerService hard-codes com.arjuna.ats.internal.jta.transaction.arjunacore.UserTransactionImple which does not have this capability.
It is necessary to support this scenario as it is tested in TCKs.
--
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
13 years, 9 months
[JBoss JIRA] Created: (AS7-1268) Can't update subhandler on async handler
by Stan Silvert (JIRA)
Can't update subhandler on async handler
----------------------------------------
Key: AS7-1268
URL: https://issues.jboss.org/browse/AS7-1268
Project: Application Server 7
Issue Type: Bug
Components: Logging
Affects Versions: 7.1.0.Alpha1
Reporter: Stan Silvert
Assignee: David Lloyd
David, sorry if I'm assigning to the wrong person. I guess this could be a CLI bug.
[standalone@localhost:9999 /] cd subsystem=logging/async-handler=ASYNC
[standalone@localhost:9999 async-handler=ASYNC] :read-resource(recursive=true)
{
"outcome" => "success",
"result" => {
"level" => "INFO",
"overflow-action" => "BLOCK",
"queue-length" => 1024,
"subhandlers" => ["FILE"]
}
}
[standalone@localhost:9999 async-handler=ASYNC] :update-properties(subhandlers=["CONSOLE"])
{"outcome" => "success"}
[standalone@localhost:9999 async-handler=ASYNC] :read-resource(recursive=true)
{
"outcome" => "success",
"result" => {
"level" => "INFO",
"overflow-action" => "BLOCK",
"queue-length" => 1024,
"subhandlers" => ["FILE"]
}
}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (JBRULES-3496) kbase.removeKnowledgePackage() aparent infinite loop
by Mariano De Maio (JIRA)
Mariano De Maio created JBRULES-3496:
----------------------------------------
Summary: kbase.removeKnowledgePackage() aparent infinite loop
Key: JBRULES-3496
URL: https://issues.jboss.org/browse/JBRULES-3496
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 5.4.0.CR1
Environment: Unix based (Ubuntu 10) Core i5 with 4GB RAM
Reporter: Mariano De Maio
Assignee: Mark Proctor
Attachments: Proj.tar.gz
I have attached a simple project containing just 1 rule and some declared classes.
The rule is compiled ok, but when after adding the generated package to a kbase, when trying to remove it, an infinite-loop (or what it seems like an infinite-loop) occurs.
If you remove some of the patterns in the rule, everything works fine.
I have debugged up to ReteooBuilder.resetMarks(). The execution never returns from that method.
--
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
13 years, 9 months