April 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1535) DMN engine not checking scope of variables on DTs

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1535?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1535: ----------------------------------- Fix Version/s: (was: 7.0.0.Final) > DMN engine not checking scope of variables on DTs > ------------------------------------------------- > > Key: DROOLS-1535 > URL: https://issues.jboss.org/browse/DROOLS-1535 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.0.0.CR1 > Reporter: Edson Tirelli > Assignee: Edson Tirelli > Priority: Critical > Fix For: 7.1.0.Final > > > DMN engine is not checking variables while compiling DTs and silently succeeding even if the referenced variable does not exist. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-9) [QE] - JMAN4-152 - Install the in-process agent via RPM into an RPM installed EAP 7 installation.

by Filip Brychta (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-9?page=com.atlassian.jira.plug... ] Filip Brychta commented on HAWKULARQE-9: ---------------------------------------- Adding found issues: https://bugzilla.redhat.com/show_bug.cgi?id=1441967 https://bugzilla.redhat.com/show_bug.cgi?id=1441599 https://bugzilla.redhat.com/show_bug.cgi?id=1441609 https://bugzilla.redhat.com/show_bug.cgi?id=1441998 https://bugzilla.redhat.com/show_bug.cgi?id=1443063 > [QE] - JMAN4-152 - Install the in-process agent via RPM into an RPM installed EAP 7 installation. > ------------------------------------------------------------------------------------------------- > > Key: HAWKULARQE-9 > URL: https://issues.jboss.org/browse/HAWKULARQE-9 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Filip Brychta > Labels: mm-integration-hawkular-qe > > See [JMAN4-152|https://issues.jboss.org/browse/JMAN4-152] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8643) RestEasy GZIP Compression Not Setting Content-Encoding

by Xavier Hammond (JIRA)

Xavier Hammond created WFLY-8643: ------------------------------------ Summary: RestEasy GZIP Compression Not Setting Content-Encoding Key: WFLY-8643 URL: https://issues.jboss.org/browse/WFLY-8643 Project: WildFly Issue Type: Feature Request Components: EE Affects Versions: 11.0.0.Alpha1 Environment: Encountered the issue running in a Windows 7 environment Reporter: Xavier Hammond The Content-Encoding is not set to gzip when a RESTful service endpoint returns GZIP compressed data. This only occurs when I deploy to the Wildfly 11 Alpha release. No issues with Wildfly 10 Final. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1537) Scheduled activations are rescheduled as if new when unmarshalling session in Drools 6.5

by Kay J (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1537?page=com.atlassian.jira.plugi... ] Kay J commented on DROOLS-1537: ------------------------------- Ok sorry, at first glance I though you were reusing the old kBase, which you didn't. I adapted my test to also use your way of creating a session and it worked. I still don't fully understand the difference between the approaches (the core seems to be the way we create the kBase), but it seems to work and I hope I can adapt my application code in the same manner. Thanks a lof for now. I'll get back to you, if I have any more questions. > Scheduled activations are rescheduled as if new when unmarshalling session in Drools 6.5 > ---------------------------------------------------------------------------------------- > > Key: DROOLS-1537 > URL: https://issues.jboss.org/browse/DROOLS-1537 > Project: Drools > Issue Type: Bug > Affects Versions: 6.5.0.Final > Reporter: Kay J > Assignee: Mario Fusco > Attachments: RestoreReproducer.java > > > Ticket representing question/bug from drools user group: https://groups.google.com/forum/#!topic/drools-usage/Gy3uhkh6J78 > Hello Drools users, > I found an anomaly in Drools 6.5. I insert an Event, which triggers a rule with a timer after some time. For backup reasons I marshal the session inbetween to back it up and on unmarshal it later. However, after unmarshalling it, the scheduled activations are sometimes scheduled as if just inserted (e.g. 1min scheduling, with marshal/unmarshal after 25s results in the activation firing after 85 (25+60) seconds instead of actual 60s. I know this worked with Drools 5.6 consistently, but now it sometimes works, sometimes not, which is indeterministic. > I created a test reproducing this behaviour, which has changing output whenever you execute it. What the example does: It create a scheduled activation, which should trigger after 20s. After 10s the session is marshalled, destroyed and unmarshalled into a new session. After another 10s it should finally trigger. (10s + 10s -> the 20s scheduled). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-2730) empty target-name in constant-permission-mapper is not allowed

