Thanks. I created https://issues.apache.org/jira/browse/DERBY-7122
Art
On Sat, 7 Aug 2021 at 01:06, Rick Hillegas wrote:
>
> You can also hack around this problem by starting the server without a
> security manager (see
> https://db.apache.org/derby/docs/10.15/security/tsecnetservopen.html):
>
You can also hack around this problem by starting the server without a
security manager (see
https://db.apache.org/derby/docs/10.15/security/tsecnetservopen.html):
java -jar $DERBY_HOME/lib/derbyrun.jar server start -noSecurityManager
I doubt that the Open JDK team will give this issue much
I agree with Bryan that this looks like a platform-specific Open JDK
bug. In your bug report, please include the version numbers for the
Derby, Open JDK, and Ubuntu distros which you use to trigger this
exception. It would be interesting to know if the bug turns up when you
use the latest Open
Hi
Here goes...
Fri Aug 06 10:14:45 AEST 2021 : Apache Derby Network Server -
10.15.2.0 - (1873585) started and ready to accept connections on port
1527
Fri Aug 06 10:14:53 AEST 2021:
Booting Derby version The Apache Software
That does look like the problem discussed in the email thread you cited:
http://apache-database.10148.n7.nabble.com/Derby-newbie-error-seen-creating-seconddb-thru-ij-for-network-server-Derby-td150684.html
Can you post the stack trace?
Thanks,
-Rick
On 8/5/21 7:51 AM, Art O Cathain wrote:
Hi
Hi
There is a very long stack trace, and the last few lines of the log file are
Cleanup action completed
Fri Aug 06 00:47:55 AEST 2021 Thread[DRDAConnThread_2,5,main]
(DATABASE = seconddb), (DRDAID = {1}), Failed to create database
'seconddb', see the next exception for details.
Fri Aug 06
