July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-8560) Tech opinion on JBAS-6244

by Misty Stanley-Jones (JIRA)

Tech opinion on JBAS-6244 ------------------------- Key: JBAS-8560 URL: https://jira.jboss.org/browse/JBAS-8560 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Misty Stanley-Jones Assignee: Jonathan Halliday I need to know if JBAS-6244 (https://jira.jboss.org/browse/JBAS-6244) is still relevant and whether this has already been documented or not. The JIRA and linked articles are extremely old, and I have gotten zero feedback from GSS on this. Jonathan, can you have a quick glance over it and let me know who I might talk ti about it? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8717) JBoss 6 RC1 crash when using MOD_JK

by Kleber Rocha (JIRA)

JBoss 6 RC1 crash when using MOD_JK ----------------------------------- Key: JBAS-8717 URL: https://jira.jboss.org/browse/JBAS-8717 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.0.0.CR1 Environment: Linux CEntOS 5.5, JDK 1.6.0_23-b05 Reporter: Kleber Rocha JBoss work fine, but when I configure Apache with mod_jk and I start a connection, JBoss crash and create a file hs_err_pidXXXX.log, with this information: # JRE version: 6.0_23-b05 # Java VM: Java HotSpot(TM) 64-Bit Server VM (19.0-b09 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libapr-1.so.0+0x1b58f] apr_pollset_add+0x8f This don´t happen with M5. Exist any workaround for this? -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

4
5
0 / 0

[JBoss JIRA] Created: (JBRULES-2995) Field "class" not recognized in some constructs

by Wolfgang Laun (JIRA)

Field "class" not recognized in some constructs ----------------------------------------------- Key: JBRULES-2995 URL: https://issues.jboss.org/browse/JBRULES-2995 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler (expert) Affects Versions: 5.2.0.CR1 Reporter: Wolfgang Laun Assignee: Mark Proctor Given this simple type: declare Foo clazz : Class end and this rule: rule yyy when $f: Foo( $cl: clazz == ( java.lang.String.class ) ) ### $f: Foo( $cl: clazz, eval( $f.getClazz().equals( java.lang.String.class ) ) ) ### $f: Foo( $cl: clazz == java.lang.String.class ) then System.out.println( "--- got a " + $cl ); end Only the first vyariant is accepted by the DRL parser. Other forms are rebuked with, e.g.: Unable to Analyse Expression $f.getClazz().equals( java.lang.String.class ) : [Error: Failed to compile: 2 compilation error(s): - (1,24) unable to resolve method using strict-mode: ex10.Foo.java() - (1,24) unqualified type in strict mode for: java] [Near : {... $f.getClazz().equals( java.lang.String.class ) ....}] ^ [Line: 1, Column: 24] : [Rule name='yyy'] Note the incorrect line number! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-3123) .rf file raises a null pointer exception when it is loaded

by Quentin Caillard (JIRA)

.rf file raises a null pointer exception when it is loaded ---------------------------------------------------------- Key: JBRULES-3123 URL: https://issues.jboss.org/browse/JBRULES-3123 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.2.0.Final Reporter: Quentin Caillard Assignee: Mark Proctor I have just switched from version 5.1.1 to 5.2.0.Final I have a ruleflow (.rf) file which can be loaded. I have the following stack trace : java.lang.NullPointerException at org.drools.compiler.PackageBuilder.addProcessFromXml(PackageBuilder.java:516) at org.drools.compiler.PackageBuilder.addKnowledgeResource(PackageBuilder.java:556) at org.drools.builder.impl.KnowledgeBuilderImpl.add(KnowledgeBuilderImpl.java:28) at com.ariadnext.NewDroolsTest$RulesUtils.loadRules(NewDroolsTest.java:106) I made a simple junit test which reproduces the bug. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

4
16
0 / 0

[JBoss JIRA] Created: (JBRULES-3140) NullPointerException thrown on JPA synchronization.afterCompletion() clearProcessInstances()

by Nick Bruno (JIRA)

NullPointerException thrown on JPA synchronization.afterCompletion() clearProcessInstances() -------------------------------------------------------------------------------------------- Key: JBRULES-3140 URL: https://issues.jboss.org/browse/JBRULES-3140 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.2.0.Final Reporter: Nick Bruno Assignee: Mark Proctor In org.drools.persistence.SingleSessionCommandService$SynchronizationImpl.afterCompletion(), the following generates a NullPointerException when no processes are implemented. {noformat}if ( ksession != null ) { ((InternalKnowledgeRuntime) ksession).getProcessRuntime().clearProcessInstances(); // NullPointerException ((JPAWorkItemManager) ksession.getWorkItemManager()).clearWorkItems(); } {noformat} The fix is to grab the InternalProcessRuntime to a local variable and test if it is null before calling clearProcessInstances(), as so: {noformat}InternalProcessRuntime ipr = ((InternalKnowledgeRuntime) ksession).getProcessRuntime(); if( ipr != null) { ipr.clearProcessInstances(); }{noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-3065) Facts currently have to be Java Beans, but Mark has used POJOS, except the attached example does not work.

by Jim Tyrrell (JIRA)

Facts currently have to be Java Beans, but Mark has used POJOS, except the attached example does not work. ---------------------------------------------------------------------------------------------------------- Key: JBRULES-3065 URL: https://issues.jboss.org/browse/JBRULES-3065 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Jim Tyrrell Assignee: Mark Proctor Attachments: Screen shot 2011-06-06 at 2.02.00 PM.png, Screen shot 2011-06-06 at 2.02.14 PM.png, Screen shot 2011-06-06 at 2.02.37 PM.png, SimpleSpreadSheetBasedPOJO.java, SimpleSpreadSheetBasedTest.drl, SimpleSpreadSheetBasedTest.java When modeling spreadsheets for form/spreadsheet validation, see the attached screen shots, all of the tools use the convention of A, B, C for the column names (Open Office, Excel, and Numbers). When trying to create an object with variable names of A, B, etc, I get errors in the JBDS as the below: Description Resource Path Location Type BuildError: Unable to create Field Extractor for 'A' of '[ClassObjectType class=com.sample.SimpleSpreadSheetBasedPOJO]' in rule 'Validation 1' SimpleSpreadSheetBasedTest.drl /BugProject/src/main/rules line 16 Drools Error No amount of massaging can get this error to go away. When I run the attached classes, I get the following error message: Unable to create Field Extractor for 'A' of '[ClassObjectType class=com.sample.SimpleSpreadSheetBasedPOJO]' in rule 'Validation 1' : [Rule name='Validation 1'] java.lang.IllegalArgumentException: Could not parse knowledge. at com.sample.SimpleSpreadSheetBasedTest.readKnowledgeBase(SimpleSpreadSheetBasedTest.java:48) at com.sample.SimpleSpreadSheetBasedTest.main(SimpleSpreadSheetBasedTest.java:23) Even though a getter and setter method is available. So I created an ID field, this seems to work fine, but if I create a field A1, this does not, if I create ID1, this seems to work...so something is amiss in the way in which fields, methods, etc are marshaled. If a Java Bean is required that is fine, but then we need to retreat from marketing POJOs as facts, and also possibly create a better error message that tells us to use Java Beans and not POJOs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-2989) Slotted/named syntax for bindings silently accepted as positional argument

by Wolfgang Laun (JIRA)

Slotted/named syntax for bindings silently accepted as positional argument -------------------------------------------------------------------------- Key: JBRULES-2989 URL: https://issues.jboss.org/browse/JBRULES-2989 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler (expert) Affects Versions: 5.2.0.CR1 Reporter: Wolfgang Laun Assignee: Mark Proctor declare Article artid : int; artname : String; custid : int; end rule "articles of a customer" when $a: Article( $artid: artid, $artname: artname, $custid : custid ; ) ### semicolon here! ### then System.out.println( "Art " + $artid + " " + $a.getArtname() + " by " + $custid ); end This is accepeted by the compiler without error indication, but preceding a semicolon only positional argument should be permitted. Expect: an error message, compilation failure. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2956) Runtime error when using non-boolean expression as a constraint

by Wolfgang Laun (JIRA)

