You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Fried Hoeben (JIRA)" <ji...@apache.org> on 2013/05/22 15:21:20 UTC
[jira] [Commented] (CAMEL-6078) Multiple http4 components modify
each other port setting
[ https://issues.apache.org/jira/browse/CAMEL-6078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664092#comment-13664092 ]
Fried Hoeben commented on CAMEL-6078:
-------------------------------------
The name of issue is misleading. The problem is not multiple http4 components, but multiple ENDPOINTS (which will be far more common).
> Multiple http4 components modify each other port setting
> --------------------------------------------------------
>
> Key: CAMEL-6078
> URL: https://issues.apache.org/jira/browse/CAMEL-6078
> Project: Camel
> Issue Type: Bug
> Affects Versions: 2.10.3
> Environment: java version "1.6.0_26"
> Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.32-1 x86_64 GNU/Linux
> Reporter: lorenzo
> Priority: Minor
>
> This works:
> from("timer://foo?fixedRate=true&delay=0&period=5000")
> .to("http4:www.google.com/search?q=Camel")
> .to("log:root");
> This does not
> from("timer://foo?fixedRate=true&delay=0&period=5000")
> .to("http4:www.google.com/search?q=Camel")
> .to("log:root")
> .to("http4:192.168.172.41:8092/MyService/?wsdl");
> A netstat shows this (173.194.35.145 is a google ip)
> tcp6 0 1 10.4.5.107:42627 173.194.35.145:8092 SYN_SENT
> It looks like the second http4 declaration modified the port of the first one.
> Setting explicitly the port fixes the problem, like this
> from("timer://foo?fixedRate=true&delay=0&period=5000")
> .to("http4:www.google.com:80/search?q=Camel")
> .to("log:root")
> .to("http4:192.168.172.41:8092/MyService/?wsdl");
> Even this works fine
> from("timer://foo?fixedRate=true&delay=0&period=5000")
> .to("http4:www.google.com/search?q=Camel")
> .to("log:root")
> .to("http4:192.168.172.41:8092/MyService/?wsdl")
> .to("http4:www.yahoo.com:80/search?q=Camel");
> camel-http does NOT have this issue (BTW camel-http4 is missing from the form component list).
> I do not think this is by design, anyway it is very confusing to debug, because suddenly a previously working route stops to work just "freezing".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira