Problem: Communication Link Failure/ derby.drda.timeSlice

[Hannes Grund <hg...@gmx.de>]

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 used: Reply.fill(). Communication API being used: InputStream.read(). Location where the error was detected: insufficient data. Communication function detecting the error: *. Protocol specific error codes(s) TCP/IP SOCKETS 
	at org.apache.derby.client.net.NetAgent.throwCommunicationsFailure(Unknown Source)
	at org.apache.derby.client.net.Reply.fill(Unknown Source)
	at org.apache.derby.client.net.Reply.ensureALayerDataInBuffer(Unknown Source)
	at org.apache.derby.client.net.Reply.readDssHeader(Unknown Source)
	at org.apache.derby.client.net.Reply.startSameIdChainParse(Unknown Source)
	at org.apache.derby.client.net.NetConnectionReply.readExchangeServerAttributes(Unknown Source)
	at org.apache.derby.client.net.NetConnection.readServerAttributesAndKeyExchange(Unknown Source)
	at org.apache.derby.client.net.NetConnection.flowServerAttributesAndKeyExchange(Unknown Source)
	at org.apache.derby.client.net.NetConnection.flowUSRIDPWDconnect(Unknown Source)
	at org.apache.derby.client.net.NetConnection.flowConnect(Unknown Source)
	at org.apache.derby.client.net.NetConnection.<init>(Unknown Source)
	at org.apache.derby.jdbc.ClientDriver.connect(Unknown Source)
	at java.sql.DriverManager.getConnection(DriverManager.java:512)
	at java.sql.DriverManager.getConnection(DriverManager.java:171)
	at 
.... [SNIP] 

This seems to be independent of any other settings (like maxThreads, minThreads, keepAlive .. etc)

Any help or reference is highly appreciated, 

best regards, 

  Hannes Grund






-- 


Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer

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

[Sunitha Kambhampati <ks...@gmail.com>]

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.