RE: [JBoss-dev]InstanceAlreadyExistsExceptionafterundeployandrepeateddeployinJBossAS5.0.0 Beta
Please don't use html e-mails.
On Thu, 2006-08-17 at 20:24 -0500, Jaroslaw Kijanowski wrote:
08:45:14,875 ERROR [MainDeployer] Could not create deployment:
file:/D:/jboss-svn4/jboss-head/build/output/jboss-5.0.0.Beta/server/all/tmp/deploy/tmp30918cts.jar-contents/test-destinations-full-service.xml
org.jboss.deployment.DeploymentException: Error during install; -
nested throwable: (java.lang.IllegalStateException:
jboss.mq.destination:name=testTopic,service=Topic is already
installed.)
at
org.jboss.deployment.DeploymentException.rethrowAsDeploymentException
(DeploymentException.java:53)
at
org.jboss.system.ServiceController.install(ServiceController.java:259)
***************************
The test ends with an error because it can't bind "ejbcts", because an
Exception cancels the whole deployment instead of printing out an
info, that "testTopic" is already bound.
Same issue in JBoss404GA.
Wouldn't it be nicer to print on stdout an info, that the resource is
already registered? The deployment would continue, "ejbcts" would
bind, the test (and some others) wouldn't fail.
There is no choice other than cancelling the whole deployment if there
is a duplicate. That is unless you install a dummy context,
e.g. "jboss.mq.destination:name=testTopic,service=Topic-**DUPLCIATE1**"
to hold the error message against so you can
continue and try to deploy any others.
In fact, this behaviour is better than it used to be 4.0.x
Now, only an xml parsing failure or a duplicate ObjectName
causes it to fail without the context going under control
of the Microcontainer.
This means much better summaries of errors can be produced.
--
xxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxx