[NIFI-5869] JMS Connection Fails After JMS servers Change behind JNDI

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.8.0
• Fix Version/s: 1.9.0
• Component/s: Extensions
• Assignee: Ed Berezitsky
• Reporter: Ed Berezitsky
• Created: 04/Dec/18 23:27
• Updated: 13/Feb/19 20:03
• Resolved: 13/Feb/19 20:03

Description

JMS Connection Fails After JMS servers Change behind JNDI.

Reproduce:

1. Define and enable JNDI Controller Service
2. Create a flow with ConsumeJMS or PublishJMS processors with controller service defined in #1.
3. Consume and publish at least one message to ensure the connectivity can be established.
4. Change JNDI configuration for the same connection factory to point to new JMS servers.
5. Stop JMS service on previous servers
6. Observe failure in ConsumeJMS/PublishJMS (Caused by: javax.jms.JMSException: Failed to connect to any server at: tcp://jms_server1:12345)

 

Work Around:

1. Disable JNDI Controller Service
2. 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. 

Issue Links

• links to: GitHub Pull Request #3261