Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Unconsumed syslog JMS messages cause shutdown deadlock

Description

If there are unconsumed messages in the OpenNMS.Syslogd.BroadcastSyslog queue it appears to block the shutdown of Syslogd inside OpenNMS until the process is killed. You can reproduce this easily by connecting a Minion device (that is receiving syslog messages) to OpenNMS without installing the opennms-syslogd-handler-default feature inside OpenNMS. Messages will accumulate in the channel and if you try to shut down OpenNMS, you should see the following stack trace in a thread dump:

The output of status shows:

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Seth Leger December 5, 2016 at 3:43 PM

We haven't seen this issue in a while and Chandra was unable to reproduce it. Marking as cannot reproduce.

Chandra Gorantla October 5, 2016 at 9:49 AM

@seth , I couldn't reproduce this issue with the steps listed above. I m sending few syslog messages to minion and stopping OpenNMS. It is stopping properly without any issues. I tried this with opennms-syslogd-handler-default installed and uninstalled. Anything I m missing here ?

Cannot Reproduce

Details

Assignee

Reporter

Components

Sprint

Affects versions

Priority

PagerDuty

Created September 2, 2016 at 4:44 PM
Updated December 5, 2016 at 3:43 PM
Resolved December 5, 2016 at 3:43 PM