camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CAMEL-9075) 1% of requests get connect exception and are not sent
Date Thu, 05 May 2016 15:08:12 GMT

     [ https://issues.apache.org/jira/browse/CAMEL-9075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Claus Ibsen resolved CAMEL-9075.
--------------------------------
    Resolution: Cannot Reproduce

Upgrade and try again.

> 1% of requests get connect exception and are not sent
> -----------------------------------------------------
>
>                 Key: CAMEL-9075
>                 URL: https://issues.apache.org/jira/browse/CAMEL-9075
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-netty
>    Affects Versions: 2.14.3
>            Reporter: Elyran Kogan
>            Priority: Minor
>
> I have a shared worker pool that I'm using for all my producers. I have a server that
sends requests to a single domain - using camel netty4-http
> when running a small load test, no more than 20 requests per sec, I see that some of
the requests (about 1%) are timed out and then the netty producer sends a ConnectException:
(code snipped from NettyProducer class
>  if (!channelFuture.isDone() || !channelFuture.isSuccess()) {
>         ConnectException cause = new ConnectException("Cannot connect to " + configuration.getAddress());
> I did a tcp dump and saw that the requests that were timed out were never sent from the
server - there was no TCP request that was made.
> the request is simply not sent and there is no indication as to why or what is the problem
- except a timeout on something that causes the ConnectException  to appear
> I don't know if it is related, but I'm sending the requests using a routing slip



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message