[
https://issues.apache.org/jira/browse/TAVERNA-971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15302291#comment-15302291
]
Stian Soiland-Reyes commented on TAVERNA-971:
---------------------------------------------
Adding {{-Djavax.net.debug=all}}
{code}
Ignoring unsupported cipher suite: TLS_RSA_WITH_AES_256_CBC_SHA256 for TLSv1
Ignoring unsupported cipher suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 for TLSv1
Ignoring unsupported cipher suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA256 for TLSv1
Ignoring unsupported cipher suite: TLS_RSA_WITH_AES_256_CBC_SHA256 for TLSv1.1
Ignoring unsupported cipher suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 for
TLSv1.1
Ignoring unsupported cipher suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA256 for
TLSv1.1
%% No cached client session
*** ClientHello, TLSv1.2
RandomCookie: GMT: 1464277862 bytes = { 218, 172, 155, 180, 11, 110, 130, 211,
54, 182, 107, 243, 61, 108, 168, 248, 63, 129, 77, 194, 57, 74, 164, 125, 65,
37, 174, 2 }
Session ID: {}
Cipher Suites: [TLS_RSA_WITH_AES_256_CBC_SHA256,
TLS_DHE_RSA_WITH_AES_256_CBC_SHA256, TLS_DHE_DSS_WITH_AES_256_CBC_SHA256,
TLS_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA,
TLS_DHE_DSS_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA256,
TLS_DHE_RSA_WITH_AES_128_CBC_SHA256, TLS_DHE_DSS_WITH_AES_128_CBC_SHA256,
TLS_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA,
TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_256_GCM_SHA384,
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384, TLS_DHE_DSS_WITH_AES_256_GCM_SHA384,
TLS_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_RSA_WITH_AES_128_GCM_SHA256,
TLS_DHE_DSS_WITH_AES_128_GCM_SHA256, SSL_RSA_WITH_3DES_EDE_CBC_SHA,
SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA,
TLS_EMPTY_RENEGOTIATION_INFO_SCSV]
Compression Methods: { 0 }
Extension signature_algorithms, signature_algorithms: SHA512withECDSA,
SHA512withRSA, SHA384withECDSA, SHA384withRSA, SHA256withECDSA, SHA256withRSA,
SHA224withECDSA, SHA224withRSA, SHA1withECDSA, SHA1withRSA, SHA1withDSA
***
[write] MD5 and SHA1 hashes: len = 117
0000: 01 00 00 71 03 03 57 47 1B 66 DA AC 9B B4 0B 6E ...q..WG.f.....n
0010: 82 D3 36 B6 6B F3 3D 6C A8 F8 3F 81 4D C2 39 4A ..6.k.=l..?.M.9J
0020: A4 7D 41 25 AE 02 00 00 2C 00 3D 00 6B 00 6A 00 ..A%....,.=.k.j.
0030: 35 00 39 00 38 00 3C 00 67 00 40 00 2F 00 33 00 5.9.8.<.g.@./.3.
0040: 32 00 9D 00 9F 00 A3 00 9C 00 9E 00 A2 00 0A 00 2...............
0050: 16 00 13 00 FF 01 00 00 1C 00 0D 00 18 00 16 06 ................
0060: 03 06 01 05 03 05 01 04 03 04 01 03 03 03 01 02 ................
0070: 03 02 01 02 02 .....
SpringOsgiExtenderThread-60, WRITE: TLSv1.2 Handshake, length = 117
[Raw write]: length = 122
0000: 16 03 03 00 75 01 00 00 71 03 03 57 47 1B 66 DA ....u...q..WG.f.
0010: AC 9B B4 0B 6E 82 D3 36 B6 6B F3 3D 6C A8 F8 3F ....n..6.k.=l..?
0020: 81 4D C2 39 4A A4 7D 41 25 AE 02 00 00 2C 00 3D .M.9J..A%....,.=
0030: 00 6B 00 6A 00 35 00 39 00 38 00 3C 00 67 00 40 .k.j.5.9.8.<.g.@
0040: 00 2F 00 33 00 32 00 9D 00 9F 00 A3 00 9C 00 9E ./.3.2..........
0050: 00 A2 00 0A 00 16 00 13 00 FF 01 00 00 1C 00 0D ................
0060: 00 18 00 16 06 03 06 01 05 03 05 01 04 03 04 01 ................
0070: 03 03 03 01 02 03 02 01 02 02 ..........
[Raw read]: length = 5
0000: 15 03 03 00 02 .....
[Raw read]: length = 2
0000: 02 50 .P
SpringOsgiExtenderThread-60, READ: TLSv1.2 Alert, length = 2
SpringOsgiExtenderThread-60, RECV TLSv1.2 ALERT: fatal, internal_error
SpringOsgiExtenderThread-60, called closeSocket()
SpringOsgiExtenderThread-60, handling exception: javax.net.ssl.SSLException:
Received fatal alert: internal_error
Can't load https://w3id.org/bundle/context
javax.net.ssl.SSLException: Received fatal alert: internal_error
at sun.security.ssl.Alerts.getSSLException(Alerts.java:208)
at sun.security.ssl.Alerts.getSSLException(Alerts.java:154)
{code}
logging it here in case other https connections from within workflows also
could fail in that way..
> jarcache not working through OSGi
> ---------------------------------
>
> Key: TAVERNA-971
> URL: https://issues.apache.org/jira/browse/TAVERNA-971
> Project: Apache Taverna
> Issue Type: Bug
> Components: Taverna Language
> Affects Versions: language 0.15.1, commandline 3.1.0
> Reporter: Stian Soiland-Reyes
> Assignee: Stian Soiland-Reyes
> Fix For: commandline 3.1.0, language 0.16.0
>
>
> taverna-robundle includes a
> [jarcache.json|https://github.com/apache/incubator-taverna-language/blob/master/taverna-robundle/src/main/resources/jarcache.json]
> which specifies
> [contexts/bundle.jsonld|https://github.com/apache/incubator-taverna-language/blob/master/taverna-robundle/src/main/resources/contexts/bundle.jsonld]
> to be loaded from the taverna-robundle JAR instead of from
> https://w3id.org/bundle/context.json
> This uses [JSONLD-Java's JAR
> cache|https://github.com/jsonld-ava/jsonld-java#loading-contexts-from-classpathjar]
> - in order to avoiding network access when parsing the manifest JSON-LD of
> the robundle.
> This does however not work well under OSGi with the Taverna Command Line, as
> the jarcache within the jsonld-java OSGi bundle can't access /jarcache.json
> in the taverna-robundle OSGi bundle - at least not without setting
> Thread.currentThread.setContextClassLoader().
> This caused running of the workflow to fail with a large stack trace at the
> point of closing the data bundle (this happen with or without -bundle)
> Note that using Jena 3.1.0 and OpenJDK on Ubuntu, access to
> https://w3id.org/bundle/context.json fails with an "internal error" SSL
> error, so even with network access it can fail.
> Note that in Taverna Language 0.15.1 there was also a bug that when adding
> the Apache header to the bundle.json an extra } was added - this worked with
> earlier versions of Jackson/JSONLD-Java but now after TAVERNA-970 upgrades
> this fails - thus for the Command Line 3.1.0 I propose a workaround to add a
> fixed bundle.json on its own classpath, and then set the thread context
> loader to its own classloader while running the workflow.
> The fix for robundle 0.16.0 would be to set the thread class loader before
> parsing the manifest.json.
> (Thus we can fix it properly for next Taverna Language, but can ship Command
> Line 3.1.0 with existing Language 0.15.1)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
