activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "amq user" <amq.u...@gmail.com>
Subject Re: two basic questions
Date Tue, 12 Dec 2006 19:38:08 GMT
Thanks for clarifying the second question!!!



On 12/12/06, Bish, Tim <Tim.Bish@sensis.com> wrote:
>
>
>
> > -----Original Message-----
> > From: amq user [mailto:amq.user@gmail.com]
> > Sent: Tuesday, December 12, 2006 2:01 PM
> > To: activemq-users
> > Subject: two basic questions
> >
> > Hi, I have two very basic questions, I couldn't figure them out
> myself.
> >
> > 1. where can I find the activemq log file? I found "activemq.log"
> under
> > var
> > directory. But it is always empty.
> > 2. in the given activemq.xml example, there are two
> transportConnectors:
> >
> >        <transportConnector name="default" uri="tcp://localhost:61616"
> > discoveryUri="multicast://default"/>
> >        <transportConnector name="stomp"
> uri="stomp://localhost:61613"/>
> >
>
> Yes, you need a transport connector for each protocol that you want the
> broker to support.
>
> > In the java producer example, I had to use:
> >
> > java ProducerTool tcp://localhost:61616  <-working
> >
>
> > java ProducerTool stomp://localhost:61613 <-NOT working
>
> There is no Stomp support in the Java client as it uses the default
> Openwire Protocol to talk, so this is not going to work.
>
> >
> > As I understand, ActiveMQ uses stomp over tcp to communicate between
> > client and broker.
>
> It uses stomp when configured to do so, Stomp is a simple protocol meant
> for native clients such as Perl, Ruby etc.
>
> > Can anyone give more detail on this? As matter of fact, the
> > activemq-cpp example has to use "tcp://127.0.0.1:61613" to work.
>
> Currently activemq-cpp only talks stomp, eventually we will get openwire
> support in there and then the url might change to be something like
> "stomp://127.0.0.1:61613" if you wanted to use the older stomp protocol.
>
>
> >
> > Thanks in advance
>

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