camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Torsten Mielke (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-6562) maxThreads property of restlet component is ignored
Date Fri, 19 Jul 2013 11:42:49 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-6562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713575#comment-13713575
] 

Torsten Mielke commented on CAMEL-6562:
---------------------------------------

Apologies, missed the fact that maxThreads is to be configured on the restlet component and
not the endpoint. 

                
> maxThreads property of restlet component is ignored
> ---------------------------------------------------
>
>                 Key: CAMEL-6562
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6562
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-restlet
>    Affects Versions: 2.11.1
>            Reporter: Torsten Mielke
>            Assignee: Claus Ibsen
>              Labels: restlet
>             Fix For: 2.12.0
>
>         Attachments: CAMEL-6562.tgz
>
>
> Starting a Camel route that consumes from restlet as 
> {code:xml}
> <from uri="restlet:http://localhost:8080/test/v1.0/test?maxThreads=20"/>
> {code}
> the maxThreads property is ignored when configuring the restlet endpoint.
> If I push >10 concurrent requests it will result in this warning
> {noformat}
> INFO: Worker service thread pool: 1 core size, 10 largest size, 10 maximum size, 10 current
size
> INFO: Stop accepting new connections and transactions. Consider increasing the maximum
number of threads.
> {noformat}
> and any more than 10 concurrent requests receive 
> {noformat}
> DEBUG Received response: HTTP/1.1 - Not Found (404) - Not Found for exchangeId: ID-mac-fritz-box-53062-1374152641597-0-28
> {noformat}
> When I debugged through the creation and configuration of the RestletEndpoint the maxThreads
property was not set. 

--
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

Mime
View raw message