Maxcube inaccessible?

[mstormi (Markus Storm)]

Since a couple of OH snapshot(s), my Maxcube has become inaccessible.
It’s up and running (do can access the MAX! java/web interface) and so is the maxcube binding.
But the OH thing is offline (configured using exclusive mode, default poll interval 30 seconds).
Debugging shows OH can connect and maxcube is receiving messages .

Any ideas ?

[hmerk (Hans-Jörg Merk)]

Did you see this post

MaxCubeBridgeHandler - IO error occurred during execution: Read timed out

Hi all, after I updated to the latest snapshot 2.4.0.20180726171757-1 tonight I found that connectivity to my MAX!Cubes is no longer working . I see the following warnings in the logs and no data at all is gathered from the cubes anymore. 2018-07-26 23:08:39.318 [WARN ] [nternal.handler.MaxCubeBridgeHandler] - IO error occurred during execution: Read timed out 2018-07-26 23:08:39.324 [WARN ] [nternal.handler.MaxCubeBridgeHandler] - IO error occurred during execution: Read timed out…

Might be the same issue

[mstormi (Markus Storm)]

thanks for pointing me there. Yes it’s apparently the same issue.

[vzorglub (Vincent Regaud)]

@mstormi
Hi Markus
Is this issue solved?

[mstormi (Markus Storm)]

Yes, since a couple of snapshots. You eventually have to redo your things.