Connection authentication failure occurred. Reason: Invalid authentication..

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Connection authentication failure occurred. Reason: Invalid authentication..

Peter Ondruška-4
Hello,

I am facing strange situation with 10.13.1.1. This error is logged when load against Derby is higher than usuall:

*******************************************
Mon May 29 08:31:10 CEST 2017 Thread[DRDAConnThread_27,5,main] (XID = 74907526), (SESSIONID = 22748), (DATABASE = /*removed*/), (DRDAID = ��������.����-43515881796
1723857{1069}), Cleanup action starting
java.sql.SQLNonTransientConnectionException: Connection authentication failure occurred.  Reason: Invalid authentication..
        at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
        at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
        at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)
        at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)
        at org.apache.derby.impl.jdbc.EmbedConnection.newSQLException(Unknown Source)
        at org.apache.derby.impl.jdbc.EmbedConnection.checkUserCredentials(Unknown Source)
        at org.apache.derby.impl.jdbc.EmbedConnection.<init>(Unknown Source)
        at org.apache.derby.jdbc.InternalDriver$1.run(Unknown Source)
        at org.apache.derby.jdbc.InternalDriver$1.run(Unknown Source)
        at java.security.AccessController.doPrivileged(AccessController.java:650)
        at org.apache.derby.jdbc.InternalDriver.getNewEmbedConnection(Unknown Source)
        at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source)
        at org.apache.derby.jdbc.BasicEmbeddedDataSource40.getConnection(Unknown Source)
        at org.apache.derby.jdbc.EmbedPooledConnection.openRealConnection(Unknown Source)
        at org.apache.derby.jdbc.EmbedXAConnection.getRealConnection(Unknown Source)
        at org.apache.derby.iapi.jdbc.BrokeredConnection.getRealConnection(Unknown Source)
        at org.apache.derby.iapi.jdbc.BrokeredConnection.isClosed(Unknown Source)
        at org.apache.derby.impl.drda.PiggyBackedSessionData.getInstance(Unknown Source)
        at org.apache.derby.impl.drda.Database.getPiggyBackedSessionData(Unknown Source)
        at org.apache.derby.impl.drda.DRDAConnThread.writePBSD(Unknown Source)
        at org.apache.derby.impl.drda.DRDAConnThread.processCommands(Unknown Source)
        at org.apache.derby.impl.drda.DRDAConnThread.run(Unknown Source)
Caused by: ERROR 08004: Connection authentication failure occurred.  Reason: Invalid authentication..
        at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
        at org.apache.derby.impl.jdbc.SQLExceptionFactory.wrapArgsForTransportAcrossDRDA(Unknown Source)
        ... 22 more
============= begin nested exception, level (1) ===========
ERROR 08004: Connection authentication failure occurred.  Reason: Invalid authentication..
        at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
        at org.apache.derby.impl.jdbc.SQLExceptionFactory.wrapArgsForTransportAcrossDRDA(Unknown Source)
        at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
        at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
        at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)
        at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)
        at org.apache.derby.impl.jdbc.EmbedConnection.newSQLException(Unknown Source)
        at org.apache.derby.impl.jdbc.EmbedConnection.checkUserCredentials(Unknown Source)
        at org.apache.derby.impl.jdbc.EmbedConnection.<init>(Unknown Source)
        at org.apache.derby.jdbc.InternalDriver$1.run(Unknown Source)
        at org.apache.derby.jdbc.InternalDriver$1.run(Unknown Source)
        at java.security.AccessController.doPrivileged(AccessController.java:650)
        at org.apache.derby.jdbc.InternalDriver.getNewEmbedConnection(Unknown Source)
        at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source)
        at org.apache.derby.jdbc.BasicEmbeddedDataSource40.getConnection(Unknown Source)
        at org.apache.derby.jdbc.EmbedPooledConnection.openRealConnection(Unknown Source)
        at org.apache.derby.jdbc.EmbedXAConnection.getRealConnection(Unknown Source)
        at org.apache.derby.iapi.jdbc.BrokeredConnection.getRealConnection(Unknown Source)
        at org.apache.derby.iapi.jdbc.BrokeredConnection.isClosed(Unknown Source)
        at org.apache.derby.impl.drda.PiggyBackedSessionData.getInstance(Unknown Source)
        at org.apache.derby.impl.drda.Database.getPiggyBackedSessionData(Unknown Source)
        at org.apache.derby.impl.drda.DRDAConnThread.writePBSD(Unknown Source)
        at org.apache.derby.impl.drda.DRDAConnThread.processCommands(Unknown Source)
        at org.apache.derby.impl.drda.DRDAConnThread.run(Unknown Source)
