November 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JASSIST-126) create OSGi bundle information

by Mark Struberg (JIRA)

create OSGi bundle information ------------------------------ Key: JASSIST-126 URL: https://jira.jboss.org/browse/JASSIST-126 Project: Javassist Issue Type: Feature Request Affects Versions: 3.12.0.GA Reporter: Mark Struberg Assignee: Shigeru Chiba Fix For: 3.13.0.GA Create OSGi bundle information for javassist at build time. -- 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

12 years

5
9
0 / 0

[JBoss JIRA] (AS7-6006) 128.4 Web URL Handler

by David Bosschaert (JIRA)

David Bosschaert created AS7-6006: ------------------------------------- Summary: 128.4 Web URL Handler Key: AS7-6006 URL: https://issues.jboss.org/browse/AS7-6006 Project: Application Server 7 Issue Type: Sub-task Components: OSGi Affects Versions: 7.2.0.Alpha1 Reporter: David Bosschaert Assignee: David Bosschaert The webbundle: URL handler needs to be provides as described in section 128.4 of the specification. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

2
2
0 / 0

[JBoss JIRA] (AS7-5738) JNDI View doesn't work in domain mode

by Heiko Braun (JIRA)

Heiko Braun created AS7-5738: -------------------------------- Summary: JNDI View doesn't work in domain mode Key: AS7-5738 URL: https://issues.jboss.org/browse/AS7-5738 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.2.0.CR1 Yields an exception on the server side: {noformat} [Server:server-one] Caused by: java.lang.ClassNotFoundException: javax.management.j2ee.ManagementHome from [Module "org.jboss.as.naming:main" from local module loader @e49d67c (roots: /Users/hbraun/dev/prj/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/modules)] [Server:server-one] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.1.3.GA] [Server:server-one] at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) [jboss-modules.jar:1.1.3.GA] [Server:server-one] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) [jboss-modules.jar:1.1.3.GA] [Server:server-one] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423) [jboss-modules.jar:1.1.3.GA] [Server:server-one] at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) [jboss-modules.jar:1.1.3.GA] {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

2
1
0 / 0

[JBoss JIRA] (AS7-4532) fix jvm management model for server and groups

by Emanuel Muckenhuber (JIRA)

Emanuel Muckenhuber created AS7-4532: ---------------------------------------- Summary: fix jvm management model for server and groups Key: AS7-4532 URL: https://issues.jboss.org/browse/AS7-4532 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.0.Final, 7.0.0.Final Reporter: Emanuel Muckenhuber Fix For: 7.2.0.Alpha1 We need to update the JVM child resource definition for server-groups and servers to only allow a single JVM configuration (i.e. configuration=JVM) resource. Currently only the first configured VM is used, where the name is the reference to the corresponding host level JVM. -- 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

12 years

2
3
0 / 0

[JBoss JIRA] (AS7-3463) Provide Unit for JVM configuration elements

by Heiko Braun (JIRA)

Heiko Braun created AS7-3463: -------------------------------- Summary: Provide Unit for JVM configuration elements Key: AS7-3463 URL: https://issues.jboss.org/browse/AS7-3463 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Heiko Braun Assignee: Brian Stansberry Fix For: 7.2.0.Alpha1 Like with any other config element, units for the JVM parameters would nice. I.e. instead of encoding it into the string value ("64m") it would be better to split the actual value from unit (value=64, unit=<kb|mb|gb>). See the thread subsystem for a reference how this is done in other places -- 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

12 years

2
3
0 / 0

[JBoss JIRA] (AS7-6024) <object-factory> schema says factoryClass but parser looks for class

by James Livingston (JIRA)

James Livingston created AS7-6024: ------------------------------------- Summary: <object-factory> schema says factoryClass but parser looks for class Key: AS7-6024 URL: https://issues.jboss.org/browse/AS7-6024 Project: Application Server 7 Issue Type: Bug Components: Naming Affects Versions: 7.1.3.Final (EAP) Reporter: James Livingston Assignee: Eduardo Martins The XSD for the naming subsystem contains a "factoryClass" attribute for objectFactoryType. NamingSubsystemXMLAttribute however defines it to be called "class". One of these needs to be changed so that the schema matches the parser, and either "class" validates or "factoryClass" can be used. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

