Just for the records: the "InstanceAlreadyExistsException" is fixed in 5.0.1GA
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4216726#4216726
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4216726
The "InstanceAlreadyExistsException" is in the AS5 forum now:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205691
Thanks
Wolfgang
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205692#4205692
Reply to the post :
http://www.jboss.com/index.html
Hi Jaikiran,
many thanks for the suggestion with the @Depends annotation, the
"NameNotFoundException" is gone now.
I modified my MDB:
@MessageDriven (activationConfig=
| {
| @ActivationConfigProperty(propertyName="destinationType",
propertyValue="javax.jms.Queue"),
| @Activation
"Wolfgang Knauf" wrote : Hi jaikiran,
|
| the -service.xml in META-INF instead of the JAR root ...
| The first error (javax.management.InstanceAlreadyExistsException) is gone.
|
As i suspected, this looks like some issue with JBossAS-5 deployment. Maybe you
could open a thread in our AS
Hi jaikiran,
the -service.xml in META-INF instead of the JAR root results only in this error:
| javax.naming.NameNotFoundException: MessageBeanQueue not bound
| at org.jnp.server.NamingServer.getBinding(NamingServer.java:771)
| at org.jnp.server.NamingServer.getBinding(NamingServer.
anonymous wrote : On first deploy, this is the console output:
|
|
| | 20:10:29,250 WARN [AbstractDeploymentContext] Unable to register
deployment mbean vfszip:/C:/temp/j
| |
boss-5.0.0.GA/server/default/deploy/Message.ear/MessageEJB.jar/knaufmq-service.xml
| | javax.management
Hi Jaikiran,
thanks for your reply.
I simply copy the EAR to the deploy folder.
On first deploy, this is the console output:
20:10:29,250 WARN [AbstractDeploymentContext] Unable to register deployment
mbean
vfszip:/C:/temp/jboss-5.0.0.GA/server/default/deploy/Message.ear/MessageEJB.jar/knaufm
anonymous wrote : Where exactly in the jar is the *-service.xml located?
I see it's at the root of your jar file.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4204909#4204909
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=rep
anonymous wrote : But on every redeploy
How do you redeploy the application? Where exactly in the jar is the
*-service.xml located? And can you post the console logs when do deploy then
redeploy your application?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p
