On 4/19/19 2:32 PM, Mark Rotteveel wrote:
Jaybird itself is intentionally calling fb_shutdown on stop of the web
application. Such a stop may be followed by a redeploy and start of
the web application **in the same process**. Given how the library is
loaded, this can result in the existing lib
On 19-4-2019 11:11, Dimitry Sibiryakov wrote:
19.04.2019 10:36, Mark Rotteveel wrote:
I'll need to investigate how I can unload and reload the library.
You can prevent fb_shutdown() from shutting client library down using
fb_shutdown_callback().
That won't help me here. Jaybird itself is
Metadata script extracted using ISQL add a extra space on a not null Timestamp
table field with CURRENT_TIMESTAMP as default value
--
Key: CORE-6053
19.04.2019 10:36, Mark Rotteveel wrote:
I'll need to investigate how I can unload and reload the library.
You can prevent fb_shutdown() from shutting client library down using
fb_shutdown_callback().
--
WBR, SD.
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.
On 19-4-2019 10:31, Alex Peshkoff via Firebird-devel wrote:
On 4/19/19 10:45 AM, Mark Rotteveel wrote:
Is it possible to recover from calling fb_shutdown?
I'm trying to make use of embedded in Jaybird a little more crashproof
by calling fb_shutdown on Java application stop.
This works fine i
On 4/19/19 10:45 AM, Mark Rotteveel wrote:
Is it possible to recover from calling fb_shutdown?
I'm trying to make use of embedded in Jaybird a little more crashproof
by calling fb_shutdown on Java application stop.
This works fine if this application stop coincides with the process
exit. But
Is it possible to recover from calling fb_shutdown?
I'm trying to make use of embedded in Jaybird a little more crashproof
by calling fb_shutdown on Java application stop.
This works fine if this application stop coincides with the process
exit. But with Java web applications this doesn't wor
