[JBoss JIRA] Created: (JBRULES-1665) put offending rule name in exception messages
by Alex McCarrier (JIRA)
put offending rule name in exception messages
---------------------------------------------
Key: JBRULES-1665
URL: http://jira.jboss.com/jira/browse/JBRULES-1665
Project: JBoss Drools
Issue Type: Feature Request
Components: Drl Parser/Builder
Affects Versions: FUTURE
Environment: all
Reporter: Alex McCarrier
Assigned To: Mark Proctor
Priority: Minor
It would be nice if drools compiler error messages would include the rule that caused the error. For instance, predicate eval errors, or "unable to resolve property" errors would state which rule was being evaluated when it encountered an error. Currently the developer has to go through the rules file looking for lines similar to the one reported in the error. Also, when it's this much work for a developer to find the offending rule, it is pretty much impossible for business users to figure out which rule they messed up.
If it's at all possible to add the rule name to these error messages, please do so. It would make our lives a lot easier. :)
--
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
12 years, 7 months
[JBoss JIRA] Created: (JBRULES-680) Support real-time problem modification during solving with utils for the single thread subsystem
by Geoffrey De Smet (JIRA)
Support real-time problem modification during solving with utils for the single thread subsystem
------------------------------------------------------------------------------------------------
Key: JBRULES-680
URL: http://jira.jboss.com/jira/browse/JBRULES-680
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Solver
Reporter: Geoffrey De Smet
Assigned To: Geoffrey De Smet
Rete/Drools is single threaded, and so is the current implementation of the localsearchsolver,
but this single thread subsystem should be documented
and utils should be provided to allow for real-time problem modification
A simple way would be to use a producer-consumer pattern with a non blocking queue which holds "problem moves".
Each step the problem moves could be used.
Problems:
- bestsolutionrecalled also needs it's score adjusted. so we'll need a 2th working memory:
-- EITHER temporary, just for the problem move (or set of problem moves)
-- EITHER all the time, but then we'd have to hold a chain of moves, some of which might not be doable at the end
- cached selectors must be notified of refreshing their cache
- solution cloning normally doesn't clone the problem facts, just the proposed solution references. Do we need a full clone now?
--
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
12 years, 7 months
[JBoss JIRA] Created: (JBRULES-2748) Missing drools-flow-compiler dependency in trunk\drools-examples\drools-examples-fusion\pom.xml
by Michael Anstis (JIRA)
Missing drools-flow-compiler dependency in trunk\drools-examples\drools-examples-fusion\pom.xml
-----------------------------------------------------------------------------------------------
Key: JBRULES-2748
URL: https://jira.jboss.org/browse/JBRULES-2748
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 5.1.1.FINAL
Environment: All
Reporter: Michael Anstis
Assignee: Mark Proctor
Fix For: FUTURE
java.lang.NullPointerException
at org.drools.compiler.PackageBuilder.addProcessFromXml(PackageBuilder.java:432)
at org.drools.compiler.PackageBuilder.addKnowledgeResource(PackageBuilder.java:468)
at org.drools.builder.impl.KnowledgeBuilderImpl.add(KnowledgeBuilderImpl.java:28)
at org.drools.examples.broker.Broker.loadRuleBase(Broker.java:95)
at org.drools.examples.broker.Broker.createSession(Broker.java:80)
at org.drools.examples.broker.Broker.<init>(Broker.java:57)
at org.drools.examples.broker.Main.main(Main.java:53)
When running drools-examples Fusion Broker example.
Patch:-
Index: pom.xml
===================================================================
--- pom.xml (revision 35658)
+++ pom.xml (working copy)
@@ -26,6 +26,10 @@
<groupId>org.drools</groupId>
<artifactId>drools-compiler</artifactId>
</dependency>
+ <dependency>
+ <groupId>org.drools</groupId>
+ <artifactId>drools-flow-compiler</artifactId>
+ </dependency>
<!-- External dependencies -->
<dependency>
--
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
12 years, 7 months
[JBoss JIRA] Created: (JBRULES-2244) MVEL raising errors for declared types when there is a package import (import x.y.x.*)
by Edson Tirelli (JIRA)
MVEL raising errors for declared types when there is a package import (import x.y.x.*)
--------------------------------------------------------------------------------------
Key: JBRULES-2244
URL: https://jira.jboss.org/jira/browse/JBRULES-2244
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-compiler, drools-core
Affects Versions: 5.0.1.FINAL, 5.0.0.FINAL
Reporter: Edson Tirelli
Assignee: Edson Tirelli
Fix For: 5.1.0.M1
The following DRL:
===================================================
package org.drools.examples.broker
import org.drools.examples.broker.model.*;
declare Statistics
symbol : String @key()
average : double
end
rule "Setup statistics"
when
$c : Company( $s : symbol )
not( Statistics( symbol == $s ) )
then
Statistics s = new Statistics();
s.symbol = $s;
insert( s );
end
===================================================
Generates the error:
-----------------------------
BuildError: Unable to build expression for 'consequence': Failed to compile: 1 compilation error(s):
- (1,10) unqualified type in strict mode for: Statistics ' Statistics s = new Statistics();
s.symbol = $s;
insert( s );
' broker.drl drools-examples-fusion/src/main/rules line 42 Drools Error
-----------------------------
But if we change the import to:
===================================================
import org.drools.examples.broker.model.Company
import org.drools.examples.broker.model.StockTick
import org.drools.examples.broker.model.SuddenDropEvent
===================================================
Everything works just fine.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] Created: (JBRULES-1801) drools-ant-4.0.7, DroolsCompilerAntTask, classloader mixup leads to ClassCastException if drools-compiler.jar part of classpathref
by Juergen none (JIRA)
drools-ant-4.0.7, DroolsCompilerAntTask, classloader mixup leads to ClassCastException if drools-compiler.jar part of classpathref
----------------------------------------------------------------------------------------------------------------------------------
Key: JBRULES-1801
URL: https://jira.jboss.org/jira/browse/JBRULES-1801
Project: JBoss Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: drools-ant
Affects Versions: 4.0.7
Reporter: Juergen none
Assignee: Mark Proctor
drools-4.0.7:
Original error in build.xml:
/home/juergen/workspace/eclipse/kusss-dev/build.xml:777: RuleBaseTask failed: Unable to load dialect 'org.drools.rule.builder.dialect.java.JavaDialectConfiguration:java'
Traceback to:
org.drools.compiler.PackageBuilderConfiguration, line 154+:
Class cls = classLoader.loadClass( dialectClass );
DialectConfiguration dialectConf = (DialectConfiguration) cls.newInstance();
cls is org.drools.rule.builder.dialect.java.JavaDialectConfiguration, but loaded via classloader given in drools compile ant task property classpathref, while DialectConfiguration is loaded via ant tool classpath used for taskdef
-->
java.lang.ClassCastException: org.drools.rule.builder.dialect.java.JavaDialectConfiguration
interim fix:
make sure drools-compiler.jar is not in classpath of classloaderref
suggested fix:
Class cls = DialectConfiguration.class.getClassLoader().loadClass( dialectClass );
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] Created: (JBRULES-2384) Unable to process deployment descriptor for context'/drools-server'
by Megha Shetty (JIRA)
Unable to process deployment descriptor for context'/drools-server'
-------------------------------------------------------------------
Key: JBRULES-2384
URL: https://jira.jboss.org/jira/browse/JBRULES-2384
Project: Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: All
Environment: windows
Reporter: Megha Shetty
Assignee: Mark Proctor
I am getting the following error when i am trying to deploy drools-server.war through jboss.
Unable to process deployment descriptor for context'/drools-server'
Following is the complete log when i am starting the jboss server
JAVA_HOME is not set. Unexpected results may occur.
Set JAVA_HOME to the directory of your local JDK to avoid this message.
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: E:\Eclipse Europa\jboss-4.2.3.GA
JAVA: java
JAVA_OPTS: -Dprogram.name=run.bat -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcIn
terval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
CLASSPATH: E:\Eclipse Europa\jboss-4.2.3.GA\bin\run.jar
===============================================================================
14:35:43,295 INFO [Server] Starting JBoss (MX MicroKernel)...
14:35:43,295 INFO [Server] Release ID: JBoss [Trinity] 4.2.3.GA (build: SVNTag=
JBoss_4_2_3_GA date=200807181417)
14:35:43,295 INFO [Server] Home Dir: E:\Eclipse Europa\jboss-4.2.3.GA
14:35:43,295 INFO [Server] Home URL: file:/E:/Eclipse Europa/jboss-4.2.3.GA/
14:35:43,295 INFO [Server] Patch URL: null
14:35:43,295 INFO [Server] Server Name: default
14:35:43,295 INFO [Server] Server Home Dir: E:\Eclipse Europa\jboss-4.2.3.GA\se
rver\default
14:35:43,311 INFO [Server] Server Home URL: file:/E:/Eclipse Europa/jboss-4.2.3
.GA/server/default/
14:35:43,311 INFO [Server] Server Log Dir: E:\Eclipse Europa\jboss-4.2.3.GA\ser
ver\default\log
14:35:43,311 INFO [Server] Server Temp Dir: E:\Eclipse Europa\jboss-4.2.3.GA\se
rver\default\tmp
14:35:43,311 INFO [Server] Root Deployment Filename: jboss-service.xml
14:35:43,482 INFO [ServerInfo] Java version: 1.6.0,Sun Microsystems Inc.
14:35:43,482 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.6.0-b105,S
un Microsystems Inc.
14:35:43,498 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
14:35:43,857 INFO [Server] Core system initialized
14:35:45,670 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083
/
14:35:45,670 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resour
ce:jboss-log4j.xml
14:35:46,513 INFO [TransactionManagerService] JBossTS Transaction Service (JTA
version) - JBoss Inc.
14:35:46,513 INFO [TransactionManagerService] Setting up property manager MBean
and JMX layer
14:35:46,701 INFO [TransactionManagerService] Starting recovery manager
14:35:46,748 INFO [TransactionManagerService] Recovery manager started
14:35:46,748 INFO [TransactionManagerService] Binding TransactionManager JNDI R
eference
14:35:50,263 INFO [EJB3Deployer] Starting java:comp multiplexer
14:35:51,607 INFO [NativeServerConfig] JBoss Web Services - Native
14:35:51,622 INFO [NativeServerConfig] jbossws-3.0.1-native-2.0.4.GA (build=200
803312044)
14:35:52,466 INFO [Embedded] Catalina naming disabled
14:35:52,575 INFO [AprLifecycleListener] The Apache Tomcat Native library which
allows optimal performance in production environments was not found on the java
.library.path: C:\WINDOWS\system32;.;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32
;C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
14:35:52,607 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0
.1-8080
14:35:52,607 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-80
09
14:35:52,607 INFO [Catalina] Initialization processed in 147 ms
14:35:52,607 INFO [StandardService] Starting service jboss.web
14:35:52,607 INFO [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.1.GA
14:35:52,638 INFO [Catalina] Server startup in 24 ms
14:35:52,794 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-w
eb.deployer/ROOT.war/
14:35:53,560 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/
http-invoker.sar/invoker.war/
14:35:53,669 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../deploy/
jbossws.sar/jbossws-context.war/
14:35:53,732 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../
deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
14:35:54,153 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../dep
loy/management/console-mgr.sar/web-console.war/
14:35:54,513 INFO [MailService] Mail Service bound to java:/Mail
14:35:54,669 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/jboss-ha-local-jdbc.rar
14:35:54,763 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/jboss-ha-xa-jdbc.rar
14:35:54,856 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/jboss-local-jdbc.rar
14:35:54,935 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/jboss-xa-jdbc.rar
14:35:55,544 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/jms/jms-ra.rar
14:35:55,716 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/mail-ra.rar
14:35:55,903 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/quartz-ra.rar
14:35:55,903 INFO [QuartzResourceAdapter] start quartz!!!
14:35:55,950 INFO [SimpleThreadPool] Job execution threads will use class loade
r of thread: main
14:35:55,950 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
14:35:55,966 INFO [RAMJobStore] RAMJobStore initialized.
14:35:55,966 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzSchedule
r' initialized from default resource file in Quartz package: 'quartz.properties'
14:35:55,966 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
14:35:55,966 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUS
TERED started.
14:35:56,966 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jb
oss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
14:35:57,200 INFO [A] Bound to JNDI name: queue/A
14:35:57,200 INFO [B] Bound to JNDI name: queue/B
14:35:57,200 INFO [C] Bound to JNDI name: queue/C
14:35:57,200 INFO [D] Bound to JNDI name: queue/D
14:35:57,200 INFO [ex] Bound to JNDI name: queue/ex
14:35:57,216 INFO [testTopic] Bound to JNDI name: topic/testTopic
14:35:57,216 INFO [securedTopic] Bound to JNDI name: topic/securedTopic
14:35:57,216 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic
14:35:57,216 INFO [testQueue] Bound to JNDI name: queue/testQueue
14:35:57,231 INFO [UILServerILService] JBossMQ UIL service available at : /127.
0.0.1:8093
14:35:57,263 INFO [DLQ] Bound to JNDI name: queue/DLQ
14:35:57,341 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jb
oss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
14:35:57,794 INFO [TomcatDeployer] deploy, ctxPath=/drools-guvnor, warUrl=.../d
eploy/drools-guvnor.war/
14:36:08,965 INFO [TomcatDeployer] deploy, ctxPath=/drools-server, warUrl=.../d
eploy/drools-server.war/
14:36:09,012 WARN [config] Unable to process deployment descriptor for context
'/drools-server'
14:36:09,371 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../dep
loy/jmx-console.war/
14:36:09,496 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8
080
14:36:09,512 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
14:36:09,512 INFO [Server] JBoss (MX MicroKernel) [4.2.3.GA (build: SVNTag=JBos
s_4_2_3_GA date=200807181417)] Started in 26s:201ms
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] Created: (JBRULES-2683) DroolsSession's initWorkItemManagerFactory method can not work in a OSGi context
by Antoine Toulme (JIRA)
DroolsSession's initWorkItemManagerFactory method can not work in a OSGi context
--------------------------------------------------------------------------------
Key: JBRULES-2683
URL: https://jira.jboss.org/browse/JBRULES-2683
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core
Affects Versions: 5.2.0.M1
Reporter: Antoine Toulme
Assignee: Mark Proctor
Fix For: FUTURE
This affects the current trunk.
The code in the method does this:
String className = this.chainedProperties.getProperty( "drools.workItemManagerFactory",
"org.drools.process.instance.impl.DefaultWorkItemManagerFactory" );
[..]
clazz = (Class<WorkItemManagerFactory>) Thread.currentThread().getContextClassLoader().loadClass( className );
[..]
clazz = (Class<WorkItemManagerFactory>) SessionConfiguration.class.getClassLoader().loadClass( className );
None of this can work for the default factory since drools-core does not depend on drools-flow-core (and creating a dependency would create a cycle). Actually, this won't work for customer code as well, since drools-core won't depend on their bundle.
I suggest to use a declarative service to work around this problem, while keeping this type of instantiation around when OSGi is not on.
--
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
12 years, 7 months