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 <ap...@standardset.com> 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<String, Object>
> parameters, String optionPrefix) {
> Map<String, Object> 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 <camel:to
> > 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] <http://user/SendEmail.jtp?type=node&node=5738064&i=0>
> > 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) Changing my Camel wiring to use tcp:....:61623 instead of
> > > stomp:....:61623:
> > >
> > > <bean class="org.apache.camel.component.stomp.StompComponent">
> > > <property name="brokerURL" value="tcp://localhost:61623" />
> > > </bean>
> > >
> > > 3) Changing the route from stomp:queue:dm6 to stomp:queue/dm6:
> > >
> > > <camel:camelContext>
> > > <camel:route>
> > > <camel:from uri="direct:sample/engine/user" />
> > > <camel:to uri="stomp:queue/dm6" />
> > > </camel:route>
> > > </camel:camelContext>
> > >
> > > 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] <http://user/SendEmail.jtp?type=node&node=5738064&i=2>>
> > 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
> > >>
> > >> <bean class="org.apache.camel.component.stomp.StompComponent">
> > >> <property name="brokerURL" value="tcp://localhost:61623" />
> > >> </bean>
> > >>
> > >> ------------------------------
> > >> 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<
> >
> http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.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.
> >
> >
> > ------------------------------
> > 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-tp5738017p5738064.html
> > To unsubscribe from STOMP: Exception: The maximum command length was
> > exceeded, click here<
> http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5738017&code=YXBhcmFAc3RhbmRhcmRzZXQuY29tfDU3MzgwMTd8LTU0MjY3MDkwOQ==
> >
> > .
> > NAML<
> http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
> >
> >
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/STOMP-Exception-The-maximum-command-length-was-exceeded-tp5738017p5738091.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
camel-activemq-stomp-ussue.tar.gz
Description: GNU Zip compressed data
