October 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-923) KieRepository is not thread safe

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-923?page=com.atlassian.jira.plugin... ] Mario Fusco commented on DROOLS-923: ------------------------------------ Fixed by https://github.com/droolsjbpm/drools/commit/b44ab2f85 > KieRepository is not thread safe > -------------------------------- > > Key: DROOLS-923 > URL: https://issues.jboss.org/browse/DROOLS-923 > Project: Drools > Issue Type: Bug > Reporter: Mario Fusco > Assignee: Mario Fusco > > KieRepository is not thread safe so concurrently adding and removing KieModules could lead to a NPE. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5554) JMS Bridge parameters are optional in schema, runtime makes them required

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/WFLY-5554?page=com.atlassian.jira.plugin.... ] Bartosz Baranowski updated WFLY-5554: ------------------------------------- Summary: JMS Bridge parameters are optional in schema, runtime makes them required (was: QOS in JMS Bridge is optional, however runtime makes it a required attribute) > JMS Bridge parameters are optional in schema, runtime makes them required > ------------------------------------------------------------------------- > > Key: WFLY-5554 > URL: https://issues.jboss.org/browse/WFLY-5554 > Project: WildFly > Issue Type: Bug > Reporter: Bartosz Baranowski > Assignee: Jason Greene > Priority: Minor > > From AMQ XSD: <xs:attribute name="quality-of-service" use="optional"> > At runtime: > 09:10:41,213 INFO [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: WildFly Core 2.0.0.CR7 "Kenny" starting > 09:10:44,070 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 20) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "messaging-activemq"), > ("jms-bridge" => "a-to-c-bridge") > ]) - failure description: "WFLYCTL0155: quality-of-service may not be null" > 09:10:44,111 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) "WFLYCTL0193: Failed executing subsystem messaging-activemq boot operations" > 09:10:44,114 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("parallel-subsystem-boot") failed - address: ([]) - failure description: "\"WFLYCTL0193: Failed executing subsystem messaging-activemq boot operations\"" > 09:10:44,118 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5554) QOS in JMS Bridge is optional, however runtime makes it a required attribute

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/WFLY-5554?page=com.atlassian.jira.plugin.... ] Bartosz Baranowski updated WFLY-5554: ------------------------------------- Issue Type: Bug (was: Feature Request) > QOS in JMS Bridge is optional, however runtime makes it a required attribute > ---------------------------------------------------------------------------- > > Key: WFLY-5554 > URL: https://issues.jboss.org/browse/WFLY-5554 > Project: WildFly > Issue Type: Bug > Reporter: Bartosz Baranowski > Assignee: Jason Greene > Priority: Minor > > From AMQ XSD: <xs:attribute name="quality-of-service" use="optional"> > At runtime: > 09:10:41,213 INFO [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: WildFly Core 2.0.0.CR7 "Kenny" starting > 09:10:44,070 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 20) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "messaging-activemq"), > ("jms-bridge" => "a-to-c-bridge") > ]) - failure description: "WFLYCTL0155: quality-of-service may not be null" > 09:10:44,111 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) "WFLYCTL0193: Failed executing subsystem messaging-activemq boot operations" > 09:10:44,114 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("parallel-subsystem-boot") failed - address: ([]) - failure description: "\"WFLYCTL0193: Failed executing subsystem messaging-activemq boot operations\"" > 09:10:44,118 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5554) QOS in JMS Bridge is optional, however runtime makes it a required attribute

by Bartosz Baranowski (JIRA)

Bartosz Baranowski created WFLY-5554: ---------------------------------------- Summary: QOS in JMS Bridge is optional, however runtime makes it a required attribute Key: WFLY-5554 URL: https://issues.jboss.org/browse/WFLY-5554 Project: WildFly Issue Type: Feature Request Reporter: Bartosz Baranowski Assignee: Jason Greene Priority: Minor >From AMQ XSD: <xs:attribute name="quality-of-service" use="optional"> At runtime: 09:10:41,213 INFO [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: WildFly Core 2.0.0.CR7 "Kenny" starting 09:10:44,070 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 20) WFLYCTL0013: Operation ("add") failed - address: ([ ("subsystem" => "messaging-activemq"), ("jms-bridge" => "a-to-c-bridge") ]) - failure description: "WFLYCTL0155: quality-of-service may not be null" 09:10:44,111 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) "WFLYCTL0193: Failed executing subsystem messaging-activemq boot operations" 09:10:44,114 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("parallel-subsystem-boot") failed - address: ([]) - failure description: "\"WFLYCTL0193: Failed executing subsystem messaging-activemq boot operations\"" 09:10:44,118 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5547) singleton-deployment-1.0.xsd file name violates the common naming scheme

