camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Parsons (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CAMEL-2978) java.net.SocketException: Too many open files with Apache Camel(Netty TCP) 2.4.0.
Date Wed, 21 Jul 2010 20:27:51 GMT

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

Sean Parsons updated CAMEL-2978:
--------------------------------

    Attachment: CamelBreakingTest.groovy

This Groovy file manifests the issue, the @Grab annotation for camel-netty can be changed
between 2.3.0 and 2.4.0 with the latter throwing the exceptions.  This also uses the latest
version of Netty in both cases.

> java.net.SocketException: Too many open files with Apache Camel(Netty TCP) 2.4.0.
> ---------------------------------------------------------------------------------
>
>                 Key: CAMEL-2978
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2978
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-netty
>    Affects Versions: 2.4.0
>         Environment: Linux laptop 2.6.32-24-generic #38-Ubuntu SMP Mon Jul 5 09:20:59
UTC 2010 x86_64 GNU/Linux
> java version "1.6.0_20"
> Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
> Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01, mixed mode)
>            Reporter: Sean Parsons
>         Attachments: CamelBreakingTest.groovy
>
>
> I've got a unit test that works fine with Apache Camel 2.3.0, but as soon as I upgraded
to 2.4.0 it consistently started to fail.
> It performs a number of concurrent requests using this url:
> netty:tcp://localhost:2048?sync=true
> In both the client and server side of the unit test.
> There's also a sister test which does the same thing with Netty directly and that works
in isolation, so it would appear something has been broken in the transition to 2.4.0.  Previously
this code was also using a beta version of Netty, but even updating that specific dependency
has made no difference.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message