-
1. Re: CDI: bus reconnects after server crash, but no subscriptions
edewit Jul 10, 2013 7:18 AM (in response to michael_jank)Hi Michael,
To answer your question, no, this is not the expected behaviour expeted is that when the server is back online again communications is resumed. Can you create a small example project that shows the error, so we can easly reproduce the problem?
Cheers,
Erik Jan
-
2. Re: CDI: bus reconnects after server crash, but no subscriptions
michael_jank Jul 10, 2013 8:06 AM (in response to edewit)Hi Erik,
here an example, generated from the CDI archetype. I am using the tomcat profile for the build and have here the same effect as described above.
Thank you!
-
frontend.zip 128.4 KB
-
-
3. Re: CDI: bus reconnects after server crash, but no subscriptions
edewit Jul 10, 2013 10:30 AM (in response to michael_jank)Hi Michael,
Looking into it... I see that messages are being sent to the server from the client but the other way around. Is this the same behaviour that you have?
Cheers,
Erik Jan
-
4. Re: CDI: bus reconnects after server crash, but no subscriptions
michael_jank Jul 10, 2013 10:40 AM (in response to edewit)Hi Erik,
true, the events are still sent from the client to the server, but not from the server to the client. Thats the behaviour that I have.
Cheers,
Michael
-
5. Re: CDI: bus reconnects after server crash, but no subscriptions
michael_jank Jul 12, 2013 2:23 AM (in response to michael_jank)Meanwhile I realized that deferredSubscriptions in ClientMessageBusImpl is cleared on bus.stop(). Something which is handled differently in release 2.4 and 3.0. Might this be the reason?
Cheers,
Michael
-
6. Re: CDI: bus reconnects after server crash, but no subscriptions
edewit Jul 12, 2013 7:33 AM (in response to michael_jank)1 of 1 people found this helpfulThe problem with the 2.3.2 release is the way restart is handeld on the client side. It seems that this is already fixed in 2.4 and 3.0. Here after the bus stops and starts it still works, only a server restart is not handled we are looking into fixing that as well.
Cheers,
Erik Jan