March 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-79) ClassCastException when compiling a rule

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-79?page=com.atlassian.jira.plugin.... ] Mario Fusco resolved DROOLS-79. ------------------------------- Fix Version/s: 5.6 6.0.0.Alpha1 Resolution: Done > ClassCastException when compiling a rule > ---------------------------------------- > > Key: DROOLS-79 > URL: https://issues.jboss.org/browse/DROOLS-79 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5 > Reporter: Radai Rosenblatt > Assignee: Mario Fusco > Fix For: 5.6, 6.0.0.Alpha1 > > Attachments: JBRULES-79.zip > > > when compiling a rule on jboss i see this exception printed out to the log: > 2013-03-13 10:54:37,517 ERROR [stderr] (Thread-264) Exception in thread "Thread-264" java.lang.ClassCastException: org.mvel2.compiler.ExecutableLiteral cannot be cast to org.mvel2.compiler.ExecutableAccessor > 2013-03-13 10:54:37,517 ERROR [stderr] (Thread-264) at org.drools.rule.constraint.ConditionAnalyzer.analyzeNode(ConditionAnalyzer.java:173) > 2013-03-13 10:54:37,517 ERROR [stderr] (Thread-264) at org.drools.rule.constraint.ConditionAnalyzer.analyzeNode(ConditionAnalyzer.java:174) > 2013-03-13 10:54:37,517 ERROR [stderr] (Thread-264) at org.drools.rule.constraint.ConditionAnalyzer.analyzeNode(ConditionAnalyzer.java:169) > 2013-03-13 10:54:37,517 ERROR [stderr] (Thread-264) at org.drools.rule.constraint.ConditionAnalyzer.analyzeNode(ConditionAnalyzer.java:169) > 2013-03-13 10:54:37,517 ERROR [stderr] (Thread-264) at org.drools.rule.constraint.ConditionAnalyzer.analyzeSingleCondition(ConditionAnalyzer.java:108) > 2013-03-13 10:54:37,517 ERROR [stderr] (Thread-264) at org.drools.rule.constraint.ConditionAnalyzer.analyzeCondition(ConditionAnalyzer.java:99) > 2013-03-13 10:54:37,518 ERROR [stderr] (Thread-264) at org.drools.rule.constraint.ConditionAnalyzer.analyzeCondition(ConditionAnalyzer.java:70) > 2013-03-13 10:54:37,518 ERROR [stderr] (Thread-264) at org.drools.rule.constraint.MvelConditionEvaluator.getAnalyzedCondition(MvelConditionEvaluator.java:83) > 2013-03-13 10:54:37,673 ERROR [stderr] (Thread-264) at org.drools.rule.constraint.MvelConstraint.executeJitting(MvelConstraint.java:270) > 2013-03-13 10:54:37,673 ERROR [stderr] (Thread-264) at org.drools.rule.constraint.MvelConstraint.access$200(MvelConstraint.java:51) > 2013-03-13 10:54:37,673 ERROR [stderr] (Thread-264) at org.drools.rule.constraint.MvelConstraint$ConditionJitter.run(MvelConstraint.java:250) > 2013-03-13 10:54:37,673 ERROR [stderr] (Thread-264) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > 2013-03-13 10:54:37,673 ERROR [stderr] (Thread-264) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > 2013-03-13 10:54:37,673 ERROR [stderr] (Thread-264) at java.lang.Thread.run(Thread.java:722) > attached to this bug is a maven project that reproduces the issue consistently -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-79) ClassCastException when compiling a rule

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-79?page=com.atlassian.jira.plugin.... ] Mario Fusco reassigned DROOLS-79: --------------------------------- Assignee: Mario Fusco (was: Mark Proctor) > ClassCastException when compiling a rule > ---------------------------------------- > > Key: DROOLS-79 > URL: https://issues.jboss.org/browse/DROOLS-79 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5 > Reporter: Radai Rosenblatt > Assignee: Mario Fusco > Attachments: JBRULES-79.zip > > > when compiling a rule on jboss i see this exception printed out to the log: > 2013-03-13 10:54:37,517 ERROR [stderr] (Thread-264) Exception in thread "Thread-264" java.lang.ClassCastException: org.mvel2.compiler.ExecutableLiteral cannot be cast to org.mvel2.compiler.ExecutableAccessor > 2013-03-13 10:54:37,517 ERROR [stderr] (Thread-264) at org.drools.rule.constraint.ConditionAnalyzer.analyzeNode(ConditionAnalyzer.java:173) > 2013-03-13 10:54:37,517 ERROR [stderr] (Thread-264) at org.drools.rule.constraint.ConditionAnalyzer.analyzeNode(ConditionAnalyzer.java:174) > 2013-03-13 10:54:37,517 ERROR [stderr] (Thread-264) at org.drools.rule.constraint.ConditionAnalyzer.analyzeNode(ConditionAnalyzer.java:169) > 2013-03-13 10:54:37,517 ERROR [stderr] (Thread-264) at org.drools.rule.constraint.ConditionAnalyzer.analyzeNode(ConditionAnalyzer.java:169) > 2013-03-13 10:54:37,517 ERROR [stderr] (Thread-264) at org.drools.rule.constraint.ConditionAnalyzer.analyzeSingleCondition(ConditionAnalyzer.java:108) > 2013-03-13 10:54:37,517 ERROR [stderr] (Thread-264) at org.drools.rule.constraint.ConditionAnalyzer.analyzeCondition(ConditionAnalyzer.java:99) > 2013-03-13 10:54:37,518 ERROR [stderr] (Thread-264) at org.drools.rule.constraint.ConditionAnalyzer.analyzeCondition(ConditionAnalyzer.java:70) > 2013-03-13 10:54:37,518 ERROR [stderr] (Thread-264) at org.drools.rule.constraint.MvelConditionEvaluator.getAnalyzedCondition(MvelConditionEvaluator.java:83) > 2013-03-13 10:54:37,673 ERROR [stderr] (Thread-264) at org.drools.rule.constraint.MvelConstraint.executeJitting(MvelConstraint.java:270) > 2013-03-13 10:54:37,673 ERROR [stderr] (Thread-264) at org.drools.rule.constraint.MvelConstraint.access$200(MvelConstraint.java:51) > 2013-03-13 10:54:37,673 ERROR [stderr] (Thread-264) at org.drools.rule.constraint.MvelConstraint$ConditionJitter.run(MvelConstraint.java:250) > 2013-03-13 10:54:37,673 ERROR [stderr] (Thread-264) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > 2013-03-13 10:54:37,673 ERROR [stderr] (Thread-264) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > 2013-03-13 10:54:37,673 ERROR [stderr] (Thread-264) at java.lang.Thread.run(Thread.java:722) > attached to this bug is a maven project that reproduces the issue consistently -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-62) Is there anyway to control standalone/tmp/vfs folder incresing size?

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-62?page=com.atlassian.jira.plugin.... ] David Lloyd resolved LOGMGR-62. ------------------------------- Resolution: Rejected Don't use JIRA to ask questions. Go here instead: https://community.jboss.org/en/jbossas?view=discussions > Is there anyway to control standalone/tmp/vfs folder incresing size? > -------------------------------------------------------------------- > > Key: LOGMGR-62 > URL: https://issues.jboss.org/browse/LOGMGR-62 > Project: JBoss Log Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: core > Reporter: Mahesh Khatal > Assignee: David Lloyd > > Hi, > my application gets sloved b'coz standalone/tmp/vfs folder size gets incresing. Is there any way to come out of this? -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-62) Is there anyway to control standalone/tmp/vfs folder incresing size?

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-62?page=com.atlassian.jira.plugin.... ] David Lloyd updated LOGMGR-62: ------------------------------ Due Date: 1/Apr/13 > Is there anyway to control standalone/tmp/vfs folder incresing size? > -------------------------------------------------------------------- > > Key: LOGMGR-62 > URL: https://issues.jboss.org/browse/LOGMGR-62 > Project: JBoss Log Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: core > Reporter: Mahesh Khatal > Assignee: David Lloyd > > Hi, > my application gets sloved b'coz standalone/tmp/vfs folder size gets incresing. Is there any way to come out of this? -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6549) Remote JNDI is not working with a HornetQ-only JMS bridge

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6549?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6549: ---------------------------------------------- nziakova <nziakova(a)redhat.com> changed the Status of [bug 912653|https://bugzilla.redhat.com/show_bug.cgi?id=912653] from ON_QA to ASSIGNED > Remote JNDI is not working with a HornetQ-only JMS bridge > --------------------------------------------------------- > > Key: AS7-6549 > URL: https://issues.jboss.org/browse/AS7-6549 > Project: Application Server 7 > Issue Type: Feature Request > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.0.Alpha1 > > > The jms-bridge can be used to bridge a hornetq server to another and should work by specifying to use the org.hornetq.module to load the JMS implementation classes. > However, this fails because this module does not have access to the JBoss remote-naming module that is required to connect to remote JBoss JNDI server. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6549) Remote JNDI is not working with a HornetQ-only JMS bridge

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6549?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6549: ---------------------------------------------- nziakova <nziakova(a)redhat.com> made a comment on [bug 912653|https://bugzilla.redhat.com/show_bug.cgi?id=912653] JMS bridge still could not be started. See configuration and log of both source and target servers in attachment. > Remote JNDI is not working with a HornetQ-only JMS bridge > --------------------------------------------------------- > > Key: AS7-6549 > URL: https://issues.jboss.org/browse/AS7-6549 > Project: Application Server 7 > Issue Type: Feature Request > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.0.Alpha1 > > > The jms-bridge can be used to bridge a hornetq server to another and should work by specifying to use the org.hornetq.module to load the JMS implementation classes. > However, this fails because this module does not have access to the JBoss remote-naming module that is required to connect to remote JBoss JNDI server. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6615) Invalid definition for HC root resource remote domain controller

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/AS7-6615?page=com.atlassian.jira.plugin.s... ] Kabir Khan edited comment on AS7-6615 at 3/28/13 8:44 AM: ---------------------------------------------------------- I have done the definition part as part of my work on "better ignoring of non-affected slave data" AS7-6808 was (Author: kabirkhan): I have done the definition part as part of my work on "better ignoring of non-affected slave data" > Invalid definition for HC root resource remote domain controller > ---------------------------------------------------------------- > > Key: AS7-6615 > URL: https://issues.jboss.org/browse/AS7-6615 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Brian Stansberry > Assignee: Kabir Khan > Fix For: 8.0.0.Alpha1 > > > HostResourceDefinition.DC_REMOTE does not include the security-realm and username fields. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1018) code generation for eclipse plugin about JCA 1.7

by Jeff Zhang (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1018?page=com.atlassian.jira.plugin... ] Jeff Zhang reassigned JBJCA-1018: --------------------------------- Assignee: Lin Gao (was: Jeff Zhang) > code generation for eclipse plugin about JCA 1.7 > ------------------------------------------------ > > Key: JBJCA-1018 > URL: https://issues.jboss.org/browse/JBJCA-1018 > Project: IronJacamar > Issue Type: Task > Components: Eclipse > Affects Versions: 1.1.0.Beta4 > Reporter: Jeff Zhang > Assignee: Lin Gao > Fix For: 1.1.0.Beta5 > > -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBMESSAGING-1943) HeuristicMixedException gets thrown if the destination has reached its maxsize

by Yong Hao Gao (JIRA)

[ https://issues.jboss.org/browse/JBMESSAGING-1943?page=com.atlassian.jira.... ] Yong Hao Gao closed JBMESSAGING-1943. ------------------------------------- Resolution: Done > HeuristicMixedException gets thrown if the destination has reached its maxsize > ------------------------------------------------------------------------------ > > Key: JBMESSAGING-1943 > URL: https://issues.jboss.org/browse/JBMESSAGING-1943 > Project: JBoss Messaging > Issue Type: Bug > Components: Messaging Core > Affects Versions: 1.4.8.SP5 > Environment: JBoss-EAP-5.1.2, JBossMessaging-1.4.8-SP5, JBossTS-4.6.1GA-CP11 +JBTM-842 &J BTM-924 > Reporter: Tyronne Wickramarathne > Assignee: Yong Hao Gao > Labels: JMS, Transactions > Fix For: 1.4.8.SP10 > > > The message producer throws a HeuristicMixedException when trying to send messages to a destination which has reached its maxsize. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBMESSAGING-1943) HeuristicMixedException gets thrown if the destination has reached its maxsize

by Yong Hao Gao (JIRA)

[ https://issues.jboss.org/browse/JBMESSAGING-1943?page=com.atlassian.jira.... ] Yong Hao Gao updated JBMESSAGING-1943: -------------------------------------- Fix Version/s: 1.4.8.SP10 > HeuristicMixedException gets thrown if the destination has reached its maxsize > ------------------------------------------------------------------------------ > > Key: JBMESSAGING-1943 > URL: https://issues.jboss.org/browse/JBMESSAGING-1943 > Project: JBoss Messaging > Issue Type: Bug > Components: Messaging Core > Affects Versions: 1.4.8.SP5 > Environment: JBoss-EAP-5.1.2, JBossMessaging-1.4.8-SP5, JBossTS-4.6.1GA-CP11 +JBTM-842 &J BTM-924 > Reporter: Tyronne Wickramarathne > Assignee: Yong Hao Gao > Labels: JMS, Transactions > Fix For: 1.4.8.SP10 > > > The message producer throws a HeuristicMixedException when trying to send messages to a destination which has reached its maxsize. -- 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

11 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2013