[JBoss JIRA] Created: (JBAS-9388) Error while opening an URLConnection
by Prasad Deshpande (JIRA)
Error while opening an URLConnection
------------------------------------
Key: JBAS-9388
URL: https://issues.jboss.org/browse/JBAS-9388
Project: Legacy JBoss Application Server 6
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 6.1.0
Environment: Windows XP, JBoss 6.1.0, Sun JDK 1.6.0_22
Reporter: Prasad Deshpande
Hi, I'm trying to open a file using URLConnection inside a servlet & it throws me following exception. I'm using jboss-6.1.0-SNAPSHOT on windows platform.
java.net.URISyntaxException: Illegal character in opaque part at index 7: file:D:\jboss-5.1.0-SVN\eFp\eFp-Current\server.properties
Not sure if anyone has tried it before. File URL seems to be correct but still I get above exception. Could anyone please highlight? Please ignore the path of the file even if it says jboss-5.1.0 I just have a directory with that name, it has nothing to do with actual 5.1.0 version.
I'm also attaching my servlet code.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 12 months
[JBoss JIRA] Created: (JBRULES-2944) Redeployment of Drools ActionHandler leads to Exception when building rules package (classLoader is not connected to a domain)
by Bernd Ruecker (JIRA)
Redeployment of Drools ActionHandler leads to Exception when building rules package (classLoader is not connected to a domain)
------------------------------------------------------------------------------------------------------------------------------
Key: JBRULES-2944
URL: https://issues.jboss.org/browse/JBRULES-2944
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core
Affects Versions: 5.0.1.FINAL
Environment: JBoss SOA-P 5.0.0
Reporter: Bernd Ruecker
Assignee: Mark Proctor
See forum entry as well.
We have an jBPM 3 Action Handler calling Drools. Drools and jBPM itself are deployed as esb archive. The ActionHandler is part of the application and normally deployed within an EAR (but we tested a plain jar and an esb as well).
When redeploying the ActionHandler, it leads to an exception, which indicates, that somehow Drools internally have cached an old classloader:
org.drools.RuntimeDroolsException: java.lang.IllegalStateException: BaseClassLoader@14f744d{vfszip:xxx.ear/} classLoader is not connected to a domain (probably undeployed?) for class org.drools.base.extractors.BaseObjectClassFieldReader
at org.drools.base.ClassFieldAccessorFactory.getClassFieldReader(ClassFieldAccessorFactory.java:152)
at org.drools.base.ClassFieldAccessorCache$CacheEntry.getReadAccessor(ClassFieldAccessorCache.java:315)
at org.drools.base.ClassFieldAccessorCache.getReadAcessor(ClassFieldAccessorCache.java:245)
at org.drools.base.ClassFieldAccessorStore.wire(ClassFieldAccessorStore.java:379)
at org.drools.base.ClassFieldAccessorStore.merge(ClassFieldAccessorStore.java:270)
at org.drools.compiler.PackageBuilder.addPackage(PackageBuilder.java:739)
at org.drools.compiler.PackageBuilder.addKnowledgeResource(PackageBuilder.java:515)
at org.drools.builder.impl.KnowledgeBuilderImpl.add(KnowledgeBuilderImpl.java:25)
at xxx.jbpm.actions.FireRules.createRulesContext(FireRules.java:94)
at xxx.jbpm.actions.FireRules.executeAction(FireRules.java:51)
at xxx.jbpm.actions.AbstractGeneralActionHandler.execute(AbstractGeneralActionHandler.java:43)
at org.jbpm.graph.def.Action.execute(Action.java:118)
....
I have seen that the code around this has changed in 5.2-SNAPSHOT, but I am not sure, if that fixes the problem and I cannot easily test this. Could somebody of you have a look? Otherwise it is a serious bug!
Quick addition: We had the problem not only when adding rules from DRL files but as well when using Guvnor.
Thanks
Bernd
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 12 months
[JBoss JIRA] Created: (JBRULES-2918) MVEL issue - inline with broken since 5.0.1
by Damon Horrell (JIRA)
MVEL issue - inline with broken since 5.0.1
-------------------------------------------
Key: JBRULES-2918
URL: https://issues.jboss.org/browse/JBRULES-2918
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-compiler
Affects Versions: 5.1.1.FINAL
Reporter: Damon Horrell
Assignee: Mark Proctor
Rules that used to compile in 5.0.1 no longer do in 5.1.1. The MVEL "inline with operator" now doesn't support accessing objects in an outer scope.
I have tried using Drools 5.1.1 with MVEL 2.0.10 but the error is still the same so the problem seems to be in Drools not in MVEL.
------------
rule "create person"
dialect "mvel"
when
raw : Map();
then
person = new TestPerson().{
name = raw["First Name"] + " " + raw["Last Name"],
dateOfBirth = stringToDate(raw["DOB"])
};
insert(person);
end
------------
Caused by: [Error: unable to resolve method: au.com.rpdata.processor.data.TestPerson.raw() [arglength=0]]
[Near : {... Unknown ....}]
^
[Line: 1, Column: 0]
at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.getMethod(ReflectiveAccessorOptimizer.java:932)
at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.getBeanProperty(ReflectiveAccessorOptimizer.java:592)
at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.getCollectionProperty(ReflectiveAccessorOptimizer.java:609)
at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.compileGetChain(ReflectiveAccessorOptimizer.java:317)
at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.optimizeAccessor(ReflectiveAccessorOptimizer.java:137)
at org.mvel2.ast.ASTNode.getReducedValueAccelerated(ASTNode.java:137)
at org.mvel2.ast.BinaryOperation.getReducedValueAccelerated(BinaryOperation.java:111)
at org.mvel2.ast.BinaryOperation.getReducedValueAccelerated(BinaryOperation.java:111)
at org.mvel2.compiler.ExecutableAccessor.getValue(ExecutableAccessor.java:37)
at org.mvel2.optimizers.impl.refl.nodes.WithAccessor.processWith(WithAccessor.java:64)
at org.mvel2.optimizers.impl.refl.nodes.WithAccessor.getValue(WithAccessor.java:50)
at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.getWithProperty(ReflectiveAccessorOptimizer.java:409)
at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.compileGetChain(ReflectiveAccessorOptimizer.java:320)
at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.compileConstructor(ReflectiveAccessorOptimizer.java:1141)
at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.optimizeObjectCreation(ReflectiveAccessorOptimizer.java:1070)
at org.mvel2.ast.NewObjectNode.getReducedValueAccelerated(NewObjectNode.java:160)
at org.mvel2.compiler.ExecutableAccessor.getValue(ExecutableAccessor.java:37)
at org.mvel2.ast.AssignmentNode.getReducedValueAccelerated(AssignmentNode.java:89)
at org.mvel2.MVELRuntime.execute(MVELRuntime.java:85)
at org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:104)
at org.mvel2.MVEL.executeExpression(MVEL.java:1001)
at org.drools.base.mvel.MVELConsequence.evaluate(MVELConsequence.java:103)
at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:917)
at org.drools.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:856)
at org.drools.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1071)
at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:785)
at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:751)
at org.drools.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:218)
at au.com.rpdata.processor.impl.DroolsMapTransformer.transform(DroolsMapTransformer.java:110)
... 29 more
------
Can you please advise if there is a syntax workaround to inform the compiler that the object referred to is in a different scope?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 12 months
[JBoss JIRA] Created: (JBRULES-2398) Rule not fired when using 'in (0)' condition and another rule with condition ' == null' exists
by Jaroslaw Wosik (JIRA)
Rule not fired when using 'in (0)' condition and another rule with condition ' == null' exists
----------------------------------------------------------------------------------------------
Key: JBRULES-2398
URL: https://jira.jboss.org/jira/browse/JBRULES-2398
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-compiler (expert)
Affects Versions: 5.0.1.FINAL
Environment: Windows Xp Pro, Java 1.5.07
Reporter: Jaroslaw Wosik
Assignee: Mark Proctor
When following package is used:
package BROKEN_TEST;
import pl.wosik.conversion.BrokenTest.Holder;
rule "_12"
salience 3
activation-group "BROKEN"
when
$a : Holder(value in (0))
then
System.out.println("setting 0");
$a.setOutcome("setting 0");
end
rule "_13"
salience 2
activation-group "BROKEN"
when
$a : Holder(value in (1))
then
System.out.println("setting 1");
$a.setOutcome("setting 1");
end
rule "_22"
salience 1
activation-group "BROKEN"
when
$a : Holder(value == null)
then
System.out.println("setting null");
$a.setOutcome("setting null");
end
Rule "_12" will not be fired even when Holder.value is 0 because some strange interference between it's and rule _22's condition (note that _22 won't be fired as expected).
When "Holder(value in (0))" is changed into "Holder(value == 0)" or "Holder(value in (0,9))" or the whole rule_22 is removed rule _12 will be fired.
This issue is important as such seemingly strange "in (0)" condition can be generated from a decision table (as was in my case).
I will attach a self-contained Test Case.
--
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
14 years, 12 months
[JBoss JIRA] Created: (JBRULES-2781) Optimization for sub-attributes in LHS conditions
by Frederico Ramos (JIRA)
Optimization for sub-attributes in LHS conditions
-------------------------------------------------
Key: JBRULES-2781
URL: https://jira.jboss.org/browse/JBRULES-2781
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-compiler, drools-core
Affects Versions: 5.1.0.FINAL
Environment: Windows XP & 7 Pro, Eclipse Galileo, JDK 1.6 update 21
Reporter: Frederico Ramos
Assignee: Mark Proctor
Priority: Minor
When building a simple rule, we discovered that the resulting "rete tree" did not reused some node conditions, dispite they are listed in the same order. After some different approaches we get to the expected tree using explicit predicates.
Shouldn't both alternatives generate the same tree? And if don't, can some optimization be created in Drools CORE to handle this?
Note that although the tree is different, it uses the same node types.
OPTION 1: OPTIMIZED RETE TREE
------
{{{
#created on: 09/11/2010
package aa
#list any import classes here.
import br.com.auster.om.invoice.telco.CallDetail;
import br.com.auster.om.invoice.telco.ServiceTypeEnum;
import br.com.auster.om.util.UnitCounter;
import br.com.auster.om.util.UnitCounter.TypeOfUnitEnum;
import br.com.auster.om.invoice.telco.TelcoCustomer;
rule "call duration check 1"
when
CallDetail( serviceType == ServiceTypeEnum.VOICE,
$realDuration : realDuration -> ($realDuration.getType() == TypeOfUnitEnum.TIME),
$billedDuration : billedDuration -> ($billedDuration.getType() == TypeOfUnitEnum.TIME),
realDuration.seconds <= 3 )
then
// TODO
end
rule "call duration check 2"
when
CallDetail( serviceType == ServiceTypeEnum.VOICE,
$realDuration : realDuration -> ($realDuration.getType() == TypeOfUnitEnum.TIME),
$billedDuration : billedDuration -> ($billedDuration.getType() == TypeOfUnitEnum.TIME),
realDuration.seconds > 3 )
then
// TODO
end
rule "call-duration-check - realDuration > 30"
when
CallDetail( serviceType == ServiceTypeEnum.VOICE,
$realDuration : realDuration -> ($realDuration.getType() == TypeOfUnitEnum.TIME),
$billedDuration : billedDuration -> ($billedDuration.getType() == TypeOfUnitEnum.TIME),
realDuration.seconds > 30 )
then
// TODO
end
}}}
OPTION 2: NOT-OPTIMIZED RETE TREE
------
{{{
#created on: 09/11/2010
package aa
#list any import classes here.
import br.com.auster.om.invoice.telco.CallDetail;
import br.com.auster.om.invoice.telco.ServiceTypeEnum;
import br.com.auster.om.util.UnitCounter;
import br.com.auster.om.util.UnitCounter.TypeOfUnitEnum;
import br.com.auster.om.invoice.telco.TelcoCustomer;
rule "call duration check 1"
when
CallDetail( serviceType == ServiceTypeEnum.VOICE,
$realDuration : realDuration.type == TypeOfUnitEnum.TIME,
$billedDuration : billedDuration.type == TypeOfUnitEnum.TIME,
realDuration.seconds <= 3 )
then
// TODO
end
rule "call duration check 2"
when
CallDetail( serviceType == ServiceTypeEnum.VOICE,
$realDuration : realDuration.type == TypeOfUnitEnum.TIME,
$billedDuration : billedDuration.type == TypeOfUnitEnum.TIME,
realDuration.seconds > 3 )
then
// TODO
end
rule "call-duration-check - realDuration > 30"
when
CallDetail( serviceType == ServiceTypeEnum.VOICE,
$realDuration : realDuration.type == TypeOfUnitEnum.TIME,
$billedDuration : billedDuration.type == TypeOfUnitEnum.TIME,
realDuration.seconds > 30 )
then
// TODO
end
}}}
--
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
15 years