CDI: bus reconnects after server crash, but no subscriptions

[michael_jank]

Hello!

I am using Errai 2.3.2.Final on tomcat 7 with CDI, SimpleDispatcher and StandardAsyncServlet. Messaging client-server and server-client is working fine.

After a server crash the message bus is going back to online again as soon as the server restarts, but it is not possible to send messages from the client to the server or vice-versa anymore.

Meaning, a full recovery after a connection loss is not possible.

Is this expected to be working with CDI?

As the bus is going back online, I see the post messages

ConnectToQueue, RemoteSubscribe of ClientBus and ClientBusErrors, FinishStateSync (all of them to ServerBus) and AttachRemote to cdi.event:Dispatcher.

But I dont see the post messages RemoteSubscribe to cdi.event:Dispatcher for my communication messages, as I do see them at initial page load.

This seems to be the reason why the messaging is not working any more - the effect is both valid for websockets and long polling.

I already tried to do a bus.init() on busOffline message of the BusLifecycleListener or on a transport error message, but without success.

Cheers,

Michael

[edewit]

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

[michael_jank]

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!

[edewit]

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

[michael_jank]

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

[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

[edewit]

The 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