Sadly, same problems with:
listener_executor_thread_count = 1
:-/ so, very often our deltas are lost / not saved.
Bests,
--
Vicente
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 v...@ourproject.org
wrote:
Sadly, same problems with:
listener_executor_thread_count = 1
:-/ so, very often
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 vega...@gmail.com 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,
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
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 conversations
