May 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-7909) AOPClassLoaderDeployer breaks OSGi integration

by Thomas Diesler (JIRA)

AOPClassLoaderDeployer breaks OSGi integration ---------------------------------------------- Key: JBAS-7909 URL: https://jira.jboss.org/jira/browse/JBAS-7909 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: AOP Reporter: Thomas Diesler Assignee: Kabir Khan Fix For: JBossAS-6.0.0.M3 11:11:21,726 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to ClassLoader: name=vfs:///home/tdiesler/svn/jbossas/trunk/build/target/jboss-6.0.0-SNAPSHOT/server/default/deploy/osgi/org.osgi.compendium.jar state=Describe mode=Manual requiredState=ClassLoader: org.jboss.deployers.spi.DeploymentException: Error during deploy: vfs:///home/tdiesler/svn/jbossas/trunk/build/target/jboss-6.0.0-SNAPSHOT/server/default/deploy/osgi/org.osgi.compendium.jar at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) Caused by: java.lang.IllegalStateException: Have ClassLoaderDomain@12078a{NOT_USED_PLACEHOLDER} but no classloader domain at org.jboss.aop.asintegration.jboss5.AOPVFSClassLoaderDomainRegistry.validateInitMaps(AOPVFSClassLoaderDomainRegistry.java:85) at org.jboss.classpool.plugins.jbosscl.VFSClassLoaderDomainRegistry.initMapsForModule(VFSClassLoaderDomainRegistry.java:119) at org.jboss.classpool.plugins.jbosscl.RegisterModuleCallback.registerModule(RegisterModuleCallback.java:87) at org.jboss.classpool.plugins.jbosscl.JBossClDelegatingClassPoolFactory.create(JBossClDelegatingClassPoolFactory.java:83) at org.jboss.classpool.plugins.jbosscl.JBossClDelegatingClassPoolFactory.create(JBossClDelegatingClassPoolFactory.java:50) at org.jboss.aop.asintegration.jboss5.JBoss5Integration.create(JBoss5Integration.java:157) at org.jboss.classpool.scoped.ScopedClassPoolRepositoryImpl.createScopedClassPool(ScopedClassPoolRepositoryImpl.java:93) at org.jboss.classpool.scoped.ScopedClassPoolRepositoryImpl.registerClassLoader(ScopedClassPoolRepositoryImpl.java:125) at org.jboss.classpool.spi.ClassPoolRepository.registerClassLoader(ClassPoolRepository.java:138) at org.jboss.aop.AspectManager.registerClassLoader(AspectManager.java:846) at org.jboss.aop.asintegration.jboss5.VFSClassLoaderScopingPolicy.registerClassLoader(VFSClassLoaderScopingPolicy.java:46) at org.jboss.aop.asintegration.jboss5.AOPClassLoaderInitializer.registerLoaders(AOPClassLoaderInitializer.java:84) at org.jboss.aop.asintegration.jboss5.AOPClassLoaderInitializer.initializeForUnit(AOPClassLoaderInitializer.java:41) at org.jboss.aop.asintegration.jboss5.AOPClassLoaderDeployer.internalDeploy(AOPClassLoaderDeployer.java:65) at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

4
9
0 / 0

[JBoss JIRA] Created: (JBAS-8730) Hudson testsuite hangs because of Null deploymentHash

by Thomas Diesler (JIRA)

Hudson testsuite hangs because of Null deploymentHash ------------------------------------------------------ Key: JBAS-8730 URL: https://issues.jboss.org/browse/JBAS-8730 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler http://jbmuc.dyndns.org:8280/hudson/job/jbosgi-remote/6/console 09:32:34,528 INFO [org.jboss.as.server.deployment] (pool-5-thread-2) Content with name example-xservice-client-module added at location /usr/share/tomcat6/workspace/hudson-home/jobs/jbosgi-remote/workspace/jboss-7.0.0.Alpha2/standalone/data/content/00/7a37a86ec7949184af8867631ca10f61c1f7a1/content 09:32:34,612 ERROR [org.jboss.as.protocol.connection] (pool-5-thread-2) Failed to read a message: java.io.IOException: Failed to handle management operation at org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:63) at org.jboss.as.protocol.ConnectionImpl.safeHandleMessage(ConnectionImpl.java:239) at org.jboss.as.protocol.ConnectionImpl$1$1.run(ConnectionImpl.java:198) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_22] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_22] at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] Caused by: java.lang.IllegalArgumentException: deploymentHash is null at org.jboss.as.model.ServerModelDeploymentAdd.<init>(ServerModelDeploymentAdd.java:48) at org.jboss.as.server.mgmt.deployment.ServerDeploymentManagerImpl.addServerGroupDeploymentUpdate(ServerDeploymentManagerImpl.java:302) at org.jboss.as.server.mgmt.deployment.ServerDeploymentManagerImpl.execute(ServerDeploymentManagerImpl.java:211) at org.jboss.as.server.standalone.management.ServerControllerOperationHandler$ExecuteDeploymentPlanOperation.sendResponse(ServerControllerOperationHandler.java:386) at org.jboss.as.protocol.mgmt.ManagementResponse$2.handle(ManagementResponse.java:119) at org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:59) ... 5 more -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8536) Cannot connect to JSR160 with IPv6

