September 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5033) Add support to specify ciphers available with Remoting

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-5033: ------------------------------------- Summary: Add support to specify ciphers available with Remoting Key: AS7-5033 URL: https://issues.jboss.org/browse/AS7-5033 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management, Remoting, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.2.0.Alpha1 -- 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

11 years, 6 months

2
2
0 / 0

[JBoss JIRA] (JGRP-1410) globalThreadGroup not destroyed creates a classloader memory leak

by Jean-Philippe Gariepy (Created) (JIRA)

globalThreadGroup not destroyed creates a classloader memory leak ----------------------------------------------------------------- Key: JGRP-1410 URL: https://issues.jboss.org/browse/JGRP-1410 Project: JGroups Issue Type: Bug Affects Versions: 3.0.1 Environment: linux w/ java 1.6 Reporter: Jean-Philippe Gariepy Assignee: Bela Ban When all channels are closed, the globalThreadGroup is not destroyed. For a normal (i.e. non-web) application, this is not a problem since the process will exit anyway. However, for a Java Enterprise web application, this causes a classloader memory leak since the ThreadGroup object has strong references to JGroups instances having strong references to their class object having strong reference to their class loader. Since the class loader is pointed by strong references, the it cannot be garbage collected and hence a leak is created each time the web application is stopped. -- 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

11 years, 6 months

5
16
0 / 0

[JBoss JIRA] (AS7-5636) Server does not start if the installation path contains non-English characters [UTF-8 characters]

by Y D Prakash (JIRA)

Y D Prakash created AS7-5636: -------------------------------- Summary: Server does not start if the installation path contains non-English characters [UTF-8 characters] Key: AS7-5636 URL: https://issues.jboss.org/browse/AS7-5636 Project: Application Server 7 Issue Type: Bug Reporter: Y D Prakash -- 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

11 years, 6 months

2
5
0 / 0

[JBoss JIRA] (AS7-5655) Cannot restart ejb3 bundle after activation failure

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-5655: ----------------------------------- Summary: Cannot restart ejb3 bundle after activation failure Key: AS7-5655 URL: https://issues.jboss.org/browse/AS7-5655 Project: Application Server 7 Issue Type: Bug Components: JPA / Hibernate, OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler {code} Caused by: java.lang.IllegalStateException: JBAS014666: Duplicate resource persistence-bundle-b.jar#simple-persistence at org.jboss.as.controller.registry.AbstractModelResource$DefaultResourceProvider.register(AbstractModelResource.java:225) at org.jboss.as.controller.registry.AbstractModelResource.registerChild(AbstractModelResource.java:135) at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.addManagementConsole(PersistenceUnitServiceHandler.java:727) at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.deployPersistenceUnit(PersistenceUnitServiceHandler.java:406) at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.addPuService(PersistenceUnitServiceHandler.java:274) at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.handleJarDeployment(PersistenceUnitServiceHandler.java:142) at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.deploy(PersistenceUnitServiceHandler.java:117) at org.jboss.as.jpa.processor.PersistenceCompleteInstallProcessor.deploy(PersistenceCompleteInstallProcessor.java:48) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2 {code} -- 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

11 years, 6 months

2
3
0 / 0

[JBoss JIRA] (JBEE-110) Add relocations from org.jboss.spec.* to non org.jboss.spec artifacts

by Pete Muir (JIRA)

Pete Muir created JBEE-110: ------------------------------ Summary: Add relocations from org.jboss.spec.* to non org.jboss.spec artifacts Key: JBEE-110 URL: https://issues.jboss.org/browse/JBEE-110 Project: JBoss JavaEE Spec APIs Issue Type: Feature Request Reporter: Pete Muir Assignee: Paul Gier For example, we use org.hibernate and javax.enterprise group ids for JPA and CDI. It would be nice if we created stubs with relocations for these under org.jboss.spec so that the new developer can just follow the naming conventions with no exceptions. -- 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

11 years, 6 months

1
2
0 / 0

[JBoss JIRA] (AS7-3160) Could not find Extension-List entry ExtensionListEntry because of Java 6+ Extension Mecanism

by Cristhian Lopez (Created) (JIRA)

