I've seen this when you leave a socket open and idle for a long time. The
connection times out.
It could be the situation ... any idea about the solution?I create the pool
once at startup and rely on this ...
Perhaps you use wrong transport in Thrift. Which version of cassandra you use?
Reconnect and try again?
On Jan 23, 2011, at 10:47 AM, cbert...@libero.it cbert...@libero.it wrote:
I've seen this when you leave a socket open and idle for a long time. The
connection times out.
It could be the situation ... any idea about the solution?
I create the pool once at
Reconnect and try again?
Sorry what do you mean by Reconnect and try again? -- You mean to shut down
the old pool and create a new pool of connections?I don't have the possibility
to handle the single connection using Pelops ...
From Dominic Williams Blog
To work with a Cassandra cluster, you
This is a known issue with the Cassandra 0.6 versions of Pelops. The issue
was fixed in the 0.7 based versions a few months ago but never back-ported
(Dominic, myself and the other contributors don't run 0.6)...
On 24 January 2011 05:25, cbert...@libero.it cbert...@libero.it wrote:
Reconnect