by Thomas Diesler (JIRA)

Cannot connect to JSR160 with IPv6 ---------------------------------- Key: JBAS-8536 URL: https://jira.jboss.org/browse/JBAS-8536 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Management services Reporter: Thomas Diesler Assignee: Dimitris Andreadis Fix For: 7.0.0.M2 jconsole cannot connect using a connection URL when server runs with IPv6 on Fedora13 -- 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

15 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8657) Provide an installer for AS7

by Thomas Diesler (JIRA)

Provide an installer for AS7 ---------------------------- Key: JBAS-8657 URL: https://jira.jboss.org/browse/JBAS-8657 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Installer Reporter: Thomas Diesler Assignee: Amit Bhayani Brian says I don't see commented out config as a solution. First, at this point, when the file is re-written following an update, comments are lost. That may change, but in general using the file as documentation is fragile. Second, if we added commented out sections for all the various options different subsystems may want to expose, we'll soon have a 1,00 line file full of confusing stuff. I think we're going to need a mix of things to solve this: 1) Ship a few different canned configs files for the most common profiles, with the user able to select which they want via a command line switch. 2) An "examples" dir in the dist where some less common choices can be highlighted. 3) Most importantly, an installer application where users can easily tell us what subsystems they want in their profile. This is the most important part; #1 is mostly to provide a very easy out-of-the-box experience. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-8722) Deployment rollback does not log the cause of the rollback

by Thomas Diesler (JIRA)

Deployment rollback does not log the cause of the rollback ---------------------------------------------------------- Key: JBAS-8722 URL: https://jira.jboss.org/browse/JBAS-8722 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployers Reporter: Thomas Diesler Assignee: Thomas Diesler -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8948) Switchboard: Add configuration option to ResourceEnvRefProvider to not throw RuntimeException upon missing @Resource annotation

by Daniel Bevenius (JIRA)

Switchboard: Add configuration option to ResourceEnvRefProvider to not throw RuntimeException upon missing @Resource annotation ------------------------------------------------------------------------------------------------------------------------------- Key: JBAS-8948 URL: https://issues.jboss.org/browse/JBAS-8948 Project: JBoss Application Server Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Daniel Bevenius Assignee: jaikiran pai Using a javax.annotation.Resource that is not intended for JBoss MC, perhaps Spring is being used, causes a RuntimeException to be throw upon startup of JBoss AS 6.0.0.Final. For example, if you have a class that looks like this: {code} import javax.annotation.Resource; public class AnnotatedClass { @Resource public void setterMethodWithAnnotation(SampleClass sample) { } } {code} And this class in packaged into a war and deployed the exception below will be thrown: {noformat} Caused by: java.lang.RuntimeException: Neither any mapped-name/lookup/jndi-name specified nor any ResourceProvider could process resource-env-ref named env/se.rl.pop.AnnotatedClass/terMethodWithAnnotation of type se.rl.pop.SampleClass at org.jboss.switchboard.mc.resource.provider.ResourceEnvRefProvider.provide(ResourceEnvRefProvider.java:136) [:1.0.0-alpha-16-SNAPSHOT] at org.jboss.switchboard.mc.resource.provider.ResourceEnvRefProvider.provide(ResourceEnvRefProvider.java:1) [:1.0.0-alpha-16-SNAPSHOT] at org.jboss.switchboard.mc.JndiEnvironmentProcessor.process(JndiEnvironmentProcessor.java:68) [:1.0.0-alpha-16-SNAPSHOT] at org.jboss.switchboard.mc.deployer.AbstractSwitchBoardDeployer.process(AbstractSwitchBoardDeployer.java:119) [:1.0.0-alpha-16-SNAPSHOT] at org.jboss.switchboard.mc.deployer.WebEnvironmentSwitchBoardDeployer.internalDeploy(WebEnvironmentSwitchBoardDeployer.java:66) [:1.0.0-alpha-16-SNAPSHOT] at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55) [:2.2.0.GA] at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179) [:2.2.0.GA] ... 43 more {noformat} Resource scanning can be turned off by adding a jboss-scanning.xml to WEB-INF/META-INF but this jira suggests that a property be added to ResourceEnvRefProvider that configures if this class should throw a RuntimeException of just log a message. This would save users to have to add a jboss-scanning.xml to their deployments. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
15
0 / 0

