[
https://issues.apache.org/jira/browse/BROOKLYN-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14994573#comment-14994573
]
ASF GitHub Bot commented on BROOKLYN-190:
-----------------------------------------
Github user CMoH commented on the pull request:
https://github.com/apache/incubator-brooklyn/pull/997#issuecomment-154560691
It seems that we are both right. By adding an `invocationCount` parameter
to the test under question I've found that "sometimes" we get
`SocketException`, and sometimes `SSLHandshakeException`. I've tracked the
problem down to a (theoretical) flaw in the way
`org.apache.http.conn.ssl.SSLSocketFactory` handles SSL socket connections.
However, it may be that this race is visible only when both ends of the socket
are on the same host, or (as in our test case) within the same process.
> Upgrade to Jetty9
> -----------------
>
> Key: BROOKLYN-190
> URL: https://issues.apache.org/jira/browse/BROOKLYN-190
> Project: Brooklyn
> Issue Type: Improvement
> Affects Versions: 0.8.0, 0.9.0
> Reporter: Ciprian Ciubotariu
> Assignee: Ciprian Ciubotariu
> Priority: Minor
> Fix For: 0.9.0
>
>
> According to [1] jetty9 is now the stable version.
> In relation to BROOKLYN-183, current stable pax-web 4.x series also support
> Jetty9 (although I believe it can be used with Jetty8 as well). However,
> migrating Brooklyn to a more current Jetty version seems preferable.
> [1] http://www.eclipse.org/jetty/documentation/current/what-jetty-version.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
