You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@geronimo.apache.org by Aman Nanner/MxI Technologies <am...@mxi.com> on 2007/03/07 23:00:26 UTC
JMS Queue/Topic definitions and external ActiveMQ XBean configuration
Hi,
I'm currently trying to configure an ActiveMQ JMS message bridge. In order
to do this, I had to recompile Geronimo 1.2 so that it would pick up its
ActiveMQ broker configuration from an external XBean configuration file. I
also deploy an EAR to Geronimo that consists of our application. Within
this EAR, I have an ActiveMQ RAR adapter with an XML plan, in which I
define all my JMS topics and queues.
The first problem is that I cannot configure a message bridge to my JMS
topics and queues, because the ActiveMQ broker cannot "see" these topics
and queues in my EAR (my EAR is the last module to start up). Because of
this problem, I considered moving all my JMS topics and queues outside of
my EAR and into the ActiveMQ XBean configuration itself. However, once I
do that, I can no longer deploy my EAR to the server due to an error that I
get. It appears that the deployer does not like my references to the
queues in my ejb-jar.xml and openejb-jar.xml descriptors, as it can no
longer find the definitions of the queues in my EAR. The actual error I
get during deployment is:
[java] Deployer operation failed: Can not resolve admin object ref
?j2eeType=JCAAdminObject,name=com/mxi/mx/jms/LocalTopic# in configuration
Mxi/Testing/1/ear
[java] org.apache.geronimo.common.DeploymentException: Can not resolve
admin object ref ?j2eeType=JCAAdminObject,name=com/mxi/mx/jms/LocalTopic#
in configuration Mxi/Testing/1/ear
Does anybody have any suggestions as how to resolve this "circular"
problem?
__________________________________________________________________________________
* This message is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. Unless you are the addressee (or authorized to receive for the addressee), you may not use, copy or disclose the message or any information contained in the message. If you have received this message in error, please advise the sender by reply e-mail , and delete the message, or call (collect) 001 613 747 4698. *
Re: JMS Queue/Topic definitions and external ActiveMQ XBean configuration
Posted by Aman Nanner/MxI Technologies <am...@mxi.com>.
Actually, this works! I had another issue (I wasn't committing the
transaction) which caused the bridge not to work. This is good as I can
leave my JMS destinations defined in the ActiveMQ RAR in my EAR. Thanks
for the advice!
Aman Nanner/MxI Technologies <am...@mxi.com> wrote on 03-08-2007
12:31:29 AM:
> I tried what you have suggested, and it did fix the deploy issue, but it
> seems like two separate topics get created with the same name. The
message
> bridge listens on the first topic that is defined, and the EAR references
> the second topic that is defined.
>
> David Jencks <da...@yahoo.com> wrote on 03-07-2007 05:38:16 PM:
>
> > I don't know how likely it is to work, but what happens if you define
> > the admin objects in both the xbean activemq plan (so your message
> > bridge can work) and also in your ear (so geronimo believes they
> > exist)? I have the rather unsubstantiated impression that AMQ thinks
> > a topic or queue is just a name and is happy to treat any use of the
> > same name as the same topic or queue.
> >
> > thanks
> > david jencks
> >
> > On Mar 7, 2007, at 5:00 PM, Aman Nanner/MxI Technologies wrote:
> >
> > >
> > > Hi,
> > >
> > > I'm currently trying to configure an ActiveMQ JMS message bridge.
> > > In order
> > > to do this, I had to recompile Geronimo 1.2 so that it would pick
> > > up its
> > > ActiveMQ broker configuration from an external XBean configuration
> > > file. I
> > > also deploy an EAR to Geronimo that consists of our application.
> > > Within
> > > this EAR, I have an ActiveMQ RAR adapter with an XML plan, in which I
> > > define all my JMS topics and queues.
> > >
> > > The first problem is that I cannot configure a message bridge to my
> > > JMS
> > > topics and queues, because the ActiveMQ broker cannot "see" these
> > > topics
> > > and queues in my EAR (my EAR is the last module to start up).
> > > Because of
> > > this problem, I considered moving all my JMS topics and queues
> > > outside of
> > > my EAR and into the ActiveMQ XBean configuration itself. However,
> > > once I
> > > do that, I can no longer deploy my EAR to the server due to an
> > > error that I
> > > get. It appears that the deployer does not like my references to the
> > > queues in my ejb-jar.xml and openejb-jar.xml descriptors, as it can
no
> > > longer find the definitions of the queues in my EAR. The actual
> > > error I
> > > get during deployment is:
> > >
> > > [java] Deployer operation failed: Can not resolve admin object
> > > ref
> > > ?j2eeType=JCAAdminObject,name=com/mxi/mx/jms/LocalTopic# in
> > > configuration
> > > Mxi/Testing/1/ear
> > > [java] org.apache.geronimo.common.DeploymentException: Can not
> > > resolve
> > > admin object ref ?j2eeType=JCAAdminObject,name=com/mxi/mx/jms/
> > > LocalTopic#
> > > in configuration Mxi/Testing/1/ear
> > >
> > > Does anybody have any suggestions as how to resolve this "circular"
> > > problem?
> > >
> > >
______________________________________________________________________
> > > ____________
> > > * This message is intended only for the use of the individual or
> > > entity to which it is addressed, and may contain information that
> > > is privileged, confidential and exempt from disclosure under
> > > applicable law. Unless you are the addressee (or authorized to
> > > receive for the addressee), you may not use, copy or disclose the
> > > message or any information contained in the message. If you have
> > > received this message in error, please advise the sender by reply e-
> > > mail , and delete the message, or call (collect) 001 613 747 4698. *
> > >
> >
>
>
__________________________________________________________________________________
> * This message is intended only for the use of the individual or
> entity to which it is addressed, and may contain information that is
> privileged, confidential and exempt from disclosure under applicable
> law. Unless you are the addressee (or authorized to receive for the
> addressee), you may not use, copy or disclose the message or any
> information contained in the message. If you have received this
> message in error, please advise the sender by reply e-mail , and
> delete the message, or call (collect) 001 613 747 4698. *
>
__________________________________________________________________________________
* This message is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. Unless you are the addressee (or authorized to receive for the addressee), you may not use, copy or disclose the message or any information contained in the message. If you have received this message in error, please advise the sender by reply e-mail , and delete the message, or call (collect) 001 613 747 4698. *
Re: JMS Queue/Topic definitions and external ActiveMQ XBean configuration
Posted by Aman Nanner/MxI Technologies <am...@mxi.com>.
I tried what you have suggested, and it did fix the deploy issue, but it
seems like two separate topics get created with the same name. The message
bridge listens on the first topic that is defined, and the EAR references
the second topic that is defined.
David Jencks <da...@yahoo.com> wrote on 03-07-2007 05:38:16 PM:
> I don't know how likely it is to work, but what happens if you define
> the admin objects in both the xbean activemq plan (so your message
> bridge can work) and also in your ear (so geronimo believes they
> exist)? I have the rather unsubstantiated impression that AMQ thinks
> a topic or queue is just a name and is happy to treat any use of the
> same name as the same topic or queue.
>
> thanks
> david jencks
>
> On Mar 7, 2007, at 5:00 PM, Aman Nanner/MxI Technologies wrote:
>
> >
> > Hi,
> >
> > I'm currently trying to configure an ActiveMQ JMS message bridge.
> > In order
> > to do this, I had to recompile Geronimo 1.2 so that it would pick
> > up its
> > ActiveMQ broker configuration from an external XBean configuration
> > file. I
> > also deploy an EAR to Geronimo that consists of our application.
> > Within
> > this EAR, I have an ActiveMQ RAR adapter with an XML plan, in which I
> > define all my JMS topics and queues.
> >
> > The first problem is that I cannot configure a message bridge to my
> > JMS
> > topics and queues, because the ActiveMQ broker cannot "see" these
> > topics
> > and queues in my EAR (my EAR is the last module to start up).
> > Because of
> > this problem, I considered moving all my JMS topics and queues
> > outside of
> > my EAR and into the ActiveMQ XBean configuration itself. However,
> > once I
> > do that, I can no longer deploy my EAR to the server due to an
> > error that I
> > get. It appears that the deployer does not like my references to the
> > queues in my ejb-jar.xml and openejb-jar.xml descriptors, as it can no
> > longer find the definitions of the queues in my EAR. The actual
> > error I
> > get during deployment is:
> >
> > [java] Deployer operation failed: Can not resolve admin object
> > ref
> > ?j2eeType=JCAAdminObject,name=com/mxi/mx/jms/LocalTopic# in
> > configuration
> > Mxi/Testing/1/ear
> > [java] org.apache.geronimo.common.DeploymentException: Can not
> > resolve
> > admin object ref ?j2eeType=JCAAdminObject,name=com/mxi/mx/jms/
> > LocalTopic#
> > in configuration Mxi/Testing/1/ear
> >
> > Does anybody have any suggestions as how to resolve this "circular"
> > problem?
> >
> > ______________________________________________________________________
> > ____________
> > * This message is intended only for the use of the individual or
> > entity to which it is addressed, and may contain information that
> > is privileged, confidential and exempt from disclosure under
> > applicable law. Unless you are the addressee (or authorized to
> > receive for the addressee), you may not use, copy or disclose the
> > message or any information contained in the message. If you have
> > received this message in error, please advise the sender by reply e-
> > mail , and delete the message, or call (collect) 001 613 747 4698. *
> >
>
__________________________________________________________________________________
* This message is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. Unless you are the addressee (or authorized to receive for the addressee), you may not use, copy or disclose the message or any information contained in the message. If you have received this message in error, please advise the sender by reply e-mail , and delete the message, or call (collect) 001 613 747 4698. *
Re: JMS Queue/Topic definitions and external ActiveMQ XBean configuration
Posted by David Jencks <da...@yahoo.com>.
I don't know how likely it is to work, but what happens if you define
the admin objects in both the xbean activemq plan (so your message
bridge can work) and also in your ear (so geronimo believes they
exist)? I have the rather unsubstantiated impression that AMQ thinks
a topic or queue is just a name and is happy to treat any use of the
same name as the same topic or queue.
thanks
david jencks
On Mar 7, 2007, at 5:00 PM, Aman Nanner/MxI Technologies wrote:
>
> Hi,
>
> I'm currently trying to configure an ActiveMQ JMS message bridge.
> In order
> to do this, I had to recompile Geronimo 1.2 so that it would pick
> up its
> ActiveMQ broker configuration from an external XBean configuration
> file. I
> also deploy an EAR to Geronimo that consists of our application.
> Within
> this EAR, I have an ActiveMQ RAR adapter with an XML plan, in which I
> define all my JMS topics and queues.
>
> The first problem is that I cannot configure a message bridge to my
> JMS
> topics and queues, because the ActiveMQ broker cannot "see" these
> topics
> and queues in my EAR (my EAR is the last module to start up).
> Because of
> this problem, I considered moving all my JMS topics and queues
> outside of
> my EAR and into the ActiveMQ XBean configuration itself. However,
> once I
> do that, I can no longer deploy my EAR to the server due to an
> error that I
> get. It appears that the deployer does not like my references to the
> queues in my ejb-jar.xml and openejb-jar.xml descriptors, as it can no
> longer find the definitions of the queues in my EAR. The actual
> error I
> get during deployment is:
>
> [java] Deployer operation failed: Can not resolve admin object
> ref
> ?j2eeType=JCAAdminObject,name=com/mxi/mx/jms/LocalTopic# in
> configuration
> Mxi/Testing/1/ear
> [java] org.apache.geronimo.common.DeploymentException: Can not
> resolve
> admin object ref ?j2eeType=JCAAdminObject,name=com/mxi/mx/jms/
> LocalTopic#
> in configuration Mxi/Testing/1/ear
>
> Does anybody have any suggestions as how to resolve this "circular"
> problem?
>
> ______________________________________________________________________
> ____________
> * This message is intended only for the use of the individual or
> entity to which it is addressed, and may contain information that
> is privileged, confidential and exempt from disclosure under
> applicable law. Unless you are the addressee (or authorized to
> receive for the addressee), you may not use, copy or disclose the
> message or any information contained in the message. If you have
> received this message in error, please advise the sender by reply e-
> mail , and delete the message, or call (collect) 001 613 747 4698. *
>