You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@geronimo.apache.org by Łukasz Budnik <lu...@gmail.com> on 2008/02/11 18:57:01 UTC
extremely annoying G2.0.2 behaviour
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
Re: extremely annoying G2.0.2 behaviour
Posted by Kevan Miller <ke...@gmail.com>.
On Feb 12, 2008, at 1:50 PM, Łukasz Budnik wrote:
> Hi Jacek!
>
> On 11/02/2008, Jacek Laskowski <ja...@laskowski.net.pl> wrote:
>> Yes, it's been very annoying, but it's over now. It's fixed in
>> Geronimo 2.1 so you may want to try out the just-voted 2.1 release -
>> http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1-dist/
>> .
>> Let us know how it works so we may fix issues before Geronimo 2.1's
>> published.
>
> ups...
>
> that bombs...
>
> The only one thing that was "wrong" with G2.0.2 was the need of
> restarting Geronimo after every deploy.
>
> But in G2.1.0 I cannot deploy my application at all!
>
> Here's the stack trace of this error (occurs when deploying
> application):
>
> Unable to resolve resource reference
> 'ProcessInvocationOrderConnectionFactory' (Could not auto-map to
> resource. Try adding a resource-ref mapping to your Geronimo
> deployment plan.
> Search conducted in current module and dependencies:
> [ALL: org.apache.geronimo.configs/j2ee-server//car]
> [ALL: org.apache.geronimo.configs/activemq-broker//car]
> [ALL: org.apache.geronimo.configs/openjpa//car]
> [ALL: org.apache.geronimo.configs/openejb//car]
> [ALL: org.apache.geronimo.configs/system-database//car]
> [ALL: org.apache.geronimo.configs/tomcat6//car]
> [ALL: com.ibm.db2/db2jcc/9.1/jar]
> [ALL: com.ibm.db2/db2jcc_license_cu/9.1/jar]
> [ALL: org.apache.geronimo.configs/transaction//car]
> [ALL: org.apache.geronimo.configs/j2ee-corba-yoko//car]
> [ALL: org.apache.geronimo.configs/axis//car]
> [ALL: org.apache.geronimo.configs/axis2//car]
> )
>
> The thing is it worked in G2.0.2...
>
> What has changed since G2.0.2?
>
> Can I see an example of deploying MDB in G2.1.0, please?
The file attached to this Jira works on 2.1 -- https://issues.apache.org/jira/browse/GERONIMO-3783
--kevan
Re: extremely annoying G2.0.2 behaviour
Posted by Łukasz Budnik <lu...@gmail.com>.
Hi Jacek!
On 11/02/2008, Jacek Laskowski <ja...@laskowski.net.pl> wrote:
> Yes, it's been very annoying, but it's over now. It's fixed in
> Geronimo 2.1 so you may want to try out the just-voted 2.1 release -
> http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1-dist/.
> Let us know how it works so we may fix issues before Geronimo 2.1's
> published.
ups...
that bombs...
The only one thing that was "wrong" with G2.0.2 was the need of
restarting Geronimo after every deploy.
But in G2.1.0 I cannot deploy my application at all!
Here's the stack trace of this error (occurs when deploying application):
Unable to resolve resource reference
'ProcessInvocationOrderConnectionFactory' (Could not auto-map to
resource. Try adding a resource-ref mapping to your Geronimo
deployment plan.
Search conducted in current module and dependencies:
[ALL: org.apache.geronimo.configs/j2ee-server//car]
[ALL: org.apache.geronimo.configs/activemq-broker//car]
[ALL: org.apache.geronimo.configs/openjpa//car]
[ALL: org.apache.geronimo.configs/openejb//car]
[ALL: org.apache.geronimo.configs/system-database//car]
[ALL: org.apache.geronimo.configs/tomcat6//car]
[ALL: com.ibm.db2/db2jcc/9.1/jar]
[ALL: com.ibm.db2/db2jcc_license_cu/9.1/jar]
[ALL: org.apache.geronimo.configs/transaction//car]
[ALL: org.apache.geronimo.configs/j2ee-corba-yoko//car]
[ALL: org.apache.geronimo.configs/axis//car]
[ALL: org.apache.geronimo.configs/axis2//car]
)
The thing is it worked in G2.0.2...
What has changed since G2.0.2?
Can I see an example of deploying MDB in G2.1.0, please?
best regards
Łukasz
Re: extremely annoying G2.0.2 behaviour
Posted by Jacek Laskowski <ja...@laskowski.net.pl>.
On Feb 11, 2008 9:57 AM, Łukasz Budnik <lu...@gmail.com> wrote:
> 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
Hi Łukasz,
Yes, it's been very annoying, but it's over now. It's fixed in
Geronimo 2.1 so you may want to try out the just-voted 2.1 release -
http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1-dist/.
Let us know how it works so we may fix issues before Geronimo 2.1's
published.
p.s. Dobrze widzieć rodaka na grupach Geronimo (tak przynajmniej
wnioskuję po imieniu i nazwisku). Napisz, co skłoniło Cię do
skorzystania z Geronimo i jak Ci się z nim pracuje.
Jacek
--
Jacek Laskowski
http://www.JacekLaskowski.pl