Receiving an Illegal Message ID Does Not Close the Transaction #16
Labels
No Label
client
server
user made
L
M
S
XL
bug
bugfix
discussion
documentation
feature
maintenance
postponed
refactoring
wontfix
No Milestone
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: zdm/envoy#16
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
When the server receives a message with an id that has already been assigned, it does handle it accordingly.
However, the current transaction is not getting closed resulting in a data blockage: No more objects can be written to the database.
This is malevolent in every way possible as it allows to crash the server by doing four simple things:
SIGKILL 15
)In order to ensure the continuation of the server, somehow the transaction should be closed. The easiest approach to this would be a
try-finally
block inside thePersistenceManager
, however many other ways are also possible.right side of the exception:
Receiving an Illegal Message Id Does Not Close the Transactionto Receiving an Illegal Message ID Does Not Close the Transaction