April 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-9261) AS7: "IllegalArgumentException: key is null" on deploy

by Wolfgang Knauf (JIRA)

AS7: "IllegalArgumentException: key is null" on deploy ------------------------------------------------------ Key: JBAS-9261 URL: https://issues.jboss.org/browse/JBAS-9261 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 7.0.0.Beta2 Reporter: Wolfgang Knauf I have a small JavaEE5 sample app, which consists of a stateless bean, a web client project (servlet + jsp) and an app client app, all bundled to an EAR file. There are no annotations, just deployment descriptors. The app worked fine on AS5. I copy it to the "standalone\deployed" folder of a JBoss pulled from GIT and built yesterday (2011-04-06). It fails with this error: 23:12:28,258 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.unit."Stateless.ear"."StatelessWeb.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."Stateless.ear"."StatelessWeb.war".INSTALL: Failed to process phase INSTALL of subdeployment "StatelessWeb.war" of deployment "Stateless.ear" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:108) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1344) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24] at java.lang.Thread.run(Thread.java:662) [:1.6.0_24] Caused by: java.lang.IllegalArgumentException: key is null at org.jboss.msc.service.UnlockedReadHashMap.put(UnlockedReadHashMap.java:230) at org.jboss.msc.service.ServiceContainerImpl.getOrCreateRegistration(ServiceContainerImpl.java:431) at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:499) at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:188) at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:1808) at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:188) at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:1808) at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:188) at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:1808) at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:188) at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:1808) at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:188) at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:1808) at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:188) at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:1808) at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:188) at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:1808) at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:188) at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:1808) at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:188) at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:1808) at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:188) at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:1808) at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:188) at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:1808) at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:188) at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:1808) at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:310) at org.jboss.as.ee.component.ModuleJndiBindingProcessor.addJndiBinding(ModuleJndiBindingProcessor.java:83) at org.jboss.as.ee.component.ModuleJndiBindingProcessor.deploy(ModuleJndiBindingProcessor.java:51) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:102) ... 4 more The sample can be found here: http://www.cs.hs-rm.de/~knauf/KomponentenArchitekturen2008/stateless/Stat... (rename EAR file to "Stateless.ear" before deploying) The same sample, which uses annotations instead of deployment descriptors, deploys without errors (http://www.cs.hs-rm.de/~knauf/KomponentenArchitekturen2008/stateless/Stat...). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

5
9
0 / 0

[JBoss JIRA] Created: (JBAS-9010) Provide more comprehensive error messages for missing dependencies

by David Lloyd (JIRA)

Provide more comprehensive error messages for missing dependencies ------------------------------------------------------------------ Key: JBAS-9010 URL: https://issues.jboss.org/browse/JBAS-9010 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: 7.0.0.Beta3 When a deployment unit's ACTIVE service set is either fully installed, a deployment complete message is printed. When this service set consists of zero or more fully installed services, where each of the remaining services in the set possess one or more of the following traits: # Has missing dependency # Has failed dependency # Is failed Then a deployment shall be considered to be failed. For each failed deployment, a failed message should be logged with a summary of the problem. All missing dependencies should be associated with the applicable deployment dependent(s) and listed. Services which are failed should be listed BUT not with the failure cause or stack trace, which will have appeared in the log already. Deployments that have failed will also cause the runtime portion of the operation to be treated as failed; the deployment or server start operation handler may act on this information as it would with any failed operation. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

4
8
0 / 0

[JBoss JIRA] Created: (JBRULES-2965) OSGi bundles's multiproject should not have a (non dependencyManagement scoped) dependency on it's own module (jxls)

by Geoffrey De Smet (JIRA)

OSGi bundles's multiproject should not have a (non dependencyManagement scoped) dependency on it's own module (jxls) -------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2965 URL: https://issues.jboss.org/browse/JBRULES-2965 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Priority: Minor Fix For: 5.2.0.M2 also blocks making a decent osgi assembly distribution -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2964) Knowledge Agent: Create a helper class to programatically define and apply Change-Sets

by Esteban Aliverti (JIRA)

Knowledge Agent: Create a helper class to programatically define and apply Change-Sets -------------------------------------------------------------------------------------- Key: JBRULES-2964 URL: https://issues.jboss.org/browse/JBRULES-2964 Project: Drools Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Esteban Aliverti Assignee: Esteban Aliverti Priority: Optional Fix For: FUTURE Create a Helper class or API that allows users to define a change-set without using xml. This class will also lets user apply the change-set to a knowledge agent instance. Right now, it is possible to do all these tasks, but it would be much better to have a centralized way to do them. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-9107) A rar deployment must always activate or error out

by Carlo de Wolf (JIRA)

