I am connecting to a UDP server port and getting data from there in my route
defined something like this:
from("netty4:udp://server:port?broadcast=true&networkInterface=eth0&keepAlive=true").to("log:SimpleLog")
I know there is no connectivity issue, however, I get following exception:
[d #0 - Ne
CleoCleo:
Thanks for the reply. These are long-standing TCP connections, meaning that
the client that connects to my Camel application establishes the connection
and in the "sunny-day" case continues to send a continual stream of messages
each of which are delimited by the ... tags. The message
Hi
MDC is also an out of the box option into Camel for several informations [1]
http://camel.apache.org/mdc-logging.html
Greg AUTRIC
JBoss Middleware Consultant
email : gautric __at__ redhat __dot__ com
twitter : @gautric_io
Red Hat Global Services
Red Hat
Hi,
maybe you should try this http://camel.apache.org/load-balancer.html
with Failover policy
Like
java.io.IOException
com.mycompany.MyOtherException
hope it helps you,
best regards,
Greg AUTRIC
JBoss Middleware
On Mon, Oct 5, 2015 at 4:13 PM, wheli wrote:
> I upgraded and it made no difference, but then I noticed that I was missing a
> closing parenthesis on my "transformBodyUsingStyleSheet" method. I fixed
> this and it resolved the issue. Sorry for not seeing that, but i am all set
> now. Thanks!
>
Ah
I upgraded and it made no difference, but then I noticed that I was missing a
closing parenthesis on my "transformBodyUsingStyleSheet" method. I fixed
this and it resolved the issue. Sorry for not seeing that, but i am all set
now. Thanks!
--
View this message in context:
http://camel.465427.n5
Our partner provides two UDP endpoints on two servers. One is primary and
other secondary.
We want to write a route that by default listens to primary but
automatically fail-over to secondary in case of primary connection problem.
Is it possible out of the box? I looked at netty4 component, but can
Hi
Yeah you can try latest 2.13.x in case you consider upgraded on
existing release branch.
But 2.15.3 is the latest stable release. And 2.16.0 is being built
this week and hopefully GA next week.
On Mon, Oct 5, 2015 at 3:02 PM, wheli wrote:
> Ok, thanks Claus.
>
> Would you recommend trying 2.
Ok, thanks Claus.
Would you recommend trying 2.15.3 or 2.16? Is 2.15.3 the latest stable?
--
View this message in context:
http://camel.465427.n5.nabble.com/Apache-Camel-bean-parameter-binding-issue-with-Spring-DSL-tp5772200p5772294.html
Sent from the Camel - Users mailing list archive at Nabb
I'd rather not be pigeon-holed with the header namemeaning, I'd like to
make it so that the creator of any route can name the header whatever they
want, and use this method, without having any knowledge of the method
parameters (having to go look at the java components).
--
View this message
Hi
I am sorry to say it but you may try a newer release to see if it works there.
I could not reproduce any issue on lastest code. And mind that
${exchange} has just only been added to simple language in 2.16
release.
On Mon, Oct 5, 2015 at 2:47 PM, wheli wrote:
> Sure...
>
> public String extr
Sure...
public String extractDocumentRootOid(Exchange exchange) throws Exception
public Organization getOrganizationByOid(Exchange exchange, String oid)
throws InterchangeException
(Organization is a custom java object)
public String extractStyleSheetAttributeFromOrganization(Exchange exchange,
Roger:
Yes, I do see camel-netty4-2.15.2.jar in my Java classpath.
My Maven *pom.xml* dependency looks like this, where *camelCoreVersion *is
2.15.2:
org.apache.camel
camel-netty4
${camelCoreVersion}
SteveR
--
View this message
for response have you configured a JMS listener? A listener runs in a
separate thread and wouldn't have the MDC information which you have set. if
you JMS response has the UUID as part of it then you should reset the MDC
with the value received from JMS.
--
View this message in context:
http:/
14 matches
Mail list logo