October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (LOGMGR-204) Short host name format yields last part of name instead of first part

by David Lloyd (Jira)

[ https://issues.jboss.org/browse/LOGMGR-204?page=com.atlassian.jira.plugin... ] David Lloyd updated LOGMGR-204: ------------------------------- Fix Version/s: 2.1.5.Final > Short host name format yields last part of name instead of first part > --------------------------------------------------------------------- > > Key: LOGMGR-204 > URL: https://issues.jboss.org/browse/LOGMGR-204 > Project: JBoss Log Manager > Issue Type: Bug > Affects Versions: 2.1.4.Final > Reporter: David Lloyd > Assignee: David Lloyd > Priority: Major > Fix For: 2.1.5.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-204) Short host name format yields last part of name instead of first part

by David Lloyd (Jira)

[ https://issues.jboss.org/browse/LOGMGR-204?page=com.atlassian.jira.plugin... ] David Lloyd updated LOGMGR-204: ------------------------------- Affects Version/s: 2.1.4.Final > Short host name format yields last part of name instead of first part > --------------------------------------------------------------------- > > Key: LOGMGR-204 > URL: https://issues.jboss.org/browse/LOGMGR-204 > Project: JBoss Log Manager > Issue Type: Bug > Affects Versions: 2.1.4.Final > Reporter: David Lloyd > Assignee: David Lloyd > Priority: Major > Fix For: 2.1.5.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-204) Short host name format yields last part of name instead of first part

by David Lloyd (Jira)

David Lloyd created LOGMGR-204: ---------------------------------- Summary: Short host name format yields last part of name instead of first part Key: LOGMGR-204 URL: https://issues.jboss.org/browse/LOGMGR-204 Project: JBoss Log Manager Issue Type: Bug Reporter: David Lloyd Assignee: David Lloyd -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

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

by Jan-Willem Gmelig Meyling (Jira)

[ https://issues.jboss.org/browse/WFLY-11099?page=com.atlassian.jira.plugin... ] Jan-Willem Gmelig Meyling commented on WFLY-11099: -------------------------------------------------- I'd rather see 0.29 as well, as I have tested that one already. > ActiveMQ 2.6.3.jbossorg-001 requires QPid Proton-J 0.27.3 (ClassNotFoundExceptions in messaging subsystem) > ---------------------------------------------------------------------------------------------------------- > > Key: WFLY-11099 > URL: https://issues.jboss.org/browse/WFLY-11099 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 14.0.1.Final, 14.0.0.Final > Reporter: Jan-Willem Gmelig Meyling > Assignee: Jeff Mesnil > Priority: Major > > 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. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

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

by Kabir Khan (Jira)

[ https://issues.jboss.org/browse/WFLY-11099?page=com.atlassian.jira.plugin... ] Kabir Khan commented on WFLY-11099: ----------------------------------- [~martyn-taylor] says: {code} Looks like JIRA is down. The version in the product should be: version=0.29.0.redhat-00001 {code} However as [~psakar] pointed out, we don't actually use qpid in the product, so for upstream we can use whatever works. But as AMQ uses 0.29, is there any reason not to use that in wildfly right now? > ActiveMQ 2.6.3.jbossorg-001 requires QPid Proton-J 0.27.3 (ClassNotFoundExceptions in messaging subsystem) > ---------------------------------------------------------------------------------------------------------- > > Key: WFLY-11099 > URL: https://issues.jboss.org/browse/WFLY-11099 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 14.0.1.Final, 14.0.0.Final > Reporter: Jan-Willem Gmelig Meyling > Assignee: Jeff Mesnil > Priority: Major > > 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. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

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

by Sarah Rambacher (Jira)

[ https://issues.jboss.org/browse/DROOLS-2522?page=com.atlassian.jira.plugi... ] Sarah Rambacher commented on DROOLS-2522: ----------------------------------------- The sizing of the icons inside the palette looks good now, thanks!! > [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 > Priority: Major > Labels: drools-tools > Attachments: DROOLS-2522 (resized).png, 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. > h2. Manual Acceptance test > h3. Stunner > - Chrome (/) > - Firefox (/) > - Edge (/) > h3. DMN > - Chrome (/) > - Firefox (/) > - Edge (/) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

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

by Jan-Willem Gmelig Meyling (Jira)

[ https://issues.jboss.org/browse/WFLY-10531?page=com.atlassian.jira.plugin... ] Jan-Willem Gmelig Meyling commented on WFLY-10531: -------------------------------------------------- Thanks Jiri! I'll create a local build and report whether the error is gone for me! I have good faith in that this fix wil indeed solve the issue, the fix looks quite obvious :) > 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 > Priority: Major > 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.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3064) POJO Unification

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3064?page=com.atlassian.jira.plugi... ] Edoardo Vacchi commented on DROOLS-3064: ---------------------------------------- tracked: https://github.com/evacchi/droolog > POJO Unification > ----------------- > > Key: DROOLS-3064 > URL: https://issues.jboss.org/browse/DROOLS-3064 > Project: Drools > Issue Type: Task > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > > implement a general algorithm for recursive unification of POJO structures -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4148) Check and consider to put escaped quotes (\") back to the -Xloggc in standalone.sh

by Marek Kopecký (Jira)

Marek Kopecký created WFCORE-4148: ------------------------------------- Summary: Check and consider to put escaped quotes (\") back to the -Xloggc in standalone.sh Key: WFCORE-4148 URL: https://issues.jboss.org/browse/WFCORE-4148 Project: WildFly Core Issue Type: Bug Components: Scripts Reporter: Marek Kopecký Assignee: James Perkins Check and consider to put escaped quotes (\") back to the -Xloggc in standalone.sh See the discussion [here|https://github.com/wildfly/wildfly-core/pull/3496#discussion_r221509989] -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

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

by Jiri Ondrusek (Jira)

[ https://issues.jboss.org/browse/WFLY-10531?page=com.atlassian.jira.plugin... ] Jiri Ondrusek commented on WFLY-10531: -------------------------------------- I've prepared PR https://github.com/wildfly/wildfly/pull/11709, wchich contains fix of regression caused by https://github.com/wildfly/wildfly/pull/10614 > 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 > Priority: Major > 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.12.1#712002)

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