-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PVManager creates another subscription after each 'disconnect' #216
Comments
Older version of CSS uses caj-1.1.10.jar Updated current snapshot of CSS ('master'):
because setDoNotShareChannels() is not supported in caj-1.1.10.jar: Still getting a new subscription for each disconnect. What might be a hint: utility.pv used to clear() the subscription on disconnect. When the connection is re-established, it would again query for meta data and subscribe to the native data type. Looks like
|
https://github.com/ControlSystemStudio/cs-studio/blob/master/core/plugins/org.csstudio.utility.pvmanager.epics/src/org/epics/pvmanager/jca/JCAChannelHandler.java actually seems to add additional subscriptions on each re-connect for |
#337 lists related tests
If those tests pass, this issue should also be solved. |
Eric had asked if this issue still persists. Yes. I checked the 'master' sources just now.
With |
No, please leave it open until it is fixed. On Thu, Feb 6, 2014 at 11:37 AM, Eric Berryman notifications@github.comwrote:
|
To reproduce, run
softIoc
with this example database on one computer:On another computer, run two different versions of CSS 'probe' on those channels:
utility.pv
-based instance of CSS, like SNS 3.1.6, using one of the PVs.pvmanager
, using the other PV.The exact PVs don't matter. Different PVs are simply used to identify the CSS client on the IOC.
Disconnect the network cable, wait for probe to show disconnect, reconnect the network cable, wait for reconnect.
Repeat a few times.
On the IOC, check
casr 2
:==>
After 5 network disconnects, the older CSS instance based on
utility.pv
, which in this example monitored both the "ramp" and "wf" channels, keeps only one connection.The current CSS instance, based on
pvmanager
, which in this example only monitored the "wf" channel, creates a new subscription after each (re-)connection. In this example, it had 5 subscriptions.Duplicate channel subscriptions, especially for waveforms, can significantly increased the IOC CPU load after such network hickups to the point where the IOC becomes unresponsive.
The text was updated successfully, but these errors were encountered: