Skip to content
This repository was archived by the owner on Feb 5, 2024. It is now read-only.
This repository was archived by the owner on Feb 5, 2024. It is now read-only.

Naming Service crashes when it tries to read a node that does not exist #6

@MoeweX

Description

@MoeweX

Log before crash:
DEBUG [16:27:32, 849] communication.AbstractReceiver - Received nodeID: N2
DEBUG [16:27:32, 849] communication.AbstractReceiver - Received message
DEBUG [16:27:33, 088] communication.AbstractReceiver - Received complete message, configID: N2
DEBUG [16:27:33, 088] communication.NamespaceReceiver - Interpreting message.
DEBUG [16:27:33, 272] namespace.Node - Reading node N2
DEBUG [16:27:33, 273] namespace.SystemEntity - Node N2 doesn't exist
ERROR [16:27:33, 275] model.JSONable - Could not translate json to model.config.NodeConfig
ERROR [16:27:33, 275] model.JSONable -

Problem occurs, when I send a message from a node that has not been recognized by the naming service before.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions