[
https://issues.apache.org/jira/browse/DERBY-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12626156#action_12626156
]
antodasana edited comment on DERBY-3848 at 8/27/08 9:27 AM:
-----------------------------------------------------------------
Just tried at different system with same results, although they are both Ubuntu
8.04.1 (2.6.24-19-generic). Not yet tried in Windows.
<<<<< COMMENT UPDATE 1 >>>>>
Works in Windows Home, java hotspot 1.6.0_04, derby 10.3.2.1 and 10.4.1.3.
<<<<< COMMENT UPDATE 2 >>>>>
Also working in Windows and java hotspot 1.6.0_07, derby 10.4.1.3. Unable to
test with java 1.6.0_06 in Windows.
NOTE: always testing using derby scripts at bin directory instead of jre call.
<<<<< COMMENT UPDATE 3 >>>>> <b>¡¡¡FOUND!!!</b>
OK, I think I got it. It works using jre instead of the scripts of the bin
distribution, exactly as Dag's script does. But previosly running
'setEmbeddedCP' did nothing so I had to explicitly set and export $CLASSPATH by
myself prior running the script.
So, it seems there must be something wrong that causes 'dblook' bin
distribution script not interacting well with my ubuntu operating system. The
first ubuntu I tried had derby installed at /usr/local as root and has months
installed; the second one is just installed and derby was user local installed.
I'm sorry I am not good with scripting, any ideas of what the problem might be?
was (Author: antodasana):
Just tried at different system with same results, although they are both
Ubuntu 8.04.1 (2.6.24-19-generic). Not yet tried in Windows.
<<<<< COMMENT UPDATE 1 >>>>>
Works in Windows Home, java hotspot 1.6.0_04, derby 10.3.2.1 and 10.4.1.3.
<<<<< COMMENT UPDATE 2 >>>>>
Also working in Windows and java hotspot 1.6.0_07, derby 10.4.1.3. Unable to
test with java 1.6.0_06 in Windows.
NOTE: always testing using derby scripts at bin directory instead of jre call.
> dblook fails to connect an authenticated database
> -------------------------------------------------
>
> Key: DERBY-3848
> URL: https://issues.apache.org/jira/browse/DERBY-3848
> Project: Derby
> Issue Type: Bug
> Components: Tools
> Affects Versions: 10.4.1.3
> Environment: [EMAIL PROTECTED]:~/temp/derby$ sysinfo
> ----------------- Información de Java ----------------
> Versión de Java: 1.6.0_06
> Proveedor de Java: Sun Microsystems Inc.
> Inicio Java: /usr/lib/jvm/java-6-sun-1.6.0.06/jre
> Classpath de Java:
> /usr/local/db-derby-10.4.1.3-bin/lib/derby.jar:/usr/local/db-derby-10.4.1.3-bin/lib/derbynet.jar:/usr/local/db-derby-10.4.1.3-bin/lib/derbytools.jar:/usr/local/db-derby-10.4.1.3-bin/lib/derbyclient.jar
> Nombre del SO: Linux
> Arquitectura del SO: i386
> Versión del SO: 2.6.24-19-generic
> Nombre usuario Java: antonio
> Dir. inicial usuario:/home/antonio
> Dir. usuario: /home/antonio/temp/derby
> java.specification.name: Java Platform API Specification
> java.specification.version: 1.6
> --------- Información de Derby --------
> JRE - JDBC: Java SE 6 - JDBC 4.0
> [/usr/local/db-derby-10.4.1.3-bin/lib/derby.jar] 10.4.1.3 - (648739)
> [/usr/local/db-derby-10.4.1.3-bin/lib/derbytools.jar] 10.4.1.3 - (648739)
> [/usr/local/db-derby-10.4.1.3-bin/lib/derbynet.jar] 10.4.1.3 - (648739)
> [/usr/local/db-derby-10.4.1.3-bin/lib/derbyclient.jar] 10.4.1.3 - (648739)
> ------------------------------------------------------
> -------------- Información de entorno local ----------
> Entorno local actual: [español/España [es_ES]]
> Se encontró soporte para el entorno local: [cs]
> versión: 10.4.1.3 - (648739)
> Se encontró soporte para el entorno local: [de_DE]
> versión: 10.4.1.3 - (648739)
> Se encontró soporte para el entorno local: [es]
> versión: 10.4.1.3 - (648739)
> Se encontró soporte para el entorno local: [fr]
> versión: 10.4.1.3 - (648739)
> Se encontró soporte para el entorno local: [hu]
> versión: 10.4.1.3 - (648739)
> Se encontró soporte para el entorno local: [it]
> versión: 10.4.1.3 - (648739)
> Se encontró soporte para el entorno local: [ja_JP]
> versión: 10.4.1.3 - (648739)
> Se encontró soporte para el entorno local: [ko_KR]
> versión: 10.4.1.3 - (648739)
> Se encontró soporte para el entorno local: [pl]
> versión: 10.4.1.3 - (648739)
> Se encontró soporte para el entorno local: [pt_BR]
> versión: 10.4.1.3 - (648739)
> Se encontró soporte para el entorno local: [ru]
> versión: 10.4.1.3 - (648739)
> Se encontró soporte para el entorno local: [zh_CN]
> versión: 10.4.1.3 - (648739)
> Se encontró soporte para el entorno local: [zh_TW]
> versión: 10.4.1.3 - (648739)
> ------------------------------------------------------
> Reporter: Antonio Sánchez
> Priority: Minor
> Attachments: dblook.log, derby.log, test.sh
>
>
> dblook is not connecting an authenticated database.
> I create an authenticated database this way:
> 1. ij
> 2. connect 'jdbc:derby:dblooktest;create=true;user=test;password=test';
> 3. CALL
> SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY('derby.connection.requireAuthentication','true');
> 4. CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY('derby.user.test', 'test');
> 5. CREATE TABLE DBLOOKTESTTABLE(I INT NOT NULL PRIMARY KEY);
> 6. disconnect;
> 7. quit;
> And use dblook this way:
> 8. dblook -d 'jdbc:derby:dblooktest;user=test;password=test';
> Then an error is reported (dblook.log contents are at the end of this
> description);
> Nevertheless, if I do not require authentication:
> 9. CALL
> SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY('derby.connection.requireAuthentication','false');
> Then dblook works properly:
> 10. dblook -d 'jdbc:derby:dblooktest;user=test;password=test';
> 11. dblook -d 'jdbc:derby:dblooktest';
> Thus, the same connection url that works in ij for an authenticated database
> does not in dblook.
> =========== dblook.log
> java.sql.SQLNonTransientConnectionException: Se ha producido una anomalía de
> autenticación de conexión. Razón: Autenticación no válida..
> at
> org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown
> Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(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.impl.jdbc.EmbedConnection30.<init>(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedConnection40.<init>(Unknown Source)
> at org.apache.derby.jdbc.Driver40.getNewEmbedConnection(Unknown Source)
> at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source)
> at org.apache.derby.jdbc.AutoloadedDriver.connect(Unknown Source)
> at java.sql.DriverManager.getConnection(DriverManager.java:582)
> at java.sql.DriverManager.getConnection(DriverManager.java:207)
> at org.apache.derby.tools.dblook.go(Unknown Source)
> at org.apache.derby.tools.dblook.<init>(Unknown Source)
> at org.apache.derby.tools.dblook.main(Unknown Source)
> Caused by: java.sql.SQLException: Se ha producido una anomalía de
> autenticación de conexión. Razón: Autenticación no válida..
> at
> org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
> at
> org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown
> Source)
> ... 17 more
> -- **--> DEBUG: Se ha producido una anomalía de autenticación de conexión.
> Razón: Autenticación no válida..
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
