Bug #19679

DPM doesn't fully support state events

Added by Richard Neswold almost 3 years ago. Updated almost 3 years ago.

Data Pool Manager
Target version:
Start date:
Due date:
% Done:


Estimated time:


Brian Hendricks noticed new DPM doesn't handle state events when the device is referred to by name. Instead it returns DPM_BAD_EVENT.


#1 Updated by Richard Neswold almost 3 years ago

Charlie modified the DRF2 module. It was only accepting a state device by name or by 0:####### format. He made it also accept an integer, which gets translated to the 0:####### form. (erl-drf2|9c6f9c20)

#2 Updated by Richard Neswold almost 3 years ago

  • Status changed from Assigned to Feedback

Charlie modified DPM to lookup the device specified in the state event. The DRF2 change he made ensures DPM always receives a device name. This commit adds an RPC to LOOKUPD to make sure the device exists. If it does, the DI is used when forwarding the event to the front-end (since front-ends can't use device names.) (commit f2a043c3)

#3 Updated by Richard Neswold almost 3 years ago

Rich rebuilt and installed the new DPM code. Although Charlie tested on the development node, we don't want to update the live system completely. The DPM on CLX25 has been restarted with the new code so Brian can also verify its operation.

#4 Updated by Charles King almost 3 years ago

  • Status changed from Feedback to Closed

Charlie updated DPM to always send the source device of a state event to the lookup service in order to get the device index to send down to the front end (f2a043c3). It also verifies that the source device is owned by the STATE front end (fcd8d2e9)

Also available in: Atom PDF