Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Wed, 8 Aug 2012 07:17:09 +0000 (UTC)
From: "Suray Philippe (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <1899693114.3319.1344410230147.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <919758351.3318.1344410110560.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Updated] (CAMEL-5490) Queue is Full in DefaultServicePool
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Suray Philippe updated CAMEL-5490:
----------------------------------

    Attachment: NettyTest.java

Here is a small test case.
                
> Queue is Full in DefaultServicePool
> -----------------------------------
>
>                 Key: CAMEL-5490
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5490
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-netty
>    Affects Versions: 2.10.0
>            Reporter: Suray Philippe
>         Attachments: NettyTest.java
>
>
> I use a Netty endPoint to forward messages to a client. These messages come from an another Netty endPoint.
> After several forwarded messages, an error occurs on every forwarded message:
> DEBUG 2012-08-06 15:30:06,482 [New I/O  worker #27] org.apache.camel.component.netty.handlers.ClientChannelHandler - Closing channel as an exception was thrown from Netty
> java.lang.IllegalStateException: Queue full
>         at java.util.AbstractQueue.add(AbstractQueue.java:71)
>         at java.util.concurrent.ArrayBlockingQueue.add(ArrayBlockingQueue.java:209)
>         at org.apache.camel.impl.DefaultServicePool.release(DefaultServicePool.java:96)
>         at org.apache.camel.impl.ProducerCache$1.done(ProducerCache.java:304)
>         at org.apache.camel.processor.SendProcessor$2$1.done(SendProcessor.java:125)
>         at org.apache.camel.component.netty.handlers.ClientChannelHandler.messageReceived(ClientChannelHandler.java:162)
>         at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296)
>         at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:423)
>         at org.jboss.netty.handler.codec.replay.ReplayingDecoder.callDecode(ReplayingDecoder.java:538)
>         at org.jboss.netty.handler.codec.replay.ReplayingDecoder.messageReceived(ReplayingDecoder.java:437)
>         at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268)
>         at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255)
>         at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:91)
>         at org.jboss.netty.channel.socket.nio.AbstractNioWorker.processSelectedKeys(AbstractNioWorker.java:373)
>         at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:247)
>         at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:35)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>         at java.lang.Thread.run(Thread.java:662)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira