Hi
You need to configure the stomp component with the id="stomp" so Camel
uses that, eg
<bean id="stomp"
class="org.apache.camel.component.stomp.StompComponent"
depends-on="jmsBroker">
<property name="brokerURL" value="tcp://localhost:61623" />
</bean>
Then it works. Also the port number should be the stomp port number
and not the regular JMS number which was also configured wrong.
On Fri, Aug 30, 2013 at 8:15 AM, Claus Ibsen <claus.ib...@gmail.com> wrote:
> Hi
>
> When using these mailing lists / user forums, then you should have a
> bit of patience as other people often dont have the time to dive into
> something right away.
>
>
>
> On Fri, Aug 30, 2013 at 6:30 AM, apara <ap...@standardset.com> wrote:
>> Dejan,
>>
>> Should I create a formal bug for this issue with the sample of code which I
>> uploaded to this group?
>>
>> At this point, I tried all the options I could think of and could not fix
>> this issue. For now, we are using JmsTemplate approach to go directly to
>> the ActiveMQ Broker bypassing Camel, however, ideally we would like to use
>> Camel in this application.
>>
>> Thanks for any help you can offer.
>>
>> -AP_
>>
>>
>>
>> --
>> View this message in context:
>> http://camel.465427.n5.nabble.com/STOMP-Exception-The-maximum-command-length-was-exceeded-tp5738017p5738253.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> Email: cib...@redhat.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
--
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cib...@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
