October 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBJCA-1225) Timers should be canceled upon shutdown

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-1225: -------------------------------------- Summary: Timers should be canceled upon shutdown Key: JBJCA-1225 URL: https://issues.jboss.org/browse/JBJCA-1225 Project: IronJacamar Issue Type: Bug Components: Core Affects Versions: 1.2.0.CR1, 1.1.8.Final, 1.0.28.Final Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.2.0.Final Let the BootstrapContext keep track of the timers, and call cancel() and purge() -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-95) Log4j Logger.getParent() inconsistent

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-95?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on LOGMGR-95: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1079106|https://bugzilla.redhat.com/show_bug.cgi?id=1079106] from POST to MODIFIED > Log4j Logger.getParent() inconsistent > ------------------------------------- > > Key: LOGMGR-95 > URL: https://issues.jboss.org/browse/LOGMGR-95 > Project: JBoss Log Manager > Issue Type: Bug > Reporter: James Livingston > Assignee: James Perkins > > Log4j Loggers have a getParent() method, whose return value is set up by JBossLogManagerFacade.updateParents(). The method locates the closest parent node which has an existing Log4J logger created *at the time*. This results in the parent being different depending on the order Log4j loggers are used in. > Consider: > Logger.getLogger("a"); > Logger.getLogger("a.b.c"); > Logger.getLogger("a.b"); > When the second line causes updateParents() to be called, LoggerNode.getOrCreate() has already created the intermediate "a.b" node. That does not yet have a Log4j Logger created, so the Logger for "a" is returned. Original log4j would have returned "a.b" due to it using the parent structure in the implementation. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-138) Upgrade log4j-jboss-logmanager from 1.1.0.Final to 1.1.1.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-138?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-138: ------------------------------------------------ Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1148632|https://bugzilla.redhat.com/show_bug.cgi?id=1148632] from POST to MODIFIED > Upgrade log4j-jboss-logmanager from 1.1.0.Final to 1.1.1.Final > -------------------------------------------------------------- > > Key: WFCORE-138 > URL: https://issues.jboss.org/browse/WFCORE-138 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Fix For: 1.0.0.Alpha9 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3925) JAX-RS bean implemented as Stateless is destroyed after response

by Sergio Samayoa (JIRA)

[ https://issues.jboss.org/browse/WFLY-3925?page=com.atlassian.jira.plugin.... ] Sergio Samayoa commented on WFLY-3925: -------------------------------------- Understood but one of the benefits of using EJBs is pooling and reuse so a "reasonable" default pooling policy without the need of any configuration (as Glassfish and Weblogic at least) should be provided out of the box. Regards. > JAX-RS bean implemented as Stateless is destroyed after response > ---------------------------------------------------------------- > > Key: WFLY-3925 > URL: https://issues.jboss.org/browse/WFLY-3925 > Project: WildFly > Issue Type: Bug > Affects Versions: 8.1.0.Final > Reporter: Sergio Samayoa > Assignee: Jason Greene > > A JAX-RS bean implemented as stateless EJB is destroyed after response is sent. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-146) Cleanup/fix IPV6 testsuite

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/WFCORE-146?page=com.atlassian.jira.plugin... ] Alexey Loubyansky updated WFCORE-146: ------------------------------------- Priority: Blocker (was: Major) This is a blocker for the CLI because its tests can't be included into the core testsuite. I am postponing work on some of the CLI issues until this is resolved. > Cleanup/fix IPV6 testsuite > -------------------------- > > Key: WFCORE-146 > URL: https://issues.jboss.org/browse/WFCORE-146 > Project: WildFly Core > Issue Type: Task > Affects Versions: 1.0.0.Alpha8 > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Priority: Blocker > Fix For: 1.0.0.Alpha9 > > > CLI testsuite cannot be ported over to Core as we have problems with IPV6 testsuite. > Testsuite configuration for ipv6 should be unified and simplified to make all this work in core and in full without extra params to build -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-145) CLI run-batch command cannot process files with comments or blank lines

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/WFCORE-145?page=com.atlassian.jira.plugin... ] Alexey Loubyansky commented on WFCORE-145: ------------------------------------------ To be able to run the testsuite we need WFCORE-146 fixed. > CLI run-batch command cannot process files with comments or blank lines > ----------------------------------------------------------------------- > > Key: WFCORE-145 > URL: https://issues.jboss.org/browse/WFCORE-145 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 1.0.0.Alpha8 > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > > In the JBoss CLI tool, the "run-batch --file=script.cli" command cannot > successfully process lines that start with "#" or blank lines. Comments and > blank lines help readability when creating cli batch scripts. > However, running the batch file containing comments/blank lines as a parameter > to jboss-cli.sh works just fine (./jboss-cli.sh -c --file=script.cli). This > difference in accepted syntax creates some confusion for users who are new to > the CLI tool. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-145) CLI run-batch command cannot process files with comments or blank lines

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-145?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated WFCORE-145: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1148642 > CLI run-batch command cannot process files with comments or blank lines > ----------------------------------------------------------------------- > > Key: WFCORE-145 > URL: https://issues.jboss.org/browse/WFCORE-145 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 1.0.0.Alpha8 > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > > In the JBoss CLI tool, the "run-batch --file=script.cli" command cannot > successfully process lines that start with "#" or blank lines. Comments and > blank lines help readability when creating cli batch scripts. > However, running the batch file containing comments/blank lines as a parameter > to jboss-cli.sh works just fine (./jboss-cli.sh -c --file=script.cli). This > difference in accepted syntax creates some confusion for users who are new to > the CLI tool. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-146) Cleanup/fix IPV6 testsuite

by Tomaz Cerar (JIRA)

Tomaz Cerar created WFCORE-146: ---------------------------------- Summary: Cleanup/fix IPV6 testsuite Key: WFCORE-146 URL: https://issues.jboss.org/browse/WFCORE-146 Project: WildFly Core Issue Type: Task Affects Versions: 1.0.0.Alpha8 Reporter: Tomaz Cerar Assignee: Tomaz Cerar Fix For: 1.0.0.Alpha9 CLI testsuite cannot be ported over to Core as we have problems with IPV6 testsuite. Testsuite configuration for ipv6 should be unified and simplified to make all this work in core and in full without extra params to build -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-145) CLI run-batch command cannot process files with comments or blank lines

by Alexey Loubyansky (JIRA)

Alexey Loubyansky created WFCORE-145: ---------------------------------------- Summary: CLI run-batch command cannot process files with comments or blank lines Key: WFCORE-145 URL: https://issues.jboss.org/browse/WFCORE-145 Project: WildFly Core Issue Type: Bug Components: CLI Affects Versions: 1.0.0.Alpha8 Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky In the JBoss CLI tool, the "run-batch --file=script.cli" command cannot successfully process lines that start with "#" or blank lines. Comments and blank lines help readability when creating cli batch scripts. However, running the batch file containing comments/blank lines as a parameter to jboss-cli.sh works just fine (./jboss-cli.sh -c --file=script.cli). This difference in accepted syntax creates some confusion for users who are new to the CLI tool. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3930) Upgrade to PicketLink 2.7.0.Beta2

by Peter Skopek (JIRA)

Peter Skopek created WFLY-3930: ---------------------------------- Summary: Upgrade to PicketLink 2.7.0.Beta2 Key: WFLY-3930 URL: https://issues.jboss.org/browse/WFLY-3930 Project: WildFly Issue Type: Component Upgrade Components: Build System Affects Versions: 9.0.0.Alpha1 Reporter: Peter Skopek Assignee: Peter Skopek Upgrade to PicketLink 2.7.0.Beta2 to get more users involved in. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 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 2014