Jaroslaw Cwiklik wrote:
Jorn, the only thing that makes sense here is that the client is timing out while the service is still handling a CAS. Do you know if the client resends the same CAS after timeout?
The client always calls getCAS() before it calls sendCAS(), and it assumes that it gets a fresh CAS from getCAS().
I think I use the client API correctly, maybe that can happen if the client internally tries to send a CAS two times, maybe due a broker connection lost issue ... ?
The UIMA AS Service also stopped processing messages afterwards, but I am not
sure if that is related to the message. Jörn
