October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11099) ActiveMQ 2.6.3.jbossorg-001 requires QPid Proton-J 0.27.3 (CastClassExceptions in messaging subsystem)

by Jan-Willem Gmelig Meyling (JIRA)

Jan-Willem Gmelig Meyling created WFLY-11099: ------------------------------------------------ Summary: ActiveMQ 2.6.3.jbossorg-001 requires QPid Proton-J 0.27.3 (CastClassExceptions in messaging subsystem) Key: WFLY-11099 URL: https://issues.jboss.org/browse/WFLY-11099 Project: WildFly Issue Type: Bug Affects Versions: 14.0.0.Final, 14.0.1.Final Reporter: Jan-Willem Gmelig Meyling Assignee: Jason Greene With the update from Artemis 1.5.x to 2.6.x in WFLY-9407, Proton-J wasn't updated from 0.16.x to 0.27.3, which leads to class not found exceptions for "Sasl... " classes when remote acceptors are created and connected to (I tested with AMQP protocol). When updating Proton-J to the newest version (0.29.0) my issues are gone. I'm not sure which other modules are using the proton-j module, but my suggestion is that we bump the version of Proton-j to the required 0.27.3 minimally, ideally newer. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3054) Highlight in expression builder previous selection in Scenario right panel

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-3054?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-3054: ------------------------------------- [~srambach] Did highlighting the selection come with the widget used for the CSS? I'm starting to wonder if [~gabriolo] is saying that node selection isn't showing up. > Highlight in expression builder previous selection in Scenario right panel > -------------------------------------------------------------------------- > > Key: DROOLS-3054 > URL: https://issues.jboss.org/browse/DROOLS-3054 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Gabriele Cardosi > Priority: Minor > Labels: UX, UXTeam > Attachments: Screen Shot 2018-09-28 at 3.45.25 PM.png > > > When the user edits the type of a column, the expression builder into the right panel should highlight the existing mapped type. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2522) [DMN Designer] Palette aesthetics

by Matthew Stevens (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2522?page=com.atlassian.jira.plugi... ] Matthew Stevens commented on DROOLS-2522: ----------------------------------------- [~manstis] The tooltips on the palette look great. Would they be the same on the toolbox icons? If so, could that code be repurposed for JBPM-7153? > [DMN Designer] Palette aesthetics > --------------------------------- > > Key: DROOLS-2522 > URL: https://issues.jboss.org/browse/DROOLS-2522 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Labels: drools-tools > Attachments: DROOLS-2522.mp4, Screen Shot 2018-10-01 at 12.26.15 PM.png, palette.png > > > The palette css styling has changed. There appeared margins between items in palette, what is probably not problem, however even when user click to this margin (to space between two item in palette) still some palette item is selected. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2522) [DMN Designer] Palette aesthetics

by Matthew Stevens (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2522?page=com.atlassian.jira.plugi... ] Matthew Stevens commented on DROOLS-2522: ----------------------------------------- Hey [~srambach] can you comment on this in Brian's place? I know you two worked closely with Roger getting the palette just right. > [DMN Designer] Palette aesthetics > --------------------------------- > > Key: DROOLS-2522 > URL: https://issues.jboss.org/browse/DROOLS-2522 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Labels: drools-tools > Attachments: DROOLS-2522.mp4, Screen Shot 2018-10-01 at 12.26.15 PM.png, palette.png > > > The palette css styling has changed. There appeared margins between items in palette, what is probably not problem, however even when user click to this margin (to space between two item in palette) still some palette item is selected. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11098) Singleton service election listeners

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-11098?page=com.atlassian.jira.plugin... ] Paul Ferraro moved EAP7-1123 to WFLY-11098: ------------------------------------------- Project: WildFly (was: EAP 7 Planning Pilot) Key: WFLY-11098 (was: EAP7-1123) Issue Type: Feature Request (was: Requirement) Workflow: GIT Pull Request workflow (was: EAP Agile Workflow 2.0) Component/s: Clustering (was: Clustering) Jirban PT Pre-Checked (PC): (was: TODO) Jirban PT Community Docs (CD): (was: TODO) Jirban PT Product Docs (PD): (was: New) Affects Version/s: 14.0.0.Final (was: 7.2.0.CD14) Jirban PT Test Dev (TD): (was: TODO) Jirban PT Docs Analysis (DA): (was: TODO) Jirban PT Test Plan (TP): (was: TODO) Jirban PT Analysis Document (AD): (was: TODO) > Singleton service election listeners > ------------------------------------ > > Key: WFLY-11098 > URL: https://issues.jboss.org/browse/WFLY-11098 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 14.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > Users want the ability to be notified when a given member is elected as the primary provider of a singleton service. The notification mechanism should be distributed, such that all members on which the given singleton service is installed will receive notifications when a new primary is elected. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10531) Wildfly leaks ActiveMQ connections

