August 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBCOMMON-128) Fix Regression introduced by JBCOMMON-106 in EAP 5.1.2

by Dimitris Andreadis (JIRA)

Dimitris Andreadis created JBCOMMON-128: ------------------------------------------- Summary: Fix Regression introduced by JBCOMMON-106 in EAP 5.1.2 Key: JBCOMMON-128 URL: https://issues.jboss.org/browse/JBCOMMON-128 Project: JBoss Common Issue Type: Bug Security Level: Public (Everyone can see) Components: common-core (2.x) Affects Versions: 2.2.18.GA Reporter: Dimitris Andreadis Assignee: Brad Maxwell Fix For: 2.2.20.GA Record in JBCommon JIRA the work done for jbpapp-8065 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] (JBCOMMON-126) NullPointerException when using PropertyMap concurrently

by Michael Pradel (JIRA)

Michael Pradel created JBCOMMON-126: --------------------------------------- Summary: NullPointerException when using PropertyMap concurrently Key: JBCOMMON-126 URL: https://issues.jboss.org/browse/JBCOMMON-126 Project: JBoss Common Issue Type: Bug Security Level: Public (Everyone can see) Components: common-core (2.x) Affects Versions: 2.2.18.GA Environment: All environments Reporter: Michael Pradel PropertyMap extends Properties, which is a thread-safe class, but it doesn't preserve its thread safety. This leads to surprising crashes if you have a reference of type Properties (documented as thread-safe) that turns out to be a PropertyMap (not thread-safe). Here's a simplified example that shows how we hit this bug: final Properties p = getProps(); p.setProperty("a", "b"); Thread t1 = new Thread(new Runnable() { public void run() { p.remove("a"); } }); Thread t2 = new Thread(new Runnable() { public void run() { p.clear(); } }); t1.start(); t2.start(); try { t1.join(); t2.join(); } catch (InterruptedException e) { e.printStackTrace(); } Properties getProps() { // return new Properties(); // OK return new PropertyMap(); // leads to NullPointerException } The code runs fine if getProps returns Properties (as it should, because Properties is thread-safe), but raises a NullPointerException if getProps returns a PropertyMap. Are you aware of this inconsistency? It seems that the safest way of extending Properties is to make methods that override synchronized methods synchronized. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBCOMMON-114) Warning for non File URLs should also check for vfszip URLs

by Darran Lofthouse (JIRA)

Warning for non File URLs should also check for vfszip URLs ----------------------------------------------------------- Key: JBCOMMON-114 URL: https://jira.jboss.org/browse/JBCOMMON-114 Project: JBoss Common Issue Type: Bug Security Level: Public (Everyone can see) Components: common-core (2.x) Affects Versions: 2.2.17.GA Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 2.2.18.GA Within the resolveSystemIDasURL method the following check is performed: - if (warnOnNonFileURLs && url.getProtocol().equalsIgnoreCase("file") == false) { log.warn("Trying to resolve systemId as a non-file URL: " + systemId); } With the introduction of vfszip URLs from JBoss 5 these should also be checked and the warning skipped if it is a vfszip URL. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBCOMMON-123) CLONE - Release jboss-common-core 2.2.18

by Dimitris Andreadis (JIRA)

CLONE - Release jboss-common-core 2.2.18 ---------------------------------------- Key: JBCOMMON-123 URL: https://issues.jboss.org/browse/JBCOMMON-123 Project: JBoss Common Issue Type: Release Security Level: Public (Everyone can see) Components: common-core (2.x) Reporter: Dimitris Andreadis Assignee: Dimitris Andreadis Fix For: 2.2.18.GA -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
3
0 / 0

[JBoss JIRA] (JBCOMMON-127) Extend JBossEntityResolver to also implement LSResourceResolver

by Dimitris Andreadis (JIRA)

Dimitris Andreadis created JBCOMMON-127: ------------------------------------------- Summary: Extend JBossEntityResolver to also implement LSResourceResolver Key: JBCOMMON-127 URL: https://issues.jboss.org/browse/JBCOMMON-127 Project: JBoss Common Issue Type: Feature Request Security Level: Public (Everyone can see) Components: common-core (2.x) Reporter: Dimitris Andreadis Assignee: Thomas Diesler Fix For: 2.2.19.GA Extend JBossEntityResolver to also implement LSResourceResolver. Thomas performed this addition without any JIRA record (too bad), so I'm adding this after the fact. I'm removing also an unnecessary dependency that had crept into the change: import com.sun.org.apache.xpath.internal.operations.Bool; -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] (EJBTHREE-2275) PreDestroy lifecycle callback not called when Activated EJB3 SFSB removal timeout is reached

by Brad Maxwell (JIRA)

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] (EJBTHREE-2275) PreDestroy lifecycle callback not called when Activated EJB3 SFSB removal timeout is reached

by Brad Maxwell (JIRA)

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-879) use-strict-min should trigger prefill of pools

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-879: ------------------------------------- Summary: use-strict-min should trigger prefill of pools Key: JBJCA-879 URL: https://issues.jboss.org/browse/JBJCA-879 Project: IronJacamar Issue Type: Bug Components: Core Reporter: Jesper Pedersen Assignee: Jesper Pedersen -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
2
0 / 0

[JBoss JIRA] (REMJMX-12) Allow for protocol versions to be excluded client and server side

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-12?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated REMJMX-12: ----------------------------------- Fix Version/s: 1.0.5.CR1 (was: 1.0.4.Final) > Allow for protocol versions to be excluded client and server side > ----------------------------------------------------------------- > > Key: REMJMX-12 > URL: https://issues.jboss.org/browse/REMJMX-12 > Project: Remoting JMX > Issue Type: Task > Components: Connection > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.0.5.CR1 > > > Once we start supporting multiple versions of the protocols we should also allow version to be excluded client and server side. > This will mean if a version is identified as being problematic is can be excluded to force the use of a previous version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-48) Release Remoting JMX 1.0.4

by Darran Lofthouse (JIRA)

Darran Lofthouse created REMJMX-48: -------------------------------------- Summary: Release Remoting JMX 1.0.4 Key: REMJMX-48 URL: https://issues.jboss.org/browse/REMJMX-48 Project: Remoting JMX Issue Type: Task Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.0.4.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
1
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 August 2012