- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
NiFi ConsumeJMS processor error(Solace eventBroker)
- Labels:
-
Apache NiFi
Created 01-21-2025 11:30 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am trying to integrate NIFI with Solace event broker and have created JMSConnectionFactoryProvidor service, which is enabled and running. However my JMSConsume processor gives this error -
ConsumeJMS failed to process session due to Host not specified;
Below are the configs for my FactoryService and processor:
What am I missing in the configuration?
Thanks.
Created 01-22-2025 09:13 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@amitjha
Providing the full stack trace from the nifi-app.log may help here in identifying the issue.
Is the controller service enabled and valid?
any other exceptions in the logs related to either the consumeJMS processor or the JMSConnectionFactoryProvider controller service?
The connectionFactory will on attempt to create the connection once first referencing component request a connection. The exception eludes to and issue there, but full stack trace may help identify exactly what went wrong.
Have you tried this tutorial from Solace:
https://solace.com/integration-hub/nifi/
Other observations:
- Keep in mind that you are using an HDF release that is going on 8 years old.
- I recommend not adding outside jars directly to the NiFi lib directory. Create a directory outside of NiFi's base directory and add your custom jars there. Just make sure the NiFi service user can access that directory and owns the jars.
Thanks,
Matt
Created 01-23-2025 11:32 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the prompt response. We are working to get the stack-trace logs and would get back to you.
Thanks,
Amit.
Created 01-28-2025 02:49 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Matt,
This is the error, we receive in the log:
Thanks,
Amit.
