This indicates that the server is running with a Java SecurityManager
and that the policy file does not grant read permission on that
file--and probably all files in the database directory.
On 11/25/22 12:30 AM, fed wrote:
testing with 10.15.2.0 from derby.log, server side, it complains about a
read permission on service.properties, some part of the file:
java.sql.SQLException: Impossibile avviare il database '/home/user/db/' con
il caricatore di classi
jdk.internal.loader.ClassLoaders$AppClassLoader@277050dc. Per i dettagli,
vedere l'eccezione successiva.
Caused by: java.security.AccessControlException: access denied
("java.io.FilePermission" "/home/user/db/service.properties" "read")
ERROR XBM0C: Privilegio mancante per l'operazione 'exists' sul file
'service.properties': access denied ("java.io.FilePermission"
There are several errors like these ones but I have read permission on this
The user that starts the server is the same that owns the file, the
permissions on the file are 664.
As I said, same setup but using 10.12.1.1 for the server, I have no
On Thu, 24 Nov 2022 at 19:52, Rick Hillegas <rick.hille...@gmail.com> wrote:
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:
Sorry for the late answer but I lost your reply.
I have a database updated to version 10.12.1.1, the server is running
the 10.12.1.1 too and the client is using 10.12.1.1 too, the connection
OK, I can use this setup.
But another test:
still the same database updated to version 10.12.1.1, the server is
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
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
vedere l'eccezione successiva.::SQLSTATE: XBM0C
Thanks for the help
On Sun, 13 Nov 2022 at 15:26, Bryan Pendleton <
I'm not aware of client-server version incompatibilities. Have you
done any experiments with different versions?
On Thu, Nov 10, 2022 at 4:16 AM fed <fury...@gmail.com> wrote:
using derby with network server setup is there any problem if the
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
use a newer version of apache derby?
Thanks for the help