Could not find Extension-List entry ExtensionListEntry because of Java 6+ Extension Mecanism -------------------------------------------------------------------------------------------- Key: AS7-3160 URL: https://issues.jboss.org/browse/AS7-3160 Project: Application Server 7 Issue Type: Bug Components: Class Loading Affects Versions: 7.1.0.Final Environment: JDK 1.6.0_30 b12 JBoss AS 7.1 CR1b Reporter: Cristhian Lopez Assignee: David Lloyd When deploying Liferay 6.1 I'm getting the following error {code}08:08:38,561 WARN [org.jboss.as.server.deployment.module.module-extension-list-processor] (MSC service thread 1-1) Could not find Extension-List entry ExtensionListEntry [name=javax.crypto, title=crypto] referenced from ResourceRoot [root="/D:/Development/Servers/jboss-as-7.1.0.CR1b/content/ROOT.war/WEB-INF/classes"]{code} After some debug on the JBoss 7.1 CR1b source I found that it uses the java.ext.dirs property to find the ext libs, but since java 1.6 the property returns a classpath formated string with more than one path where the extensions are located(http://docs.oracle.com/javase/tutorial/ext/basics/install.html), but on the JBoss code I found that it's trying to parse the property value as a File path directly. As you can se on the ServerEnvironment.java line 292 {code}// Java system-wide extension dirs javaExtDirs = getFilesFromProperty(JAVA_EXT_DIRS, props);{code} and line 524 {code} private File getFileFromProperty(final String name, final Properties props) { String value = props.getProperty(name, null); if (value != null) { File f = new File(value); return f; } return null; } {code} This is causing that the server can´t find the extensions and warning about it. -- 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

11 years, 6 months

6
11
0 / 0

[JBoss JIRA] (AS7-3623) mod_cluster schema 1.1

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-3623: ----------------------------------- Summary: mod_cluster schema 1.1 Key: AS7-3623 URL: https://issues.jboss.org/browse/AS7-3623 Project: Application Server 7 Issue Type: Feature Request Reporter: Radoslav Husar Assignee: Radoslav Husar Fix For: 7.1.0.Final TODO -- 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

11 years, 6 months

3
7
0 / 0

[JBoss JIRA] (AS7-5170) add deployed JMS destinations to the Web console

by Jeff Mesnil (JIRA)

Jeff Mesnil created AS7-5170: -------------------------------- Summary: add deployed JMS destinations to the Web console Key: AS7-5170 URL: https://issues.jboss.org/browse/AS7-5170 Project: Application Server 7 Issue Type: Enhancement Components: Console Reporter: Jeff Mesnil Assignee: Heiko Braun The user can deploy JMS destinations as parts of deployed archives. These destinations are manageable from the CLI and exposes their metrics (e.g. /deployment=jboss-as-helloworld-mdb.war/subsystem=messaging/hornetq-server=default/jms-queue=HELLOWORLDMDBQueue) It'd be useful for users if these deployed JMS destinations could display their metrics in the runtime tab of the Web console in addition to the regular JMS destinations -- 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

11 years, 6 months

3
14
0 / 0

[JBoss JIRA] (AS7-5652) POJO subsytem isn't setting the TCCL to the application's class loader

by Michael Vetter (JIRA)

Michael Vetter created AS7-5652: ----------------------------------- Summary: POJO subsytem isn't setting the TCCL to the application's class loader Key: AS7-5652 URL: https://issues.jboss.org/browse/AS7-5652 Project: Application Server 7 Issue Type: Bug Components: POJO Affects Versions: 7.2.0.Alpha1 Reporter: Michael Vetter Assignee: Ales Justin The POJO subsytem isn't setting the TCCL (Thread.currentThread().getContextClassLoader()) to the application's class loader while invoking on the application's lifecycle methods. The TCCL is set to the "ModuleClassLoader for Module "org.jboss.as.pojo:main" from local module loader". It was working in JBoss5.1 to start a bean with an xml file (<deployment xmlns="urn:jboss:bean-deployer:2.0"> ...) and to use the TCCL during deployment to load resources and classes from the ear. With the pojo ModuleClassLoader these resources are not found. -- 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

11 years, 6 months

5
6
0 / 0

[JBoss JIRA] (SECURITY-638) The login modules need to be modified to check for (complain about) configuration options that have been specified but are not used (invalid, unrecognized, etc). This might be helpful in catching situations where the option name was spelled incorrectly or

by Tom Fonteyne (Created) (JIRA)

The login modules need to be modified to check for (complain about) configuration options that have been specified but are not used (invalid, unrecognized, etc). This might be helpful in catching situations where the option name was spelled incorrectly or --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: SECURITY-638 URL: https://issues.jboss.org/browse/SECURITY-638 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: PicketBox Affects Versions: JBossSecurity_2.0.4.SP9 Reporter: Tom Fonteyne Assignee: Anil Saldhana Priority: Minor Fix For: JBossSecurity_2.0.4.SP9 porting https://issues.jboss.org/browse/JBPAPP-7794 to PicketBox -- 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

11 years, 6 months

7
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2012