3
2
0 / 0

[JBoss JIRA] (JBAOP-814) When the system property sun.io.serialization.extendedDebugInfo is set, JBoss AOP throws java.lang.NullPointerException

by Kabir Khan (JIRA)

Kabir Khan created JBAOP-814: -------------------------------- Summary: When the system property sun.io.serialization.extendedDebugInfo is set, JBoss AOP throws java.lang.NullPointerException Key: JBAOP-814 URL: https://issues.jboss.org/browse/JBAOP-814 Project: JBoss AOP Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.1.6.CP06 Reporter: Kabir Khan Assignee: Kabir Khan Fix For: 2.1.6.CP07 See JBPAPP-10467 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] Created: (JBAOP-796) Creation of ClassAdvisor must use the AspectManager equivalent to the advised class' ClassLoader

by Flavia Rainone (JIRA)

Creation of ClassAdvisor must use the AspectManager equivalent to the advised class' ClassLoader ------------------------------------------------------------------------------------------------ Key: JBAOP-796 URL: https://jira.jboss.org/browse/JBAOP-796 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.1.9.Alpha1 Reporter: Flavia Rainone Assignee: Flavia Rainone Fix For: 2.1.6 CP01, 2.1.9.GA, 2.2.1.GA Currently, an Advisor is created by calling AspectManager.instance().getAdvisor(). The correct is to create the advisor by calling AspectManager.instance(WovenClass.class).getAdvisor(WovenClass.class). Otherwise, the Advisor will be created as part of the AspectManager/Domain corresponding to the current context class loader: public static synchronized AspectManager instance() { return instance(Thread.currentThread().getContextClassLoader()); } In the JBoss AS environment, if the woven class is loaded during an archive deployment, this is equivalent to say that the Advisor will be erroneously created by the domain of the current deployment, instead of being created by the appropriate AspectManager/Domain instance. -- 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

12 years

2
10
0 / 0

[JBoss JIRA] (JBAOP-812) AspectManager.getAdvisors throws ConcurrentModificationException

by Flavia Rainone (JIRA)

Flavia Rainone created JBAOP-812: ------------------------------------ Summary: AspectManager.getAdvisors throws ConcurrentModificationException Key: JBAOP-812 URL: https://issues.jboss.org/browse/JBAOP-812 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.1.6.CP03 Reporter: Flavia Rainone Assignee: Flavia Rainone Fix For: 2.1.6.CP04 The problem can be observed sometimes when running JBoss AS. The stack trace: ERROR [STDERR] (AOPListner:) java.util.ConcurrentModificationException ERROR [STDERR] (AOPListner:) at java.util.WeakHashMap$HashIterator.next(WeakHashMap.java:169) ERROR [STDERR] (AOPListner:) at org.jboss.aop.AspectManager.getAdvisors(AspectManager.java:543) ERROR [STDERR] (AOPListner:) at org.jboss.console.plugins.AOPLister$RefreshPoller.run(AOPLister.java:891) -- 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

12 years

2
2
0 / 0

[JBoss JIRA] Created: (JBAOP-806) Using UnmodifiableLinkedHashMap constructor causes an UnsupportedOperationException exception to be thrown on IBM JDK

by Dustin Kut Moy Cheung (JIRA)

Using UnmodifiableLinkedHashMap constructor causes an UnsupportedOperationException exception to be thrown on IBM JDK --------------------------------------------------------------------------------------------------------------------- Key: JBAOP-806 URL: https://issues.jboss.org/browse/JBAOP-806 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Components: Aspect Library Environment: OS: Fedora 14 JDK: IBM JDK Reporter: Dustin Kut Moy Cheung Priority: Critical Read Summary. This error is caused because the IBM JDK LinkedHashMap invokes the putAll method on HashMap. Since the putAll method is overwridden in UnmodifiableLinkedHashMap.java, the UnmodifiableLinkedHashMap putAll method is called instead of the HashMap constructor and therefore throws that exception. The fix is to change the signature of the constructor being called (LinkedHashMap constructor) so that the putAll method is not called. Please see the patch that attempts to solve this issue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

3
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2012