MDB Deployed Twice/Once not even under the JAR that contains it

Question

We have an application that has multiple jars bundled into one ear. Our application
tag looks like follows from the config.xml for the project:
<Application Name="Central"
Path="C:\PPOS\2004.1.0\Application\Central Server\weblogic\applications\pposcentralserver.ear"
StagedTargets="central" StagingMode="stage" TwoPhase="true">
<EJBComponent Name="commonserver" Targets="central" URI="commonserver.jar"/>
<EJBComponent Name="hostcommonserver" Targets="central" URI="hostcommonserver.jar"/>
</Application>
hostcommonserver.jar contains a MDB. It gets deployed properly and if I monitor
the queue it looks at on another server I can see it has "connected". The problem
however is on this server if I monitor commonserver.jar, the same MDB shows up
there even though it is NOT contained in the deployment descriptors for that jar.
If I look on the server that contains the queue I can see that there are twice
as many consumers as there should be.
The weird part. If I change the name in the <EJBComponent> tag above from "commonserver"
to anything else, this does not happen.
I have not tested putting a message on the queue to see which MDB consumes it
(getting to that point of testing will take me some time so I wanted to get the
ball rolling on this) however I feel there is some bug here and since using the
WLS console to look at the properties of this MDB is an often used part of support
troubleshooting for this product, I can't have the wrong version of the MDB in
place consuming messages while the correct one sits idly by making it appear it
is not getting messages.
Thanks.

Answer 1

Try posting to the jms newsgroup.
cheers
mbg
"Jeff Walsh" <jeff.walsh@no_spam_jda.com> wrote in message
news:3fb298e4$[email protected]..
>
Bump...
"Jeff Walsh" <[email protected]> wrote:
We have an application that has multiple jars bundled into one ear.
Our application
tag looks like follows from the config.xml for the project:
<Application Name="Central"
Path="C:\PPOS\2004.1.0\Application\Central
Server\weblogic\applications\pposcentralserver.ear"
StagedTargets="central" StagingMode="stage" TwoPhase="true">
<EJBComponent Name="commonserver" Targets="central"URI="commonserver.jar"/>
<EJBComponent Name="hostcommonserver" Targets="central"URI="hostcommonserver.jar"/>
</Application>
hostcommonserver.jar contains a MDB. It gets deployed properly and if
I monitor
the queue it looks at on another server I can see it has "connected".
The problem
however is on this server if I monitor commonserver.jar, the same MDB
shows up
there even though it is NOT contained in the deployment descriptors for
that jar.
If I look on the server that contains the queue I can see that there
are twice
as many consumers as there should be.
The weird part. If I change the name in the <EJBComponent> tag above
from "commonserver"
to anything else, this does not happen.
I have not tested putting a message on the queue to see which MDBconsumes
it
(getting to that point of testing will take me some time so I wanted
to get the
ball rolling on this) however I feel there is some bug here and since
using the
WLS console to look at the properties of this MDB is an often used part
of support
troubleshooting for this product, I can't have the wrong version of the
MDB in
place consuming messages while the correct one sits idly by making it
appear it
is not getting messages.
Thanks.