# Ignition OPC Client open Two Session connection to PLC Siemens 1500 **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [February 7, 2024, 10:32pm UTC](https://forum.inductiveautomation.com/t/ignition-opc-client-open-two-session-connection-to-plc-siemens-1500/85412 "2024-02-07T22:32:19Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Yousef\_Ali](https://avatars.discourse-cdn.com/v4/letter/y/87869e/32.png) [@Yousef\_Ali](https://forum.inductiveautomation.com/u/Yousef_Ali)\ **Post date:** [February 7, 2024, 10:32pm UTC](https://forum.inductiveautomation.com/t/ignition-opc-client-open-two-session-connection-to-plc-siemens-1500/85412/1 "2024-02-07T22:32:19Z")
Hi @Kevin.Herron I have different PLCs S7-1500 connected to Ignition Gateway , i noticed Ignition GW one PLC opens two sessions of connection to PLC . i delete the connection twice and still same issue . Both session getting same EndpointUrl came from same Server with same name only the last numbers are different as showing in snapshoot Rest of PLC is working fine, Only one session per PLC connection . This cause issue in data quality as some of these data showing bad quality with error `Bad_TooManyMonitoredItems: The request could not be processed because there are too many monitored items in the subscription.` any guidance for troubleshooting ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/3/b3a9f28bd88ca8d4b2311bac4ecb771bef8c59be.png) Noticed also both sessions had same applicationuri ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/6/56ca1600c75f269a6323991c022e4903cdcf8dd0.png) ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [February 7, 2024, 10:42pm UTC](https://forum.inductiveautomation.com/t/ignition-opc-client-open-two-session-connection-to-plc-siemens-1500/85412/2 "2024-02-07T22:42:59Z")
Disable the connection and see if both sessions disappear. You can use UaExpert to view that server's diagnostics. Make sure you don't have another Ignition gateway that's e.g. running a backup of this one that is also making a connection. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [February 7, 2024, 10:45pm UTC](https://forum.inductiveautomation.com/t/ignition-opc-client-open-two-session-connection-to-plc-siemens-1500/85412/3 "2024-02-07T22:45:42Z")
BTW, those numbers Ignition uses in the session name are timestamps. In your case, one session is significantly older: ```auto jshell> new Date(1707217324900L) $1 ==> Tue Feb 06 03:02:04 PST 2024 jshell> new Date(1707344060550L) $2 ==> Wed Feb 07 14:14:20 PST 2024 ``` ---
**Author:** ![Yousef\_Ali](https://avatars.discourse-cdn.com/v4/letter/y/87869e/32.png) [@Yousef\_Ali](https://forum.inductiveautomation.com/u/Yousef_Ali)\ **Post date:** [February 7, 2024, 10:55pm UTC](https://forum.inductiveautomation.com/t/ignition-opc-client-open-two-session-connection-to-plc-siemens-1500/85412/4 "2024-02-07T22:55:29Z")
Disable connection from Gateway . one session disappeared and other session sttil valid ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/6/f678c92f5eb485c5f3093a2b6db84485bc558421.png) ```auto jshell> new Date(1707217324900L) $1 ==> Tue Feb 06 03:02:04 PST 2024 ``` ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [February 7, 2024, 10:56pm UTC](https://forum.inductiveautomation.com/t/ignition-opc-client-open-two-session-connection-to-plc-siemens-1500/85412/5 "2024-02-07T22:56:39Z")
Is there another Gateway running? Is this part of a redundant pair? ---
**Author:** ![Yousef\_Ali](https://avatars.discourse-cdn.com/v4/letter/y/87869e/32.png) [@Yousef\_Ali](https://forum.inductiveautomation.com/u/Yousef_Ali)\ **Post date:** [February 7, 2024, 10:59pm UTC](https://forum.inductiveautomation.com/t/ignition-opc-client-open-two-session-connection-to-plc-siemens-1500/85412/6 "2024-02-07T22:59:46Z")
i was part of a Redundant but now main gateway running as an independent Gateway . Rest of PLC was connected as well before ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [February 7, 2024, 11:01pm UTC](https://forum.inductiveautomation.com/t/ignition-opc-client-open-two-session-connection-to-plc-siemens-1500/85412/7 "2024-02-07T23:01:43Z")
If the backup gateway is still running then it would have a connection. The default session lifetime is only 2 minutes. There's either a bug causing an orphaned session or there's another Ignition gateway connected to it. If you shut down this gateway you know about and the other session doesn't disappear after a couple minutes (at most), then you definitely have another gateway running. ---
**Author:** ![Yousef\_Ali](https://avatars.discourse-cdn.com/v4/letter/y/87869e/32.png) [@Yousef\_Ali](https://forum.inductiveautomation.com/u/Yousef_Ali)\ **Post date:** [February 7, 2024, 11:03pm UTC](https://forum.inductiveautomation.com/t/ignition-opc-client-open-two-session-connection-to-plc-siemens-1500/85412/8 "2024-02-07T23:03:01Z")
Thanks, Kevin , i will update the outcome once back to IT team . ---
**Author:** ![Yousef\_Ali](https://avatars.discourse-cdn.com/v4/letter/y/87869e/32.png) [@Yousef\_Ali](https://forum.inductiveautomation.com/u/Yousef_Ali)\ **Post date:** [February 8, 2024, 3:19pm UTC](https://forum.inductiveautomation.com/t/ignition-opc-client-open-two-session-connection-to-plc-siemens-1500/85412/9 "2024-02-08T15:19:02Z")
This PLC add in redundant server by mistake. Thanks @Kevin.Herron