A rar deployment must always activate or error out -------------------------------------------------- Key: JBAS-9107 URL: https://issues.jboss.org/browse/JBAS-9107 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JCA service Reporter: Carlo de Wolf Assignee: Jesper Pedersen Priority: Critical Fix For: 7.0.0.Beta2 If AbstractResourceDeployerAdapter.checkActivation returns false the deployment is silently accepted but never activated. Should the RAR deployment contain a ResourceAdapter this would still result in CommonDeployment.resourceAdapter being null. CommonDeployment.resourceAdapter must never be null at this point. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

4
9
0 / 0

[JBoss JIRA] Created: (JBAS-9334) Undeployment of a RAR attempts to write RO naming context

by Brian Stansberry (JIRA)

Undeployment of a RAR attempts to write RO naming context --------------------------------------------------------- Key: JBAS-9334 URL: https://issues.jboss.org/browse/JBAS-9334 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JCA service Reporter: Brian Stansberry Assignee: Jesper Pedersen Fix For: 7.0.0.Beta3 Affects AS trunk as of April 15: [Server:other-2] 13:08:10,198 WARN [org.jboss.as.connector.jndi] (MSC service thread 1-1) Exception during unbind: java.lang.UnsupportedOperationException: Naming context is read-only [Server:other-2] at org.jboss.as.naming.NamingContext.unbind(NamingContext.java:232) [Server:other-2] at javax.naming.InitialContext.unbind(InitialContext.java:420) [:1.6.0_24] [Server:other-2] at org.jboss.util.naming.Util.unbind(Util.java:151) [Server:other-2] at org.jboss.util.naming.Util.unbind(Util.java:141) [Server:other-2] at org.jboss.as.connector.jndi.AS7JndiStrategy.unbindObject(AS7JndiStrategy.java:194) [Server:other-2] at org.jboss.as.connector.jndi.AS7JndiStrategy.unbindConnectionFactories(AS7JndiStrategy.java:108) [Server:other-2] at org.jboss.as.connector.metadata.deployment.AbstractResourceAdapterDeploymentService.stop(AbstractResourceAdapterDeploymentService.java:101) [Server:other-2] at org.jboss.as.connector.metadata.deployment.ResourceAdapterDeploymentService.stop(ResourceAdapterDeploymentService.java:146) [Server:other-2] at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:1444) [Server:other-2] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24] [Server:other-2] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24] [Server:other-2] at java.lang.Thread.run(Thread.java:680) [:1.6.0_24] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-2869) Split up the build, the repositories and hudson jobs in seperate projects: at least drools, jBPM, guvnor and eclipse so it's easier to fork, checkout and build one project

by Geoffrey De Smet (JIRA)

Split up the build, the repositories and hudson jobs in seperate projects: at least drools, jBPM, guvnor and eclipse so it's easier to fork, checkout and build one project --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2869 URL: https://issues.jboss.org/browse/JBRULES-2869 Project: Drools Issue Type: Task Security Level: Public (Everyone can see) Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Fix For: 5.2.0.M2 still use a parent pom. Learn from seam 3. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-9240) Logging in ResourceAdaptersExtension needs cleaning

by jaikiran pai (JIRA)

Logging in ResourceAdaptersExtension needs cleaning --------------------------------------------------- Key: JBAS-9240 URL: https://issues.jboss.org/browse/JBAS-9240 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JCA service Environment: JBoss AS upstream (April 5 2011) Reporter: jaikiran pai Assignee: Jesper Pedersen Fix For: 7.0.0.Beta3 The ResourceAdaptersExtension has various INFO level log statements like these: {code} Logger.getLogger(ResourceAdaptersExtension.class).infof("###########node=%s", node); {code} {code} Logger.getLogger(ResourceAdaptersExtension.class).infof("************ra node=%s", ra); {code} which appear to have be created while debugging some work. These need to be cleaned, since they keep appearing on the console. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

3
6
0 / 0

[JBoss JIRA] Created: (JBRULES-2901) Eclipse plugins: First build should not fail - Tycho must not be used with Bundle-ClassPath in MANIFEST.MF and lib hack

by Geoffrey De Smet (JIRA)

Eclipse plugins: First build should not fail - Tycho must not be used with Bundle-ClassPath in MANIFEST.MF and lib hack ----------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2901 URL: https://issues.jboss.org/browse/JBRULES-2901 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Currently, you have to build it 3 times before it builds succesfully. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
8
0 / 0

[JBoss JIRA] Created: (JBRULES-833) Maven2ize drools-examples

by Geoffrey De Smet (JIRA)

Maven2ize drools-examples ------------------------- Key: JBRULES-833 URL: http://jira.jboss.com/jira/browse/JBRULES-833 Project: JBoss Rules Issue Type: Patch Security Level: Public (Everyone can see) Affects Versions: 3.1-m1 Reporter: Geoffrey De Smet Assigned To: Mark Proctor Priority: Minor - the eclipse files can now be generate and generate the maven builder in it too - it compiles with a mvn install => catch compile errors early -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
21
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 April 2011