db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oskar Zinger (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-5994) Different SQL State is returned when executing "shutdown=true" - locally or remotely using ClientDriver
Date Sat, 17 Nov 2012 00:17:12 GMT

     [ https://issues.apache.org/jira/browse/DERBY-5994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Oskar Zinger updated DERBY-5994:
--------------------------------

    Description: 
Different SQL State is returned when executing "shutdown=true" Derby URL attribute while executing
the shutdown Database connection locally or remotely. Using "embedded" vs "client" Derby drivers.

Here is some background information:
- Using the embedded Derby Network Server deployment (derbynet.jar)
- Using the JDBC Derby Client (derbyclient.jar)
- Using the Derby Engine (derby.jar)

Note: in both cases the client driver is used: "org.apache.derby.jdbc.ClientDriver". The only
difference is the URL, when host and port is not specified execution happens in the same JVM
(local), when host and port is specified execution happens into another JVM (remote).

When executing the following - if database has not been booted yet (or already shutdown) -
the SQL State Code is "XJ004":
  DriverManager.getConnection("jdbc:derby:MyDatabase;shutdown=true;deregister=false", user,
pass);

When executing the following - if database has not been booted yet (or already shutdown) -
the SQL State Code is "08004":
  DriverManager.getConnection("jdbc:derby://myhost.mycompany.net:1527/MyDatabase;shutdown=true;deregister=false",
user, pass);

The SQL State Code of "08004" usually is returned with an SQL Exception if "User Authentication
is Invalid" for example username and / or password is incorrect.

Here is the error message: 
Error Code: '40000', SQL State Code: '08004' and Exception: 'java.sql.SQLNonTransientConnectionException:
The connection was refused because the database <database_name>;shutdown=true;deregister=false
was not found.'

Separately, the error message "database was not found" is actually misleading because the
database actually does exist and it just has not been been booted yet, or it has already been
shutdown. The Derby Network Server has not been shutdown, only the database and it is possible
to check if the database exists on the file system.

The reason why this is important is because when using Derby Replication, when replication
is started - the databases must be identical and in sync, so the database must be shutdown
cleanly, copied over, and replication will be started. Since the Salve Derby must start before
Master Derby, it is required to be able to remotely shutdown the Master Derby database from
the Slave Derby instance (host).


  was:
Different SQL State is returned when executing "shutdown=true" Derby URL attribute while executing
the shutdown Database connection locally or remotely. Note: in both cases the client driver
is used: "org.apache.derby.jdbc.ClientDriver"

Here is some background information:
- Using the embedded Derby Network Server deployment (derbynet.jar)
- Using the JDBC Derby Client (derbyclient.jar)
- Using the Derby Engine (derby.jar)

Note: in both cases the client driver is used: "org.apache.derby.jdbc.ClientDriver". The only
difference is the URL, when host and port is not specified execution happens in the same JVM
(local), when host and port is specified execution happens into another JVM (remote).

When executing the following - if database has not been booted yet (or already shutdown) -
the SQL State Code is "XJ004":
  DriverManager.getConnection("jdbc:derby:MyDatabase;shutdown=true;deregister=false", user,
pass);

When executing the following - if database has not been booted yet (or already shutdown) -
the SQL State Code is "08004":
  DriverManager.getConnection("jdbc:derby://myhost.mycompany.net:1527/MyDatabase;shutdown=true;deregister=false",
user, pass);

The SQL State Code of "08004" usually is returned with an SQL Exception if "User Authentication
is Invalid" for example username and / or password is incorrect.

Here is the error message: 
Error Code: '40000', SQL State Code: '08004' and Exception: 'java.sql.SQLNonTransientConnectionException:
The connection was refused because the database <database_name>;shutdown=true;deregister=false
was not found.'

Separately, the error message "database was not found" is actually misleading because the
database actually does exist and it just has not been been booted yet, or it has already been
shutdown. The Derby Network Server has not been shutdown, only the database and it is possible
to check if the database exists on the file system.

The reason why this is important is because when using Derby Replication, when replication
is started - the databases must be identical and in sync, so the database must be shutdown
cleanly, copied over, and replication will be started. Since the Salve Derby must start before
Master Derby, it is required to be able to remotely shutdown the Master Derby database from
the Slave Derby instance (host).


    
> Different SQL State is returned when executing "shutdown=true" - locally or remotely
using ClientDriver
> -------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5994
>                 URL: https://issues.apache.org/jira/browse/DERBY-5994
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC, Network Client, Network Server, Replication
>    Affects Versions: 10.8.2.2
>         Environment: Derby Embedded Network Server - Not specific to operating systems,
software platforms or hardware specifications.
>            Reporter: Oskar Zinger
>         Attachments: Derby5994Repro.java
>
>
> Different SQL State is returned when executing "shutdown=true" Derby URL attribute while
executing the shutdown Database connection locally or remotely. Using "embedded" vs "client"
Derby drivers.
> Here is some background information:
> - Using the embedded Derby Network Server deployment (derbynet.jar)
> - Using the JDBC Derby Client (derbyclient.jar)
> - Using the Derby Engine (derby.jar)
> Note: in both cases the client driver is used: "org.apache.derby.jdbc.ClientDriver".
The only difference is the URL, when host and port is not specified execution happens in the
same JVM (local), when host and port is specified execution happens into another JVM (remote).
> When executing the following - if database has not been booted yet (or already shutdown)
- the SQL State Code is "XJ004":
>   DriverManager.getConnection("jdbc:derby:MyDatabase;shutdown=true;deregister=false",
user, pass);
> When executing the following - if database has not been booted yet (or already shutdown)
- the SQL State Code is "08004":
>   DriverManager.getConnection("jdbc:derby://myhost.mycompany.net:1527/MyDatabase;shutdown=true;deregister=false",
user, pass);
> The SQL State Code of "08004" usually is returned with an SQL Exception if "User Authentication
is Invalid" for example username and / or password is incorrect.
> Here is the error message: 
> Error Code: '40000', SQL State Code: '08004' and Exception: 'java.sql.SQLNonTransientConnectionException:
The connection was refused because the database <database_name>;shutdown=true;deregister=false
was not found.'
> Separately, the error message "database was not found" is actually misleading because
the database actually does exist and it just has not been been booted yet, or it has already
been shutdown. The Derby Network Server has not been shutdown, only the database and it is
possible to check if the database exists on the file system.
> The reason why this is important is because when using Derby Replication, when replication
is started - the databases must be identical and in sync, so the database must be shutdown
cleanly, copied over, and replication will be started. Since the Salve Derby must start before
Master Derby, it is required to be able to remotely shutdown the Master Derby database from
the Slave Derby instance (host).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message