by Eva Jarkovská (JIRA)

Eva Jarkovská created WFCORE-2730: ------------------------------------- Summary: empty target-name in constant-permission-mapper is not allowed Key: WFCORE-2730 URL: https://issues.jboss.org/browse/WFCORE-2730 Project: WildFly Core Issue Type: Bug Reporter: Eva Jarkovská I need to have an empty target-name because of the WebResourcePermission. But with unspecified target-name the primary underlying error message was: | > ParseError at [row,col]:[367,5] | > Message: "WFLYCTL0113: '' is an invalid value for parameter | > target-name. Values must have a minimum length of 1 characters" -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-2696) Upgrade JBoss Remoting to 5.0.0.Beta20

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2696?page=com.atlassian.jira.plugi... ] Kabir Khan resolved WFCORE-2696. -------------------------------- Fix Version/s: (was: 3.0.0.Beta16) Resolution: Duplicate Issue Duplicate of WFCORE-2613 > Upgrade JBoss Remoting to 5.0.0.Beta20 > -------------------------------------- > > Key: WFCORE-2696 > URL: https://issues.jboss.org/browse/WFCORE-2696 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: David Lloyd > Assignee: David Lloyd > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-2696) Upgrade JBoss Remoting to 5.0.0.Beta20

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2696?page=com.atlassian.jira.plugi... ] Kabir Khan closed WFCORE-2696. ------------------------------ > Upgrade JBoss Remoting to 5.0.0.Beta20 > -------------------------------------- > > Key: WFCORE-2696 > URL: https://issues.jboss.org/browse/WFCORE-2696 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: David Lloyd > Assignee: David Lloyd > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-2696) Upgrade JBoss Remoting to 5.0.0.Beta20

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2696?page=com.atlassian.jira.plugi... ] Kabir Khan reopened WFCORE-2696: -------------------------------- > Upgrade JBoss Remoting to 5.0.0.Beta20 > -------------------------------------- > > Key: WFCORE-2696 > URL: https://issues.jboss.org/browse/WFCORE-2696 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 3.0.0.Beta16 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-2613) Upgrade JBoss Remoting to 5.0.0.Beta20

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2613?page=com.atlassian.jira.plugi... ] Kabir Khan resolved WFCORE-2613. -------------------------------- Fix Version/s: 3.0.0.Beta16 Resolution: Done > Upgrade JBoss Remoting to 5.0.0.Beta20 > -------------------------------------- > > Key: WFCORE-2613 > URL: https://issues.jboss.org/browse/WFCORE-2613 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Remoting > Reporter: Martin Simka > Assignee: David Lloyd > Fix For: 3.0.0.Beta16 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1537) Scheduled activations are rescheduled as if new when unmarshalling session in Drools 6.5

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1537?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-1537: ------------------------------------- Did you give a look at the test I linked in my former comment? It does exactly this: creating a KieBase from a String containing the drl. > Scheduled activations are rescheduled as if new when unmarshalling session in Drools 6.5 > ---------------------------------------------------------------------------------------- > > Key: DROOLS-1537 > URL: https://issues.jboss.org/browse/DROOLS-1537 > Project: Drools > Issue Type: Bug > Affects Versions: 6.5.0.Final > Reporter: Kay J > Assignee: Mario Fusco > Attachments: RestoreReproducer.java > > > Ticket representing question/bug from drools user group: https://groups.google.com/forum/#!topic/drools-usage/Gy3uhkh6J78 > Hello Drools users, > I found an anomaly in Drools 6.5. I insert an Event, which triggers a rule with a timer after some time. For backup reasons I marshal the session inbetween to back it up and on unmarshal it later. However, after unmarshalling it, the scheduled activations are sometimes scheduled as if just inserted (e.g. 1min scheduling, with marshal/unmarshal after 25s results in the activation firing after 85 (25+60) seconds instead of actual 60s. I know this worked with Drools 5.6 consistently, but now it sometimes works, sometimes not, which is indeterministic. > I created a test reproducing this behaviour, which has changing output whenever you execute it. What the example does: It create a scheduled activation, which should trigger after 20s. After 10s the session is marshalled, destroyed and unmarshalled into a new session. After another 10s it should finally trigger. (10s + 10s -> the 20s scheduled). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

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 April 2017