Skip to content
This repository has been archived by the owner on Sep 7, 2023. It is now read-only.

Processors don't properly reconnect to restarted readers #17

Open
RockinRoel opened this issue May 3, 2016 · 1 comment
Open

Processors don't properly reconnect to restarted readers #17

RockinRoel opened this issue May 3, 2016 · 1 comment
Labels
bug

Comments

@RockinRoel
Copy link
Collaborator

Currently, the processor needs to be restarted if a reader has restarted for some reason. It's no problem to do this restart, but it should be able to automatically reconnect to a reader.
@RockinRoel RockinRoel added the bug label May 3, 2016
@RockinRoel RockinRoel added this to the 24 urenloop 2016 milestone May 3, 2016
@RockinRoel RockinRoel removed this from the 24 urenloop 2016 milestone Oct 26, 2016
@RockinRoel
Copy link
Collaborator Author

24 urenloop 2016 milestone was missed, new milestone is 10 urenloop maybe?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug
Milestone
No milestone
Development

No branches or pull requests
1 participant
@RockinRoel