============= end nested exception, level (1) ===========
Cleanup action completed
*******************************************

This is running network server with -Dderby.authentication.native.passwordLifetimeMillis=0 just to be sure but it has no influence. All the connections are pool from Payara/Glassfish with ClientXADataSource and therefore it is strange that I see mentions of Embedded in the trace. And there are no messages from Payara about failed authentications.

Any ideas? :)

--
Peter Ondruška

kaibo, s.r.o., ID 28435036, registered with the commercial register administered by the Municipal Court in Prague, section C, insert 141269.
Registered office and postal address: kaibo, s.r.o., Kališnická 379/10, Prague 3, 130 00, Czech Republic.
https://www.kaibo.eu
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Connection authentication failure occurred. Reason: Invalid authentication..

Rick Hillegas-3
Hi Peter,

This is the error which Derby raises when the user presents invalid credentials at connection time. Are you confident that correct credentials were given? Are the NATIVE credentials stored in the database being connected to? Or are they stored in a system-wide credentials database? What other errors appear in the diagnostic log prior to this error?

Thanks,
-Rick

On 5/29/17 12:12 AM, Peter Ondruška wrote:
Hello,

I am facing strange situation with 10.13.1.1. This error is logged when load against Derby is higher than usuall:

*******************************************
Mon May 29 08:31:10 CEST 2017 Thread[DRDAConnThread_27,5,main] (XID = 74907526), (SESSIONID = 22748), (DATABASE = /*removed*/), (DRDAID = ��������.����-43515881796
1723857{1069}), Cleanup action starting
java.sql.SQLNonTransientConnectionException: Connection authentication failure occurred.  Reason: Invalid authentication..
        at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
        at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
        at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)
        at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)
        at org.apache.derby.impl.jdbc.EmbedConnection.newSQLException(Unknown Source)
        at org.apache.derby.impl.jdbc.EmbedConnection.checkUserCredentials(Unknown Source)
        at org.apache.derby.impl.jdbc.EmbedConnection.<init>(Unknown Source)
        at org.apache.derby.jdbc.InternalDriver$1.run(Unknown Source)
        at org.apache.derby.jdbc.InternalDriver$1.run(Unknown Source)
        at java.security.AccessController.doPrivileged(AccessController.java:650)
        at org.apache.derby.jdbc.InternalDriver.getNewEmbedConnection(Unknown Source)
        at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source)
        at org.apache.derby.jdbc.BasicEmbeddedDataSource40.getConnection(Unknown Source)
        at org.apache.derby.jdbc.EmbedPooledConnection.openRealConnection(Unknown Source)
        at org.apache.derby.jdbc.EmbedXAConnection.getRealConnection(Unknown Source)
        at org.apache.derby.iapi.jdbc.BrokeredConnection.getRealConnection(Unknown Source)
        at org.apache.derby.iapi.jdbc.BrokeredConnection.isClosed(Unknown Source)
        at org.apache.derby.impl.drda.PiggyBackedSessionData.getInstance(Unknown Source)
        at org.apache.derby.impl.drda.Database.getPiggyBackedSessionData(Unknown Source)
        at org.apache.derby.impl.drda.DRDAConnThread.writePBSD(Unknown Source)
        at org.apache.derby.impl.drda.DRDAConnThread.processCommands(Unknown Source)
        at org.apache.derby.impl.drda.DRDAConnThread.run(Unknown Source)
Caused by: ERROR 08004: Connection authentication failure occurred.  Reason: Invalid authentication..
        at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
        at org.apache.derby.impl.jdbc.SQLExceptionFactory.wrapArgsForTransportAcrossDRDA(Unknown Source)
        ... 22 more
