7:46 a.m.
Mostly I'm hitting a snag with this:
"All Java EE modules have a name. The name can be explicitly set
in the
deployment descriptor for the module. If not set, the name of the module
is the
pathname of the module in the ear file with any filename extension
(.jar, .war, .rar)
removed, but with any directory names included. The name of a module must be
unique within an application. If and only if the name is not unique
(e.g., because
two names are identical after removing different filename extensions) the
deployment tool may choose new unique names for any of the conflicting
modules; module names that do not conflict must not be changed. The
algorithm
for choosing unique names in such a case is product specific.
Applications that
depend on the names of their modules must ensure that their module names are
unique."
The naming deployers assume that a module name is unique, but we have a
lot of tests that do not adhere to this.
Carlo
On 01/14/2010 04:23 AM, Brian Stansberry wrote:
I suspect something in this area is the cause of the numerous
failures
in tests-standard-stress shown in the latest hudson run:
https://hudson.jboss.org/hudson/job/JBoss-AS-6.0.x-testSuite-sun16/504/te...
Looking into the failure of
org.jboss.test.bank.test.BankEJB20StressTestCase I see the deployment
failed with the stack trace below:
2010-01-13 19:06:57,835 DEBUG
[org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer] (RMI TCP
Connection(679)-127.0.0.1) Error during deploy:
jboss.naming:module=bank-ejb20:
org.jboss.deployers.spi.DeploymentException: Error deploying:
jboss.naming:module=bank-ejb20
at
org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
at
org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:185)
at
org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:58)
at
org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
at
org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55)
at
org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1660)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1378)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1399)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1319)
at
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:378)
at
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1856)
at
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:999)
at
org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1217)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1141)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1048)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:887)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:602)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:898)
at
org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:677)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:370)
at ....
Caused by: java.lang.IllegalStateException: java:module an alias of
jboss.naming:module=bank-ejb20 is already installed.
at
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:792)
at
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:589)
at
org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:180)
... 68 more
On 01/13/2010 09:00 PM, Brian Stansberry wrote:
> I'm seeing a bunch of failures of tests in the
> "tests-security-basic-unit" target with failures deploying that look
> like this:
>
> DEPLOYMENTS IN ERROR:
> Deployment
> "jboss.naming:application=security-jaas,module=security-jaas"
> is in error due to the following reason(s):
> java.lang.IllegalStateException: Unable to register context
> name=jboss.naming:application=security-jaas,module=security-jaas
> aliases=[java:module] state=Real, name already exists:
> jboss.naming:application=security-jaas,module=security-jaas
>
> On 01/12/2010 10:12 AM, Carlo de Wolf wrote:
>
>> New jboss-reloaded-naming-deployers is in. Let's see what that gives.
>>
>> Carlo
>>
>> On 01/12/2010 03:02 PM, Carlo de Wolf wrote:
>>
>>> Hmm, BeanMetaDataDeployer.undeploy doesn't take scoping into account
>>> and will undeploy a 'random' context.
>>>
>>> Carlo
>>>
>>>
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>
>
>