I have an established PTCP connection between two systems that has been running for some time. In order to leverage the ability to create watchlists using a tag query on the remote system, I added an extra tag using the fields in the PTCP Publisher. Once saved I expected to drop the connection with the remote system while the publisher restarted, but this lasted for 30 mins. When I deleted the extra tag the connection returned. Tested a few more time with the same result. Is this expected? - Thank you
Adding Extra tags via PTCP Publisher breaks connection
I wonder, are you using encryption?
I just did some testing and found I had no issue transmitting a tag of full size (255 characters for key, 255 for value) if I was not using encryption, but got what you described and an urgent event about decryption failed on the receiver side if I tried the same setup with encryption. I also recall an exchange with someone about how they were getting decryption failed events during their point syncs, and I found that turning down the max values per packet helped some. I suspect there are still some issues with the encryption for us to iron out. How large was the tag key / value you were trying to send?
No encryption on this today, but I have had it enabled at one point for testing. Key/Value were only 5 characters each.
I am seeing the following in the log on the publisher side, nothing on the receiving side.
ERROR 2018-06-15T10:53:26,837 (com.serotonin.m2m2.rt.publish.SendThread.run:59) - Send thread PersistentSenderRT.SendThread failed with an exception java.lang.UnsupportedOperationException: null at java.util.Collections$UnmodifiableMap.put(Collections.java:1457) ~[?:1.8.0_144] at com.serotonin.m2m2.persistent.pub.PersistentSendThread.openConnection(PersistentSendThread.java:586) ~[persistent-pub-ds-3.4.3.jar:?] at com.serotonin.m2m2.persistent.pub.PersistentSendThread.runImpl(PersistentSendThread.java:194) ~[persistent-pub-ds-3.4.3.jar:?] at com.serotonin.m2m2.rt.publish.SendThread.run(SendThread.java:56) [mango-3.4.4.jar:?]
Aha. I will have a fix for that out today. Thanks for bringing it to our attention.
Should be fixed with the publisher side on 3.4.4
Thank you, Phillip - Working now.