Matt, I am not seeing any error messages at all related to the JMS server connection. I am also not seeing and connection tear down messages. This is really odd.
It seems fairly easy to replicate, just add a GetJMS processor, then remove it then add another one. I am using ActiveMQ as the broker. On Mon, May 4, 2015 at 12:05 PM, Matt Gilman <[email protected]> wrote: > Rob, > > It looks as though the connection is closed when the processor is stopped. > If that is not the behavior you're seeing can you check the logs for any > warnings that contain the message > > "unable to close connection to JMS Server due to " > > followed by a more detailed explanation. Thanks. > > Matt > > On Mon, May 4, 2015 at 11:59 AM, Rob Weiss <[email protected]> wrote: > > > All, > > What is the expectation of the connection state when the processor is not > > in a running state? We have seen that the connection does not release and > > has to be forced to release by shutting the NiFi process down. This is > > causing a major headache when trying to consume the queue via another > > process (either within NiFi or outside of NiFi). > > > > Thoughts? > > > > Thanks, > > Rob. > > >