============= begin nested exception, level (1) ===========
ERROR 08004: Connection authentication failure occurred.  Reason: Invalid authentication..
        at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
        at org.apache.derby.impl.jdbc.SQLExceptionFactory.wrapArgsForTransportAcrossDRDA(Unknown Source)
        at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
        at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
        at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)
        at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)
        at org.apache.derby.impl.jdbc.EmbedConnection.newSQLException(Unknown Source)
        at org.apache.derby.impl.jdbc.EmbedConnection.checkUserCredentials(Unknown Source)
        at org.apache.derby.impl.jdbc.EmbedConnection.<init>(Unknown Source)
        at org.apache.derby.jdbc.InternalDriver$1.run(Unknown Source)
        at org.apache.derby.jdbc.InternalDriver$1.run(Unknown Source)
        at java.security.AccessController.doPrivileged(AccessController.java:650)
        at org.apache.derby.jdbc.InternalDriver.getNewEmbedConnection(Unknown Source)
        at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source)
        at org.apache.derby.jdbc.BasicEmbeddedDataSource40.getConnection(Unknown Source)
        at org.apache.derby.jdbc.EmbedPooledConnection.openRealConnection(Unknown Source)
        at org.apache.derby.jdbc.EmbedXAConnection.getRealConnection(Unknown Source)
        at org.apache.derby.iapi.jdbc.BrokeredConnection.getRealConnection(Unknown Source)
        at org.apache.derby.iapi.jdbc.BrokeredConnection.isClosed(Unknown Source)
        at org.apache.derby.impl.drda.PiggyBackedSessionData.getInstance(Unknown Source)
        at org.apache.derby.impl.drda.Database.getPiggyBackedSessionData(Unknown Source)
        at org.apache.derby.impl.drda.DRDAConnThread.writePBSD(Unknown Source)
        at org.apache.derby.impl.drda.DRDAConnThread.processCommands(Unknown Source)
        at org.apache.derby.impl.drda.DRDAConnThread.run(Unknown Source)
============= end nested exception, level (1) ===========
Cleanup action completed
*******************************************

This is running network server with -Dderby.authentication.native.passwordLifetimeMillis=0 just to be sure but it has no influence. All the connections are pool from Payara/Glassfish with ClientXADataSource and therefore it is strange that I see mentions of Embedded in the trace. And there are no messages from Payara about failed authentications.

Any ideas? :)

--
Peter Ondruška

kaibo, s.r.o., ID 28435036, registered with the commercial register administered by the Municipal Court in Prague, section C, insert 141269.
Registered office and postal address: kaibo, s.r.o., Kališnická 379/10, Prague 3, 130 00, Czech Republic.
https://www.kaibo.eu


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Connection authentication failure occurred. Reason: Invalid authentication..

Peter Ondruška-4
Dear Rick,

well, that is why it is strange because I am very certain I use correct username and password to connect and the data from database can be accessed. Yes, NATIVE credentials are stored in the database itself. There are no other errors or warnings besides this one.

Peter

On 29 May 2017 at 19:26, Rick Hillegas <[hidden email]> wrote:
Hi Peter,

This is the error which Derby raises when the user presents invalid credentials at connection time. Are you confident that correct credentials were given? Are the NATIVE credentials stored in the database being connected to? Or are they stored in a system-wide credentials database? What other errors appear in the diagnostic log prior to this error?

Thanks,
-Rick


On 5/29/17 12:12 AM, Peter Ondruška wrote:
Hello,

I am facing strange situation with 10.13.1.1. This error is logged when load against Derby is higher than usuall:

*******************************************
Mon May 29 08:31:10 CEST 2017 Thread[DRDAConnThread_27,5,main] (XID = 74907526), (SESSIONID = 22748), (DATABASE = /*removed*/), (DRDAID = ��������.����-43515881796
1723857{1069}), Cleanup action starting
java.sql.SQLNonTransientConnectionException: Connection authentication failure occurred.  Reason: Invalid authentication..
        at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
        at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
        at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)
        at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)
        at org.apache.derby.impl.jdbc.EmbedConnection.newSQLException(Unknown Source)
        at org.apache.derby.impl.jdbc.EmbedConnection.checkUserCredentials(Unknown Source)
        at org.apache.derby.impl.jdbc.EmbedConnection.<init>(Unknown Source)
        at org.apache.derby.jdbc.InternalDriver$1.run(Unknown Source)
        at org.apache.derby.jdbc.InternalDriver$1.run(Unknown Source)
        at java.security.AccessController.doPrivileged(AccessController.java:650)
        at org.apache.derby.jdbc.InternalDriver.getNewEmbedConnection(Unknown Source)
        at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source)
        at org.apache.derby.jdbc.BasicEmbeddedDataSource40.getConnection(Unknown Source)
        at org.apache.derby.jdbc.EmbedPooledConnection.openRealConnection(Unknown Source)
        at org.apache.derby.jdbc.EmbedXAConnection.getRealConnection(Unknown Source)
        at org.apache.derby.iapi.jdbc.BrokeredConnection.getRealConnection(Unknown Source)
        at org.apache.derby.iapi.jdbc.BrokeredConnection.isClosed(Unknown Source)
        at org.apache.derby.impl.drda.PiggyBackedSessionData.getInstance(Unknown Source)
        at org.apache.derby.impl.drda.Database.getPiggyBackedSessionData(Unknown Source)
        at org.apache.derby.impl.drda.DRDAConnThread.writePBSD(Unknown Source)
        at org.apache.derby.impl.drda.DRDAConnThread.processCommands(Unknown Source)
        at org.apache.derby.impl.drda.DRDAConnThread.run(Unknown Source)
