October 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-642) Named Consequences do not respect timers in STREAM mode

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-642?page=com.atlassian.jira.plugin... ] Mario Fusco reassigned DROOLS-642: ---------------------------------- Assignee: Mario Fusco (was: Mark Proctor) > Named Consequences do not respect timers in STREAM mode > ------------------------------------------------------- > > Key: DROOLS-642 > URL: https://issues.jboss.org/browse/DROOLS-642 > Project: Drools > Issue Type: Bug > Reporter: Davide Sottara > Assignee: Mario Fusco > > In the rule: > {code} > when > $a : A() > not B( this after[0,10s] $a ) do[something] > C() > then > then[something] > {code} > No timer node is created for the named consequence, resulting in the named consequence firing immediately, even in STREAM mode -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-639) Multiple declarations of the same fact from different packages are ignored or conflicting

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-639?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-639. -------------------------------- Fix Version/s: 6.2.0.CR2 Resolution: Done Fixed by https://github.com/droolsjbpm/drools/commit/b85fedaad > Multiple declarations of the same fact from different packages are ignored or conflicting > ----------------------------------------------------------------------------------------- > > Key: DROOLS-639 > URL: https://issues.jboss.org/browse/DROOLS-639 > Project: Drools > Issue Type: Bug > Affects Versions: 5.6.0.Final, 6.0.0.Final, 6.1.0.Final, 6.2.0.CR1 > Reporter: Davide Sottara > Assignee: Mario Fusco > Fix For: 6.2.0.CR2 > > > If a fact is (re)declared multiple times from different packages: > {code} > package p1; > declare Foo @propertyReactive end > {code} > and > {code} > package p2; > declare Foo @role(event) end > {code} > The two declarations result in a conflict. > If the DRL files are in the same package, one of the declarations will be lost -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-639) Multiple declarations of the same fact from different packages are ignored or conflicting

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-639?page=com.atlassian.jira.plugin... ] Mario Fusco reassigned DROOLS-639: ---------------------------------- Assignee: Mario Fusco (was: Davide Sottara) > Multiple declarations of the same fact from different packages are ignored or conflicting > ----------------------------------------------------------------------------------------- > > Key: DROOLS-639 > URL: https://issues.jboss.org/browse/DROOLS-639 > Project: Drools > Issue Type: Bug > Affects Versions: 5.6.0.Final, 6.0.0.Final, 6.1.0.Final, 6.2.0.CR1 > Reporter: Davide Sottara > Assignee: Mario Fusco > > If a fact is (re)declared multiple times from different packages: > {code} > package p1; > declare Foo @propertyReactive end > {code} > and > {code} > package p2; > declare Foo @role(event) end > {code} > The two declarations result in a conflict. > If the DRL files are in the same package, one of the declarations will be lost -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3651) permissions.xml is not used

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-3651?page=com.atlassian.jira.plugin.... ] David Lloyd edited comment on WFLY-3651 at 10/27/14 10:45 AM: -------------------------------------------------------------- You cannot have set JAVA_OPTS=%JAVA_OPTS% -Djava.security.manager=default set JAVA_OPTS=%JAVA_OPTS% -Djava.security.policy=/tmp/test.policy as part of your startup scripts, as this way you are overriding server's security manager and hence permissions.xml cannot work. -only thing needed to enable security manager in wildfly is to add -scrmgr to jboss-modules parameters-. was (Author: ctomc): You cannot have set JAVA_OPTS=%JAVA_OPTS% -Djava.security.manager=default set JAVA_OPTS=%JAVA_OPTS% -Djava.security.policy=/tmp/test.policy as part of your startup scripts, as this way you are overriding server's security manager and hence permissions.xml cannot work. only thing needed to enable security manager in wildfly is to add -scrmgr to jboss-modules parameters. > permissions.xml is not used > --------------------------- > > Key: WFLY-3651 > URL: https://issues.jboss.org/browse/WFLY-3651 > Project: WildFly > Issue Type: Bug > Components: Security Manager > Affects Versions: 8.1.0.Final > Environment: Fedora 20, jdk1.7.0_60 > Reporter: Ondrej Kotek > Assignee: David Lloyd > Priority: Blocker > Attachments: permissions-bug-1.0-SNAPSHOT.war > > > With security manager turned on, an application cannot use permissions allowed by permissions.xml configuration -- against EE 7 specification. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3651) permissions.xml is not used

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-3651?page=com.atlassian.jira.plugin.... ] David Lloyd resolved WFLY-3651. ------------------------------- Resolution: Rejected This is a usage problem, not a bug. To use the security manager feature of WildFly with 8.1, all you need to do is configure the security manager subsystem. Using {{-secmgr}} is not required (or supported) for WildFly 8.1, though it will be the preferred mechanism starting with WildFly 9. > permissions.xml is not used > --------------------------- > > Key: WFLY-3651 > URL: https://issues.jboss.org/browse/WFLY-3651 > Project: WildFly > Issue Type: Bug > Components: Security Manager > Affects Versions: 8.1.0.Final > Environment: Fedora 20, jdk1.7.0_60 > Reporter: Ondrej Kotek > Assignee: David Lloyd > Priority: Blocker > Attachments: permissions-bug-1.0-SNAPSHOT.war > > > With security manager turned on, an application cannot use permissions allowed by permissions.xml configuration -- against EE 7 specification. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-134) Make sure CLIWrapper doesn't use default encoding

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-134?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-134: ------------------------------------------------ Petr Kremensky <pkremens(a)redhat.com> changed the Status of [bug 980923|https://bugzilla.redhat.com/show_bug.cgi?id=980923] from ON_QA to ASSIGNED > Make sure CLIWrapper doesn't use default encoding > ------------------------------------------------- > > Key: WFCORE-134 > URL: https://issues.jboss.org/browse/WFCORE-134 > Project: WildFly Core > Issue Type: Bug > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Minor > Fix For: 1.0.0.Alpha9 > > > CLIWrapper is using the default encoding which might lead to issue with non US locales. > Also take advantage of this fix to remove some hard coded strings from tests. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1650) Legacy subsystem testing needs some classloading exclusion mecanism

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1650?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1650: ----------------------------------------------- Petr Kremensky <pkremens(a)redhat.com> changed the Status of [bug 980923|https://bugzilla.redhat.com/show_bug.cgi?id=980923] from ON_QA to ASSIGNED > Legacy subsystem testing needs some classloading exclusion mecanism > ------------------------------------------------------------------- > > Key: WFLY-1650 > URL: https://issues.jboss.org/browse/WFLY-1650 > Project: WildFly > Issue Type: Bug > Components: Logging, Test Suite > Affects Versions: 8.0.0.Alpha3 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Fix For: 8.0.0.Beta1 > > > When translation messages are used (which is the case of EAP) we have conflicts between generated $logger classes when testing submodules. > Some $logger classes exis thus they are loaded by the parent classloader before the childfirstclassloader tries to load them, thus we have a potential ClassCastException brewing. > For exemple this breaks the EAP build on a French OS. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-641) Named Consequences don't work with events

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-641?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-641. -------------------------------- Fix Version/s: 6.2.0.CR2 Resolution: Done Fixed by https://github.com/droolsjbpm/drools/commit/8bc35f571 > Named Consequences don't work with events > ----------------------------------------- > > Key: DROOLS-641 > URL: https://issues.jboss.org/browse/DROOLS-641 > Project: Drools > Issue Type: Bug > Affects Versions: 6.0.0.Final, 6.1.0.Final, 6.2.0.CR1 > Reporter: Davide Sottara > Assignee: Mario Fusco > Fix For: 6.2.0.CR2 > > > Given e.g. a rule : > {code} > when > Event() > AnotherEvent() do[something] > then ... end > {code} > A stream queue is created only for the main path (main consequence). > The events never reach then named consequence, failing to match it. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-641) Named Consequences don't work with events

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-641?page=com.atlassian.jira.plugin... ] Mario Fusco reassigned DROOLS-641: ---------------------------------- Assignee: Mario Fusco (was: Mark Proctor) > Named Consequences don't work with events > ----------------------------------------- > > Key: DROOLS-641 > URL: https://issues.jboss.org/browse/DROOLS-641 > Project: Drools > Issue Type: Bug > Affects Versions: 6.0.0.Final, 6.1.0.Final, 6.2.0.CR1 > Reporter: Davide Sottara > Assignee: Mario Fusco > > Given e.g. a rule : > {code} > when > Event() > AnotherEvent() do[something] > then ... end > {code} > A stream queue is created only for the main path (main consequence). > The events never reach then named consequence, failing to match it. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3255) IllegalArgumentException occurs while accessing the handler information via JMX MBean?

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3255?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3255: ----------------------------------------------- mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1152929|https://bugzilla.redhat.com/show_bug.cgi?id=1152929] from NEW to CLOSED > IllegalArgumentException occurs while accessing the handler information via JMX MBean? > --------------------------------------------------------------------------------------- > > Key: WFLY-3255 > URL: https://issues.jboss.org/browse/WFLY-3255 > Project: WildFly > Issue Type: Bug > Components: JMX > Affects Versions: 8.1.0.CR1 > Reporter: Jay Kumar SenSharma > Assignee: James Perkins > Labels: dmr > Fix For: 9.0.0.Alpha1 > > Attachments: WFLY-3255_TestCase.zip > > > - While trying to get the "handler" information via JMX code the following kind of exception is encountered: > {code} > 12:09:24,853 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /LoggerJMX/index.jsp: org.apache.jasper.JasperException: java.lang.IllegalArgumentException > at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:410) [jastow-1.0.0.Final.jar:1.0.0.Final] > at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:326) [jastow-1.0.0.Final.jar:1.0.0.Final] > at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:259) [jastow-1.0.0.Final.jar:1.0.0.Final] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) [undertow-servlet-1.0.5.Final.jar:1.0.5.Final] > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) [undertow-servlet-1.0.5.Final.jar:1.0.5.Final] > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.5.Final.jar:1.0.5.Final] > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.5.Final.jar:1.0.5.Final] > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.5.Final.jar:1.0.5.Final] > at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:56) [undertow-servlet-1.0.5.Final.jar:1.0.5.Final] > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.5.Final.jar:1.0.5.Final] > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) [undertow-servlet-1.0.5.Final.jar:1.0.5.Final] > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) [undertow-core-1.0.5.Final.jar:1.0.5.Final] > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) [undertow-servlet-1.0.5.Final.jar:1.0.5.Final] > at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) [undertow-core-1.0.5.Final.jar:1.0.5.Final] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.5.Final.jar:1.0.5.Final] > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.5.Final.jar:1.0.5.Final] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.5.Final.jar:1.0.5.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:240) [undertow-servlet-1.0.5.Final.jar:1.0.5.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) [undertow-servlet-1.0.5.Final.jar:1.0.5.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) [undertow-servlet-1.0.5.Final.jar:1.0.5.Final] > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) [undertow-servlet-1.0.5.Final.jar:1.0.5.Final] > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:168) [undertow-core-1.0.5.Final.jar:1.0.5.Final] > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:727) [undertow-core-1.0.5.Final.jar:1.0.5.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21] > Caused by: java.lang.IllegalArgumentException > at org.jboss.dmr.ModelValue.getChild(ModelValue.java:112) > at org.jboss.dmr.ModelNode.get(ModelNode.java:856) > at org.jboss.as.jmx.model.TypeConverters$ComplexTypeConverter.fromModelNode(TypeConverters.java:538) > at org.jboss.as.jmx.model.TypeConverters$ListTypeConverter.fromModelNode(TypeConverters.java:444) > at org.jboss.as.jmx.model.TypeConverters.fromModelNode(TypeConverters.java:114) > at org.jboss.as.jmx.model.ModelControllerMBeanHelper.getAttribute(ModelControllerMBeanHelper.java:245) > at org.jboss.as.jmx.model.ModelControllerMBeanHelper.getAttribute(ModelControllerMBeanHelper.java:200) > at org.jboss.as.jmx.model.ModelControllerMBeanServerPlugin.getAttribute(ModelControllerMBeanServerPlugin.java:96) > at org.jboss.as.jmx.PluggableMBeanServerImpl.getAttribute(PluggableMBeanServerImpl.java:384) > at org.apache.jsp.index_jsp._jspService(index_jsp.java:73) > at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:69) [jastow-1.0.0.Final.jar:1.0.0.Final] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final] > at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:366) [jastow-1.0.0.Final.jar:1.0.0.Final] > ... 28 more > {code} > - The Handler is configured as following: > {code} > <logger category="org.jboss.as.config"> > <handlers> > <handler name="CONSOLE"/> > </handlers> > <level name="DEBUG"/> > </logger> > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 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 October 2014