camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joshua Watkins (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CAMEL-4730) Change cometd SslSocketConnetor to use SslSelectChannelConnector
Date Mon, 05 Dec 2011 15:20:40 GMT

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

Joshua Watkins updated CAMEL-4730:
----------------------------------

    Attachment: cometdSslConnectorPatchWithStartFix.txt

Patch for SslSelectChannelConnector being used instead of SslSocketConnector. Additionally
there was a memory leak involving the CometdProducer.start() and CometdConsumer.start() being
called multiple times and creating a new related service.
                
> Change cometd SslSocketConnetor to use SslSelectChannelConnector
> ----------------------------------------------------------------
>
>                 Key: CAMEL-4730
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4730
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-cometd
>    Affects Versions: 2.9.0
>            Reporter: Joshua Watkins
>         Attachments: cometdSslConnectorPatchWithStartFix.txt
>
>
> Currently cometd uses SslSocketConnector for cometds connections. In its current configuration
it can only support about 35 connections as SslSocketConnector is a blocking connector. Switching
this to use the SslSelectChannelConnector in the same way it uses the SelectChannelConnector
will fix this and allow the cometds to perform as the non ssl version.

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

        

Mime
View raw message