Client hangs indefinitely while synchronizing subscriptions #1536
Replies: 5 comments 12 replies
-
Wireshark capture and thread dumps may help. Can you run this in a debugger and step into the |
Beta Was this translation helpful? Give feedback.
-
dumped all threads, this one looks like its handling the task at hand - blocking @
|
Beta Was this translation helpful? Give feedback.
-
@peterfranciscook this should be fixed if you can build and test against a SNAPSHOT version from the latest commit. |
Beta Was this translation helpful? Give feedback.
-
Still hung =/ full thread dump
|
Beta Was this translation helpful? Give feedback.
-
@kevinherron I refuse to speculate as to reasons why, but the same jarfile built with milo 1.0.3-SNAPSHOT running on graalvm (graalvm-jdk-21.0.8+12.1) doesn't hang here! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
In this service/class, my first call to
OpcUaSubscription::synchronizeMonitoredItems
completes as expected.But after the service is running, an additional call (via the
subscribeToUdts
) method to eitherOpcUaSubscription::synchronizeMonitoredItems
orOpcUaSubscription::createMonitoredItems
hangs the client indefinitely.The last few log entries I see when this happens:
I do see a log message with the same PID during my first call to
synchronizeMonitoredItems
:DEBUG: id=37182249, createMonitoredItems partition.size(): 80
After the client is hung here, I can't perform a graceful shutdown with
OpcUaClient::disconnect
(spins indefinitely) orOpcUaClient::disconnectAsync
(throws or times out when I try to get or join the thread)I'm not sure what is happening - is this a milo bug or am I doing something wrong?
My subscription service code (method
subscribeToUdts
is where my second synchronization call is made):Beta Was this translation helpful? Give feedback.
All reactions