[
https://issues.apache.org/jira/browse/DERBY-6972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16277949#comment-16277949
]
Rick Hillegas commented on DERBY-6972:
--------------------------------------
I think that the root cause is this line near the end of the stack trace:
Caused by: java.net.SocketTimeoutException: Read timed out
I don't know why your socket activity is timing out. Is it possible that your
connection pool is setting a default login timeout which too short for your
network or machine load?
You may be able to tease more information out of the protocol layer by turning
on network tracing as described in the Server Administration Guide at
http://db.apache.org/derby/docs/10.14/adminguide/index.html
> Delay for getting derby connection (Connection Reset and Waiting for a
> connection)
> ----------------------------------------------------------------------------------
>
> Key: DERBY-6972
> URL: https://issues.apache.org/jira/browse/DERBY-6972
> Project: Derby
> Issue Type: Bug
> Components: Network Server
> Affects Versions: 10.11.1.1
> Reporter: Sridhar Jena
> Priority: Critical
>
> Hi Team,
> This is regarding a derby connection issue in network mode.
> We are using Apache derby in network mode. Below are the version we are using
> for client server communication,
> Client Jar Version : *derbyclient-10.13.1.1.jar*
> Server Version : * Apache Derby Network Server - 10.11.1.1*
> We are facing three types of connection issue while getting database
> connection from our java application.
> 1. A communications error has been detected: Connection reset
> 2. Waiting for a connection with a long period of time.
> 3. Error connecting to server 127.0.0.1 on port 1,527 with message connect
> timed out.
> At the same time if we are checking the derby.log in derby server, we found
> below exceptions,
> *Fri Oct 20 17:19:30 EDT 2017* Thread[DRDAConnThread_107,5,main] (DATABASE =
> null), (DRDAID = null), Execution failed because of a Distributed Protocol
> Error: DRDA_Proto_SYNTAXRM; CODPNT arg = 0; Error Code Value = 3. Plaintext
> connection attempt from an SSL enabled client?
> *Fri Oct 20 17:19:30 EDT 2017* : Execution failed because of a Distributed
> Protocol Error: DRDA_Proto_SYNTAXRM; CODPNT arg = 0; Error Code Value = 3.
> Plaintext connection attempt from an SSL enabled client?
> org.apache.derby.impl.drda.DRDAProtocolException: Execution failed because of
> a Distributed Protocol Error: DRDA_Proto_SYNTAXRM; CODPNT arg = 0; Error
> Code Value = 3. Plaintext connection attempt from an SSL enabled client?
> at org.apache.derby.impl.drda.DRDAConnThread.throwSyntaxrm(Unknown
> Source)
> at org.apache.derby.impl.drda.DDMReader.readDssHeader(Unknown Source)
> at
> org.apache.derby.impl.drda.DRDAConnThread.exchangeServerAttributes(Unknown
> Source)
> at
> org.apache.derby.impl.drda.DRDAConnThread.sessionInitialState(Unknown Source)
> at org.apache.derby.impl.drda.DRDAConnThread.run(Unknown Source)
> We have no idea about the above Exceptions why it is coming while getting
> connection in java client application.
> Could you please help us to identify the exact reason for the above problem.
> Thanks & Regards,
> Sridhar Jena
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
