You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2015/10/13 12:37:05 UTC
[jira] [Resolved] (QPIDJMS-128)
TransportSupportTest#testCreateSslContextIncorrectStoreType fails following
Keystore changes in recent JDK8 builds
[ https://issues.apache.org/jira/browse/QPIDJMS-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell resolved QPIDJMS-128.
------------------------------------
Resolution: Fixed
> TransportSupportTest#testCreateSslContextIncorrectStoreType fails following Keystore changes in recent JDK8 builds
> ------------------------------------------------------------------------------------------------------------------
>
> Key: QPIDJMS-128
> URL: https://issues.apache.org/jira/browse/QPIDJMS-128
> Project: Qpid JMS
> Issue Type: Test
> Components: qpid-jms-client
> Affects Versions: 0.6.0
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Priority: Minor
> Fix For: 0.7.0
>
>
> In future the default Java keystore type will transition from the current JKS format to PKCS12. In preparation for this move, newer JDK8 installs now support a compatibility feature (enabled by default, disabled on request) that autodetects the actual keystore file type, so that even when a 'JKS' Keystore object instance is in use it can also open a PKCS12 format store file. TransportSupportTest#testCreateSslContextIncorrectStoreType verifies behaviour when a different store type is specified than the file actually supplied, and does this using a PKCS12 file with 'JKS' Keystore object instance, so the test fails on the most recent JDK8 versions as this is now a supported combination.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org