January 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-9) Exception in User-defined Java method when rules are optimized by the JIT compiler

by Andreas Bentele (JIRA)

[ https://issues.jboss.org/browse/DROOLS-9?page=com.atlassian.jira.plugin.s... ] Andreas Bentele updated DROOLS-9: --------------------------------- Steps to Reproduce: - compile the attached project: open with Eclipse, or compile with maven - start the java class /DroolsJITTestCase/src/main/java/com/sample/DroolsTest.java as an Application - you will see this output: SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. Service.getAllTimers Service.getAllTimers Service.getAllTimers Service.getAllTimers Service.getAllTimers Service.getAllTimers Service.getAllTimers Service.getAllTimers Service.getAllTimers Service.getAllTimers Service.getAllTimers Service.getAllTimers Service.getAllTimers Service.getAllTimers Service.getAllTimers Service.getAllTimers Service.getAllTimers Service.getAllTimers Service.getAllTimers Service.getAllTimers Exception in thread "Thread-0" [Error: service.getTimePerStroke($service.getLongValue(service.workplaceIdForMachineId($machineId, $actionTimestamp), "RC.WORKPLACE_LEADING_OPERATION_ID")): null] [Near : {... $service.getLongValue(service. ....}] ^ [Line: 1, Column: 1] at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.compileGetChain(ReflectiveAccessorOptimizer.java:416) at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.optimizeAccessor(ReflectiveAccessorOptimizer.java:143) at org.mvel2.ast.ASTNode.optimize(ASTNode.java:159) at org.mvel2.ast.ASTNode.getReducedValueAccelerated(ASTNode.java:115) at org.mvel2.ast.BinaryOperation.getReducedValueAccelerated(BinaryOperation.java:108) at org.mvel2.MVELRuntime.execute(MVELRuntime.java:85) at org.mvel2.compiler.CompiledExpression.getDirectValue(CompiledExpression.java:123) at org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:119) at org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:113) at org.mvel2.MVEL.executeExpression(MVEL.java:930) at org.drools.rule.constraint.MvelConditionEvaluator.evaluate(MvelConditionEvaluator.java:70) at org.drools.rule.constraint.MvelConditionEvaluator.ensureBranchEvaluation(MvelConditionEvaluator.java:117) at org.drools.rule.constraint.MvelConditionEvaluator.ensureCompleteEvaluation(MvelConditionEvaluator.java:102) at org.drools.rule.constraint.MvelConditionEvaluator.ensureCompleteEvaluation(MvelConditionEvaluator.java:90) at org.drools.rule.constraint.MvelConditionEvaluator.getAnalyzedCondition(MvelConditionEvaluator.java:82) at org.drools.rule.constraint.MvelConstraint.executeJitting(MvelConstraint.java:270) at org.drools.rule.constraint.MvelConstraint.access$200(MvelConstraint.java:51) at org.drools.rule.constraint.MvelConstraint$ConditionJitter.run(MvelConstraint.java:250) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.getMethod(ReflectiveAccessorOptimizer.java:1104) at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.getMethod(ReflectiveAccessorOptimizer.java:987) at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.compileGetChain(ReflectiveAccessorOptimizer.java:377) ... 20 more Caused by: java.lang.RuntimeException at com.sample.Service.getTimePerStroke(Service.java:42) ... 27 more > Exception in User-defined Java method when rules are optimized by the JIT compiler > ----------------------------------------------------------------------------------- > > Key: DROOLS-9 > URL: https://issues.jboss.org/browse/DROOLS-9 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Andreas Bentele > Assignee: Mark Proctor > Attachments: DroolsJITTestCase.zip > > > I watched this issue after upgrading from Drools 5.3.1 to Drools 5.5.0.Final. > I didn't find any trivial example, so I reproduced the error with a non-trivial test case, and attached the test case to this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-9) Exception in User-defined Java method when rules are optimized by the JIT compiler

by Andreas Bentele (JIRA)

[ https://issues.jboss.org/browse/DROOLS-9?page=com.atlassian.jira.plugin.s... ] Andreas Bentele updated DROOLS-9: --------------------------------- Description: I watched this issue after upgrading from Drools 5.3.1 to Drools 5.5.0.Final. I didn't find any trivial example, so I reproduced the error with a non-trivial test case, and attached the test case to this issue. was: I watched this issue after upgrading from Drools 5.3.1 to Drools 5.5.0.Final. I didn't find any trivial example, so I reproduced the error with a non-trivial test case, and attached the test case to this issue.  > Exception in User-defined Java method when rules are optimized by the JIT compiler > ----------------------------------------------------------------------------------- > > Key: DROOLS-9 > URL: https://issues.jboss.org/browse/DROOLS-9 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Andreas Bentele > Assignee: Mark Proctor > Attachments: DroolsJITTestCase.zip > > > I watched this issue after upgrading from Drools 5.3.1 to Drools 5.5.0.Final. > I didn't find any trivial example, so I reproduced the error with a non-trivial test case, and attached the test case to this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-9) Exception in User-defined Java method when rules are optimized by the JIT compiler

by Andreas Bentele (JIRA)

Andreas Bentele created DROOLS-9: ------------------------------------ Summary: Exception in User-defined Java method when rules are optimized by the JIT compiler Key: DROOLS-9 URL: https://issues.jboss.org/browse/DROOLS-9 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Andreas Bentele Assignee: Mark Proctor Attachments: DroolsJITTestCase.zip I watched this issue after upgrading from Drools 5.3.1 to Drools 5.5.0.Final. I didn't find any trivial example, so I reproduced the error with a non-trivial test case, and attached the test case to this issue.  -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-9) Exception in User-defined Java method when rules are optimized by the JIT compiler

by Andreas Bentele (JIRA)

[ https://issues.jboss.org/browse/DROOLS-9?page=com.atlassian.jira.plugin.s... ] Andreas Bentele updated DROOLS-9: --------------------------------- Attachment: DroolsJITTestCase.zip > Exception in User-defined Java method when rules are optimized by the JIT compiler > ----------------------------------------------------------------------------------- > > Key: DROOLS-9 > URL: https://issues.jboss.org/browse/DROOLS-9 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Andreas Bentele > Assignee: Mark Proctor > Attachments: DroolsJITTestCase.zip > > > I watched this issue after upgrading from Drools 5.3.1 to Drools 5.5.0.Final. > I didn't find any trivial example, so I reproduced the error with a non-trivial test case, and attached the test case to this issue. >  -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWEB-227) Globally configure a Valve for the whole JBoss.

by Dimitris Andreadis (JIRA)

[ https://issues.jboss.org/browse/JBWEB-227?page=com.atlassian.jira.plugin.... ] Dimitris Andreadis reassigned JBWEB-227: ---------------------------------------- Assignee: Jean-Frederic Clere (was: Remy Maucherat) Same here? :-) > Globally configure a Valve for the whole JBoss. > ----------------------------------------------- > > Key: JBWEB-227 > URL: https://issues.jboss.org/browse/JBWEB-227 > Project: JBoss Web > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Environment: All > Reporter: Mo Zo > Assignee: Jean-Frederic Clere > Labels: as7, web > > Please provide a way to set and configure a Valve globally for all applications within a JBoss by using standard JBoss mechanisms like domain.xml, standalone.xml and DMR. > Now it is only possible to configure it per application. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-715) Release JBoss Negotiation 2.2.2.Final

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-715?page=com.atlassian.jira.plug... ] Darran Lofthouse resolved SECURITY-715. --------------------------------------- Resolution: Done > Release JBoss Negotiation 2.2.2.Final > ------------------------------------- > > Key: SECURITY-715 > URL: https://issues.jboss.org/browse/SECURITY-715 > Project: PicketBox > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Negotiation > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: Negotiation_2_2_2 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWEB-228) Globally configure an Authenticator Valve for the whole JBoss.

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/JBWEB-228?page=com.atlassian.jira.plugin.... ] Jean-Frederic Clere commented on JBWEB-228: ------------------------------------------- yep > Globally configure an Authenticator Valve for the whole JBoss. > -------------------------------------------------------------- > > Key: JBWEB-228 > URL: https://issues.jboss.org/browse/JBWEB-228 > Project: JBoss Web > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: JBossWeb-7.0.0.GA, JBossWeb-7.0.1.GA , JBossWeb-7.0.2.GA, JBossWeb-7.0.9.GA > Reporter: Mo Zo > Assignee: Jean-Frederic Clere > > Please add an option to set and configure an Authenticator (Valve) globally for all applications in a JBoss by using standard JBoss mechanisms like domain.xml, standalone.xml and DMR, so that it would be possible to reference an Authenticator like this: > web.xml > <login-config> > <auth-method>CUSTOM</auth-method> > </login-config> > To achieve this I had to modify: > ...\modules\org\jboss\as\web\main\jbossweb-7.0.X.Final.jar\org\apache\catalina\startup\Authenticators.properties > CUSTOM=<full qualified authenticator class name> > which certainly is not a good way. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWEB-228) Globally configure an Authenticator Valve for the whole JBoss.

by Dimitris Andreadis (JIRA)

[ https://issues.jboss.org/browse/JBWEB-228?page=com.atlassian.jira.plugin.... ] Dimitris Andreadis reassigned JBWEB-228: ---------------------------------------- Assignee: Jean-Frederic Clere (was: Remy Maucherat) I think we need to change the resolution for this issue from Rejected to Resolved? > Globally configure an Authenticator Valve for the whole JBoss. > -------------------------------------------------------------- > > Key: JBWEB-228 > URL: https://issues.jboss.org/browse/JBWEB-228 > Project: JBoss Web > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: JBossWeb-7.0.0.GA, JBossWeb-7.0.1.GA , JBossWeb-7.0.2.GA, JBossWeb-7.0.9.GA > Reporter: Mo Zo > Assignee: Jean-Frederic Clere > > Please add an option to set and configure an Authenticator (Valve) globally for all applications in a JBoss by using standard JBoss mechanisms like domain.xml, standalone.xml and DMR, so that it would be possible to reference an Authenticator like this: > web.xml > <login-config> > <auth-method>CUSTOM</auth-method> > </login-config> > To achieve this I had to modify: > ...\modules\org\jboss\as\web\main\jbossweb-7.0.X.Final.jar\org\apache\catalina\startup\Authenticators.properties > CUSTOM=<full qualified authenticator class name> > which certainly is not a good way. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-717) Get JBoss Negotiation into Maven Central

by Darran Lofthouse (JIRA)

Darran Lofthouse created SECURITY-717: ----------------------------------------- Summary: Get JBoss Negotiation into Maven Central Key: SECURITY-717 URL: https://issues.jboss.org/browse/SECURITY-717 Project: PicketBox Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2_2_3 This will allow the JBoss Negotiation Toolkit to be removed from the project and instead moved to the quick starts making it much easier for end users to deploy and test. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-1833) CLI usability: operations that shutdown the server-side management interface result in "Communication error"

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/AS7-1833?page=com.atlassian.jira.plugin.s... ] Alexey Loubyansky commented on AS7-1833: ---------------------------------------- Here is the pull request https://github.com/jbossas/jboss-as/pull/3808 The cli is now notified when the connection is closed. But this happens asynchronously. I.e. normally the CLI is in the waiting for the user input state and when the notification is received, it can internally switch to the disconnected state but it can't change the prompt to indicate that until the user enters the next line (i.e. it will remain indicating standalone or domain mode). Perhaps, Stale will add some trick to aesh to fix this issue later. The above is mostly for the operations. The commit also adds higher level commands: shutdown and reload. They reflect the operations. The only difference is that they wait/block until the connection has been closed and then return the control to the client. This fixes the prompt issue above (i.e. it's correctly updated during the command execution) but there could still be race conditions. Commands following immediately after reload or 'shutdown --restart=true' might be executed by the CLI before the target has finished the reload/restart since there is no notification of the server/controller being up again. > CLI usability: operations that shutdown the server-side management interface result in "Communication error" > ------------------------------------------------------------------------------------------------------------ > > Key: AS7-1833 > URL: https://issues.jboss.org/browse/AS7-1833 > Project: Application Server 7 > Issue Type: Enhancement > Components: CLI > Affects Versions: 7.0.0.Final, 7.0.1.Final > Reporter: Radoslav Husar > Assignee: Alexey Loubyansky > Priority: Critical > Labels: eap6-ux > Fix For: 7.2.0.CR1 > > > If you shutdown the server, you get an error: > {code} > [standalone@localhost:9999 /] :shutdown > Communication error: Channel closed > Closed connection to localhost:9999 > {code} > Even though its considered by this comment clean - https://issues.jboss.org/browse/AS7-689?focusedCommentId=12614756&page=co... - I is not really clean as you get an error but termination of the channel can be anticipated. Users might be confused now knowing if its an actual error or not. For example take a look at SSH. > The same basic issue exists for the :reload operation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2013