October 2015 - jboss-jira - Jboss List Archives

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-125?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on LOGMGR-125: ------------------------------------------------ Panagiotis Sotiropoulos <psotirop(a)redhat.com> changed the Status of [bug 1274572|https://bugzilla.redhat.com/show_bug.cgi?id=1274572] from NEW to ASSIGNED > 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 > Assignee: James Perkins > Fix For: 2.0.4.Final, 2.1.0.Beta1 > > > 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, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1083) Login Module is messed up when one of the module-option is empty

by J Prasanna Venkatesan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1083?page=com.atlassian.jira.plugi... ] J Prasanna Venkatesan commented on WFCORE-1083: ----------------------------------------------- Any solution is much appreciated. Please let us know. > Login Module is messed up when one of the module-option is empty > ---------------------------------------------------------------- > > Key: WFCORE-1083 > URL: https://issues.jboss.org/browse/WFCORE-1083 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Environment: CentOS Linux release 7.1.1503 (Core) > /usr/java/jdk1.8.0_45/ > WildFly 8.2.0 > Reporter: J Prasanna Venkatesan > Assignee: Alexey Loubyansky > Priority: Critical > > When one of the module-option is given as empty the whole login-module is messed up. But in real time there will be cases where the module-option can be empty. For Eg. while configuring org.jboss.security.auth.spi.LdapLoginModule, the principalDNPrefix can be empty > *+Command with principalDNPrefix empty+* > /subsystem=security/security-domain=SourceForge/authentication=classic/login-module=org.jboss.security.auth.spi.LdapLoginModule33:add(code=org.jboss.security.auth.spi.LdapLoginModule, flag=sufficient, module-options=[ "java.naming.provider.url" => "ldap://ldaphost.jboss.org:1", "java.naming.security.authentication" => "simple", *"principalDNPrefix" => ""*, "principalDNSuffix" => ",ou=People,o=jboss.org", "allowEmptyPasswords" => "false", "java.naming.factory.initial" => "com.sun.jndi.ldap.LdapCtxFactory", "throwValidateError" => "true" ]){allow-resource-service-restart=true} > +Output in standalone-full.xml+ > Wrong value is stored as principalDNPrefix > <login-module name="org.jboss.security.auth.spi.LdapLoginModule33" code="org.jboss.security.auth.spi.LdapLoginModule" flag="sufficient"> > <module-option name="java.naming.provider.url" value="ldap://ldaphost.jboss.org:1"/> > <module-option name="java.naming.security.authentication" value="simple"/> > *<module-option name="principalDNPrefix" value="principalDNSuffix"/>* > <module-option name="allowEmptyPasswords" value="false"/> > <module-option name="java.naming.factory.initial" value="com.sun.jndi.ldap.LdapCtxFactory"/> > <module-option name="throwValidateError" value="true"/> > </login-module> > *+Command with principalDNPrefix with some value+* > /subsystem=security/security-domain=SourceForge/authentication=classic/login-module=org.jboss.security.auth.spi.LdapLoginModule44:add(code=org.jboss.security.auth.spi.LdapLoginModule, flag=sufficient, module-options=[ "java.naming.provider.url" => "ldap://ldaphost.jboss.org:1", "java.naming.security.authentication" => "simple", *"principalDNPrefix" => "test"*, "principalDNSuffix" => ",ou=People,o=jboss.org", "allowEmptyPasswords" => "false", "java.naming.factory.initial" => "com.sun.jndi.ldap.LdapCtxFactory", "throwValidateError" => "true" ]){allow-resource-service-restart=true} > +Output in standalone-full.xml+ > Values are stored correctly. > <login-module name="org.jboss.security.auth.spi.LdapLoginModule44" code="org.jboss.security.auth.spi.LdapLoginModule" flag="sufficient"> > <module-option name="java.naming.provider.url" value="ldap://ldaphost.jboss.org:1"/> > <module-option name="java.naming.security.authentication" value="simple"/> > *<module-option name="principalDNPrefix" value="test"/>* > <module-option name="principalDNSuffix" value=",ou=People,o=jboss.org"/> > <module-option name="allowEmptyPasswords" value="false"/> > <module-option name="java.naming.factory.initial" value="com.sun.jndi.ldap.LdapCtxFactory"/> > <module-option name="throwValidateError" value="true"/> > </login-module> -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-5565) JMSBridge executor service is oblivious to TCCL

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-5565?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFLY-5565: ------------------------------ Affects Version/s: 10.0.0.CR4 > JMSBridge executor service is oblivious to TCCL > ----------------------------------------------- > > Key: WFLY-5565 > URL: https://issues.jboss.org/browse/WFLY-5565 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.CR4 > Reporter: Bartosz Baranowski > Assignee: Jason Greene > > In certain conditions( time sensitive) TCCL of JMS Bridge handle failure use artemis module, rather than custom one provided to bridge. Check BZ. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-5565) JMSBridge executor service is oblivious to TCCL

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-5565?page=com.atlassian.jira.plugin.... ] Jeff Mesnil reassigned WFLY-5565: --------------------------------- Assignee: Jeff Mesnil (was: Jason Greene) > JMSBridge executor service is oblivious to TCCL > ----------------------------------------------- > > Key: WFLY-5565 > URL: https://issues.jboss.org/browse/WFLY-5565 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.CR4 > Reporter: Bartosz Baranowski > Assignee: Jeff Mesnil > > In certain conditions( time sensitive) TCCL of JMS Bridge handle failure use artemis module, rather than custom one provided to bridge. Check BZ. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-5565) JMSBridge executor service is oblivious to TCCL

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-5565?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFLY-5565: ------------------------------ Component/s: JMS > JMSBridge executor service is oblivious to TCCL > ----------------------------------------------- > > Key: WFLY-5565 > URL: https://issues.jboss.org/browse/WFLY-5565 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Bartosz Baranowski > Assignee: Jason Greene > > In certain conditions( time sensitive) TCCL of JMS Bridge handle failure use artemis module, rather than custom one provided to bridge. Check BZ. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

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

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-5554?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFLY-5554: ------------------------------ Component/s: JMS > 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 > Components: JMS > Affects Versions: 10.0.0.CR4 > Reporter: Bartosz Baranowski > Assignee: Jason Greene > Priority: Minor > Fix For: 10.0.0.Final > > > 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, 1 month

