Just submitted a bug which might be related:
https://issues.apache.org/jira/browse/WAVE-312
On Thu, Dec 15, 2011 at 15:34, Yuri Z wrote:
> Try to set the other thread counts to 1 as well. As I mentioned it doesn't
> solve the issue, but only reduces the probability.
>
> On Thu, Dec 15, 2011 at
Try to set the other thread counts to 1 as well. As I mentioned it doesn't
solve the issue, but only reduces the probability.
On Thu, Dec 15, 2011 at 4:19 PM, Vicente J. Ruiz Jurado wrote:
> Sadly, same problems with:
> listener_executor_thread_count = 1
> :-/ so, very often our deltas are lost
Sadly, same problems with:
listener_executor_thread_count = 1
:-/ so, very often our deltas are lost / not saved.
Bests,
--
Vicente
I just see your commit. Grat job (as usual) Yuri...
It seems like setting the LISTENER_EXECUTOR_THREAD_COUNT to value 1 instead
of 2 reduces probability of the issue to happen.
On Mon, Dec 5, 2011 at 6:16 PM, Yuri Z wrote:
> Yes, this is bug is annoying. I mean the "No conversations in
> this wave". The most nasty part is that I cannot reproduce
Yes, this is bug is annoying. I mean the "No conversations in
this wave". The most nasty part is that I cannot reproduce it in my dev
environment as well. This is not a new issue though, it happened also
before, but at lower frequency. Server restart fixes it.
My theory is that the "No conversatio
Hi there:
Since some weeks ago we are experimenting some exception randomly:
https://issues.apache.org/jira/browse/WAVE-307
(see RemoteWaveViewService.getServerVersion) that makes WIAB very
unstable/unusable because we cannot edit or reply some waves, or we lost
editions, or access to that wave wi
