[
https://issues.apache.org/jira/browse/QPIDJMS-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14954741#comment-14954741
]
ASF subversion and git services commented on QPIDJMS-128:
---------------------------------------------------------
Commit 47b67bfdf1f3bccdc32f8ba59afce4ac60d78207 in qpid-jms's branch
refs/heads/master from Robert Gemmell
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=47b67bf ]
QPIDJMS-128: update test to use a different combination that remains unsupported
> 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: Bug
> Components: qpid-jms-client
> Affects Versions: 0.6.0
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> 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: [email protected]
For additional commands, e-mail: [email protected]
