September 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9393) Upgrade JGroups to 3.6.14.Final

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9393?page=com.atlassian.jira.plugin.... ] Radoslav Husar reassigned WFLY-9393: ------------------------------------ Assignee: Radoslav Husar (was: Paul Ferraro) > Upgrade JGroups to 3.6.14.Final > ------------------------------- > > Key: WFLY-9393 > URL: https://issues.jboss.org/browse/WFLY-9393 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Affects Versions: 11.0.0.CR1 > Reporter: Leandro Kersting de Freitas > Assignee: Radoslav Husar > Fix For: 11.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6973) Upgrade Infinispan to 9.x

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6973?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on WFLY-6973: -------------------------------------- [~sannegrinovero] No, planned for WF 12. > Upgrade Infinispan to 9.x > ------------------------- > > Key: WFLY-6973 > URL: https://issues.jboss.org/browse/WFLY-6973 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Affects Versions: No Release > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 12.0.0.Alpha1 > > > http://blog.infinispan.org/2017/03/infinispan-9.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6973) Upgrade Infinispan to 9.x

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6973?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-6973: --------------------------------- Description: http://blog.infinispan.org/2017/03/infinispan-9.html > Upgrade Infinispan to 9.x > ------------------------- > > Key: WFLY-6973 > URL: https://issues.jboss.org/browse/WFLY-6973 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Affects Versions: No Release > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 12.0.0.Alpha1 > > > http://blog.infinispan.org/2017/03/infinispan-9.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9395) Move ClusteringRequirement to the public API module

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-9395?page=com.atlassian.jira.plugin.... ] Paul Ferraro commented on WFLY-9395: ------------------------------------ The proposal is to create a new public wildfly-clustering-msc module which contains: * singleton service API * clustering api requirement enums > Move ClusteringRequirement to the public API module > --------------------------------------------------- > > Key: WFLY-9395 > URL: https://issues.jboss.org/browse/WFLY-9395 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 11.0.0.CR1 > Reporter: Radoslav Husar > Assignee: Paul Ferraro > > Currently the user needs to rely on using the capability name as service name to establish a dependency, e.g.: > {code:java} > policy.createSingletonServiceBuilder(SINGLETON_SERVICE_NAME, service) > .build(serviceActivatorContext.getServiceTarget()) > .addDependency(ServiceName.parse("org.wildfly.clustering.default-group"), Group.class, group) > .install(); > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9265) Upgrade JGroups to 4.0.7.Final

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9265?page=com.atlassian.jira.plugin.... ] Radoslav Husar closed WFLY-9265. -------------------------------- Resolution: Duplicate Issue Duplicates WFLY-8207 (note that this is already being worked on). > Upgrade JGroups to 4.0.7.Final > ------------------------------ > > Key: WFLY-9265 > URL: https://issues.jboss.org/browse/WFLY-9265 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Reporter: Leandro Kersting de Freitas > Assignee: Paul Ferraro > Fix For: 12.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9265) Upgrade JGroups to 4.0.7.Final

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9265?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9265: --------------------------------- Summary: Upgrade JGroups to 4.0.7.Final (was: Upgrade Jgroups to 4.0.7.Final) > Upgrade JGroups to 4.0.7.Final > ------------------------------ > > Key: WFLY-9265 > URL: https://issues.jboss.org/browse/WFLY-9265 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Reporter: Leandro Kersting de Freitas > Assignee: Paul Ferraro > Fix For: 12.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9393) Upgrade JGroups to 3.6.14.Final

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9393?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9393: --------------------------------- Summary: Upgrade JGroups to 3.6.14.Final (was: Upgrade Jgroups to 3.6.14.Final) > Upgrade JGroups to 3.6.14.Final > ------------------------------- > > Key: WFLY-9393 > URL: https://issues.jboss.org/browse/WFLY-9393 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Affects Versions: 11.0.0.CR1 > Reporter: Leandro Kersting de Freitas > Assignee: Paul Ferraro > Fix For: 11.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9393) Upgrade JGroups to 3.6.14.Final

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9393?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9393: --------------------------------- Affects Version/s: 11.0.0.CR1 > Upgrade JGroups to 3.6.14.Final > ------------------------------- > > Key: WFLY-9393 > URL: https://issues.jboss.org/browse/WFLY-9393 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Affects Versions: 11.0.0.CR1 > Reporter: Leandro Kersting de Freitas > Assignee: Paul Ferraro > Fix For: 11.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9395) Move ClusteringRequirement to the public API module

by Radoslav Husar (JIRA)

