

19:28, EEST

August 21, 2024

Hello,
I have a client that is connected to the Prosys Simulator. However, when the channel lifetime of the connection expires, Instead of renewing the token, the channel is closed. Prosys does not perform the token renewal. I am confident this is not an issue with the client because it works correctly with a simple Python simulator. Nevertheless, I need to use Prosys since it supports certificates.
In this scenario, I am attempting a basic connection to the Simulator with no Security Policy and no Message security. Despite this, the connection still fails.
Currently, I am using the following settings:
– channel-lifetime = 120,000
– session-timeout = 30,000
Do you have any suggestions on how to enable token renewal?
Additionally, is it possible to enable more detailed logs in `.prosysopc/prosys-opc-ua-simulation-server/log`? I would like to have access to all logs with more detailed information if possible.
Thank you very much for your assistance!
Best regards,
Gustavo
9:27, EEST

Moderators
February 11, 2020

Hello,
Renewing SecureChannel token is initiated by the Client. Have you made sure that your Client is doing that at proper timing?
You can enable more logging by editing log4j2.xml file in .prosysopc/prosys-opc-ua-simulation-server folder. By default, it defines only Root logger that logs everything at INFO level like this “”. You can get more logging if you change the level from INFO to DEBUG or TRACE. Note, that there will be a lot more logging if you do change the logging level.
However, instead of changing the logging level, you could use Wireshark to capture traffic between your Client and Simulation Server and sent the logs to us to simulation-server-support@prosysopc.com. See https://prosysopc.com/blog/opc-ua-wireshark/ for instructions on how to capture OPC UA communication with Wireshark. If you’re running the applications on the same host, remember to select “Support loopback traffic” option when installing Wireshark.
Most Users Ever Online: 1919
Currently Online:
69 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
Heikki Tahvanainen: 402
hbrackel: 144
rocket science: 88
pramanj: 86
Francesco Zambon: 83
Ibrahim: 78
Sabari: 62
kapsl: 57
gjevremovic: 49
Xavier: 43
Member Stats:
Guest Posters: 0
Members: 793
Moderators: 7
Admins: 1
Forum Stats:
Groups: 3
Forums: 15
Topics: 1538
Posts: 6493
Newest Members:
sophiadavis, Waynegalse, Phillipbus, Oscarsat, WilliamJer, WilliamTunse, mvsjonah79, RaymondSmutt, Merlin AI pap, patlawrence98Moderators: Jouni Aro: 1027, Pyry: 1, Petri: 0, Bjarne Boström: 1037, Jimmy Ni: 26, Matti Siponen: 353, Lusetti: 0
Administrators: admin: 1