[
https://issues.apache.org/jira/browse/NIFI-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15764704#comment-15764704
]
Michael Moser commented on NIFI-3230:
-------------------------------------
By "GetJMSQueue doesn't work with ActiveMQ SSL" I mean I get this error message
when I start the GetJMSQueue processor.
ERROR [Timer-Driven Process Thread-10] o.a.nifi.processors.standard.GetJMSQueue
GetJMSQueue[id=0943d5cc-0159-1000-059e-6f460652b59b] Failed to connect to JMS
Server due to javax.jms.JMSException: Could not connect to broker URL:
ssl://localhost:61615. Reason: javax.net.ssl.SSLHandshakeException:
sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target
> Get/Put JMS broken for simple ActiveMQ SSL URIs
> -----------------------------------------------
>
> Key: NIFI-3230
> URL: https://issues.apache.org/jira/browse/NIFI-3230
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 0.5.1, 0.6.1, 1.1.0, 0.7.1
> Reporter: Michael Moser
> Assignee: Michael Moser
>
> The GetJMS* and PutJMS processors don't work with ActiveMQ SSL using the
> simple ssl://127.0.0.1:65189 URI. It does work, though, with composite URIs
> like failover:(ssl://127.0.0.1:65189,ssl://127.0.0.1:65188)?randomize=false
> Even though we want people to use ConsumeJMS and PublishJMS, we should fix
> the GetJMS* and PutJMS processors because they are still in the baseline.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
