9:43, EEST
March 28, 2018
15:32, EEST
April 17, 2013
Hello,
Browsing for 40,000 references is a relatively big operation and it might take some time. If you don’t receive a specific error message, but instead the client application just becomes unresponsive, this means that the application is doing Browse and BrowseNext service calls and it will come responsive again later when the references have been read.
In other words, this is not necessarily a timeout issue. It may just take some time to read the references.
That being said, it would be better if the client would stay responsive while doing the requests. However, this is not the case currently.
As for the configuration parameters: you actually cannot change any parameters that are relevant in this case.
19:16, EEST
March 28, 2018
Thank you for the response.
Unfortunately I do not see any error being returned nor the logs any where. The client become responsive after some time but it doesn’t get any items in address space.
could you please help me with client trace or logs on which I can check for any errors as such?
Also could you comment on what’s the default timeout set for browsing in client or the client wait for unlimited time until it reads whole address space?
12:56, EEST
April 17, 2013
Hi,
Your report “The client become responsive after some time but it doesn’t get any items in address space” is exactly correct. This is the current behaviour if the browse service call timeouts. It would be better if the client would clearly report this timeout situation to the user. I’ll mark this up into our issue tracker.
The timeout value used by the Prosys OPC UA Client is 30 seconds.
By default, the client requests server to return 1000 references at a time until the whole 40k references are read. The client shouldn’t timeout unless fetching 1000 references takes longer than 30 seconds. In other words: the client could handle this situation more robustly but the server also seems to be very slow to return references.
There’s no logs that would show you the timeout error. Also, you cannot set the relevant parameters in the Prosys OPC UA Client.
In the end, I’d like to mention that we’re talking about a free testing application here. If you’d like to develop your own customized OPC UA client application, please download our Java based OPC UA SDK: https://prosysopc.com/products/opc-ua-java-sdk/
Most Users Ever Online: 1919
Currently Online:
17 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: 724
Moderators: 7
Admins: 1
Forum Stats:
Groups: 3
Forums: 15
Topics: 1526
Posts: 6457
Newest Members:
forrestdilke5, ernestoportus31, martin123, rickie5305, shaylamaggard4, rickyjuarez140, jonathonmcintyre, fannielima, kristiewinkle8, rustModerators: Jouni Aro: 1026, Pyry: 1, Petri: 0, Bjarne Boström: 1028, Jimmy Ni: 26, Matti Siponen: 346, Lusetti: 0
Administrators: admin: 1