You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-user@db.apache.org by Orange Trees <or...@outlook.com> on 2022/12/22 05:29:26 UTC

Re: not getting proper database shutdown message in embedded mode

Hello,

Any further suggestions please where and what should I check?

Regards,
Orange
________________________________
From: Orange Trees <or...@outlook.com>
Sent: 27 November 2022 12:35
To: Derby Discussion <de...@db.apache.org>
Subject: Re: not getting proper database shutdown message in embedded mode

Hi,

I investigated this even further. Derby DB version 10.14.2.0 is not having this problem. So in the same environment (LinuxMint 19, Java 17, NetBeans14) problems are at least with Derby DB 10.15.2.0 and 10.16.1.1.

Thus I still unsure where exactly the problem is, is it NetBeans or Derby DB? Any help or hints appreciated.

Anyway, as a workaround, I will stick with 10.14.2.0 for now until the issue is resolved.

Regards,
Orange

Re: not getting proper database shutdown message in embedded mode

Posted by Rick Hillegas <ri...@gmail.com>.

Since it only happens with Derby 10.15 onward, the problem is probably 
caused by a misconfigured classpath: Derby 10.15 requires more jar 
files. I would take this up with the Netbeans community and point them 
at the release notes for 10.15.1.3: 
https://db.apache.org/derby/releases/release-10.15.1.3.html

On 12/21/22 9:29 PM, Orange Trees wrote:
> Hello,
>
> Any further suggestions please where and what should I check?
>
> Regards,
> Orange
> ________________________________
> From: Orange Trees <or...@outlook.com>
> Sent: 27 November 2022 12:35
> To: Derby Discussion <de...@db.apache.org>
> Subject: Re: not getting proper database shutdown message in embedded mode
>
> Hi,
>
> I investigated this even further. Derby DB version 10.14.2.0 is not having this problem. So in the same environment (LinuxMint 19, Java 17, NetBeans14) problems are at least with Derby DB 10.15.2.0 and 10.16.1.1.
>
> Thus I still unsure where exactly the problem is, is it NetBeans or Derby DB? Any help or hints appreciated.
>
> Anyway, as a workaround, I will stick with 10.14.2.0 for now until the issue is resolved.
>
> Regards,
> Orange
>