Radoslav Husar created WFLY-9395: ------------------------------------ Summary: Move ClusteringRequirement to the public API module Key: WFLY-9395 URL: https://issues.jboss.org/browse/WFLY-9395 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 11.0.0.CR1 Reporter: Radoslav Husar Assignee: Paul Ferraro Currently the user needs to rely on using the capability name as service name to establish a dependency, e.g.: {code:java} policy.createSingletonServiceBuilder(SINGLETON_SERVICE_NAME, service) .build(serviceActivatorContext.getServiceTarget()) .addDependency(ServiceName.parse("org.wildfly.clustering.default-group"), Group.class, group) .install(); {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-785) no MVEL debugger registered to handle breakpoint

by Peter Durica (JIRA)

[ https://issues.jboss.org/browse/DROOLS-785?page=com.atlassian.jira.plugin... ] Peter Durica commented on DROOLS-785: ------------------------------------- Drools version 6.5.0.Final, Eclipse 4.6 Neon: The problem is in this class: {{org.drools.core.base.mvel.MVELDebugHandler}} This class is a Debug bridge between the Drools and MVEL engine. It registers the debugger instance (MVELDebugger) to the MVEL engine: {{ public static void setDebugMode(boolean b) { debugMode = Boolean.valueOf( b ); if (debugMode) { if (!MVELRuntime.hasDebuggerContext()) { MVELRuntime.setThreadDebugger(new MVELDebugger()); } } else { MVELRuntime.resetDebugger(); } System.setProperty( DEBUG_LAUNCH_KEY, debugMode.toString()); } }} The problem is with the line {{MVELRuntime.hasDebuggerContext()}} it always returns true as the MVELRuntime is initialized with the default context so the Drools debugger is never set. After patching this class the debugging seems to work: {{public static void setDebugMode(boolean b) { debugMode = Boolean.valueOf( b ); if (debugMode) { MVELRuntime.setThreadDebugger(new MVELDebugger()); } else { MVELRuntime.resetDebugger(); } System.setProperty( DEBUG_LAUNCH_KEY, debugMode.toString()); }}} If somebody finds a better solution for this problem, please post it here. > no MVEL debugger registered to handle breakpoint > ------------------------------------------------ > > Key: DROOLS-785 > URL: https://issues.jboss.org/browse/DROOLS-785 > Project: Drools > Issue Type: Bug > Components: core engine, eclipse plugin > Affects Versions: 6.2.0.Final, 6.3.0.Final > Environment: Win 7 64, JBoss Developer Studio Version: 8.1.0.GA, JBossAS Tools 3.0.3.Final-v20150325-0035-B129, Java 1.7.0_76 > Reporter: Maurice Betzel > Assignee: Petr Široký > > Executing Drools-Examples 6.0.2.Final from github containing MVEL dialect resulted in runtime exception: > 2015-05-16 14:35:28,603 [main] INFO Found kmodule: file:/C:/Users/x3.mbetzel/Development/workspaces/jboss-drools/drools-examples-62/target/classes/META-INF/kmodule.xml > 2015-05-16 14:35:28,999 [main] INFO KieModule was added: FileKieModule[releaseId=org.drools:drools-examples:6.2.0.Final,file=C:\Users\x3.mbetzel\Development\workspaces\jboss-drools\drools-examples-62\target\classes] > Exception in thread "main" java.lang.RuntimeException: no debugger registered to handle breakpoint > at org.mvel2.debug.DebuggerContext.checkBreak(DebuggerContext.java:98) > at org.mvel2.MVELRuntime.execute(MVELRuntime.java:76) > 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.core.util.MVELSafeHelper$RawMVELEvaluator.executeExpression(MVELSafeHelper.java:481) > at org.drools.core.rule.constraint.MvelConditionEvaluator.evaluate(MvelConditionEvaluator.java:77) > at org.drools.core.rule.constraint.MvelConditionEvaluator.evaluate(MvelConditionEvaluator.java:62) > at org.drools.core.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:230) > at org.drools.core.rule.constraint.MvelConstraint.isAllowed(MvelConstraint.java:187) > at org.drools.core.reteoo.AlphaNode.assertObject(AlphaNode.java:141) > at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateAssertObject(CompositeObjectSinkAdapter.java:504) > at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:379) > at org.drools.core.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:290) > at org.drools.core.reteoo.EntryPointNode.assertObject(EntryPointNode.java:253) > at org.drools.core.common.NamedEntryPoint.insert(NamedEntryPoint.java:370) > at org.drools.core.common.NamedEntryPoint.insert(NamedEntryPoint.java:289) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:1480) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:1422) > at org.drools.examples.helloworld.HelloWorldExample.main(HelloWorldExample.java:65) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2017