You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-user@db.apache.org by Sunitha Kambhampati <ks...@gmail.com> on 2006/09/15 21:25:58 UTC

Re: Problem: Communication Link Failure/ derby.drda.timeSlice

Hannes Grund wrote:

>Dear all, 
>
>I'm using the Derby-10.1.3.1 package on a Suse 9.1 Machine, 
>for certain reasons, I want the Derby-NetworkServer to run in 
>the same VM as any clients accessing the database (are there any 
>problems related to that particular setup ?), the database 
>is accessed using the "org.apache.derby.jdbc.ClientDriver"-
>driver.
>
>However, I have the following problem, when setting the 
>"derby.drda.timeSlice" to any non-zero value, any attempt to 
>connect to causes the accessing client to throw the following 
>exception (when setting timeSlice to zero everything works fine): 
>
>org.apache.derby.client.am.DisconnectException: A communication error has been detected. Communication protocol being 
>
I tried the derby.drda.timeSlice property when starting the server  and 
I also hit this issue and other communication errors...
I have opened a jira issue for this bug: 
http://issues.apache.org/jira/browse/DERBY-1856

Thanks,
Sunitha.