Caused by: ERROR 08004: Connection authentication failure occurred.  Reason: Invalid authentication..
        at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
        at org.apache.derby.impl.jdbc.SQLExceptionFactory.wrapArgsForTransportAcrossDRDA(Unknown Source)
        ... 22 more
============= begin nested exception, level (1) ===========
ERROR 08004: Connection authentication failure occurred.  Reason: Invalid authentication..
        at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
        at org.apache.derby.impl.jdbc.SQLExceptionFactory.wrapArgsForTransportAcrossDRDA(Unknown Source)
        at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
        at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
        at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)
        at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)
        at org.apache.derby.impl.jdbc.EmbedConnection.newSQLException(Unknown Source)
        at org.apache.derby.impl.jdbc.EmbedConnection.checkUserCredentials(Unknown Source)
        at org.apache.derby.impl.jdbc.EmbedConnection.<init>(Unknown Source)
        at org.apache.derby.jdbc.InternalDriver$1.run(Unknown Source)
        at org.apache.derby.jdbc.InternalDriver$1.run(Unknown Source)
        at java.security.AccessController.doPrivileged(AccessController.java:650)
        at org.apache.derby.jdbc.InternalDriver.getNewEmbedConnection(Unknown Source)
        at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source)
        at org.apache.derby.jdbc.BasicEmbeddedDataSource40.getConnection(Unknown Source)
        at org.apache.derby.jdbc.EmbedPooledConnection.openRealConnection(Unknown Source)
        at org.apache.derby.jdbc.EmbedXAConnection.getRealConnection(Unknown Source)
        at org.apache.derby.iapi.jdbc.BrokeredConnection.getRealConnection(Unknown Source)
        at org.apache.derby.iapi.jdbc.BrokeredConnection.isClosed(Unknown Source)
        at org.apache.derby.impl.drda.PiggyBackedSessionData.getInstance(Unknown Source)
        at org.apache.derby.impl.drda.Database.getPiggyBackedSessionData(Unknown Source)
        at org.apache.derby.impl.drda.DRDAConnThread.writePBSD(Unknown Source)
        at org.apache.derby.impl.drda.DRDAConnThread.processCommands(Unknown Source)
        at org.apache.derby.impl.drda.DRDAConnThread.run(Unknown Source)
============= end nested exception, level (1) ===========
Cleanup action completed
*******************************************

This is running network server with -Dderby.authentication.native.passwordLifetimeMillis=0 just to be sure but it has no influence. All the connections are pool from Payara/Glassfish with ClientXADataSource and therefore it is strange that I see mentions of Embedded in the trace. And there are no messages from Payara about failed authentications.

Any ideas? :)

--
Peter Ondruška

kaibo, s.r.o., ID 28435036, registered with the commercial register administered by the Municipal Court in Prague, section C, insert 141269.
Registered office and postal address: kaibo, s.r.o., Kališnická 379/10, Prague 3, 130 00, Czech Republic.
https://www.kaibo.eu





--
Peter Ondruška

kaibo, s.r.o., ID 28435036, registered with the commercial register administered by the Municipal Court in Prague, section C, insert 141269.
Registered office and postal address: kaibo, s.r.o., Kališnická 379/10, Prague 3, 130 00, Czech Republic.
https://www.kaibo.eu
Loading...