Hi All!
I'm deploying an enterprise application that has an application-scoped MDB.
Every time I deploy a new version of my application I need to restart
whole Geronimo.
If not, application throws this error:
Caused by: javax.naming.NameAlreadyBoundException
at org.apache.openejb.core.ivm.naming.NameNode.bind(NameNode.java:90)
at org.apache.openejb.core.ivm.naming.NameNode.bind(NameNode.java:99)
at org.apache.openejb.core.ivm.naming.NameNode.bind(NameNode.java:99)
at org.apache.openejb.core.ivm.naming.NameNode.bind(NameNode.java:84)
at org.apache.openejb.core.ivm.naming.NameNode.bind(NameNode.java:105)
at org.apache.openejb.core.ivm.naming.NameNode.bind(NameNode.java:99)
at org.apache.openejb.core.ivm.naming.NameNode.bind(NameNode.java:105)
at org.apache.openejb.core.ivm.naming.NameNode.bind(NameNode.java:84)
at org.apache.openejb.core.ivm.naming.NameNode.bind(NameNode.java:99)
at
org.apache.openejb.core.ivm.naming.IvmContext.bind(IvmContext.java:274)
at
org.apache.openejb.assembler.classic.Assembler.createContainer(Assembler.java:717)
... 30 more
Stack trace contains far more lines, but the most important one are above.
As far as I have traced this error is related to jms-resources used by MDBs.
Any idea?
Is it Geronimo or OpenEJB issue?
My shot is that name binding is not revoked after undeployment - which
is Geronimo issue.
Maybe there is some kind of work-around?
best regards
Łukasz
