-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ISSUE-5334 Disconnection: the distributed way #1473
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks overall good!
...ckend/data/data-rabbitmq/src/main/java/com/linagora/tmail/DisconnectorRequestSerializer.java
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we have a small test suite with 2 distributed disconnectors>
IE
GIVEN bob connected on A
WHEN I ask B to disconnect bob
THEN bob is well disconnected
GIVEN bob connected on A and B
WHEN I ask B to disconnect bob
THEN bob is well disconnected on both...
I can't start 2
|
I think the test case |
Regarding the "javax.management.InstanceAlreadyExistsException" error #1473 (comment) We cannot disable An alternative is to use tmail docker for testing (similar to the deployment-test module), but I think it is not suitable for the deployment module. |
...ackend/data/data-rabbitmq/src/main/java/com/linagora/tmail/RabbitMQDisconnectorOperator.java
Show resolved
Hide resolved
An alternative is to write unit tests only for the component you need. |
resolve linagora/james-project#5334
Require
Todo