You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by huntc <hu...@mac.com> on 2009/05/06 10:17:23 UTC
Jetty unit https test messages
Hi there,
I've made some local changes to the jetty unit tests so they are able to
support a key/trust store path that has spaces in it (such as on my
machine). The change is pretty simple - instead of passing the result of a
URL's getPath to the system property we convert to a URI and then use
getPath.
Anyhow I noticed the following output from HttpsRouteTest and wondered if it
was normal:
Running org.apache.camel.component.jetty.HttpsRouteTest
2009-05-06 18:10:17.264::INFO: jetty-6.1.14
2009-05-06 18:10:17.530::INFO: Started SslSocketConnector@localhost:9080
2009-05-06 18:10:17.869::INFO: jetty-6.1.14
2009-05-06 18:10:17.871::INFO: Started SslSocketConnector@localhost:9080
2009-05-06 18:10:18.06::WARN: EXCEPTION
javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
at
com.sun.net.ssl.internal.ssl.InputRecord.handleUnknownRecord(InputRecord.java:523)
at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:355)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:723)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1030)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1057)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1041)
at
org.mortbay.jetty.security.SslSocketConnector$SslConnection.run(SslSocketConnector.java:631)
at
org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522)
2009-05-06 18:10:18.132::INFO: jetty-6.1.14
2009-05-06 18:10:18.134::INFO: Started SslSocketConnector@localhost:9080
2009-05-06 18:10:18.523::INFO: jetty-6.1.14
2009-05-06 18:10:18.525::INFO: Started SslSocketConnector@localhost:9080
2009-05-06 18:10:18.544::WARN: EXCEPTION
javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
at
com.sun.net.ssl.internal.ssl.InputRecord.handleUnknownRecord(InputRecord.java:523)
at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:355)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:723)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1030)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1057)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1041)
at
org.mortbay.jetty.security.SslSocketConnector$SslConnection.run(SslSocketConnector.java:631)
at
org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522)
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.415 sec
Kind regards,
Christopher
--
View this message in context: http://www.nabble.com/Jetty-unit-https-test-messages-tp23402063p23402063.html
Sent from the Camel Development mailing list archive at Nabble.com.
Re: Jetty unit https test messages
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
I think these exceptions has always been in the unit test of camel-jetty.
On Wed, May 6, 2009 at 10:17 AM, huntc <hu...@mac.com> wrote:
>
> Hi there,
>
> I've made some local changes to the jetty unit tests so they are able to
> support a key/trust store path that has spaces in it (such as on my
> machine). The change is pretty simple - instead of passing the result of a
> URL's getPath to the system property we convert to a URI and then use
> getPath.
>
> Anyhow I noticed the following output from HttpsRouteTest and wondered if it
> was normal:
>
>
> Running org.apache.camel.component.jetty.HttpsRouteTest
> 2009-05-06 18:10:17.264::INFO: jetty-6.1.14
> 2009-05-06 18:10:17.530::INFO: Started SslSocketConnector@localhost:9080
> 2009-05-06 18:10:17.869::INFO: jetty-6.1.14
> 2009-05-06 18:10:17.871::INFO: Started SslSocketConnector@localhost:9080
> 2009-05-06 18:10:18.06::WARN: EXCEPTION
> javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
> at
> com.sun.net.ssl.internal.ssl.InputRecord.handleUnknownRecord(InputRecord.java:523)
> at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:355)
> at
> com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:723)
> at
> com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1030)
> at
> com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1057)
> at
> com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1041)
> at
> org.mortbay.jetty.security.SslSocketConnector$SslConnection.run(SslSocketConnector.java:631)
> at
> org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522)
> 2009-05-06 18:10:18.132::INFO: jetty-6.1.14
> 2009-05-06 18:10:18.134::INFO: Started SslSocketConnector@localhost:9080
> 2009-05-06 18:10:18.523::INFO: jetty-6.1.14
> 2009-05-06 18:10:18.525::INFO: Started SslSocketConnector@localhost:9080
> 2009-05-06 18:10:18.544::WARN: EXCEPTION
> javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
> at
> com.sun.net.ssl.internal.ssl.InputRecord.handleUnknownRecord(InputRecord.java:523)
> at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:355)
> at
> com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:723)
> at
> com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1030)
> at
> com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1057)
> at
> com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1041)
> at
> org.mortbay.jetty.security.SslSocketConnector$SslConnection.run(SslSocketConnector.java:631)
> at
> org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522)
> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.415 sec
>
>
> Kind regards,
> Christopher
> --
> View this message in context: http://www.nabble.com/Jetty-unit-https-test-messages-tp23402063p23402063.html
> Sent from the Camel Development mailing list archive at Nabble.com.
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
Apache Camel Reference Card:
http://refcardz.dzone.com/refcardz/enterprise-integration
Interview with me:
http://architects.dzone.com/articles/interview-claus-ibsen-about?mz=7893-progress