by Ladislav Thon (JIRA)

[ https://issues.jboss.org/browse/WFLY-5547?page=com.atlassian.jira.plugin.... ] Ladislav Thon updated WFLY-5547: -------------------------------- Affects Version/s: 10.0.0.CR3 > singleton-deployment-1.0.xsd file name violates the common naming scheme > ------------------------------------------------------------------------ > > Key: WFLY-5547 > URL: https://issues.jboss.org/browse/WFLY-5547 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Affects Versions: 10.0.0.CR3 > Reporter: Ladislav Thon > Assignee: Radoslav Husar > > The singleton deployment schema file \[1\] is called {{singleton-deployment-1.0.xsd}} and it uses > - a dash {{-}} as a separator between name an version, > - a period {{.}} as a delimiter in the version number. > This is inconsistent with all other schema files that use an underscore {{\_}} on both places (well, there are _some_ schemas that also use a dash {{-}} between name and version, but they are a minority). I believe that this file should be made consistent by renaming it to {{singleton-deployment_1_0.xsd}}. > \[1\] clustering/singleton/extension/src/main/resources/schema/singleton-deployment-1.0.xsd -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-124) Add marker support

by Andreas Liebscher (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-124?page=com.atlassian.jira.plugin... ] Andreas Liebscher commented on LOGMGR-124: ------------------------------------------ Large change!? Just update the Logger to a more current one. The Logger in WildFly is so old, we cannot even activate compression on logfile rotation. Even JBoss 5 had the posssibility to do that! So please UPDATE THE LOGGER! > Add marker support > ------------------ > > Key: LOGMGR-124 > URL: https://issues.jboss.org/browse/LOGMGR-124 > Project: JBoss Log Manager > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.2.Final > Reporter: Rob Heine > Priority: Optional > > The logging engine currently (talking about the one included in WF-9) does not support Markers (like in implementations like "logback" and/or "log4j2"). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-125) Log rotation fails on Windows if target already exists

by James Livingston (JIRA)

James Livingston created LOGMGR-125: --------------------------------------- Summary: Log rotation fails on Windows if target already exists Key: LOGMGR-125 URL: https://issues.jboss.org/browse/LOGMGR-125 Project: JBoss Log Manager Issue Type: Bug Reporter: James Livingston PeriodicRotatingFileHandler (and others) use File.renameTo() to rename the file. That method is documented as having many implementation-defined aspects, see http://docs.oracle.com/javase/7/docs/api/java/io/File.html#renameTo%28jav... One that can be a problem is that on Windows, it will fail if the target file already exists. If you use a ".dd" suffix, this will occur when it rolls over to a new month. It has rarely been a problem, since most people use the year month and day so they are unique. Files.move() can replace existing files, so may be better, and some of the costs of that are likely not to be a problem with how it is using here. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-157) Write expressions to logging.properties configuration file

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-157?page=com.atlassian.jira.plugin... ] James Perkins updated WFCORE-157: --------------------------------- Priority: Optional (was: Critical) > Write expressions to logging.properties configuration file > ---------------------------------------------------------- > > Key: WFCORE-157 > URL: https://issues.jboss.org/browse/WFCORE-157 > Project: WildFly Core > Issue Type: Enhancement > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Optional > > Allow properties that use expressions to write the expression out to the logging.properties configuration file. This allows properties passed in at runtime to affect the initial logging configuration. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-69) Allow syslog severity level to log level mapping to be user defined

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-69?page=com.atlassian.jira.plugin.... ] James Perkins reassigned LOGMGR-69: ----------------------------------- Assignee: (was: James Perkins) > Allow syslog severity level to log level mapping to be user defined > ------------------------------------------------------------------- > > Key: LOGMGR-69 > URL: https://issues.jboss.org/browse/LOGMGR-69 > Project: JBoss Log Manager > Issue Type: Feature Request > Reporter: James Perkins > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-86) Create an exception filter

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-86?page=com.atlassian.jira.plugin.... ] James Perkins reassigned LOGMGR-86: ----------------------------------- Assignee: (was: James Perkins) > Create an exception filter > -------------------------- > > Key: LOGMGR-86 > URL: https://issues.jboss.org/browse/LOGMGR-86 > Project: JBoss Log Manager > Issue Type: Feature Request > Reporter: James Perkins > Priority: Optional > > For now this is just a thought so that users can filter messages based on an exception in the stack trace. Currently it's not possible to use a regex filter as the stack trace is not used in when testing for matches and it probably shouldn't be used. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 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 2015