by Mohamed Bd (JIRA)

[ https://issues.jboss.org/browse/WFLY-10531?page=com.atlassian.jira.plugin... ] Mohamed Bd edited comment on WFLY-10531 at 10/1/18 2:26 PM: ------------------------------------------------------------ I had the same issue while upgrading my applications to wildfly 13/14, and had to stop using injected JMSContext, and reverted back to jms 1.1 as a workaround. was (Author: mohtech): I had the same issue while upgrading my applications to wildfly 13/14, and had to stop using inject JMSContext, and reverted back to jms 1.1 as a workaround. > Wildfly leaks ActiveMQ connections > ---------------------------------- > > Key: WFLY-10531 > URL: https://issues.jboss.org/browse/WFLY-10531 > Project: WildFly > Issue Type: Bug > Affects Versions: 13.0.0.Final > Environment: openjdk 8 / openjdk 9, Linux > Reporter: Marcel Šebek > Assignee: Jeff Mesnil > Attachments: WFLY-10531-ear-1.0.ear, WFLY10531.zip > > > After upgrading our application from wildfly 12 to 13, the app started to crash after a while (hours, days, depending on circumstances). It crashes on > IJ000453: Unable to get managed connection for java:/JmsXA > and other errors (it simply cannot perform all the jobs it contains). I found that when shutting down the server which has been running for a while, I can see a bunch of these messages in the log: > WARN [org.jboss.jca.core.connectionmanager.pool.strategy.PoolByCri] (ServerService Thread Pool -- 117) [:::] IJ000615: Destroying active connection in pool: ActiveMQConnectionDefinition (org.apache.activemq.artemis.ra.ActiveMQRAManagedConnection@2f37f69) > Bascially, the longer the server was running, more of these messages are shown. I cannot find a way how to reproduce the issue. When the server runs for short time but with some load, no connection is leaked (or just one, rarely). On the other side, it leaks connections even without any particularly high load (just a few requests and @Schedule jobs) when running for longer time. > It may also be a bug in our application, which just happen to have more serious impact with the new wildfly version. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10531) Wildfly leaks ActiveMQ connections

by Mohamed Bd (JIRA)

[ https://issues.jboss.org/browse/WFLY-10531?page=com.atlassian.jira.plugin... ] Mohamed Bd commented on WFLY-10531: ----------------------------------- I had the same issue while upgrading my applications to wildfly 13/14, and had to stop using inject JMSContext, and reverted back to jms 1.1 as a workaround. > Wildfly leaks ActiveMQ connections > ---------------------------------- > > Key: WFLY-10531 > URL: https://issues.jboss.org/browse/WFLY-10531 > Project: WildFly > Issue Type: Bug > Affects Versions: 13.0.0.Final > Environment: openjdk 8 / openjdk 9, Linux > Reporter: Marcel Šebek > Assignee: Jeff Mesnil > Attachments: WFLY-10531-ear-1.0.ear, WFLY10531.zip > > > After upgrading our application from wildfly 12 to 13, the app started to crash after a while (hours, days, depending on circumstances). It crashes on > IJ000453: Unable to get managed connection for java:/JmsXA > and other errors (it simply cannot perform all the jobs it contains). I found that when shutting down the server which has been running for a while, I can see a bunch of these messages in the log: > WARN [org.jboss.jca.core.connectionmanager.pool.strategy.PoolByCri] (ServerService Thread Pool -- 117) [:::] IJ000615: Destroying active connection in pool: ActiveMQConnectionDefinition (org.apache.activemq.artemis.ra.ActiveMQRAManagedConnection@2f37f69) > Bascially, the longer the server was running, more of these messages are shown. I cannot find a way how to reproduce the issue. When the server runs for short time but with some load, no connection is leaked (or just one, rarely). On the other side, it leaks connections even without any particularly high load (just a few requests and @Schedule jobs) when running for longer time. > It may also be a bug in our application, which just happen to have more serious impact with the new wildfly version. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3059) Serial Version UUID on Declared Types

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-3059: ----------------------------------- Summary: Serial Version UUID on Declared Types Key: DROOLS-3059 URL: https://issues.jboss.org/browse/DROOLS-3059 Project: Drools Issue Type: Enhancement Components: core engine Affects Versions: 7.12.0.Final Reporter: Stylianos Koussouris Assignee: Mario Fusco We wish to update DeclaredTypes whilst session is in use but the generated serial version ID changes when the DeclaredType pojo is recompiled resulting InvalidClassExceptions. We therefore suggest the usage of an annotation @SerialVersionUUID to set in a constant manner the UUID -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4145) --admin-only might be worth marking as deprecated with ./standalone.sh --help

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4145?page=com.atlassian.jira.plugi... ] Brian Stansberry moved JBEAP-8273 to WFCORE-4145: ------------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-4145 (was: JBEAP-8273) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Management (was: Management) Target Release: (was: 7.backlog.GA) Affects Version/s: (was: 7.1.0.DR10) > --admin-only might be worth marking as deprecated with ./standalone.sh --help > ----------------------------------------------------------------------------- > > Key: WFCORE-4145 > URL: https://issues.jboss.org/browse/WFCORE-4145 > Project: WildFly Core > Issue Type: Task > Components: Management > Reporter: Radim Hatlapatka > Assignee: Brian Stansberry > Priority: Optional > > As part of [EAP7-636] there was introduced {{\-\-start-mode}} option which allows to define starting mode and basically replaces {{\-\-admin-only}} option and {{\-\-start-mode}} option is more universal one. > I believe we should mark {{\-\-admin-only}} option as deprecated in favor of {{\-\-start-mode=admin-only}} option in standalone mode. > [~bstansberry2], WDYT? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2996) Existing Rules are not working as expected after migrating the Drools version from 6.0.3 to 7.4.1.Final

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2996?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-2996. --------------------------------- Resolution: Done Fixed by https://github.com/kiegroup/drools/commit/c49666e9200c4a079a1979909c5a297... > Existing Rules are not working as expected after migrating the Drools version from 6.0.3 to 7.4.1.Final > ------------------------------------------------------------------------------------------------------- > > Key: DROOLS-2996 > URL: https://issues.jboss.org/browse/DROOLS-2996 > Project: Drools > Issue Type: Bug > Affects Versions: 7.4.1.Final > Reporter: Prameela Pod > Assignee: Mario Fusco > Attachments: DroolsTestPortlet.zip, logs.txt > > > After drools migration from 6.0.3 to 7.4.1.Final version , modify property in 1st rule not validating conditions in 2nd rule. > Ex: modify($alarm){setEVENTO_EN_TAREA("YES")} - In 1st rule then condition > $alarm: ALARMA_ERICSSON_2G("NO" == getEVENTO_EN_TAREA()) - When condition in 2nd rule. > If getEVENTO_EN_TAREA() = "YES" then only it should go inside 2nd rule.But here in this case getEVENTO_EN_TAREA()="YES" or "NO" - For both cases 2nd rule when condition is matched and going inside then condition.Which is wrong > Please find the attached sample test project with logs. > Kindly let me know additional information is required. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 3 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 2018