A java service client app reported getting this error message. Initially, I thought of it as a C* emitting the error back to the client. But searching the C* logs (system/gc/debug) for 'queue full' or some variation of it returned zero instances. I have seen some log snippets on the web where [CassandraDaemon.java:78] emits such error.
But, I have also read about java clients returning this error without interacting with C* or any other DBMS system. Further research showed that Java has a queueing interface as part of java.util package and when using class ThreadPoolExecutor. Java can use queueing interface natively e.g. logging facility of explicitly if the developer invokes such queue interface. Some users reported resolving the error by adjusting parameter like queue-capacity & pool-size. These appear to be associated with the abve class. I have not seen them as tunable C* parameters. Have you seen such errors for java clients interacting with C*? Any ideas on how to narrow the source of the error down? ---------------------------------------- Thank you
