[
https://issues.apache.org/jira/browse/DERBY-6972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276636#comment-16276636
]
Sridhar Jena commented on DERBY-6972:
-------------------------------------
Thanks Rick for the reply,
I was using "org.apache.derby.jdbc.ClientDriver" driver for connection pooling.
After updating the driver into
"org.apache.derby.jdbc.ClientConnectionPoolDataSource", now i am not getting
any connection reset issue.
But intermediately i am getting "Login timeout exceeded." while getting
connection from the ClientConnectionPoolDataSource.
java.sql.SQLTimeoutException: Login timeout exceeded.
at
org.apache.derby.client.am.SQLExceptionFactory.getSQLException(Unknown Source)
at org.apache.derby.client.am.SqlException.getSQLException(Unknown
Source)
at org.apache.derby.client.ClientPooledConnection.<init>(Unknown Source)
at
org.apache.derby.client.net.ClientJDBCObjectFactoryImpl.newClientPooledConnection(Unknown
Source)
at
org.apache.derby.jdbc.BasicClientDataSource40.getPooledConnectionX(Unknown
Source)
at
org.apache.derby.jdbc.BasicClientDataSource40.getPooledConnectionMinion(Unknown
Source)
at
org.apache.derby.jdbc.ClientConnectionPoolDataSource.getPooledConnection(Unknown
Source)
at
com.caucho.sql.DriverConfig.createPooledConnection(DriverConfig.java:665)
at
com.caucho.sql.ManagedConnectionImpl.initDriverConnection(ManagedConnectionImpl.java:268)
at
com.caucho.sql.ManagedConnectionImpl.<init>(ManagedConnectionImpl.java:147)
at
com.caucho.sql.ManagedFactoryImpl.createManagedConnection(ManagedFactoryImpl.java:153)
at
com.caucho.env.dbpool.ConnectionPool.createConnection(ConnectionPool.java:1006)
at
com.caucho.env.dbpool.ConnectionPool.allocatePoolConnection(ConnectionPool.java:848)
at
com.caucho.env.dbpool.ConnectionPool.allocateConnection(ConnectionPool.java:740)
at
com.caucho.env.dbpool.ConnectionPool.allocateConnection(ConnectionPool.java:714)
at com.caucho.sql.UserDataSource.getConnection(UserDataSource.java:75)
at com.caucho.sql.DBPool.getConnection(DBPool.java:808)
at
com.auruspay.database.ConnectionPoolObject.getPrimaryEmbeddedConnection(ConnectionPoolObject.java:783)
at
com.auruspay.database.AbstractAurusPayBaseDAO.getPrimaryEmbeddedConnection(AbstractAurusPayBaseDAO.java:84)
at
com.auruspay.database.transaction.TransactionDAOImpl.getDerbyliveConn(TransactionDAOImpl.java:3561)
at
com.auruspay.database.transaction.TransactionDAOImpl.insertProcessorToken(TransactionDAOImpl.java:2391)
at
com.auruspay.database.transaction.TransactionServiceImpl.insertProcessorToken(TransactionServiceImpl.java:143)
at
com.auruspay.manager.issuer.participants.IssuerDirPollParticipant.buildApprovalQuery(IssuerDirPollParticipant.java:842)
at
com.auruspay.manager.issuer.participants.IssuerDirPollParticipant.buildTransQuery(IssuerDirPollParticipant.java:172)
at
com.auruspay.manager.issuer.participants.IssuerDirPollParticipant.getTransQueryList(IssuerDirPollParticipant.java:138)
at
com.auruspay.manager.issuer.participants.IssuerDirPollParticipant.prepare(IssuerDirPollParticipant.java:94)
at
org.jpos.transaction.TransactionManager.prepare(TransactionManager.java:569)
at
org.jpos.transaction.TransactionManager.prepare(TransactionManager.java:635)
at
org.jpos.transaction.TransactionManager.run(TransactionManager.java:308)
at java.lang.Thread.run(Thread.java:745)
Caused by: ERROR XBDA0: Login timeout exceeded.
at org.apache.derby.client.net.NetConnection.handleLoginTimeout(Unknown
Source)
at org.apache.derby.client.net.NetConnection.flowConnect(Unknown Source)
at org.apache.derby.client.net.NetConnection.initialize(Unknown Source)
at org.apache.derby.client.net.NetConnection.<init>(Unknown Source)
at
org.apache.derby.client.net.ClientJDBCObjectFactoryImpl.newNetConnection(Unknown
Source)
... 28 more
Caused by: ERROR 08006: A communications error has been detected: Read timed
out.
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)
... 32 more
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
at java.net.SocketInputStream.read(SocketInputStream.java:170)
at java.net.SocketInputStream.read(SocketInputStream.java:141)
... 40 more
Could you please suggest why "ERROR XBDA0: Login timeout exceeded." is coming
intermediately and how to avoid this exception.
Thanks in advance.
> 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)