Runtime error when using non-boolean expression as a constraint --------------------------------------------------------------- Key: JBRULES-2956 URL: https://issues.jboss.org/browse/JBRULES-2956 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 5.2.0.M2 Reporter: Wolfgang Laun Assignee: Mark Proctor declare Num num : Integer even : boolean end rule start when then insert( new Num( 42, true ) ); end rule sumem when $n: Num( num, num + 1, eval(num + 1) ) then end All of these constraints result in a RUNTIME error ar java.lang.ClassCastException: java.lang.Integer cannot be cast to java.lang.Boolean org.drools.base.mvel.MVELPredicateExpression.evaluate(MVELPredicateExpression.java:97) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-3139) NPE in KnowledgeAgentImpl due to missing change set

by Wolfgang Laun (JIRA)

NPE in KnowledgeAgentImpl due to missing change set --------------------------------------------------- Key: JBRULES-3139 URL: https://issues.jboss.org/browse/JBRULES-3139 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (expert) Reporter: Wolfgang Laun Assignee: Mark Proctor A missing Change Set causes a NPE in KnowledgeAgentImpl. import java.net.URL; import org.drools.*; import org.drools.agent.*; import org.drools.conf.*; import org.drools.builder.*; import org.drools.io.*; public void setup() throws Exception { KnowledgeBaseConfiguration kBaseConfig = KnowledgeBaseFactory.newKnowledgeBaseConfiguration(); kBaseConfig.setOption(EventProcessingOption.STREAM); // kBaseConfig.setOption( cehOption ); ResourceChangeScannerConfiguration rcsConf = ResourceFactory.getResourceChangeScannerService() .newResourceChangeScannerConfiguration(); rcsConf.setProperty("drools.resource.scanner.interval", "20"); ResourceFactory.getResourceChangeScannerService().configure( rcsConf ); KnowledgeAgentConfiguration kaConf = KnowledgeAgentFactory.newKnowledgeAgentConfiguration(); kaConf.setProperty("drools.agent.scanDirectories", "true"); kaConf.setProperty("drools.agent.scanResources", "true"); kaConf.setProperty("drools.agent.newInstance", "false"); KnowledgeBase kBase = KnowledgeBaseFactory.newKnowledgeBase(kBaseConfig); KnowledgeAgent kAgent = KnowledgeAgentFactory.newKnowledgeAgent( "drools agent", kBase, kaConf); String urlString = "file://tmp/MissingChangeSet.xml"; try { URL url = new URL(urlString); Resource urlResource = ResourceFactory.newUrlResource(url); if( urlResource != null ){ System.out.println( "Resource " + urlResource ); } kAgent.applyChangeSet( urlResource ); } catch (Exception e) { System.out.println("Caught exception: " + e.getMessage()); e.printStackTrace(); } } Caught exception: null java.lang.NullPointerException at org.drools.agent.impl.KnowledgeAgentImpl.processChangeSet(KnowledgeAgentImpl.java:223) at org.drools.agent.impl.KnowledgeAgentImpl.applyChangeSet(KnowledgeAgentImpl.java:189) at org.drools.agent.impl.KnowledgeAgentImpl.applyChangeSet(KnowledgeAgentImpl.java:174) at hashcode.Main.setup(Main.java:75) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2801) Entry-point defaults for type, rule, package

by Wolfgang Laun (JIRA)

Entry-point defaults for type, rule, package -------------------------------------------- Key: JBRULES-2801 URL: https://jira.jboss.org/browse/JBRULES-2801 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Wolfgang Laun Assignee: Mark Proctor Implement the definition of the default entry point for an Event or Fact type via a metadata attribute, e.g.: declare X @role( event ) @entry-point( y ) end so that this a) declares the entry-point in the KnowledgeBase (the same way from entry-point "x" does) b) removes the need to use from entry-point with all patterns referring to X c) would still let me override the entry point with a "from entry-point" clause. The same attribute can be used inside a rule, where it is associated with all fact patterns without an explicit entry point. Here it also overrides an entry-point declared with the type's declare, if any. Since all rule attributes may also be used at package level (outside rules), this includes the new entry-point attribute. It will then be honoured in rules according to the current strategy for all other rule attributes. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2011