activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Clebert Suconic <clebert.suco...@gmail.com>
Subject Re: Creating queues via activemq-configuration.xml when using ActiveMQ6
Date Fri, 12 Dec 2014 21:17:14 GMT
For now always use jms queues and jms topics only.. They would be visible
for you if you did like that.

We are changing things as we go.. perhaps you got us in between changes?
but it should be working fine now anyways.



On Fri, Dec 12, 2014 at 4:09 PM, Robbie Gemmell <robbie.gemmell@gmail.com>
wrote:
>
> On 12 December 2014 at 19:00, Clebert Suconic <clebert.suconic@gmail.com>
> wrote:
> > JMS Queues would have core-queues by result.
> >
>
> Yes, as I say I got that to work, and could see both the 'JMS Queue'
> and the resulting core queue MBeans via JMX when I did, and use the
> queue via an AMQP client.
>
> However I wasnt able to get any visible sign via JMX of a different
> core queue being created when I defined it in
> activemq-configuration.xml. I'm mainly asking if I did anything wrong
> with that configuration, because if I didnt then something might need
> updated, e.g that process could be broken in some way, or the docs
> might be out of date, etc.
>
> >
> > But why you need a core-queue anyways?
>
> I didnt strictly need a core queue, I needed a queue. Defining queues
> in the main configuration file was the first thing I came across in
> the docs regarding creating queues when first using the broker several
> months ago. I think I was able at the time able to create a queue via
> what was then hornetq-configuration.xml and use it from an AMQP
> client, and was essentially aiming to repeat that today to no success.
>
> > a Core queue is only useful when
> > using the HornetQ Core API. It doesn't even work through AMQP as the
> > destination won't following the naming convestions on the protocol layer.
> >
>
> Does that mean that if there is a core queue called "myQueue", that
> wouldnt work from an AMQP client using a link address of "myQueue"
> because it isnt following the "jms.queue.foo" convention?
>
> Equally, if there was a core queue which happened to be called
> "jms.queue.myQueue" (created directly rather than as side effect of
> defining a JMS queue "myQueue", assuming the broker allows doing
> that?) would that fail to work for an AMQP client using link address
> of "jms.queue.myQueue" because it wasnt created as a side effect of
> defining JMS queue "myQueue"?
>
> (Mainly trying to establish what AMQP addresses will or will not work
> in future when the broker supports auto-creation of destinations)
>
> Thanks,
> Robbie
>
> > On Fri, Dec 12, 2014 at 11:53 AM, Robbie Gemmell <
> robbie.gemmell@gmail.com>
> > wrote:
> >>
> >> Hi all,
> >>
> >> I figured I would ask on the list about this one rather than raise a
> >> JIRA, potential user error :D
> >>
> >> When reading the docs I saw mention of being able to define core
> >> queues in activemq-configuration.xml, or 'JMS queues' via
> >> activemq-jms.xml. I have got the latter working fine, but was unable
> >> to get the former to work.
> >>
> >> Adding this in activemq-configuration.xml appeared to make no
> >> difference, I didnt see the new queue via JMX after restarting and was
> >> unsurprisingly thus unable to produce/consume from it using an AMQP
> >> client.
> >>    <queues>
> >>       <queue name="myQueue">
> >>          <address>myQueue</address>
> >>       </queue>
> >>    </queues>
> >>
> >> I don't see what I'm doing wrong, and think I got this to work against
> >> an old version of the broker several months ago, so I was wondering if
> >> anyone else sees the problem, or whether anything has changed in this
> >> area - is it still supported?
> >>
> >> Thanks,
> >> Robbie
> >>
> >
> >
> > --
> > Clebert Suconic
> > http://community.jboss.org/people/clebert.suconic@jboss.com
> > http://clebertsuconic.blogspot.com
>


-- 
Clebert Suconic
http://community.jboss.org/people/clebert.suconic@jboss.com
http://clebertsuconic.blogspot.com

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message