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
UaClient.connect call blocks all ports
August 28, 2024
18:32, EEST
Avatar
ivfa
Member
Members
Forum Posts: 9
Member Since:
October 21, 2019
sp_UserOfflineSmall Offline
Go to Top
1sp_Permalink sp_Print

Hey,
I have a problem with the client SDK running in a spring boot service in a kubernetes cluster.
The application creates one UaClient instance per server it connects to. The problem is that as soon as uaclient.connect() gets called for any of the instances, all ports of the service are blocked for the duration of the connect call. This leads to Spring Actuator Mectrics being not reachable when connect is not instant or fails, which leads to failed health checks. I really have no idea why this happens since the calls are executed in their own threads. I also cannot pinpoint to any change i have made or since when this is happening. SDK I am using is 5.2.2. I think we have had the problem since SDK 4.X,
Maybe anybody an idea?

Thanks

Best regards
FA

August 29, 2024
12:02, EEST
Avatar
Bjarne Boström
Moderator
Moderators
Forum Posts: 1003
Member Since:
April 3, 2012
sp_UserOfflineSmall Offline
Go to Top
2sp_Permalink sp_Print

Hi,

UaClient.connect by default does Read/Browse all Types from the server, which might take network and cpu resources. I’m not that familiar with kubernetes, but maybe that is enough to temporarily cause other activities to pause or slow down enough to cause a timeout for the Metrics (maybe there is a way to configure a larger “timeout” for it somehow?).

IF you do not have any custom Structures on the server(s) that you would need to read or write, you can also try to see if setting UaClient.setInitTypeDictionaryOnConnect(boolean) and UaClient.setInitTypeDictionaryAutoUsage(boolean) to false before calling connect changes anything. Note that as a result once you use any UaNodes there will be ~100 smaller calls to the server (compared to like ~5-10 larger ones that would have happened on connect; skipping over some details).

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

Most Users Ever Online: 518

Currently Online:
18 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