[
https://issues.apache.org/jira/browse/CASSANDRA-10908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15848640#comment-15848640
]
Yuki Morishita commented on CASSANDRA-10908:
--------------------------------------------
Do you mean you get the same exception as below:
{noformat}
Caused by: java.lang.IllegalArgumentException: Cannot support
TLS_RSA_WITH_AES_256_CBC_SHA with currently installed providers
{noformat}
You need to install JCE.
https://support.datastax.com/hc/en-us/articles/204226129-Receiving-error-Caused-by-java-lang-IllegalArgumentException-Cannot-support-TLS-RSA-WITH-AES-256-CBC-SHA-with-currently-installed-providers-on-DSE-startup-after-setting-up-client-to-node-encryption
> bad report: client_encryption seems to prevent startup in 2.2.4 and 3.1
> -----------------------------------------------------------------------
>
> Key: CASSANDRA-10908
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10908
> Project: Cassandra
> Issue Type: Bug
> Environment: Amazon Linux 2015.09
> Reporter: Will Hayworth
> Attachments: 2.2.4-client-log-trace.log, client_encryption.log
>
>
> Hi there! I'm a total Cassandra novice, so please forgive me if this report
> is lacking or malformed. I've been setting up a new cluster and trying to use
> 3.1 but I've noticed that so much as *enabling* client-to-node encryption
> causes the node to shut down after determining there's no gossip backlog.
> Notably, I set up node-to-node encryption beforehand and that was working
> just fine. I thought they might be interfering with each other, but that
> seems not to be the case. Logs attached. (Please let me know how I can be of
> further help!)
> Thanks for looking at this,
> Will
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