1
0
0 / 0

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

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-5554?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFLY-5554: ------------------------------ Affects Version/s: 10.0.0.CR4 > 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 > Components: JMS > Affects Versions: 10.0.0.CR4 > Reporter: Bartosz Baranowski > Assignee: Jason Greene > Priority: Minor > Fix For: 10.0.0.Final > > > 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, 1 month

1
0
0 / 0

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

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-5554?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFLY-5554: ------------------------------ Fix Version/s: 10.0.0.Final > 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 > Components: JMS > Affects Versions: 10.0.0.CR4 > Reporter: Bartosz Baranowski > Assignee: Jason Greene > Priority: Minor > Fix For: 10.0.0.Final > > > 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, 1 month

1
0
0 / 0

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

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-5554?page=com.atlassian.jira.plugin.... ] Jeff Mesnil reassigned WFLY-5554: --------------------------------- Assignee: Jeff Mesnil (was: Jason Greene) > 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 > Components: JMS > Affects Versions: 10.0.0.CR4 > Reporter: Bartosz Baranowski > Assignee: Jeff Mesnil > Priority: Minor > Fix For: 10.0.0.Final > > > 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, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-5609) Upgrade Artemis 1.1.0.wildfly-008

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFLY-5609: --------------------------------- Summary: Upgrade Artemis 1.1.0.wildfly-008 Key: WFLY-5609 URL: https://issues.jboss.org/browse/WFLY-5609 Project: WildFly Issue Type: Component Upgrade Components: JMS Reporter: Jeff Mesnil Assignee: Jeff Mesnil Fix For: 10.0.0.Final Commits from Artemis 1.1.0.wildfly.007 to 1.1.0.wildfly-008: https://github.com/rh-messaging/jboss-activemq-artemis/compare/1.1.0.wild... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2015