The SQLState indicates that the server was not able to boot the
database. Look in the server-side derby.log to see if there is a
detailed error message describing why the boot failed.
On 11/23/22 4:42 PM, fed wrote:
Hi,
Sorry for the late answer but I lost your reply.
Two tests:
I have a database updated to version 10.12.1.1, the server is running with
the 10.12.1.1 too and the client is using 10.12.1.1 too, the connection is
OK, I can use this setup.
But another test:
still the same database updated to version 10.12.1.1, the server is running
10.15.2.0 so a newer version and the client is using 10.12.1.1: I have
problems in this case the client can't connect to the database with this
error:
Caused by: org.apache.derby.client.am.SqlException: DERBY SQL error:
ERRORCODE: 40000, SQLSTATE: XJ040, SQLERRMC: Impossibile avviare il
database '/home/user/some_db_path/' con il caricatore di classi
jdk.internal.loader.ClassLoaders$AppClassLoader@277050dc. Per i dettagli,
vedere l'eccezione successiva.::SQLSTATE: XBM0C
Thanks for the help
On Sun, 13 Nov 2022 at 15:26, Bryan Pendleton <bpendleton.de...@gmail.com>
wrote:
I'm not aware of client-server version incompatibilities. Have you
done any experiments with different versions?
thanks,
bryan
On Thu, Nov 10, 2022 at 4:16 AM fed <fury...@gmail.com> wrote:
Hi,
using derby with network server setup is there any problem if the server
and the client are running on different java versions?
Still on this, considering the database created/updated with the apache
derby version that the client uses, is there any problem if the server will
use a newer version of apache derby?
Thanks for the help
-fed
