You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 14, 2019. It is now read-only.
I have a C-broker running and see that the broker is losing its connection to his downstream broker from a DGLux instance. Initially I suspected this to be an issue with DGLux but I have a second broker running with the dart implementation and there are no connection issues whatsoever over a period of 24h. Note that all brokers are running on the same machine.
Excerpt from the log (note there are dozens of reconnects over a period of ~24h):
...
2016-09-08 11:52:38 INFO [handshake] - DSLink `DGLuxInternalBroker-Pr8QZnE8tm7VBC8Y8h0x_1NYKF3mE4NZAZP2-4QvP2I` has connected
2016-09-08 11:55:34 INFO [broker] - DSLink `DGLuxInternalBroker-Pr8QZnE8tm7VBC8Y8h0x_1NYKF3mE4NZAZP2-4QvP2I` has disconnected
2016-09-08 11:55:38 INFO [broker] - DGLuxInternalBroker-Pr8QZnE8tm7VBC8Y8h0x_1NYKF3mE4NZAZP2-4QvP2I connecting
2016-09-08 11:55:38 INFO [handshake] - DSLink `DGLuxInternalBroker-Pr8QZnE8tm7VBC8Y8h0x_1NYKF3mE4NZAZP2-4QvP2I` has connected
2016-09-08 11:58:35 INFO [broker] - DSLink `DGLuxInternalBroker-Pr8QZnE8tm7VBC8Y8h0x_1NYKF3mE4NZAZP2-4QvP2I` has disconnected
2016-09-08 11:58:38 INFO [broker] - DGLuxInternalBroker-Pr8QZnE8tm7VBC8Y8h0x_1NYKF3mE4NZAZP2-4QvP2I connecting
2016-09-08 11:58:38 INFO [handshake] - DSLink `DGLuxInternalBroker-Pr8QZnE8tm7VBC8Y8h0x_1NYKF3mE4NZAZP2-4QvP2I` has connected
2016-09-08 12:01:35 INFO [broker] - DSLink `DGLuxInternalBroker-Pr8QZnE8tm7VBC8Y8h0x_1NYKF3mE4NZAZP2-4QvP2I` has disconnected
2016-09-08 12:01:38 INFO [broker] - DGLuxInternalBroker-Pr8QZnE8tm7VBC8Y8h0x_1NYKF3mE4NZAZP2-4QvP2I connecting
2016-09-08 12:01:38 INFO [handshake] - DSLink `DGLuxInternalBroker-Pr8QZnE8tm7VBC8Y8h0x_1NYKF3mE4NZAZP2-4QvP2I` has connected
2016-09-08 12:04:35 INFO [broker] - DSLink `DGLuxInternalBroker-Pr8QZnE8tm7VBC8Y8h0x_1NYKF3mE4NZAZP2-4QvP2I` has disconnected
2016-09-08 12:04:38 INFO [broker] - DGLuxInternalBroker-Pr8QZnE8tm7VBC8Y8h0x_1NYKF3mE4NZAZP2-4QvP2I connecting
2016-09-08 12:04:38 INFO [handshake] - DSLink `DGLuxInternalBroker-Pr8QZnE8tm7VBC8Y8h0x_1NYKF3mE4NZAZP2-4QvP2I` has connected
2016-09-08 12:07:35 INFO [broker] - DSLink `DGLuxInternalBroker-Pr8QZnE8tm7VBC8Y8h0x_1NYKF3mE4NZAZP2-4QvP2I` has disconnected
2016-09-08 12:07:38 INFO [broker] - DGLuxInternalBroker-Pr8QZnE8tm7VBC8Y8h0x_1NYKF3mE4NZAZP2-4QvP2I connecting
2016-09-08 12:07:38 INFO [handshake] - DSLink `DGLuxInternalBroker-Pr8QZnE8tm7VBC8Y8h0x_1NYKF3mE4NZAZP2-4QvP2I` has connected
2016-09-08 12:10:35 INFO [broker] - DSLink `DGLuxInternalBroker-Pr8QZnE8tm7VBC8Y8h0x_1NYKF3mE4NZAZP2-4QvP2I` has disconnected
2016-09-08 12:10:38 INFO [broker] - DGLuxInternalBroker-Pr8QZnE8tm7VBC8Y8h0x_1NYKF3mE4NZAZP2-4QvP2I connecting
2016-09-08 12:10:38 INFO [handshake] - DSLink `DGLuxInternalBroker-Pr8QZnE8tm7VBC8Y8h0x_1NYKF3mE4NZAZP2-4QvP2I` has connected
2016-09-08 12:13:35 INFO [broker] - DSLink `DGLuxInternalBroker-Pr8QZnE8tm7VBC8Y8h0x_1NYKF3mE4NZAZP2-4QvP2I` has disconnected
2016-09-08 12:13:38 INFO [broker] - DGLuxInternalBroker-Pr8QZnE8tm7VBC8Y8h0x_1NYKF3mE4NZAZP2-4QvP2I connecting
2016-09-08 12:13:38 INFO [handshake] - DSLink `DGLuxInternalBroker-Pr8QZnE8tm7VBC8Y8h0x_1NYKF3mE4NZAZP2-4QvP2I` has connected
2016-09-08 12:16:35 INFO [broker] - DSLink `DGLuxInternalBroker-Pr8QZnE8tm7VBC8Y8h0x_1NYKF3mE4NZAZP2-4QvP2I` has disconnected
2016-09-08 12:16:38 INFO [broker] - DGLuxInternalBroker-Pr8QZnE8tm7VBC8Y8h0x_1NYKF3mE4NZAZP2-4QvP2I connecting
2016-09-08 12:16:38 INFO [handshake] - DSLink `DGLuxInternalBroker-Pr8QZnE8tm7VBC8Y8h0x_1NYKF3mE4NZAZP2-4QvP2I` has connected
...
I have a C-broker running and see that the broker is losing its connection to his downstream broker from a DGLux instance. Initially I suspected this to be an issue with DGLux but I have a second broker running with the dart implementation and there are no connection issues whatsoever over a period of 24h. Note that all brokers are running on the same machine.
Excerpt from the log (note there are dozens of reconnects over a period of ~24h):
Setup:
The text was updated successfully, but these errors were encountered: