It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,882
×10,916

question asked: Dec 17 '14, 6:15 p.m.
question was seen: 6,130 times
last updated: Mar 23 '15, 7:05 a.m.

Related questions

Workshop 4.x Extensions: Received fatal alert: handshake_failure in Jetty Server

0
Fran Burgos (123●1●23●52) | asked Dec 17 '14, 6:15 p.m.
I am following the workshop about extensions 4.x https://jazz.net/library/article/1000 but when I reach the step 1.6 Test the Jetty Based Server Launch __27. Connect with your browser. I get an error trying to connect to https://localhost:7443/jazz/admin

2014-12-18 00:06:36.597:WARN::EXCEPTION
javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
    at com.ibm.jsse2.o.a(o.java:30)
    at com.ibm.jsse2.o.a(o.java:23)
    at com.ibm.jsse2.SSLSocketImpl.b(SSLSocketImpl.java:356)
    at com.ibm.jsse2.SSLSocketImpl.a(SSLSocketImpl.java:58)
    at com.ibm.jsse2.SSLSocketImpl.h(SSLSocketImpl.java:63)
    at com.ibm.jsse2.SSLSocketImpl.a(SSLSocketImpl.java:316)
    at com.ibm.jsse2.SSLSocketImpl.startHandshake(SSLSocketImpl.java:220)
    at org.mortbay.jetty.security.SslSocketConnector$SslConnection.run(SslSocketConnector.java:675)
    at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
2014-12-18 00:06:36.613:WARN::EXCEPTION
javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
    at com.ibm.jsse2.o.a(o.java:30)
    at com.ibm.jsse2.o.a(o.java:23)
    at com.ibm.jsse2.SSLSocketImpl.b(SSLSocketImpl.java:356)
    at com.ibm.jsse2.SSLSocketImpl.a(SSLSocketImpl.java:58)
    at com.ibm.jsse2.SSLSocketImpl.h(SSLSocketImpl.java:63)
    at com.ibm.jsse2.SSLSocketImpl.a(SSLSocketImpl.java:316)
    at com.ibm.jsse2.SSLSocketImpl.startHandshake(SSLSocketImpl.java:220)
    at org.mortbay.jetty.security.SslSocketConnector$SslConnection.run(SslSocketConnector.java:675)
    at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
2014-12-18 00:06:36.613:WARN::EXCEPTION
javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
    at com.ibm.jsse2.o.a(o.java:30)
    at com.ibm.jsse2.o.a(o.java:23)
    at com.ibm.jsse2.SSLSocketImpl.b(SSLSocketImpl.java:356)
    at com.ibm.jsse2.SSLSocketImpl.a(SSLSocketImpl.java:58)
    at com.ibm.jsse2.SSLSocketImpl.h(SSLSocketImpl.java:63)
    at com.ibm.jsse2.SSLSocketImpl.a(SSLSocketImpl.java:316)
    at com.ibm.jsse2.SSLSocketImpl.startHandshake(SSLSocketImpl.java:220)
    at org.mortbay.jetty.security.SslSocketConnector$SslConnection.run(SslSocketConnector.java:675)
    at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)

RTC is version 4.0.7 and on the one hand the error is thrown only when I try to access via web. By the other hand I can create a connection correctly to Jetty in the Eclipse client.
Comments
Ralph Schoon commented Dec 18 '14, 2:40 a.m. | edited Dec 18 '14, 2:40 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

I have used it with all 4.x versions, except 4.0.7 so far and I have not seen this kind of error. I have seen issues with connecting, sometimes something blocks the entire port, however, what you describe does not seem to fall into that category.

Have you tried a different browser?

Fran Burgos commented Dec 18 '14, 5:54 p.m.

Now that you said these, I just test it on Chrome 39, Firefox 34 and IE 8 and it only works on IE.
I remember I did this Workshop with RTC 4.0.5 and it worked on every browser.

Donald Nong commented Dec 18 '14, 6:38 p.m.

You may have to enable SSL debugging to find out what's going on. In the Jetty launch file, add the following line to enable SSL handshake debugging.

<listEntry value="-Djavax.net.debug=ssl:handshake:verbose"/>
Or
<listEntry value="-Djavax.net.debug=all:handshake:verbose"/>
if you want to debug all handshakes.

Accepted answer

2
permanent link
Kamil Jezek (46●1●3) | answered Mar 18 '15, 4:38 p.m.
edited Mar 18 '15, 4:39 p.m.
 I fixed this problem in Chrome following this answear: http://superuser.com/a/876294 I believe that something simillar is happening in FF

Chrome probably blocks SSLv3 as too old/vulnerable. So perhaps use only locally for testing. 
Fran Burgos selected this answer as the correct answer
Comments
Fran Burgos commented Mar 23 '15, 7:04 a.m. | edited Mar 23 '15, 7:05 a.m.

This works.

One other answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Ralph Schoon (63.5k●3●36●46) | answered Dec 19 '14, 3:01 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
It worked for me and still works with all browsers. However, since there have been some SSL bugs recently, maybe your company or you changed the SSL protocol versions supported to one that is not yet supported with CLM? Just a guess.
Comments
Fran Burgos commented Dec 23 '14, 7:43 a.m.

I did nothing special. I am working with a Virtual Machine where I have installed RTC following the Workshop's steps. Then I have installed Chrome and Firefox from official sites. Nothing else.

Ralph Schoon commented Dec 23 '14, 4:04 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

I realized, that VMWARE uses one of the ports used by the workshop. Can you check that?

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.