geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <j...@apache.org>
Subject [jira] Closed: (GERONIMO-3034) Use jettys NIO based connectors by default.
Date Sat, 02 Jun 2007 08:13:15 GMT

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

David Jencks closed GERONIMO-3034.
----------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 2.0-M5)
                   2.0-M6

rev 543715.  Actually using the HTTPSSelectChannelConnector will have to wait for JETTY-355
to be applied.  This also makes jetty connectors use our thread pool.

> Use jettys NIO based connectors by default.
> -------------------------------------------
>
>                 Key: GERONIMO-3034
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3034
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: Jetty
>    Affects Versions: 2.0-M4
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: 2.0-M6
>
>
> Jetty has nio based SelectChannelConnector and SslSelectChannelConnector that we should
wrap and use by default.  Also the ssl wrapper should override createSslEngine and get the
sslEngine from our KeystoreManager, which also needs that method.

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