Avatar

Please consider registering
guest

sp_LogInOut Log In sp_Registration Register

Register | Lost password?
sp_Search Search
Advanced Search
Advanced Search

— Forum Scope —




— Match —





— Forum Options —





Minimum search word length is 3 characters - maximum search word length is 84 characters

sp_Search Search
Go to Bottom
No permission to create posts
sp_Feed Topic RSS sp_TopicIcon
Prosys Token Renewal
August 21, 2024
19:28, EEST
Avatar
gustavo_schewinski
New Member
Members
Forum Posts: 1
Member Since:
August 21, 2024
sp_UserOfflineSmall Offline
Go to Top
1sp_EditHistory sp_Permalink sp_Print

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! Smile

Best regards,
Gustavo

August 22, 2024
9:27, EEST
Avatar
Matti Siponen
Moderator
Members

Moderators
Forum Posts: 337
Member Since:
February 11, 2020
sp_UserOfflineSmall Offline
Go to Top
2sp_Permalink sp_Print

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.

No permission to create posts
sp_Feed All RSS
Go to top
Forum Timezone: Europe/Helsinki

Most Users Ever Online: 518

Currently Online: iivanov
14 Guest(s)

Currently Browsing this Page:
1 Guest(s)

Top Posters:

Heikki Tahvanainen: 402

hbrackel: 142

pramanj: 86

rocket science: 85

Francesco Zambon: 83

Ibrahim: 78

Sabari: 62

kapsl: 57

gjevremovic: 49

Xavier: 43

Member Stats:

Guest Posters: 0

Members: 724

Moderators: 7

Admins: 1

Forum Stats:

Groups: 3

Forums: 15

Topics: 1496

Posts: 6353

Newest Members:

armandovarley, dole, rustyhammer, braydenaquino6, blaircleveland0, maribelkeeler7, Nicky, rickymeade2, niamhtoussaint0, adamq0505309

Moderators: Jouni Aro: 1017, Pyry: 1, Petri: 0, Bjarne Boström: 1003, Jimmy Ni: 26, Matti Siponen: 337, Lusetti: 0

Administrators: admin: 1