Re: STOMP: Exception: The maximum command length was exceeded
Claus, thanks for your help, your changes worked and helped. "Claus Ibsen-2 [via Camel]" wrote: > Hi > >You need to configure the stomp component with the id="stomp" so Camel >uses that, eg > > class="org.apache.camel.component.stomp.StompComponent" >depends-on="jmsBroker"> > > > >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 <[hidden email]> 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 <[hidden email]> 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: [hidden email] >> Twitter: davsclaus >> Blog: http://davsclaus.com >> Author of Camel in Action: http://www.manning.com/ibsen > > > > >-- >Claus Ibsen >- >Red Hat, Inc. >Email: [hidden email] >Twitter: davsclaus >Blog: http://davsclaus.com >Author of Camel in Action: http://www.manning.com/ibsen > > > > > > >If you reply to this email, your message will be added to the discussion below: > > > http://camel.465427.n5.nabble.com/STOMP-Exception-The-maximum-command-length-was-exceeded-tp5738017p5738257.html > > > > > To unsubscribe from STOMP: Exception: The > maximum command length was exceeded, click here. > NAML > -- View this message in context: http://camel.465427.n5.nabble.com/STOMP-Exception-The-maximum-command-length-was-exceeded-tp5738017p5738264.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: STOMP: Exception: The maximum command length was exceeded
Hi You need to configure the stomp component with the id="stomp" so Camel uses that, eg 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 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 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
Re: STOMP: Exception: The maximum command length was exceeded
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 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
Re: STOMP: Exception: The maximum command length was exceeded
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.
Re: STOMP: Exception: The maximum command length was exceeded
Dejan and all,
Here is quick isolated sample of the code breaking (2 java classes,
configuration and pom).
Execute with:
mvn clean install
The unit test starts up embedded broker and attempts to create a camel
route via stomp.
Thanks for any help you can offer.
-AP_
On Tue, Aug 27, 2013 at 8:17 PM, apara wrote:
> Just tried the options you proposed:
>
> Seeing this exception instead:
>
> org.apache.camel.ResolveEndpointFailedException: Failed to resolve
> endpoint: stomp://queue:dm6?brokerURL=tcp%3A%2F%2Flocalhost%3A61623 due to:
> There are 1 parameters that couldn't be set on the endpoint. Check the uri
> if the parameters are spelt correctly and that they are properties of the
> endpoint. Unknown parameters=[{brokerURL=tcp://localhost:61623}]
> at
>
> org.apache.camel.impl.DefaultComponent.validateParameters(DefaultComponent.java:189)
> at
>
> org.apache.camel.impl.DefaultComponent.createEndpoint(DefaultComponent.java:134)
> at
>
> org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:508)
> at
>
> org.apache.camel.util.CamelContextHelper.getMandatoryEndpoint(CamelContextHelper.java:63)
> at
>
> org.apache.camel.model.RouteDefinition.resolveEndpoint(RouteDefinition.java:192)
> at
>
> org.apache.camel.impl.DefaultRouteContext.resolveEndpoint(DefaultRouteContext.java:106)
> at
>
> org.apache.camel.impl.DefaultRouteContext.resolveEndpoint(DefaultRouteContext.java:112)
> at
>
> org.apache.camel.model.SendDefinition.resolveEndpoint(SendDefinition.java:61)
> at
>
> org.apache.camel.model.SendDefinition.createProcessor(SendDefinition.java:55)
> at
>
> org.apache.camel.model.ProcessorDefinition.makeProcessor(ProcessorDefinition.java:500)
> at
>
> org.apache.camel.model.ProcessorDefinition.addRoutes(ProcessorDefinition.java:213)
> at
> org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:909)
> at
> org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:177)
> at
>
> org.apache.camel.impl.DefaultCamelContext.startRoute(DefaultCamelContext.java:770)
> at
>
> org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:1914)
> at
>
> org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:1670)
> at
>
> org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:1544)
> at
>
> org.apache.camel.spring.SpringCamelContext.doStart(SpringCamelContext.java:179)
> at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
> at
>
> org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:1512)
> at
>
> org.apache.camel.spring.SpringCamelContext.maybeStart(SpringCamelContext.java:228)
> at
>
> org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:118)
> at
>
> org.apache.camel.spring.CamelContextFactoryBean.onApplicationEvent(CamelContextFactoryBean.java:301)
> at
>
> org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:97)
> at
>
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicat
>
> Due to this:
>
> protected void validateParameters(String uri, Map
> parameters, String optionPrefix) {
> Map param = parameters;
> if (optionPrefix != null) {
> param = IntrospectionSupport.extractProperties(parameters,
> optionPrefix);
> }
>
> if (param.size() > 0) {
> throw new ResolveEndpointFailedException(uri, "There are " +
> param.size()
> + " parameters that couldn't be set on the endpoint."
> + " Check the uri if the parameters are spelt correctly and
> that they are properties of the endpoint."
> + " Unknown parameters=[" + param + "]");
> }
> }
>
> -AP_
>
>
> On Tue, Aug 27, 2013 at 7:46 AM, Dejan Bosanac [via Camel] <
> ml-node+s465427n5738064...@n5.nabble.com> wrote:
>
> > Coupe more things to try.
> >
> > 1. Use 61613 for the stomp transport in the broker configuration
> >
> > 2. Use stomp endpoint like > uri="stomp:queue:dm6?brokerUrl=tcp://localhost:61623" /> (use the same
> > port you configure in the broker)
> >
> > If all fails, it's best to create a test case that demonstrate your
> > problem, so we can examine it further.
> >
> > Regards
> > --
> > Dejan Bosanac
> > --
> > Red Hat, Inc.
> > FuseSource is now part of Red Hat
> > [hidden email]
> > Twitter: @dejanb
> > Blog: http://sensatic.net
> > ActiveMQ in Action: http://www.manning.com/snyder/
> >
> > On Tue, Aug 27, 2013 at 4:07 PM, apara <[hidden email]<
> http://user/SendEmail.jtp?type=node&node=5738064&i=1>>
> > wrote:
> >
> > > I tried a number of things:
> > >
> > > 1) Changing broker configuration to:
> > > final TransportConnector
> > > stompConnector =
> > > broker.addConnector("stomp+nio://0.0.0.0:61623");
> > >
> > >
> > > 2)
Re: STOMP: Exception: The maximum command length was exceeded
Just tried the options you proposed:
Seeing this exception instead:
org.apache.camel.ResolveEndpointFailedException: Failed to resolve
endpoint: stomp://queue:dm6?brokerURL=tcp%3A%2F%2Flocalhost%3A61623 due to:
There are 1 parameters that couldn't be set on the endpoint. Check the uri
if the parameters are spelt correctly and that they are properties of the
endpoint. Unknown parameters=[{brokerURL=tcp://localhost:61623}]
at
org.apache.camel.impl.DefaultComponent.validateParameters(DefaultComponent.java:189)
at
org.apache.camel.impl.DefaultComponent.createEndpoint(DefaultComponent.java:134)
at
org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:508)
at
org.apache.camel.util.CamelContextHelper.getMandatoryEndpoint(CamelContextHelper.java:63)
at
org.apache.camel.model.RouteDefinition.resolveEndpoint(RouteDefinition.java:192)
at
org.apache.camel.impl.DefaultRouteContext.resolveEndpoint(DefaultRouteContext.java:106)
at
org.apache.camel.impl.DefaultRouteContext.resolveEndpoint(DefaultRouteContext.java:112)
at
org.apache.camel.model.SendDefinition.resolveEndpoint(SendDefinition.java:61)
at
org.apache.camel.model.SendDefinition.createProcessor(SendDefinition.java:55)
at
org.apache.camel.model.ProcessorDefinition.makeProcessor(ProcessorDefinition.java:500)
at
org.apache.camel.model.ProcessorDefinition.addRoutes(ProcessorDefinition.java:213)
at
org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:909)
at
org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:177)
at
org.apache.camel.impl.DefaultCamelContext.startRoute(DefaultCamelContext.java:770)
at
org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:1914)
at
org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:1670)
at
org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:1544)
at
org.apache.camel.spring.SpringCamelContext.doStart(SpringCamelContext.java:179)
at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
at
org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:1512)
at
org.apache.camel.spring.SpringCamelContext.maybeStart(SpringCamelContext.java:228)
at
org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:118)
at
org.apache.camel.spring.CamelContextFactoryBean.onApplicationEvent(CamelContextFactoryBean.java:301)
at
org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:97)
at
org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicat
Due to this:
protected void validateParameters(String uri, Map
parameters, String optionPrefix) {
Map param = parameters;
if (optionPrefix != null) {
param = IntrospectionSupport.extractProperties(parameters,
optionPrefix);
}
if (param.size() > 0) {
throw new ResolveEndpointFailedException(uri, "There are " +
param.size()
+ " parameters that couldn't be set on the endpoint."
+ " Check the uri if the parameters are spelt correctly and
that they are properties of the endpoint."
+ " Unknown parameters=[" + param + "]");
}
}
-AP_
On Tue, Aug 27, 2013 at 7:46 AM, Dejan Bosanac [via Camel] <
ml-node+s465427n5738064...@n5.nabble.com> wrote:
> Coupe more things to try.
>
> 1. Use 61613 for the stomp transport in the broker configuration
>
> 2. Use stomp endpoint like uri="stomp:queue:dm6?brokerUrl=tcp://localhost:61623" /> (use the same
> port you configure in the broker)
>
> If all fails, it's best to create a test case that demonstrate your
> problem, so we can examine it further.
>
> Regards
> --
> Dejan Bosanac
> --
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> [hidden email]
> Twitter: @dejanb
> Blog: http://sensatic.net
> ActiveMQ in Action: http://www.manning.com/snyder/
>
> On Tue, Aug 27, 2013 at 4:07 PM, apara <[hidden
> email]>
> wrote:
>
> > I tried a number of things:
> >
> > 1) Changing broker configuration to:
> > final TransportConnector
> > stompConnector =
> > broker.addConnector("stomp+nio://0.0.0.0:61623");
> >
> >
> > 2) Changing my Camel wiring to use tcp::61623 instead of
> > stomp::61623:
> >
> >
> >
> >
> >
> > 3) Changing the route from stomp:queue:dm6 to stomp:queue/dm6:
> >
> >
> >
> >
> >
> >
> >
> >
> > And still I get the same exception in each of the above changes. One
> thing
> > to note, I also see a WARN message for unknown data type which I did not
> > notice before:
> >
> > 06:56:56.841 engine [ActiveMQ Transport: tcp:///127.0.0.1:63277@61613]
> WARN
> > Transport - Transport Connection to: tcp://127.0.0.1:63
Re: STOMP: Exception: The maximum command length was exceeded
Most of the day in meetings today, I did not have a chance to put together
an isolated example. What I did manage to do re-connect a Spring
JmsTemplate implementation back into my code. The JmsTemplate
implementation seems to work fine.
Here is how its wired:
In my class:
@Resource(name="jmsStompTemplate")
private JmsTemplate
jmsTemplate;
...
//Send a stomp message on its way
//
jmsTemplate.send(
//Create a specifically stop destination, regular
destination will not do
//
new StompJmsDestination(
getTopicName(userId)
),
//Message creator to create a stomp message
//
new MessageCreator() {
@Override
public Message createMessage(final Session session)
throws JMSException {
return
session.createTextMessage(messageText);
}
}
);
So, the above appears to work talking to Broker's at tcp://localhost:61623,
recall my broker's configuration is:
final BrokerService
broker =
new BrokerService();
//Create the network connector
//
final TransportConnector
stompConnector =
broker.addConnector("stomp+nio://0.0.0.0:61623");
So, the issue does not appear to be on the Broker's side but rather on the
sending side. Still working on figuring out what the difference is. By
the way, does anyone know where the code for camel-stomp is, specifically
version 2.12-SNAPSHOT ?
Thanks.
-AP_
On Tue, Aug 27, 2013 at 7:46 AM, Dejan Bosanac [via Camel] <
ml-node+s465427n5738064...@n5.nabble.com> wrote:
> Coupe more things to try.
>
> 1. Use 61613 for the stomp transport in the broker configuration
>
> 2. Use stomp endpoint like uri="stomp:queue:dm6?brokerUrl=tcp://localhost:61623" /> (use the same
> port you configure in the broker)
>
> If all fails, it's best to create a test case that demonstrate your
> problem, so we can examine it further.
>
> Regards
> --
> Dejan Bosanac
> --
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> [hidden email]
> Twitter: @dejanb
> Blog: http://sensatic.net
> ActiveMQ in Action: http://www.manning.com/snyder/
>
> On Tue, Aug 27, 2013 at 4:07 PM, apara <[hidden
> email]>
> wrote:
>
> > I tried a number of things:
> >
> > 1) Changing broker configuration to:
> > final TransportConnector
> > stompConnector =
> > broker.addConnector("stomp+nio://0.0.0.0:61623");
> >
> >
> > 2) Changing my Camel wiring to use tcp::61623 instead of
> > stomp::61623:
> >
> >
> >
> >
> >
> > 3) Changing the route from stomp:queue:dm6 to stomp:queue/dm6:
> >
> >
> >
> >
> >
> >
> >
> >
> > And still I get the same exception in each of the above changes. One
> thing
> > to note, I also see a WARN message for unknown data type which I did not
> > notice before:
> >
> > 06:56:56.841 engine [ActiveMQ Transport: tcp:///127.0.0.1:63277@61613]
> WARN
> > Transport - Transport Connection to: tcp://127.0.0.1:63277 failed:
> > java.io.IOException: Unknown data type: 69
> > 06:56:56.873 engine [main] ERROR ContextLoader - Context initialization
> > failed
> > org.apache.camel.RuntimeCamelException:
> > org.apache.camel.FailedToCreateRouteException: Failed to create route
> > route1 at: >>> To[stomp:queue/dm6] <<< in route:
> > Route(route1)[[From[direct:sample/engine/user]] -> [To[stomp... because
> of
> > Failed to resolve endpoint: stomp://queue/dm6 due to: The maximum
> command
> > length was exceeded
> > at
> >
> org.apache.camel.util.ObjectHelper.wrapRuntimeCamelException(ObjectHelper.java:1344)
>
> > ~[camel-core-2.12-SNAPSHOT.jar:2.12-SNAPSHOT]
> >
> > I am going to go back to try to send messages via JmsTemplate in Spring
> to
> > see if that still works. Perhaps there was another change that I did
> which
> > I don't remember. If that does not work, I will know there is something
> > with my configuration. Perhaps the salad bar of dependencies needs to
> be
> > revisited.
> >
> > If you guys have any other suggestions I can try them out...
> >
> > Thanks for your help.
> > -AP_
> >
> >
> > On Tue, Aug 27, 2013 at 12:49 AM, dejanb [via Camel] <
> > [hidden email] >
> wrote:
> >
> >> Hi, the problem is that you're trying to send stomp messages to
> openwire
> >> transport connector. Try changing your stomp component to something
> like
> >>
> >>
> >>
> >>
> >>
> >> --
> >> If you reply to this email, your message wil
Re: STOMP: Exception: The maximum command length was exceeded
Coupe more things to try.
1. Use 61613 for the stomp transport in the broker configuration
2. Use stomp endpoint like (use the same
port you configure in the broker)
If all fails, it's best to create a test case that demonstrate your
problem, so we can examine it further.
Regards
--
Dejan Bosanac
--
Red Hat, Inc.
FuseSource is now part of Red Hat
dbosa...@redhat.com
Twitter: @dejanb
Blog: http://sensatic.net
ActiveMQ in Action: http://www.manning.com/snyder/
On Tue, Aug 27, 2013 at 4:07 PM, apara wrote:
> I tried a number of things:
>
> 1) Changing broker configuration to:
> final TransportConnector
> stompConnector =
> broker.addConnector("stomp+nio://0.0.0.0:61623");
>
>
> 2) Changing my Camel wiring to use tcp::61623 instead of
> stomp::61623:
>
>
>
>
>
> 3) Changing the route from stomp:queue:dm6 to stomp:queue/dm6:
>
>
>
>
>
>
>
>
> And still I get the same exception in each of the above changes. One thing
> to note, I also see a WARN message for unknown data type which I did not
> notice before:
>
> 06:56:56.841 engine [ActiveMQ Transport: tcp:///127.0.0.1:63277@61613] WARN
> Transport - Transport Connection to: tcp://127.0.0.1:63277 failed:
> java.io.IOException: Unknown data type: 69
> 06:56:56.873 engine [main] ERROR ContextLoader - Context initialization
> failed
> org.apache.camel.RuntimeCamelException:
> org.apache.camel.FailedToCreateRouteException: Failed to create route
> route1 at: >>> To[stomp:queue/dm6] <<< in route:
> Route(route1)[[From[direct:sample/engine/user]] -> [To[stomp... because of
> Failed to resolve endpoint: stomp://queue/dm6 due to: The maximum command
> length was exceeded
> at
> org.apache.camel.util.ObjectHelper.wrapRuntimeCamelException(ObjectHelper.java:1344)
> ~[camel-core-2.12-SNAPSHOT.jar:2.12-SNAPSHOT]
>
> I am going to go back to try to send messages via JmsTemplate in Spring to
> see if that still works. Perhaps there was another change that I did which
> I don't remember. If that does not work, I will know there is something
> with my configuration. Perhaps the salad bar of dependencies needs to be
> revisited.
>
> If you guys have any other suggestions I can try them out...
>
> Thanks for your help.
> -AP_
>
>
> On Tue, Aug 27, 2013 at 12:49 AM, dejanb [via Camel] <
> ml-node+s465427n5738023...@n5.nabble.com> wrote:
>
>> Hi, the problem is that you're trying to send stomp messages to openwire
>> transport connector. Try changing your stomp component to something like
>>
>>
>>
>>
>>
>> --
>> If you reply to this email, your message will be added to the discussion
>> below:
>>
>> http://camel.465427.n5.nabble.com/STOMP-Exception-The-maximum-command-length-was-exceeded-tp5738017p5738023.html
>> To unsubscribe from STOMP: Exception: The maximum command length was
>> exceeded, click
>> here
>> .
>> NAML
>>
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/STOMP-Exception-The-maximum-command-length-was-exceeded-tp5738017p5738059.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
Re: STOMP: Exception: The maximum command length was exceeded
I tried a number of things:
1) Changing broker configuration to:
final TransportConnector
stompConnector =
broker.addConnector("stomp+nio://0.0.0.0:61623");
2) Changing my Camel wiring to use tcp::61623 instead of
stomp::61623:
3) Changing the route from stomp:queue:dm6 to stomp:queue/dm6:
And still I get the same exception in each of the above changes. One thing
to note, I also see a WARN message for unknown data type which I did not
notice before:
06:56:56.841 engine [ActiveMQ Transport: tcp:///127.0.0.1:63277@61613] WARN
Transport - Transport Connection to: tcp://127.0.0.1:63277 failed:
java.io.IOException: Unknown data type: 69
06:56:56.873 engine [main] ERROR ContextLoader - Context initialization
failed
org.apache.camel.RuntimeCamelException:
org.apache.camel.FailedToCreateRouteException: Failed to create route
route1 at: >>> To[stomp:queue/dm6] <<< in route:
Route(route1)[[From[direct:sample/engine/user]] -> [To[stomp... because of
Failed to resolve endpoint: stomp://queue/dm6 due to: The maximum command
length was exceeded
at
org.apache.camel.util.ObjectHelper.wrapRuntimeCamelException(ObjectHelper.java:1344)
~[camel-core-2.12-SNAPSHOT.jar:2.12-SNAPSHOT]
I am going to go back to try to send messages via JmsTemplate in Spring to
see if that still works. Perhaps there was another change that I did which
I don't remember. If that does not work, I will know there is something
with my configuration. Perhaps the salad bar of dependencies needs to be
revisited.
If you guys have any other suggestions I can try them out...
Thanks for your help.
-AP_
On Tue, Aug 27, 2013 at 12:49 AM, dejanb [via Camel] <
ml-node+s465427n5738023...@n5.nabble.com> wrote:
> Hi, the problem is that you're trying to send stomp messages to openwire
> transport connector. Try changing your stomp component to something like
>
>
>
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://camel.465427.n5.nabble.com/STOMP-Exception-The-maximum-command-length-was-exceeded-tp5738017p5738023.html
> To unsubscribe from STOMP: Exception: The maximum command length was
> exceeded, click
> here
> .
> NAML
>
--
View this message in context:
http://camel.465427.n5.nabble.com/STOMP-Exception-The-maximum-command-length-was-exceeded-tp5738017p5738059.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: STOMP: Exception: The maximum command length was exceeded
Hi, the problem is that you're trying to send stomp messages to openwire transport connector. Try changing your stomp component to something like -- View this message in context: http://camel.465427.n5.nabble.com/STOMP-Exception-The-maximum-command-length-was-exceeded-tp5738017p5738023.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: STOMP: Exception: The maximum command length was exceeded
Hi,
Try using Stomp protocol over NIO transport.For better scalability
(and performance) you might want to run Stomp protocol over NIO transport.
To do that just use stomp+nio transport prefix instead of stomp.
For example, add the following transport configuration
stompConnector =
broker.addConnector("stomp+nio://localhost:61612")
This transport use NIO transport underneath and will generally use much less
threads than standard connector. This connector can help if you want to use
large number of queues
I don't know this will help you or not but just give a try
For info please refer this link
http://activemq.apache.org/stomp.html
Cheers!!!
Bharath.R
--
View this message in context:
http://camel.465427.n5.nabble.com/STOMP-Exception-The-maximum-command-length-was-exceeded-tp5738017p5738019.html
Sent from the Camel - Users mailing list archive at Nabble.com.
