I have noticed some odd behavior in Ignition Gateway v7.6.3, running on Server 2008 R2.
I have a project with 10 transaction groups in it. It is running on several systems and I frequently make updates to one, export it and import it on another system. This works fine for the Vision elements. However, I am noticing that the Status page on the Gateway web interface shows too many transaction groups are active. It seems to add 10 each time I upload the project.
The projects view on the Gateway web interface shows only the one project (I select the overwrite option when uploading). If I open that project in Designer, it shows only the desired 10 transaction groups.
Is there any way to determine how many transaction groups are actually running? Who is right, the Gateway or Designer? I certainly don’t want multiple instances of a transaction group running simultaneously. These groups involve handshaking with triggers and multiple instances could definitely mess that up as well as causing duplicate entries in my databases.
Update - I’ve noticed the number of transaction groups goes back to 10 after I restart the Gateway. Refreshing the status display of the web interface is not sufficient to do it, I had to restart the Gateway service. This appears to be a bug with 7.6.3.
Unfortunately it does look like there’s a bug with this right now. When you upload a project over an existing one, the group gets replaced in the internal database, and the new version started, but the previous group is not correctly shut down.
We will fix this for 7.6.5. However, in the mean time, the best route is to delete the existing project before uploading the modified one, instead of just overwriting it.
I will delete first and then upload in the future. For the gateways that are exhibiting this problem, the transaction count in the status view looks OK after a gateway restart. Is a gateway restart sufficient, or are there other steps I need to take to make sure the “old” transaction groups get shutdown?
Restarting is fine, the internal database is being updated correctly, just not the running projects.