Hi
So on the Apache CI servers running Ubuntu on java7 we got the last
missing pieces with SSL.
I had to dig a big and enable logging to System.out, to let it be
visibile in Jenkins what is the problem.
I dugged out this. The "bad record MAC".
Apart from that, then all other pieces seems okay on Java7.
It works on my osx and windows xp etc.
org.eclipse.jetty.io.EofException
at org.eclipse.jetty.http.HttpParser.fill(HttpParser.java:954)
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:274)
at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:218)
at
org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:51)
at
org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:586)
at
org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:44)
at
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:598)
at
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:533)
at java.lang.Thread.run(Thread.java:722)
Caused by: javax.net.ssl.SSLException: bad record MAC
at sun.security.ssl.Alerts.getSSLException(Alerts.java:208)
at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1605)
at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1573)
at sun.security.ssl.SSLEngineImpl.readRecord(SSLEngineImpl.java:971)
at sun.security.ssl.SSLEngineImpl.readNetRecord(SSLEngineImpl.java:876)
at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:750)
at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:624)
at
org.eclipse.jetty.io.nio.SslSelectChannelEndPoint.unwrap(SslSelectChannelEndPoint.java:557)
at
org.eclipse.jetty.io.nio.SslSelectChannelEndPoint.fill(SslSelectChannelEndPoint.java:397)
at org.eclipse.jetty.http.HttpParser.fill(HttpParser.java:949)
... 8 more
On Fri, May 11, 2012 at 10:14 AM, Claus Ibsen <claus.ib...@gmail.com> wrote:
> Hi
>
> I installed the Java7 update 4 on my windows xp box.
> And gave the latest source code a test spin
>
> Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
> Maven home: E:\maven\bin\..
> Java version: 1.7.0_04, vendor: Oracle Corporation
> Java home: E:\jdk1.7.0_04\jre
> Default locale: en_GB, platform encoding: Cp1252
> OS name: "windows xp", version: "5.1", arch: "x86", family: "windows"
>
> The core + the components has now been tested, and I go only a slights issues
> - camel-jibx could not download the JARs needed for its test
> compiling. I skipped this
> - camel-zookeeper fails with a single test in some assertion
> - i had to re-run camel-sql due a transient error, worked the 2nd run
>
> I have not yet run the osgi and itests, but will give them a spin as well.
> So far it does look good.
>
>
>
> On Tue, May 8, 2012 at 7:23 PM, Christian Müller
> <christian.muel...@gmail.com> wrote:
>> There is no indication that quickfix 1.5.2 supports Java 7 [1]. But I will
>> give it a try today later. If it works, I will request a new bundle from
>> the SMX guys...
>>
>> [1]
>> http://www.quickfixj.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=fixVersion+%3D+%221.5.2%22+AND+project+%3D+QFJ
>>
>> Best,
>> Christian
>>
>> On Tue, May 8, 2012 at 3:36 PM, Claus Ibsen <claus.ib...@gmail.com> wrote:
>>
>>> On Tue, May 8, 2012 at 3:26 PM, Daniel Kulp <dk...@apache.org> wrote:
>>> > On Tuesday, May 08, 2012 07:12:28 AM Daniel Kulp wrote:
>>> >> On Tuesday, May 08, 2012 09:24:43 AM Claus Ibsen wrote:
>>> >> > For the fix in XStreamDataFormat.java, i wonder if the hardcoded
>>> >> > namespace to @XmlType(name = "converterList", namespace =
>>> >> > "http://camel.apache.org/schema/spring";)
>>> >> >
>>> >> > would be an issue for Blueprint XML, as we have the schema as:
>>> >> > "http://camel.apache.org/schema/blueprint"; instead
>>> >>
>>> >> Hmm... Good point. I'll try moving them out from being nested classes
>>> >> and seeing if that helps.
>>> >
>>> > Actually, this turns out to be the correct thing. Internally,
>>> everything
>>> > is in the "spring" namespace. The package-info.java uses the spring
>>> > namespace and the XmlType namespaces need to match that.
>>> >
>>> > The blueprint namespace handler renames all the blueprint namespaces in
>>> the
>>> > blueprint DOM to the spring namespace prior to parsing so the parsing
>>> will
>>> > work. Kind of a hack, but works.
>>> >
>>>
>>> Ah perfect.
>>>
>>> Yeah I thought that as well, but didn't realize how far the "hack"
>>> goes with the rename.
>>> But better raise a concern that none.
>>>
>>> The Camel Karaf commands which spit out the routes in XML, actually
>>> uses the spring namespace,
>>> also if the route is from Blueprint. But that is what the JAXB model
>>> namespaces was designed with in the first
>>> place, when it was created about 5 years ago.
>>>
>>> We could do a hack in the Karaf commands and spit out the namespace as
>>> blueprint if its a blueprint route.
>>> That would probably be nicer.
>>>
>>>
>>> >
>>> > --
>>> > Daniel Kulp
>>> > dk...@apache.org - http://dankulp.com/blog
>>> > Talend Community Coder - http://coders.talend.com
>>> >
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
>>> FuseSource
>>> Email: cib...@fusesource.com
>>> Web: http://fusesource.com
>>> Twitter: davsclaus, fusenews
>>> Blog: http://davsclaus.blogspot.com/
>>> Author of Camel in Action: http://www.manning.com/ibsen/
>>>
>
>
>
> --
> Claus Ibsen
> -----------------
> CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
> FuseSource
> Email: cib...@fusesource.com
> Web: http://fusesource.com
> Twitter: davsclaus, fusenews
> Blog: http://davsclaus.blogspot.com/
> Author of Camel in Action: http://www.manning.com/ibsen/
--
Claus Ibsen
-----------------
CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
