You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Johann Ungerer <Jo...@pyrogenesis.co.za> on 2008/02/25 22:06:50 UTC
JBoss Messaging Stomp Configuration
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/
Re: JBoss Messaging Stomp Configuration
Posted by Gregory Mostizky <gr...@gmail.com>.
See this issue at JBoss Jira
https://jira.jboss.org/jira/browse/JBMESSAGING-1384 JBMESSAGING-1384 for a
solution that allows running StompConnect as JBoss Service. It allows
running StompConnect as JBoss Service in the same JVM. It worked for me with
JBoss 5.0.1 - not sure if other versions work too.
To use it, just download and unzip the attached file, set your jboss home in
the build.properties and then run the build with ant. After you done that,
find stompservice.sar in the <server-config>/deploy/ directory and put
stompconnect.jar from the zip (not from the codehaus site) inside it at top
level. Then restart your JBoss and voila - StompConnect run automatically as
service inside JBoss JVM.
--
View this message in context: http://www.nabble.com/JBoss-Messaging-Stomp-Configuration-tp15677725p22848408.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: JBoss Messaging Stomp Configuration
Posted by James Strachan <ja...@gmail.com>.
Great stuff! I've added this page to the STOMP wiki
http://docs.codehaus.org/display/STOMP/StompConnect+with+JBoss
On 10/03/2008, Johann Ungerer <Jo...@pyrogenesis.co.za> wrote:
> Hi all,
>
> After some fun and games, we managed to configure STOMPConnect to work with JBOSS. Thought I'd share our experience with everyone.
>
> ----------------
>
>
> @echo off
> cls
> setlocal
> title STOMPConnect:61613 - jbosssrv
>
>
> set uri=tcp://169.254.109.194:61613
> set providerurl=jnp://localhost:1099
>
> set classes=stompconnect-1.0.jar;commons-logging-1.1.jar;jboss-messaging.jar;jnpserver.jar;jboss-common.jar;jboss-messaging-client.jar;jbossall-client.jar;jboss-remoting.jar;javassist.jar;jboss-j2ee.jar;trove.jar;jboss-aop-jdk50.jar
>
> set properties=-Djava.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
> set properties=%properties% -Djava.naming.provider.url=%providerurl%
> set properties=%properties% -Djava.naming.security.principal=guest
> set properties=%properties% -Djava.naming.security.credentials=guest
>
> echo Connecting to %providerurl%
>
> java %properties% -classpath %classes% org.codehaus.stomp.jms.Main %uri% ConnectionFactory
>
>
> --------------
>
> Thanks to the list for the help in getting me on the right road.
>
> Regards,
>
> j/
>
>
> -----Original Message-----
> From: Johann Ungerer [mailto:JohannU@pyrogenesis.co.za]
> Sent: 28 February 2008 23:11
> To: users@activemq.apache.org
>
> Subject: RE: JBoss Messaging Stomp Configuration
>
> Hi Jim,
>
> Thank you for the reply, its gotten me quite a bit further.
>
> I am currently experiencing a connectivity issue from stomp to JBM, so I'm posting the startup file that I'm using for stomp in hopes that I'm doing something silly. I am able to connect to the JBM via code on the provider url i'm using, so the url "should" be right.
>
> If anyone sees anything obviously wrong, it would be greatly appreciated.
>
> --
>
> set uri=stomp://localhost:61613
> set providerurl=tcp://192.168.0.53:1099
>
> set classes=stompconnect-1.0.jar;commons-logging-1.1.jar;jboss-messaging.jar;jnpserver.jar;jboss-common.jar
> set properties=-Djava.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
> set properties=%properties% -Djava.naming.provider.url=%providerurl%
> set properties=%properties% -Djava.naming.security.principal=guest
> set properties=%properties% -Djava.naming.security.credentials=guest
>
> echo Connecting to %providerurl%
>
> java %properties% -classpath %classes% org.codehaus.stomp.jms.Main %uri% ConnectionFactory
>
> --
>
> TIA,
> j/
>
> -----Original Message-----
> From: Jim Gomes [mailto:e.semog@gmail.com]
> Sent: 26 February 2008 17:15
> To: users@activemq.apache.org
> Subject: Re: JBoss Messaging Stomp Configuration
>
> Hi Johann,
>
> It can take a little bit to figure out STOMPConnect, but once you have it
> configured, it's very low maintenance. I had to do something very similar
> to what you are attempting to do. I needed to be able to connect to TIBCO
> EMS using the Apache NMS client (this was before direct support was added
> for TIBCO). I used STOMPConnect to be my bridging mechanism. I ran the
> TIBCO server on one machine, the STOMPConnect on a second machine, and my
> NMS client on a third machine. The STOMPConnect portion could actually be
> run on any machine. I created a simple batch file that would run it on a
> Windows box. Essentially, the connection works as follows: The NMS client
> connects to STOMPConnect on port 61613. STOMPConnect translates the STOMP
> messages and forwards them as native JMS messages by connecting to TIBCO on
> port 7222. Here's the batch file. Hopefully, you can take this and
> customize it to use the JBOSS Messaging class factory and JMS clients. No
> custom Java coding required.
>
> ------------- 8< ----- SNIP ---- 8< ---------
>
> @echo off
> cls
> setlocal
> title STOMPConnect:61613 - jbosssrv
>
> set uri=stomp://localhost:61613
> set providerurl=tcp://jbosssrv:7222
>
> set classes=stompconnect-1.0.jar;commons-logging-1.1.jar;jms.jar;tibjms.jar
> set properties=-
> Djava.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContextFactory
> set properties=%properties% -Djava.naming.provider.url=%providerurl%
> set properties=%properties% -Djava.naming.security.principal=guest
> set properties=%properties% -Djava.naming.security.credentials=guest
>
> echo Connecting to %providerurl%
>
> java %properties% -classpath %classes% org.codehaus.stomp.jms.Main %uri%
> GenericConnectionFactory
>
> ------------- 8< ----- SNIP ---- 8< ---------
>
> You should replace the
> com.tibco.tibjms.naming.tibjmsInitialContextFactorywith the
> corresponding JBOSS Messaging context factory. The
> tibjms.jar file will be replaced with the JBOSS Messaging client jar file.
>
> Hope this helps you get further.
>
> - Jim
>
> On Mon, Feb 25, 2008 at 8:54 PM, Johann Ungerer <Jo...@pyrogenesis.co.za>
> wrote:
>
> > Hi Jim,
> >
> > Thanks for the reply. I've pretty much gotten that far. The trick I'm not
> > able to sort out on my own is actually configuring STOMPConnect to bridge to
> > JBM. The documentation is a little patchy, I'm not sure which configs to
> > touch, would I run STOMPConnect as a stand-alone product, or can I use the
> > "Injection Dependency" mentioned in the docs? I'm comfortable that I'll sort
> > the client out, it's the server and bridge config that I'm not too sure of.
> >
> > TIA,
> > j/
> >
> > -----Original Message-----
> > From: Jim Gomes [mailto:e.semog@gmail.com]
> > Sent: 25 February 2008 23:50
> > To: users@activemq.apache.org
> > Subject: Re: JBoss Messaging Stomp Configuration
> >
> > 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/
> > >
> > >
> >
>
--
James
-------
http://macstrac.blogspot.com/
Open Source Integration
http://open.iona.com
RE: JBoss Messaging Stomp Configuration
Posted by Johann Ungerer <Jo...@pyrogenesis.co.za>.
Hi all,
After some fun and games, we managed to configure STOMPConnect to work with JBOSS. Thought I'd share our experience with everyone.
----------------
@echo off
cls
setlocal
title STOMPConnect:61613 - jbosssrv
set uri=tcp://169.254.109.194:61613
set providerurl=jnp://localhost:1099
set classes=stompconnect-1.0.jar;commons-logging-1.1.jar;jboss-messaging.jar;jnpserver.jar;jboss-common.jar;jboss-messaging-client.jar;jbossall-client.jar;jboss-remoting.jar;javassist.jar;jboss-j2ee.jar;trove.jar;jboss-aop-jdk50.jar
set properties=-Djava.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
set properties=%properties% -Djava.naming.provider.url=%providerurl%
set properties=%properties% -Djava.naming.security.principal=guest
set properties=%properties% -Djava.naming.security.credentials=guest
echo Connecting to %providerurl%
java %properties% -classpath %classes% org.codehaus.stomp.jms.Main %uri% ConnectionFactory
--------------
Thanks to the list for the help in getting me on the right road.
Regards,
j/
-----Original Message-----
From: Johann Ungerer [mailto:JohannU@pyrogenesis.co.za]
Sent: 28 February 2008 23:11
To: users@activemq.apache.org
Subject: RE: JBoss Messaging Stomp Configuration
Hi Jim,
Thank you for the reply, its gotten me quite a bit further.
I am currently experiencing a connectivity issue from stomp to JBM, so I'm posting the startup file that I'm using for stomp in hopes that I'm doing something silly. I am able to connect to the JBM via code on the provider url i'm using, so the url "should" be right.
If anyone sees anything obviously wrong, it would be greatly appreciated.
--
set uri=stomp://localhost:61613
set providerurl=tcp://192.168.0.53:1099
set classes=stompconnect-1.0.jar;commons-logging-1.1.jar;jboss-messaging.jar;jnpserver.jar;jboss-common.jar
set properties=-Djava.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
set properties=%properties% -Djava.naming.provider.url=%providerurl%
set properties=%properties% -Djava.naming.security.principal=guest
set properties=%properties% -Djava.naming.security.credentials=guest
echo Connecting to %providerurl%
java %properties% -classpath %classes% org.codehaus.stomp.jms.Main %uri% ConnectionFactory
--
TIA,
j/
-----Original Message-----
From: Jim Gomes [mailto:e.semog@gmail.com]
Sent: 26 February 2008 17:15
To: users@activemq.apache.org
Subject: Re: JBoss Messaging Stomp Configuration
Hi Johann,
It can take a little bit to figure out STOMPConnect, but once you have it
configured, it's very low maintenance. I had to do something very similar
to what you are attempting to do. I needed to be able to connect to TIBCO
EMS using the Apache NMS client (this was before direct support was added
for TIBCO). I used STOMPConnect to be my bridging mechanism. I ran the
TIBCO server on one machine, the STOMPConnect on a second machine, and my
NMS client on a third machine. The STOMPConnect portion could actually be
run on any machine. I created a simple batch file that would run it on a
Windows box. Essentially, the connection works as follows: The NMS client
connects to STOMPConnect on port 61613. STOMPConnect translates the STOMP
messages and forwards them as native JMS messages by connecting to TIBCO on
port 7222. Here's the batch file. Hopefully, you can take this and
customize it to use the JBOSS Messaging class factory and JMS clients. No
custom Java coding required.
------------- 8< ----- SNIP ---- 8< ---------
@echo off
cls
setlocal
title STOMPConnect:61613 - jbosssrv
set uri=stomp://localhost:61613
set providerurl=tcp://jbosssrv:7222
set classes=stompconnect-1.0.jar;commons-logging-1.1.jar;jms.jar;tibjms.jar
set properties=-
Djava.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContextFactory
set properties=%properties% -Djava.naming.provider.url=%providerurl%
set properties=%properties% -Djava.naming.security.principal=guest
set properties=%properties% -Djava.naming.security.credentials=guest
echo Connecting to %providerurl%
java %properties% -classpath %classes% org.codehaus.stomp.jms.Main %uri%
GenericConnectionFactory
------------- 8< ----- SNIP ---- 8< ---------
You should replace the
com.tibco.tibjms.naming.tibjmsInitialContextFactorywith the
corresponding JBOSS Messaging context factory. The
tibjms.jar file will be replaced with the JBOSS Messaging client jar file.
Hope this helps you get further.
- Jim
On Mon, Feb 25, 2008 at 8:54 PM, Johann Ungerer <Jo...@pyrogenesis.co.za>
wrote:
> Hi Jim,
>
> Thanks for the reply. I've pretty much gotten that far. The trick I'm not
> able to sort out on my own is actually configuring STOMPConnect to bridge to
> JBM. The documentation is a little patchy, I'm not sure which configs to
> touch, would I run STOMPConnect as a stand-alone product, or can I use the
> "Injection Dependency" mentioned in the docs? I'm comfortable that I'll sort
> the client out, it's the server and bridge config that I'm not too sure of.
>
> TIA,
> j/
>
> -----Original Message-----
> From: Jim Gomes [mailto:e.semog@gmail.com]
> Sent: 25 February 2008 23:50
> To: users@activemq.apache.org
> Subject: Re: JBoss Messaging Stomp Configuration
>
> 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/
> >
> >
>
JBoss Messaging Stomp Configuration
Posted by Jai_aXIS <ja...@gmail.com>.
Hi All,
I am new to JMS .
I am uisng Jboss-5.0.0GA which has Java Messaging 1.4.1. GA . In the
JBoss I have created a new connection factory .
Then from a stand alone program I try to get connection factory from jboss
and succeeded , but when i try to get connection from the connection factory
I get the error below :
2009 Jun 15 17:18:56 [main] ERROR
org.jboss.remoting.transport.socket.SocketClientInvoker - Got marshalling
exception, exiting
java.io.IOException:
EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment
at java.io.ObjectOutputStream.writeObject0(Unknown Source)
at java.io.ObjectOutputStream.writeArray(Unknown Source)
at java.io.ObjectOutputStream.writeObject0(Unknown Source)
at java.io.ObjectOutputStream.defaultWriteFields(Unknown Source)
at java.io.ObjectOutputStream.defaultWriteObject(Unknown Source)
at
EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap.writeObject(ConcurrentHashMap.java:1170)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at java.io.ObjectStreamClass.invokeWriteObject(Unknown Source)
at java.io.ObjectOutputStream.writeSerialData(Unknown Source)
at java.io.ObjectOutputStream.writeOrdinaryObject(Unknown Source)
at java.io.ObjectOutputStream.writeObject0(Unknown Source)
at java.io.ObjectOutputStream.defaultWriteFields(Unknown Source)
at java.io.ObjectOutputStream.writeSerialData(Unknown Source)
at java.io.ObjectOutputStream.writeOrdinaryObject(Unknown Source)
at java.io.ObjectOutputStream.writeObject0(Unknown Source)
at java.io.ObjectOutputStream.writeObject(Unknown Source)
at
org.jboss.jms.wireformat.SerializedPacket.write(SerializedPacket.java:80)
at org.jboss.jms.wireformat.JMSWireFormat.write(JMSWireFormat.java:237)
at
org.jboss.remoting.transport.socket.MicroSocketClientInvoker.versionedWrite(MicroSocketClientInvoker.java:956)
at
org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:552)
at
org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:269)
at
org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
at org.jboss.remoting.LeasePinger.sendClientPing(LeasePinger.java:283)
at org.jboss.remoting.LeasePinger.addClient(LeasePinger.java:117)
at
org.jboss.remoting.MicroRemoteClientInvoker.establishLease(MicroRemoteClientInvoker.java:398)
at org.jboss.remoting.Client.setupClientLease(Client.java:1504)
at org.jboss.remoting.Client.connect(Client.java:1404)
at org.jboss.remoting.Client.connect(Client.java:441)
at
org.jboss.jms.client.remoting.JMSRemotingConnection$1.run(JMSRemotingConnection.java:319)
at java.security.AccessController.doPrivileged(Native Method)
at
org.jboss.jms.client.remoting.JMSRemotingConnection.start(JMSRemotingConnection.java:315)
at
org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:154)
at
org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
at
org.jboss.jms.client.container.StateCreationAspect.handleCreateConnectionDelegate(StateCreationAspect.java:83)
at
org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect0.invoke(StateCreationAspect0.java)
at
org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
at
org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java)
at
org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:205)
at
org.jboss.jms.client.JBossConnectionFactory.createConnection(JBossConnectionFactory.java:87)
at
org.jboss.jms.client.JBossConnectionFactory.createConnection(JBossConnectionFactory.java:82)
at com.jms.test.SimpleTestClient.main(SimpleTestClient.java:22)
2009 Jun 15 17:18:56 [main] WARN org.jboss.remoting.LeasePinger -
LeasePinger[SocketClientInvoker[1c80b01,
bisocket://127.0.0.1:4457](aaw19-i6j7nu-fvyz3zgo-1-fvyz3zse-6)] failed to
ping to server: Failed to communicate. Problem during
marshalling/unmarshalling; nested exception is:
java.io.IOException:
EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment
2009 Jun 15 17:19:06 [Timer-0] ERROR
org.jboss.remoting.transport.socket.SocketClientInvoker - Got marshalling
exception, exiting
java.io.IOException:
EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment
at java.io.ObjectOutputStream.writeObject0(Unknown Source)
at java.io.ObjectOutputStream.writeArray(Unknown Source)
at java.io.ObjectOutputStream.writeObject0(Unknown Source)
at java.io.ObjectOutputStream.defaultWriteFields(Unknown Source)
at java.io.ObjectOutputStream.defaultWriteObject(Unknown Source)
at
EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap.writeObject(ConcurrentHashMap.java:1170)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at java.io.ObjectStreamClass.invokeWriteObject(Unknown Source)
at java.io.ObjectOutputStream.writeSerialData(Unknown Source)
at java.io.ObjectOutputStream.writeOrdinaryObject(Unknown Source)
at java.io.ObjectOutputStream.writeObject0(Unknown Source)
at java.io.ObjectOutputStream.defaultWriteFields(Unknown Source)
at java.io.ObjectOutputStream.writeSerialData(Unknown Source)
at java.io.ObjectOutputStream.writeOrdinaryObject(Unknown Source)
at java.io.ObjectOutputStream.writeObject0(Unknown Source)
at java.io.ObjectOutputStream.writeObject(Unknown Source)
at
org.jboss.jms.wireformat.SerializedPacket.write(SerializedPacket.java:80)
at org.jboss.jms.wireformat.JMSWireFormat.write(JMSWireFormat.java:237)
at
org.jboss.remoting.transport.socket.MicroSocketClientInvoker.versionedWrite(MicroSocketClientInvoker.java:956)
at
org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:552)
at
org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:269)
at
org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
at org.jboss.remoting.LeasePinger.sendClientPing(LeasePinger.java:283)
at org.jboss.remoting.LeasePinger.access$100(LeasePinger.java:20)
at org.jboss.remoting.LeasePinger$LeaseTimerTask.run(LeasePinger.java:300)
at java.util.TimerThread.mainLoop(Unknown Source)
at java.util.TimerThread.run(Unknown Source)
2009 Jun 15 17:19:06 [Timer-0] WARN org.jboss.remoting.LeasePinger -
LeasePinger[SocketClientInvoker[1c80b01,
bisocket://127.0.0.1:4457](aaw19-i6j7nu-fvyz3zgo-1-fvyz3zse-6)] failed to
ping to server: Failed to communicate. Problem during
marshalling/unmarshalling; nested exception is:
java.io.IOException:
EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment
org.jboss.jms.exception.MessagingNetworkFailureException
at
org.jboss.jms.client.delegate.DelegateSupport.handleThrowable(DelegateSupport.java:245)
at
org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:187)
at
org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
at
org.jboss.jms.client.container.StateCreationAspect.handleCreateConnectionDelegate(StateCreationAspect.java:83)
at
org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect0.invoke(StateCreationAspect0.java)
at
org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
at
org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java)
at
org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:205)
at
org.jboss.jms.client.JBossConnectionFactory.createConnection(JBossConnectionFactory.java:87)
at
org.jboss.jms.client.JBossConnectionFactory.createConnection(JBossConnectionFactory.java:82)
at com.jms.test.SimpleTestClient.main(SimpleTestClient.java:22)
Caused by: org.jboss.remoting.ConnectionFailedException: Timed out trying to
create control socket
at
org.jboss.remoting.transport.bisocket.BisocketClientInvoker.handleConnect(BisocketClientInvoker.java:273)
at
org.jboss.remoting.MicroRemoteClientInvoker.connect(MicroRemoteClientInvoker.java:294)
at org.jboss.remoting.Client.connect(Client.java:1596)
at org.jboss.remoting.Client.connect(Client.java:498)
at
org.jboss.remoting.callback.ServerInvokerCallbackHandler.connect(ServerInvokerCallbackHandler.java:166)
at
org.jboss.remoting.ServerInvoker.getCallbackHandler(ServerInvoker.java:2047)
at
org.jboss.remoting.ServerInvoker.handleInternalInvocation(ServerInvoker.java:1663)
at
org.jboss.remoting.transport.bisocket.BisocketServerInvoker.handleInternalInvocation(BisocketServerInvoker.java:863)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:895)
at
org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:742)
at
org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:695)
at
org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:549)
at
org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:230)
at
org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163)
at org.jboss.remoting.Client.invoke(Client.java:1513)
at org.jboss.remoting.Client.addCallbackListener(Client.java:1582)
at org.jboss.remoting.Client.addListener(Client.java:885)
at
org.jboss.jms.client.remoting.JMSRemotingConnection.addInvokerCallbackHandler(JMSRemotingConnection.java:230)
at
org.jboss.jms.client.remoting.JMSRemotingConnection.start(JMSRemotingConnection.java:340)
at
org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:154)
... 9 more
Kindly help me to solve the issue shortly .
Thanks in Advance .
Regards
Jai
Ovidiu Feodorov-2 wrote:
>
> Tim Fox wrote:
>> Ram Venkataraman wrote:t
>>> I talked to Ovididu about a month or so ago when Messaging went GA
>>> and spoke about integration JBM into 4.x and I clearly remember
>>> asking about remoting. He did not raise any red flags, in fact we
>>> spoke of it being compatible.
>>
>> I don't have any explanations why he would say that - we have been
>> dependent on remoting 2.2 for some time now.
>
> There is misunderstanding then. I could not have said JBM is compatible
> with Remoting currently used by JBM 4.x because it's clearly not, and
> this is a well know problem. I probably said there's no problem if we go
> scoped, which cannot be avoided for 4.2.0, but we should align our
> dependencies in 4.2.1. I also remember that this was still an open
> discussion.
>
> _______________________________________________
> jboss-development mailing list
> jboss-development@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
>
>
Johann Ungerer wrote:
>
> Hi Jim,
>
> Thank you for the reply, its gotten me quite a bit further.
>
> I am currently experiencing a connectivity issue from stomp to JBM, so I'm
> posting the startup file that I'm using for stomp in hopes that I'm doing
> something silly. I am able to connect to the JBM via code on the provider
> url i'm using, so the url "should" be right.
>
> If anyone sees anything obviously wrong, it would be greatly appreciated.
>
> --
>
> set uri=stomp://localhost:61613
> set providerurl=tcp://192.168.0.53:1099
>
> set
> classes=stompconnect-1.0.jar;commons-logging-1.1.jar;jboss-messaging.jar;jnpserver.jar;jboss-common.jar
> set
> properties=-Djava.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
> set properties=%properties% -Djava.naming.provider.url=%providerurl%
> set properties=%properties% -Djava.naming.security.principal=guest
> set properties=%properties% -Djava.naming.security.credentials=guest
>
> echo Connecting to %providerurl%
>
> java %properties% -classpath %classes% org.codehaus.stomp.jms.Main %uri%
> ConnectionFactory
>
> --
>
> TIA,
> j/
>
> -----Original Message-----
> From: Jim Gomes [mailto:e.semog@gmail.com]
> Sent: 26 February 2008 17:15
> To: users@activemq.apache.org
> Subject: Re: JBoss Messaging Stomp Configuration
>
> Hi Johann,
>
> It can take a little bit to figure out STOMPConnect, but once you have it
> configured, it's very low maintenance. I had to do something very similar
> to what you are attempting to do. I needed to be able to connect to TIBCO
> EMS using the Apache NMS client (this was before direct support was added
> for TIBCO). I used STOMPConnect to be my bridging mechanism. I ran the
> TIBCO server on one machine, the STOMPConnect on a second machine, and my
> NMS client on a third machine. The STOMPConnect portion could actually be
> run on any machine. I created a simple batch file that would run it on a
> Windows box. Essentially, the connection works as follows: The NMS client
> connects to STOMPConnect on port 61613. STOMPConnect translates the STOMP
> messages and forwards them as native JMS messages by connecting to TIBCO
> on
> port 7222. Here's the batch file. Hopefully, you can take this and
> customize it to use the JBOSS Messaging class factory and JMS clients. No
> custom Java coding required.
>
> ------------- 8< ----- SNIP ---- 8< ---------
>
> @echo off
> cls
> setlocal
> title STOMPConnect:61613 - jbosssrv
>
> set uri=stomp://localhost:61613
> set providerurl=tcp://jbosssrv:7222
>
> set
> classes=stompconnect-1.0.jar;commons-logging-1.1.jar;jms.jar;tibjms.jar
> set properties=-
> Djava.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContextFactory
> set properties=%properties% -Djava.naming.provider.url=%providerurl%
> set properties=%properties% -Djava.naming.security.principal=guest
> set properties=%properties% -Djava.naming.security.credentials=guest
>
> echo Connecting to %providerurl%
>
> java %properties% -classpath %classes% org.codehaus.stomp.jms.Main %uri%
> GenericConnectionFactory
>
> ------------- 8< ----- SNIP ---- 8< ---------
>
> You should replace the
> com.tibco.tibjms.naming.tibjmsInitialContextFactorywith the
> corresponding JBOSS Messaging context factory. The
> tibjms.jar file will be replaced with the JBOSS Messaging client jar file.
>
> Hope this helps you get further.
>
> - Jim
>
> On Mon, Feb 25, 2008 at 8:54 PM, Johann Ungerer
> <Jo...@pyrogenesis.co.za>
> wrote:
>
>> Hi Jim,
>>
>> Thanks for the reply. I've pretty much gotten that far. The trick I'm not
>> able to sort out on my own is actually configuring STOMPConnect to bridge
>> to
>> JBM. The documentation is a little patchy, I'm not sure which configs to
>> touch, would I run STOMPConnect as a stand-alone product, or can I use
>> the
>> "Injection Dependency" mentioned in the docs? I'm comfortable that I'll
>> sort
>> the client out, it's the server and bridge config that I'm not too sure
>> of.
>>
>> TIA,
>> j/
>>
>> -----Original Message-----
>> From: Jim Gomes [mailto:e.semog@gmail.com]
>> Sent: 25 February 2008 23:50
>> To: users@activemq.apache.org
>> Subject: Re: JBoss Messaging Stomp Configuration
>>
>> 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/
>> >
>> >
>>
>
>
--
View this message in context: http://www.nabble.com/JBoss-Messaging-Stomp-Configuration-tp15677725p24032215.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
RE: JBoss Messaging Stomp Configuration
Posted by Johann Ungerer <Jo...@pyrogenesis.co.za>.
Hi Jim,
Thank you for the reply, its gotten me quite a bit further.
I am currently experiencing a connectivity issue from stomp to JBM, so I'm posting the startup file that I'm using for stomp in hopes that I'm doing something silly. I am able to connect to the JBM via code on the provider url i'm using, so the url "should" be right.
If anyone sees anything obviously wrong, it would be greatly appreciated.
--
set uri=stomp://localhost:61613
set providerurl=tcp://192.168.0.53:1099
set classes=stompconnect-1.0.jar;commons-logging-1.1.jar;jboss-messaging.jar;jnpserver.jar;jboss-common.jar
set properties=-Djava.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
set properties=%properties% -Djava.naming.provider.url=%providerurl%
set properties=%properties% -Djava.naming.security.principal=guest
set properties=%properties% -Djava.naming.security.credentials=guest
echo Connecting to %providerurl%
java %properties% -classpath %classes% org.codehaus.stomp.jms.Main %uri% ConnectionFactory
--
TIA,
j/
-----Original Message-----
From: Jim Gomes [mailto:e.semog@gmail.com]
Sent: 26 February 2008 17:15
To: users@activemq.apache.org
Subject: Re: JBoss Messaging Stomp Configuration
Hi Johann,
It can take a little bit to figure out STOMPConnect, but once you have it
configured, it's very low maintenance. I had to do something very similar
to what you are attempting to do. I needed to be able to connect to TIBCO
EMS using the Apache NMS client (this was before direct support was added
for TIBCO). I used STOMPConnect to be my bridging mechanism. I ran the
TIBCO server on one machine, the STOMPConnect on a second machine, and my
NMS client on a third machine. The STOMPConnect portion could actually be
run on any machine. I created a simple batch file that would run it on a
Windows box. Essentially, the connection works as follows: The NMS client
connects to STOMPConnect on port 61613. STOMPConnect translates the STOMP
messages and forwards them as native JMS messages by connecting to TIBCO on
port 7222. Here's the batch file. Hopefully, you can take this and
customize it to use the JBOSS Messaging class factory and JMS clients. No
custom Java coding required.
------------- 8< ----- SNIP ---- 8< ---------
@echo off
cls
setlocal
title STOMPConnect:61613 - jbosssrv
set uri=stomp://localhost:61613
set providerurl=tcp://jbosssrv:7222
set classes=stompconnect-1.0.jar;commons-logging-1.1.jar;jms.jar;tibjms.jar
set properties=-
Djava.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContextFactory
set properties=%properties% -Djava.naming.provider.url=%providerurl%
set properties=%properties% -Djava.naming.security.principal=guest
set properties=%properties% -Djava.naming.security.credentials=guest
echo Connecting to %providerurl%
java %properties% -classpath %classes% org.codehaus.stomp.jms.Main %uri%
GenericConnectionFactory
------------- 8< ----- SNIP ---- 8< ---------
You should replace the
com.tibco.tibjms.naming.tibjmsInitialContextFactorywith the
corresponding JBOSS Messaging context factory. The
tibjms.jar file will be replaced with the JBOSS Messaging client jar file.
Hope this helps you get further.
- Jim
On Mon, Feb 25, 2008 at 8:54 PM, Johann Ungerer <Jo...@pyrogenesis.co.za>
wrote:
> Hi Jim,
>
> Thanks for the reply. I've pretty much gotten that far. The trick I'm not
> able to sort out on my own is actually configuring STOMPConnect to bridge to
> JBM. The documentation is a little patchy, I'm not sure which configs to
> touch, would I run STOMPConnect as a stand-alone product, or can I use the
> "Injection Dependency" mentioned in the docs? I'm comfortable that I'll sort
> the client out, it's the server and bridge config that I'm not too sure of.
>
> TIA,
> j/
>
> -----Original Message-----
> From: Jim Gomes [mailto:e.semog@gmail.com]
> Sent: 25 February 2008 23:50
> To: users@activemq.apache.org
> Subject: Re: JBoss Messaging Stomp Configuration
>
> 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/
> >
> >
>
Re: Newby question on message routing
Posted by James Strachan <ja...@gmail.com>.
On 26/02/2008, jimmy Zhang <cr...@comcast.net> wrote:
> Hi, all, I have just recently joined the list and wonder if
> someone can explain to me how FUSE routes XML messages
> in its current implementation... Is it DOM/XPath based or
> is it SAX/PULL based?
For FUSE related questions you should use the FUSE forums; these
forums are for the Apache distros...
http://open.iona.com/forums/index.jspa
When routing XML messages using Camel
http://activemq.apache.org/camel/
you can use various expression languages like XPath or XQuery to do
routing but its easy to add your own expression mechanism (you can use
any Java code to evaluate an expression); when using XPath by default
we use JAXP under the covers to evaluate XPath expressions.
If you use Artix Data Services for your XML payloads then it uses fast
in memory objects...
http://activemq.apache.org/camel/artix-data-services.html
We've a pending JIRA for SXC support which might help for more high
performance XML based routers using a more pull mechanism - but that
only supports a subset of XPath.
http://issues.apache.org/activemq/browse/CAMEL-326
> What is the performance number etc?
We've no specific performance tests; it kinda depends what your XML
looks like and what kinds routes you're doing.
--
James
-------
http://macstrac.blogspot.com/
Open Source Integration
http://open.iona.com
Newby question on message routing
Posted by jimmy Zhang <cr...@comcast.net>.
Hi, all, I have just recently joined the list and wonder if
someone can explain to me how FUSE routes XML messages
in its current implementation... Is it DOM/XPath based or
is it SAX/PULL based? What is the performance number etc?
I appreciate any suggestions on this...
thanks,
Jimmy Zhang
Re: JBoss Messaging Stomp Configuration
Posted by Jim Gomes <e....@gmail.com>.
Hi Johann,
It can take a little bit to figure out STOMPConnect, but once you have it
configured, it's very low maintenance. I had to do something very similar
to what you are attempting to do. I needed to be able to connect to TIBCO
EMS using the Apache NMS client (this was before direct support was added
for TIBCO). I used STOMPConnect to be my bridging mechanism. I ran the
TIBCO server on one machine, the STOMPConnect on a second machine, and my
NMS client on a third machine. The STOMPConnect portion could actually be
run on any machine. I created a simple batch file that would run it on a
Windows box. Essentially, the connection works as follows: The NMS client
connects to STOMPConnect on port 61613. STOMPConnect translates the STOMP
messages and forwards them as native JMS messages by connecting to TIBCO on
port 7222. Here's the batch file. Hopefully, you can take this and
customize it to use the JBOSS Messaging class factory and JMS clients. No
custom Java coding required.
------------- 8< ----- SNIP ---- 8< ---------
@echo off
cls
setlocal
title STOMPConnect:61613 - jbosssrv
set uri=stomp://localhost:61613
set providerurl=tcp://jbosssrv:7222
set classes=stompconnect-1.0.jar;commons-logging-1.1.jar;jms.jar;tibjms.jar
set properties=-
Djava.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContextFactory
set properties=%properties% -Djava.naming.provider.url=%providerurl%
set properties=%properties% -Djava.naming.security.principal=guest
set properties=%properties% -Djava.naming.security.credentials=guest
echo Connecting to %providerurl%
java %properties% -classpath %classes% org.codehaus.stomp.jms.Main %uri%
GenericConnectionFactory
------------- 8< ----- SNIP ---- 8< ---------
You should replace the
com.tibco.tibjms.naming.tibjmsInitialContextFactorywith the
corresponding JBOSS Messaging context factory. The
tibjms.jar file will be replaced with the JBOSS Messaging client jar file.
Hope this helps you get further.
- Jim
On Mon, Feb 25, 2008 at 8:54 PM, Johann Ungerer <Jo...@pyrogenesis.co.za>
wrote:
> Hi Jim,
>
> Thanks for the reply. I've pretty much gotten that far. The trick I'm not
> able to sort out on my own is actually configuring STOMPConnect to bridge to
> JBM. The documentation is a little patchy, I'm not sure which configs to
> touch, would I run STOMPConnect as a stand-alone product, or can I use the
> "Injection Dependency" mentioned in the docs? I'm comfortable that I'll sort
> the client out, it's the server and bridge config that I'm not too sure of.
>
> TIA,
> j/
>
> -----Original Message-----
> From: Jim Gomes [mailto:e.semog@gmail.com]
> Sent: 25 February 2008 23:50
> To: users@activemq.apache.org
> Subject: Re: JBoss Messaging Stomp Configuration
>
> 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/
> >
> >
>
RE: JBoss Messaging Stomp Configuration
Posted by Johann Ungerer <Jo...@pyrogenesis.co.za>.
Hi Jim,
Thanks for the reply. I've pretty much gotten that far. The trick I'm not able to sort out on my own is actually configuring STOMPConnect to bridge to JBM. The documentation is a little patchy, I'm not sure which configs to touch, would I run STOMPConnect as a stand-alone product, or can I use the "Injection Dependency" mentioned in the docs? I'm comfortable that I'll sort the client out, it's the server and bridge config that I'm not too sure of.
TIA,
j/
-----Original Message-----
From: Jim Gomes [mailto:e.semog@gmail.com]
Sent: 25 February 2008 23:50
To: users@activemq.apache.org
Subject: Re: JBoss Messaging Stomp Configuration
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 <Jo...@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/
>
>
Re: JBoss Messaging Stomp Configuration
Posted by Jim Gomes <e....@gmail.com>.
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 <Jo...@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/
>
>
Re: JBoss Messaging Stomp Configuration
Posted by James Strachan <ja...@gmail.com>.
BTW StompConnect is not a connection factory - is a Java bean that
uses a ConnectionFactory and has a start() method that must be called.
So we're talking about running this Java code...
StompConnect connector = new StompConnect(connectionFactory);
connector.start();
Feel free to wrap it up as an MBean if you wanna configure it in JBoss
MBean XML if you like.
On 26/02/2008, Johann Ungerer <Jo...@pyrogenesis.co.za> wrote:
> And that's exactly where I lose coherence. I'm not going to be writing any Java code here, so want to do it all via config. I created a datasource config for JBOSS as follows:
>
> <connection-factories>
> <!-- ==================================================================== -->
> <!-- STOMP Stuff -->
> <!-- ==================================================================== -->
> <!-- STOMPConnect -->
> <mbean code="org.codehaus.stomp.jms.StompConnect"
> name="jboss.messaging:service=StompConnect,name=StompConnect">
> <attribute name="ProviderName">StompConnect</attribute>
> <attribute name="Uri">tcp://localhost:61616</attribute>
> <attribute name="JNDIProvider">stomp/connect</attribute>
> </mbean>
> </connection-factories>
>
> And get a funky exception. However, I think I'll get around that problem by implementing a bean-dd xml section. What I firstly need to know is if I'm even remotely on the right track, or else how do I actually "run" StompConnect.
>
> Thanks again,
>
> j/
>
> -----Original Message-----
> From: James Strachan [mailto:james.strachan@gmail.com]
>
> Sent: 26 February 2008 13:45
> To: users@activemq.apache.org
> Subject: Re: JBoss Messaging Stomp Configuration
>
> Just create a StomConnect object, configure it with whatever
> ConnectionFactory you want from JBoss and call its start() method.
>
> Use whatever JBoss mechanisms you want (EJB/MBeans/spring) to configure that
>
> e.g. here's the JavaDoc
> http://stomp.codehaus.org/maven/apidocs/org/codehaus/stomp/jms/StompConnect.html
>
> On 26/02/2008, Johann Ungerer <Jo...@pyrogenesis.co.za> wrote:
> > Indeed... ;)
> >
> > My problem is the documentation seems a little light, or I don't have enough of a frame of reference to make sense of it.
> >
> > Below the documentation from Stomp:
> > If you use some kind of dependency injection framework like Spring you can configure StompConnect using XML if you prefer. Just configure the StompConnect POJO with
> >
> > the JMS ConnectionFactory instance
> > you can provide a JNDI InitialContext if you prefer, though its typcially easier to just provide the JMS ConnectionFactory
> > optionally you can provide the uri to expose the Stomp services on.
> > i.e. the host name and port that Stomp clients will connect to. Typically this will default to tcp://localhost:61613 but it can be any hostname/port
> >
> > http://stomp.codehaus.org/Running+StompConnect
> >
> > That does not tell me much I'm afraid.
> >
> > So, if anyone knows how to demystify that, I'll be very grateful.
> >
> > Thanks,
> >
> > j/
> >
> > -----Original Message-----
> > From: James Strachan [mailto:james.strachan@gmail.com]
> >
> > Sent: 26 February 2008 13:19
> > To: users@activemq.apache.org
> > Subject: Re: JBoss Messaging Stomp Configuration
> >
> >
> > On 26/02/2008, Johann Ungerer <Jo...@pyrogenesis.co.za> wrote:
> > > Hi James,
> > >
> > > See http://www.jboss.com/index.html?module=bb&op=viewtopic&t=128884 for the response from JBOSS.
> >
> > So basically they are passing the buck :)
> >
> > --
> > James
> > -------
> > http://macstrac.blogspot.com/
> >
> > Open Source Integration
> > http://open.iona.com
> >
>
>
> --
> James
> -------
> http://macstrac.blogspot.com/
>
> Open Source Integration
> http://open.iona.com
>
--
James
-------
http://macstrac.blogspot.com/
Open Source Integration
http://open.iona.com
Re: JBoss Messaging Stomp Configuration
Posted by James Strachan <ja...@gmail.com>.
On 26/02/2008, Johann Ungerer <Jo...@pyrogenesis.co.za> wrote:
> And that's exactly where I lose coherence. I'm not going to be writing any Java code here, so want to do it all via config.
Unfortunately right now you have to write Java code. There's no JBoss
specific configuration yet for StompConnect.
--
James
-------
http://macstrac.blogspot.com/
Open Source Integration
http://open.iona.com
RE: JBoss Messaging Stomp Configuration
Posted by Johann Ungerer <Jo...@pyrogenesis.co.za>.
And that's exactly where I lose coherence. I'm not going to be writing any Java code here, so want to do it all via config. I created a datasource config for JBOSS as follows:
<connection-factories>
<!-- ==================================================================== -->
<!-- STOMP Stuff -->
<!-- ==================================================================== -->
<!-- STOMPConnect -->
<mbean code="org.codehaus.stomp.jms.StompConnect"
name="jboss.messaging:service=StompConnect,name=StompConnect">
<attribute name="ProviderName">StompConnect</attribute>
<attribute name="Uri">tcp://localhost:61616</attribute>
<attribute name="JNDIProvider">stomp/connect</attribute>
</mbean>
</connection-factories>
And get a funky exception. However, I think I'll get around that problem by implementing a bean-dd xml section. What I firstly need to know is if I'm even remotely on the right track, or else how do I actually "run" StompConnect.
Thanks again,
j/
-----Original Message-----
From: James Strachan [mailto:james.strachan@gmail.com]
Sent: 26 February 2008 13:45
To: users@activemq.apache.org
Subject: Re: JBoss Messaging Stomp Configuration
Just create a StomConnect object, configure it with whatever
ConnectionFactory you want from JBoss and call its start() method.
Use whatever JBoss mechanisms you want (EJB/MBeans/spring) to configure that
e.g. here's the JavaDoc
http://stomp.codehaus.org/maven/apidocs/org/codehaus/stomp/jms/StompConnect.html
On 26/02/2008, Johann Ungerer <Jo...@pyrogenesis.co.za> wrote:
> Indeed... ;)
>
> My problem is the documentation seems a little light, or I don't have enough of a frame of reference to make sense of it.
>
> Below the documentation from Stomp:
> If you use some kind of dependency injection framework like Spring you can configure StompConnect using XML if you prefer. Just configure the StompConnect POJO with
>
> the JMS ConnectionFactory instance
> you can provide a JNDI InitialContext if you prefer, though its typcially easier to just provide the JMS ConnectionFactory
> optionally you can provide the uri to expose the Stomp services on.
> i.e. the host name and port that Stomp clients will connect to. Typically this will default to tcp://localhost:61613 but it can be any hostname/port
>
> http://stomp.codehaus.org/Running+StompConnect
>
> That does not tell me much I'm afraid.
>
> So, if anyone knows how to demystify that, I'll be very grateful.
>
> Thanks,
>
> j/
>
> -----Original Message-----
> From: James Strachan [mailto:james.strachan@gmail.com]
>
> Sent: 26 February 2008 13:19
> To: users@activemq.apache.org
> Subject: Re: JBoss Messaging Stomp Configuration
>
>
> On 26/02/2008, Johann Ungerer <Jo...@pyrogenesis.co.za> wrote:
> > Hi James,
> >
> > See http://www.jboss.com/index.html?module=bb&op=viewtopic&t=128884 for the response from JBOSS.
>
> So basically they are passing the buck :)
>
> --
> James
> -------
> http://macstrac.blogspot.com/
>
> Open Source Integration
> http://open.iona.com
>
--
James
-------
http://macstrac.blogspot.com/
Open Source Integration
http://open.iona.com
Re: JBoss Messaging Stomp Configuration
Posted by James Strachan <ja...@gmail.com>.
Just create a StomConnect object, configure it with whatever
ConnectionFactory you want from JBoss and call its start() method.
Use whatever JBoss mechanisms you want (EJB/MBeans/spring) to configure that
e.g. here's the JavaDoc
http://stomp.codehaus.org/maven/apidocs/org/codehaus/stomp/jms/StompConnect.html
On 26/02/2008, Johann Ungerer <Jo...@pyrogenesis.co.za> wrote:
> Indeed... ;)
>
> My problem is the documentation seems a little light, or I don't have enough of a frame of reference to make sense of it.
>
> Below the documentation from Stomp:
> If you use some kind of dependency injection framework like Spring you can configure StompConnect using XML if you prefer. Just configure the StompConnect POJO with
>
> the JMS ConnectionFactory instance
> you can provide a JNDI InitialContext if you prefer, though its typcially easier to just provide the JMS ConnectionFactory
> optionally you can provide the uri to expose the Stomp services on.
> i.e. the host name and port that Stomp clients will connect to. Typically this will default to tcp://localhost:61613 but it can be any hostname/port
>
> http://stomp.codehaus.org/Running+StompConnect
>
> That does not tell me much I'm afraid.
>
> So, if anyone knows how to demystify that, I'll be very grateful.
>
> Thanks,
>
> j/
>
> -----Original Message-----
> From: James Strachan [mailto:james.strachan@gmail.com]
>
> Sent: 26 February 2008 13:19
> To: users@activemq.apache.org
> Subject: Re: JBoss Messaging Stomp Configuration
>
>
> On 26/02/2008, Johann Ungerer <Jo...@pyrogenesis.co.za> wrote:
> > Hi James,
> >
> > See http://www.jboss.com/index.html?module=bb&op=viewtopic&t=128884 for the response from JBOSS.
>
> So basically they are passing the buck :)
>
> --
> James
> -------
> http://macstrac.blogspot.com/
>
> Open Source Integration
> http://open.iona.com
>
--
James
-------
http://macstrac.blogspot.com/
Open Source Integration
http://open.iona.com
RE: JBoss Messaging Stomp Configuration
Posted by Johann Ungerer <Jo...@pyrogenesis.co.za>.
Indeed... ;)
My problem is the documentation seems a little light, or I don't have enough of a frame of reference to make sense of it.
Below the documentation from Stomp:
If you use some kind of dependency injection framework like Spring you can configure StompConnect using XML if you prefer. Just configure the StompConnect POJO with
the JMS ConnectionFactory instance
you can provide a JNDI InitialContext if you prefer, though its typcially easier to just provide the JMS ConnectionFactory
optionally you can provide the uri to expose the Stomp services on.
i.e. the host name and port that Stomp clients will connect to. Typically this will default to tcp://localhost:61613 but it can be any hostname/port
http://stomp.codehaus.org/Running+StompConnect
That does not tell me much I'm afraid.
So, if anyone knows how to demystify that, I'll be very grateful.
Thanks,
j/
-----Original Message-----
From: James Strachan [mailto:james.strachan@gmail.com]
Sent: 26 February 2008 13:19
To: users@activemq.apache.org
Subject: Re: JBoss Messaging Stomp Configuration
On 26/02/2008, Johann Ungerer <Jo...@pyrogenesis.co.za> wrote:
> Hi James,
>
> See http://www.jboss.com/index.html?module=bb&op=viewtopic&t=128884 for the response from JBOSS.
So basically they are passing the buck :)
--
James
-------
http://macstrac.blogspot.com/
Open Source Integration
http://open.iona.com
Re: JBoss Messaging Stomp Configuration
Posted by James Strachan <ja...@gmail.com>.
On 26/02/2008, Johann Ungerer <Jo...@pyrogenesis.co.za> wrote:
> Hi James,
>
> See http://www.jboss.com/index.html?module=bb&op=viewtopic&t=128884 for the response from JBOSS.
So basically they are passing the buck :)
--
James
-------
http://macstrac.blogspot.com/
Open Source Integration
http://open.iona.com
RE: JBoss Messaging Stomp Configuration
Posted by Johann Ungerer <Jo...@pyrogenesis.co.za>.
Hi James,
See http://www.jboss.com/index.html?module=bb&op=viewtopic&t=128884 for the response from JBOSS.
Regards,
j/
-----Original Message-----
From: James Strachan [mailto:james.strachan@gmail.com]
Sent: 26 February 2008 11:13
To: users@activemq.apache.org
Subject: Re: JBoss Messaging Stomp Configuration
On 26/02/2008, Johann Ungerer <Jo...@pyrogenesis.co.za> wrote:
> Hi Rob,
>
> Unfortunately the choice of messaging platform is not in my control, so I have to go with one of the STOMP integration methods. I guess first prize will be StompConnect, but I'm struggling a little to make out head or tail of the process.
>
> I saw an article on ActiveMQ integration and tried the same strategy with the Stomp connect class, by creating a stomp-ds.xml in the deploy directory. However, I'm getting the following exception: org.jboss.deployment.DeploymentException: Class does not expose a management interface: java.lang.Object; - nested throwable: (javax.management.NotCompliantMBeanException: Class does not expose a management interface: java.lang.Object)
>
> I've traced that to the point where I now need to create some form of xmbean-dd file, but before I continue down that road, can you confirm that I'm on the right track here, or am I missing something simple and obvious?
You could try asking JBoss support why they can't work with StompConnect.
--
James
-------
http://macstrac.blogspot.com/
Open Source Integration
http://open.iona.com
Re: JBoss Messaging Stomp Configuration
Posted by James Strachan <ja...@gmail.com>.
On 26/02/2008, Johann Ungerer <Jo...@pyrogenesis.co.za> wrote:
> Hi Rob,
>
> Unfortunately the choice of messaging platform is not in my control, so I have to go with one of the STOMP integration methods. I guess first prize will be StompConnect, but I'm struggling a little to make out head or tail of the process.
>
> I saw an article on ActiveMQ integration and tried the same strategy with the Stomp connect class, by creating a stomp-ds.xml in the deploy directory. However, I'm getting the following exception: org.jboss.deployment.DeploymentException: Class does not expose a management interface: java.lang.Object; - nested throwable: (javax.management.NotCompliantMBeanException: Class does not expose a management interface: java.lang.Object)
>
> I've traced that to the point where I now need to create some form of xmbean-dd file, but before I continue down that road, can you confirm that I'm on the right track here, or am I missing something simple and obvious?
You could try asking JBoss support why they can't work with StompConnect.
--
James
-------
http://macstrac.blogspot.com/
Open Source Integration
http://open.iona.com
RE: JBoss Messaging Stomp Configuration
Posted by Johann Ungerer <Jo...@pyrogenesis.co.za>.
Hi Rob,
Unfortunately the choice of messaging platform is not in my control, so I have to go with one of the STOMP integration methods. I guess first prize will be StompConnect, but I'm struggling a little to make out head or tail of the process.
I saw an article on ActiveMQ integration and tried the same strategy with the Stomp connect class, by creating a stomp-ds.xml in the deploy directory. However, I'm getting the following exception: org.jboss.deployment.DeploymentException: Class does not expose a management interface: java.lang.Object; - nested throwable: (javax.management.NotCompliantMBeanException: Class does not expose a management interface: java.lang.Object)
I've traced that to the point where I now need to create some form of xmbean-dd file, but before I continue down that road, can you confirm that I'm on the right track here, or am I missing something simple and obvious?
Thanks again,
j/
-----Original Message-----
From: Rob Davies [mailto:rajdavies@gmail.com]
Sent: 26 February 2008 10:04
To: users@activemq.apache.org
Subject: Re: JBoss Messaging Stomp Configuration
On 25 Feb 2008, at 21:06, Johann Ungerer 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/
ActiveMQ is both client and sever side implementation - JBoss
messaging doesn't use openwire - or know about STOMP. So either:
use ActiveMQ with the NMS client - and use ActiveMQ instead of JBoss
messaging (best option ;)
or
use STOMP with Stomp Connect - configure that to bridge to JBoss
messaging
or
use ActiveMQ with stomp client and bridge to JBoss messaging
or
use NMS client with ActiveMQ and connect to JBoss messaging
cheers,
Rob
Re: JBoss Messaging Stomp Configuration
Posted by Rob Davies <ra...@gmail.com>.
On 25 Feb 2008, at 21:06, Johann Ungerer 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/
ActiveMQ is both client and sever side implementation - JBoss
messaging doesn't use openwire - or know about STOMP. So either:
use ActiveMQ with the NMS client - and use ActiveMQ instead of JBoss
messaging (best option ;)
or
use STOMP with Stomp Connect - configure that to bridge to JBoss
messaging
or
use ActiveMQ with stomp client and bridge to JBoss messaging
or
use NMS client with ActiveMQ and connect to JBoss messaging
cheers,
Rob