[
https://issues.apache.org/jira/browse/NIFI-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16297172#comment-16297172
]
ASF GitHub Bot commented on NIFI-614:
-------------------------------------
Github user jugi92 commented on the issue:
https://github.com/apache/nifi/pull/222
Was the Tibco issue ever followed up on?
I tried to set sSLTrustedCertificate as dynamic property but it gives the
following error:
```
2017-12-19 17:48:09,788 ERROR [StandardProcessScheduler Thread-7]
o.a.n.c.s.StandardControllerServiceNode
JMSConnectionFactoryProvider[id=a7cf3b99-c426-18a4-0000-00003dc28240] Failed to
invoke @OnEnabled method due to java.lang.IllegalStateException:
java.lang.IllegalStateException: Failed to set property sSLTrustedCertificate:
{}
java.lang.IllegalStateException: java.lang.IllegalStateException: Failed to
set property sSLTrustedCertificate
```
Tibco Java Doc is available here:
https://docs.tibco.com/pub/enterprise_message_service/6.3.0-february-2012/doc/html/tib_ems_api_reference/api/javadoc/com/tibco/tibjms/TibjmsConnectionFactory.html#setSSLTrustedCertificate(java.lang.String)
> Create a JMS ConnectionFactory controller service and refactor JMS processors
> to use it
> ---------------------------------------------------------------------------------------
>
> Key: NIFI-614
> URL: https://issues.apache.org/jira/browse/NIFI-614
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: 0.1.0
> Reporter: Michael Moser
> Assignee: Oleg Zhurakousky
> Labels: JMS
> Fix For: 0.6.0
>
>
> It is difficult to extend the standard JMS processors to use a different JMS
> provider besides the included ActiveMQ. Improve the process of adding
> support for other JMS providers.
> Create a JMS ConnectionFactoryService API in nifi-standard-services. Create
> an ActiveMQConnectionFactoryService with the ActiveMQ implementation in
> nifi-standard-services. Modify the JMS processors in
> nifi-standard-processors to use a ConnectionFactoryService to pick the JMS
> Provider to use.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
