camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Schneider (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CAMEL-2518) Test failures in camel-jetty SpringHttpsRouteTest and HttpRouteUsingUrlPostTest
Date Mon, 08 Mar 2010 08:09:44 GMT

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

Christian Schneider updated CAMEL-2518:
---------------------------------------

    Attachment: JettyHttpComponent.java-2010-03-08.patch

Hi Willem,

your suggestion works very well. This seems like a good solution. I have added another small
patch for JettyHttpComponent. I propose to stop the connectors in doClose(). In case the routes
did not close all connectors this will clean up. I had to do this when I converted the SpringHttpsRouteTest
to a plain spring integration test. So I think it is a good idea to do so.

Btw. Are you interested in the patch for SpringHttpsRouteTest too? It is not necessary to
solve the problem but I think it is more spring standard like than the current test. 

Greetings

Christian


> Test failures in camel-jetty SpringHttpsRouteTest and HttpRouteUsingUrlPostTest
> -------------------------------------------------------------------------------
>
>                 Key: CAMEL-2518
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2518
>             Project: Apache Camel
>          Issue Type: Test
>          Components: camel-jetty
>    Affects Versions: 2.2.0
>         Environment: Windows Vista JDK 1.6 Upadte 14
>            Reporter: Christian Schneider
>            Assignee: Willem Jiang
>             Fix For: 2.3.0
>
>         Attachments: JettyHttpComponent.java-2010-03-08.patch, surefire-report.html
>
>
> The test results are added as an attachment
> Running org.apache.camel.component.jetty.SpringHttpsRouteTest
> 2010-03-03 08:30:48.092:INFO::jetty-6.1.22
> 2010-03-03 08:30:48.100:INFO::Started SslSocketConnector@localhost:9080
> 2010-03-03 08:30:48.183:WARN::EXCEPTION 
> javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_unknown
> 	at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:174)
> 	at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:136)
> 	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.recvAlert(SSLSocketImpl.java:1682)
> 	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:932)
> 	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1112)
> 	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1139)
> 	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1123)
> 	at org.mortbay.jetty.security.SslSocketConnector$SslConnection.run(SslSocketConnector.java:675)
> 	at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
> 2010-03-03 08:30:49.404:INFO::jetty-6.1.22
> 2010-03-03 08:30:49.411:INFO::Started SslSocketConnector@localhost:9080
> 2010-03-03 08:30:49.438: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:789)
> 	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1112)
> 	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1139)
> 	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1123)
> 	at org.mortbay.jetty.security.SslSocketConnector$SslConnection.run(SslSocketConnector.java:675)
> 	at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
> Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.556 sec <<<
FAILURE!
> Running org.apache.camel.component.jetty.HttpRouteUsingUrlPostTest
> 2010-03-03 08:31:27.291:INFO::jetty-6.1.22
> 2010-03-03 08:31:27.294:INFO::Started SelectChannelConnector@localhost:9080
> 2010-03-03 08:31:28.029:INFO::jetty-6.1.22
> 2010-03-03 08:31:28.032:INFO::Started SelectChannelConnector@localhost:9080
> 2010-03-03 08:31:28.637:INFO::jetty-6.1.22
> 2010-03-03 08:31:28.639:INFO::Started SelectChannelConnector@localhost:9080
> 2010-03-03 08:31:29.210:INFO::jetty-6.1.22
> 2010-03-03 08:31:29.213:INFO::Started SelectChannelConnector@localhost:9080
> 2010-03-03 08:31:29.773:INFO::jetty-6.1.22
> 2010-03-03 08:31:29.777:INFO::Started SelectChannelConnector@localhost:9080
> 2010-03-03 08:31:30.465:INFO::jetty-6.1.22
> 2010-03-03 08:31:30.467:INFO::Started SelectChannelConnector@localhost:9080
> 2010-03-03 08:31:31.154:INFO::jetty-6.1.22
> 2010-03-03 08:31:31.156:INFO::Started SelectChannelConnector@localhost:9080
> Tests run: 7, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 4.648 sec <<<
FAILURE!

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