Can you turn on debug logging, it should help seeing what's wrong. One thing
I noticed is that you're missing some dependencies like xstream for example.
Regards
--
Dejan Bosanac - http://twitter.com/dejanb
-
The experts in open source integration and messaging - http://fusesource
http://activemq.2283324.n4.nabble.com/STOMP-transport-in-embedded-Broker-not-working-tp3640473p3643511.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
I added the activemq-optional artifact to my POM and this is now working.
org.apache.activemq
activemq-core
-SketchCND
--
View this message in context:
http://activemq.2283324.n4.nabble.com/STOMP-transport-in-embedded-Broker-not-working-tp3640473p3643511.html
Sent from the ActiveMQ
Hi,
On Sat, Jul 2, 2011 at 7:18 PM, SketchCND
wrote:
> Hi Martin,
>
> Thanks for the reply. I don't believe that this issue is on the client side.
[...]
Hmm, I suppose you are right and I think my reply might have been
meant for another topic. I just need to find it again. Sorry!
Best regards,
embedded broker?
- SketchCND
--
View this message in context:
http://activemq.2283324.n4.nabble.com/STOMP-transport-in-embedded-Broker-not-working-tp3640473p3640811.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hi,
I just noticed I got the documentation for the C++ project, but I
suppose there will be similar settings for the broker itself.
Best regards,
Martin
On Sat, Jul 2, 2011 at 3:11 PM, Martin C. wrote:
> Hi,
>
> maybe http://activemq.apache.org/cms/configuring.html can help,
> especially the wi
Hi,
maybe http://activemq.apache.org/cms/configuring.html can help,
especially the wireFormat.maxInactivityDuration setting. But I don't
know if/how it applies to STOMP connections, but I would also be very
interested in this, as it might be that I need to connect some clients
via STOMP.
Best reg
I have a maven project embedding a broker using Spring XML / XBean with the
STOMP transport configured. Any help would be greatly appreciated!
Logging indicates the broker starts and the STOMP transport has started on the
configured port. However, using the STOMP example in the ActiveMQ 5.5 do