You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Matt Burgess (JIRA)" <ji...@apache.org> on 2019/02/13 20:04:00 UTC
[jira] [Updated] (NIFI-5869) JMS Connection Fails After JMS servers
Change behind JNDI
[ https://issues.apache.org/jira/browse/NIFI-5869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Burgess updated NIFI-5869:
-------------------------------
Resolution: Fixed
Fix Version/s: 1.9.0
Status: Resolved (was: Patch Available)
> JMS Connection Fails After JMS servers Change behind JNDI
> ---------------------------------------------------------
>
> Key: NIFI-5869
> URL: https://issues.apache.org/jira/browse/NIFI-5869
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.8.0
> Reporter: Ed Berezitsky
> Assignee: Ed Berezitsky
> Priority: Major
> Fix For: 1.9.0
>
> Attachments: 3261.patch.txt, JNDI_JMS_Exception.txt
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> JMS Connection Fails After JMS servers Change behind JNDI.
> Reproduce:
> # Define and enable JNDI Controller Service
> # Create a flow with ConsumeJMS or PublishJMS processors with controller service defined in #1.
> # Consume and publish at least one message to ensure the connectivity can be established.
> # Change JNDI configuration for the same connection factory to point to new JMS servers.
> # Stop JMS service on previous servers
> # Observe failure in ConsumeJMS/PublishJMS (Caused by: javax.jms.JMSException: Failed to connect to any server at: tcp://jms_server1:12345)
>
> Work Around:
> # Disable JNDI Controller Service
> # Enable JNDI Controller Service and dependent processors.
>
> Possible Issue/Fix:
> * AbstractJMSProcessor has a method "buildTargetResource", in which connection factory is instantiated and then cached in workerPool in onTrigger .
> * Issue: Once cached, it will be reused forever.
> * Fix: on connectivity failure there should be an attempt to rebuild the worker.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)