[JBoss JIRA] Created: (JBAS-9386) Upgrade to Remoting 2.5.4.SP2

by Ron Sigal (JIRA)

Upgrade to Remoting 2.5.4.SP2 ----------------------------- Key: JBAS-9386 URL: https://issues.jboss.org/browse/JBAS-9386 Project: Legacy JBoss Application Server 6 Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Ron Sigal Assignee: Shelly McGowan Fix For: 6.1.0 Remoting release 2.5.4.SP2 incorporates the issues from "ephemeral" releases 2.5.4 and 2.5.4.SP1 (see JBAS-9043 "Upgrade to Remoting 2.5.4.SP1") plus Release Notes - JBoss Remoting - Version 2.5.4.SP2 Bug * [JBREM-1276] - SecondaryServerSocketThread should catch java.lang.Error * [JBREM-1282] - ServerInvoker does not close StreamHandler in the case of "addstreamcallback" * [JBREM-1285] - Callback Connector for in-jvm connection should create a LocalServerInvoker * [JBREM-1288] - StreamServer for in-jvm connection should create a LocalServerInvoker Enhancement * [JBREM-1277] - Allow configuration of socket and bisocket accept thread priority * [JBREM-1283] - CLONE [JBREM-1281] - Support setting executor in CoyoteInvoker Release * [JBREM-1291] - Release 2.5.4.SP2 Task * [JBREM-1290] - Assure version compatibility with earlier versions of Remoting -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBEE-79) Release 1.0.0.Final of the jboss-rmi-api_1.0_spec

by Stefan Guilhen (JIRA)

Release 1.0.0.Final of the jboss-rmi-api_1.0_spec ------------------------------------------------- Key: JBEE-79 URL: https://issues.jboss.org/browse/JBEE-79 Project: JBoss JavaEE APIs Issue Type: Task Reporter: Stefan Guilhen Assignee: Stefan Guilhen -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBEE-78) Create a RMI API module that includes the javax.rmi and javax.rmi.CORBA packages

by Stefan Guilhen (JIRA)

Create a RMI API module that includes the javax.rmi and javax.rmi.CORBA packages -------------------------------------------------------------------------------- Key: JBEE-78 URL: https://issues.jboss.org/browse/JBEE-78 Project: JBoss JavaEE APIs Issue Type: Task Reporter: Stefan Guilhen Assignee: Stefan Guilhen The IIOP/AS7 integration requires a build of the javax.rmi and javax.rmi.CORBA packages that uses JacORB's org.omg API to avoid conflicts with the JDK CORBA API. As a result, a RMI API module is to be added to the specs project with the relevant packages extracted from the OpenJDK. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Moved: (AS7-766) EAR and other top level deployments should be Atomic

by Brad Maxwell (JIRA)

[ https://issues.jboss.org/browse/AS7-766?page=com.atlassian.jira.plugin.sy... ] Brad Maxwell moved JBPAPP-6518 to AS7-766: ------------------------------------------ Project: Application Server 7 (was: JBoss Enterprise Application Platform) Key: AS7-766 (was: JBPAPP-6518) Workflow: GIT Pull Request workflow (was: jira) Affects Version/s: (was: EAP_EWP 5.1.0) Component/s: Server (was: System) Security: (was: Public) Fix Version/s: (was: EAP_EWP 5.1.2) Docs QE Status: (was: NEW) > EAR and other top level deployments should be Atomic > ---------------------------------------------------- > > Key: AS7-766 > URL: https://issues.jboss.org/browse/AS7-766 > Project: Application Server 7 > Issue Type: Bug > Components: Server > Reporter: Brad Maxwell > Assignee: Jason Greene > > Issue: If an ear or other deployment that contains sub-deployments is deployed and one of the sub-deployments fails to deploy, the ear should fail and unwind all sub-deployments. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

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 May 2011