Concurrency issue when creating Notification Events

Description

If you have multiple tabs of Opennms open and are creating or editing multiple event notifications, the data cross populates into both of the events,
an example of this is copying some data from 1 event to another with changes ,
the end result will be that there will only be 1 at the end or the data will get mixed up.
This has been tested on 1.8.12-1 and 1.10.5-1 and is the same on both

Regards
Darren

Environment

Centos 6. - issue is not OS specific

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Jeff Gehlbach December 16, 2013 at 11:33 AM

This issue is a duplicate of

Jeff Gehlbach September 18, 2012 at 8:57 AM

Also reclassifying, since it was opened under a component that's meant to cover the contents of configuration files as shipped.

Jeff Gehlbach September 18, 2012 at 8:55 AM

So this guy says to his doctor, "Doc, it hurts when I do this." And the doctor says, "Well then, don't do that!"

Seriously, though, the notification wizard as currently implemented really wasn't designed for concurrent use by the same logged in user. You could work around this problem by logging in as a different user in each tab. In that case you'd still need to watch out for simultaneous edits on the same event notification definition (there's an inevitable race condition if this happens) but you should not see cross-definition data mixing.

Thanks for the report. I'm going to kick this issue to the "Backlog" release, so that when the time comes to reimplement this bit of the UI we'll think about the problem during the design phase.

Duplicate

Details

Assignee

Reporter

Components

Affects versions

Priority

PagerDuty

Created September 17, 2012 at 12:52 AM
Updated December 16, 2013 at 11:33 AM
Resolved December 16, 2013 at 11:33 AM