activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Gomes" <e.se...@gmail.com>
Subject Re: JBoss Messaging Stomp Configuration
Date Mon, 25 Feb 2008 21:50:03 GMT
Hi Johann,

To get the NMS client to talk the stomp protocol, you will need to set your
connection string in one of the following formats.  Either is acceptable, so
it's up to you which one you prefer.

activemq:tcp://jbosssrvr:61613?transport.wireformat=stomp
      OR
activemq:stomp://jbosssrvr:61613

The port 61613 is the port that ActiveMQ listens on for STOMP protocol
messages.  You will need to set the correct port entry for the JBOSS
Messaging broker.  If JBOSS Messaging does not support STOMP natively, you
may need to use the STOMPConnect product to bridge between your client and
JBOSS Messaging.

Good Luck,
Jim

On Mon, Feb 25, 2008 at 1:06 PM, Johann Ungerer <JohannU@pyrogenesis.co.za>
wrote:

> Hi All,
>
> I'm totally new to the entire JMS environment, but am trying to connect a
> .NET Client to a JBOSS Messaging implementation. Thus far I've tried with
> the NMS client, using an OpenWire connector, but I figure this will never
> work.
>
> It's been recommended that I use a STOMP connector, but can't quite get
> either my JBOSS Server configured to listen on STOMP, or get STOMP to talk
> to the JBOSS.
>
> Has anyone tried to make a C# client talk to JBOSS and if so, please
> provide some guidance on what I need to do in order to achieve this.
>
> TIA,
> j/
>
>

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