I am testing my own implementation of SparkplugB. While testing the Edge Node -> Primary host tests, my application does not react so quick (3 seconds apart from ONLINE <-> OFFLINE transitions).
In the source code PrimaryHostTest.java in the calls like below(all executorService.schedule(new Runnable() calls) I increased the time from 3 to 30.
executorService.schedule(new Runnable() {
@Override
public void run() {
hostOnlineAgain();
}
}, 3, TimeUnit.SECONDS);
In this case the TCK hangs and is unresponsive.
How can I increase the time to wait between ONLINE - OFFLINE transitions?
Why does the implementation need such a long delay? Processing a Primary Host online/offline is similar to handling a Node Control/Rebirth or a write. When the TCK hangs, does restarting the test restart the test?
What do you want to know?
I am testing my own implementation of SparkplugB. While testing the Edge Node -> Primary host tests, my application does not react so quick (3 seconds apart from ONLINE <-> OFFLINE transitions).
In the source code PrimaryHostTest.java in the calls like below(all executorService.schedule(new Runnable() calls) I increased the time from 3 to 30. executorService.schedule(new Runnable() { @Override public void run() { hostOnlineAgain(); } }, 3, TimeUnit.SECONDS);
In this case the TCK hangs and is unresponsive.
How can I increase the time to wait between ONLINE - OFFLINE transitions?
Is this related to a Sparkplug Listing request? If so, link the issue from https://github.com/eclipse-sparkplug/sparkplug.listings here.
No response
Version
3.0.0 (Default)
Accept EFTL Terms