Jaybird 5. Rollback not completed, state was ROLLING

Hugo Larson

unread,

Jul 28, 2026, 4:14:34 PM (2 days ago) Jul 28

to Firebird-java

Hi,

We recently upgraded to Jaybird 5 (from 4) and have since then seen the phenomenon.
No further trance is printed.
What can the reason be?

Thanks,
Hugo

org.firebirdsql.gds.ng.wire.version10.V10Transaction [Finalizer|]:org.firebirdsql.logging.JulLogger warn Rollback not completed, state was ROLLING_BACK; see debug level for stacktrace

Mark Rotteveel

unread,

Jul 28, 2026, 5:26:04 PM (2 days ago) Jul 28

to firebi...@googlegroups.com

On 28-07-2026 22:14, 'Hugo Larson' via firebird-java wrote:
> Hi,
>
> We recently upgraded to Jaybird 5 (from 4) and have since then seen the
> phenomenon.
> No further trance is printed.
> What can the reason be?
>
> Thanks,
> Hugo
>

> *org.firebirdsql.gds.ng.wire.version10.V10Transaction

> [Finalizer|]:org.firebirdsql.logging.JulLogger warn Rollback not

> completed, state was ROLLING_BACK; see debug level for stacktrace *

Enable debug level logging and it will also log the stacktrace where
this occurred.

Given this seems to have been logged from the finalizer thread, this is
probably a transaction that was still active when the connection was
closed. The finalizer eventually tries to roll it back, but the
connection is probably already gone at that point, throwing an
exception, resulting in that log.

Unfortunately, the finalizer doesn't log the actual exception that
triggered this, just the unexpected state after the rollback attempt.
The finalizer was removed in Jaybird 6 when I removed finalization (in
some limited cases replacing it with a cleaner).

The cause might be a connection leak in your application (not closing it
before it becomes garbage), because connection finalization happens on a
level that doesn't track transactions, so if that finalizer is called
before the transaction finalizer, the connection will be gone before the
rollback happened (on connection close, the server will roll back active
transactions anyway).

I'll see if maybe I should just get rid of that finalizer in Jaybird 5
as well, but I'll first try to see if I might be losing a transaction
somewhere internally in Jaybird itself.

Mark
--
Mark Rotteveel

Hugo Larson

unread,

Jul 29, 2026, 12:03:39 AM (yesterday) Jul 29

to firebi...@googlegroups.com

Hi

Yes good idea to remove finalize.

Also Firebird engine has parameter to drop limbo connections.

Thx

Hugo

Yahoo Mail: Search, organise, conquer

--
Support the ongoing development of Firebird! Consider donating to the Firebird Foundation and help ensure its future. Every contribution makes a difference. Learn more and donate here:
https://www.firebirdsql.org/donate
---
You received this message because you are subscribed to the Google Groups "firebird-java" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebird-jav...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/firebird-java/588fc8d1-8660-4b3e-bd0b-8c3a3a388869%40lawinegevaar.nl.

Mark Rotteveel

unread,

Jul 29, 2026, 3:34:09 AM (yesterday) Jul 29

to firebi...@googlegroups.com

On 29-07-2026 06:03, 'Hugo Larson' via firebird-java wrote:
> Hi
> Yes good idea to remove finalize.

You could also migrate to Jaybird 6, where this was already done (but
the you need to be on Java 17 or higher).

> Also Firebird engine has parameter to drop limbo connections.

I'm not aware of such a parameter, only a gfix option to resolve them,
or reattach them to a connection and then commit or rollback (which
Jaybird supports for XA).

Mark
--
Mark Rotteveel

Hugo Larson

unread,

Jul 29, 2026, 3:54:52 AM (yesterday) Jul 29

to 'Mark Rotteveel' via firebird-java

Hi,

Unfortunately we are stuck with java 8.

There is this parameter in firebird.conf. Maybe it's not same thing.

# ----------------------------

# Set number of minutes after which idle attachment will be disconnected by the

# engine. Zero means no timeout is set.

#

# Per-database configurable.

#

# Type: integer

#

#ConnectionIdleTimeout = 0

--

Support the ongoing development of Firebird! Consider donating to the Firebird Foundation and help ensure its future. Every contribution makes a difference. Learn more and donate here:

https://www.firebirdsql.org/donate

---

You received this message because you are subscribed to the Google Groups "firebird-java" group.

To unsubscribe from this group and stop receiving emails from it, send an email to firebird-jav...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/firebird-java/d469d528-ea17-451e-ae40-d02aaa59b3bb%40lawinegevaar.nl.

Mark Rotteveel

unread,

Jul 29, 2026, 3:59:36 AM (yesterday) Jul 29

to firebi...@googlegroups.com

On 29-07-2026 09:54, 'Hugo Larson' via firebird-java wrote:
> There is this parameter in firebird.conf. Maybe it's not same thing.
>
> # ----------------------------
> # Set number of minutes after which idle attachment will be disconnected
> by the
> # engine. Zero means no timeout is set.
> #
> # Per-database configurable.
> #
> # Type: integer
> #
> #ConnectionIdleTimeout = 0

That parameter controls how long a connection may be idle (i.e. not
receive requests from the client), it's not related to transactions
(though, when a connection is terminated, any active transactions are
rolled back, but it doesn't affect limbo transactions).

Mark
--
Mark Rotteveel

Hugo Larson

unread,

Jul 29, 2026, 4:05:06 AM (yesterday) Jul 29

to 'Mark Rotteveel' via firebird-java

"

I'll first try to see if I might be losing a transaction

somewhere internally in Jaybird itself.

"

It could be the case because we se this problem daily at sites that are upgraded to jaybird 5 (from 4).

--

Support the ongoing development of Firebird! Consider donating to the Firebird Foundation and help ensure its future. Every contribution makes a difference. Learn more and donate here:

https://www.firebirdsql.org/donate

---

You received this message because you are subscribed to the Google Groups "firebird-java" group.

To unsubscribe from this group and stop receiving emails from it, send an email to firebird-jav...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/firebird-java/588fc8d1-8660-4b3e-bd0b-8c3a3a388869%40lawinegevaar.nl.

Mark Rotteveel

unread,

Jul 29, 2026, 4:58:06 AM (yesterday) Jul 29

to firebi...@googlegroups.com

On 29-07-2026 10:05, 'Hugo Larson' via firebird-java wrote:
> "
> I'll first try to see if I might be losing a transaction
> somewhere internally in Jaybird itself.
> "
> It could be the case because we se this problem daily at sites that are
> upgraded to jaybird 5 (from 4).

Yes, and this finalizer and the logging of invalid state was already
present in Jaybird 4, so that would seem to point to something in

Mark Rotteveel

unread,

Jul 29, 2026, 7:23:33 AM (yesterday) Jul 29

to firebi...@googlegroups.com

On 28-07-2026 22:14, 'Hugo Larson' via firebird-java wrote:
> We recently upgraded to Jaybird 5 (from 4) and have since then seen the
> phenomenon.
> No further trance is printed.
> What can the reason be?

Could you enable debug logging on
org.firebirdsql.gds.ng.AbstractFbAttachment?

I suspect it'll log "Exception on safely detach" with an exception with
message "cannot disconnect database with open transactions ({0} active)"
(where the {0} is probably 1).

Mark
--
Mark Rotteveel

Hugo Larson

unread,

Jul 29, 2026, 8:06:06 AM (yesterday) Jul 29

to 'Mark Rotteveel' via firebird-java

Mark,

Need to ask you a dumb question. How to enable logging?
Create a file jaybird-logging.properties?

--

Support the ongoing development of Firebird! Consider donating to the Firebird Foundation and help ensure its future. Every contribution makes a difference. Learn more and donate here:

https://www.firebirdsql.org/donate

---

You received this message because you are subscribed to the Google Groups "firebird-java" group.

To unsubscribe from this group and stop receiving emails from it, send an email to firebird-jav...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/firebird-java/a45e7484-db90-4ef2-8cef-cd69bb203d8c%40lawinegevaar.nl.

Mark Rotteveel

unread,

Jul 29, 2026, 9:34:31 AM (yesterday) Jul 29

to firebi...@googlegroups.com

On 29-07-2026 14:06, 'Hugo Larson' via firebird-java wrote:
> Mark,
>
> Need to ask you a dumb question. How to enable logging?
> Create a file jaybird-logging.properties?

By default, java.util.logging is used, and if you have no explicit
java.util.logging configuration, it uses the JVM default config (in
%JAVA_HOME%/conf/logging.properties).

See for example this tutorial:
https://mkyong.com/logging/java-logging-apis-tutorial/

As a small example, create a logging.properties file with contents
(without the backticks):

```
handlers = java.util.logging.ConsoleHandler
# Set root logger to WARNING and higher
.level = WARNING
# Set org.firebirdsql logger to INFO and higher
org.firebirdsql.level = INFO
# Set org.firebirdsql.gds.ng.AbstractFbAttachment logger to FINE
org.firebirdsql.gds.ng.AbstractFbAttachment.level = FINE
# Set org.firebirdsql.gds.ng.wire.version10.V10Transaction logger to FINE
org.firebirdsql.gds.ng.wire.version10.V10Transaction.level = FINE

# Configure handler to output FINE
java.util.logging.ConsoleHandler.level = FINE
```

(JUL level FINE corresponds to what Jaybird 5 calls debug level)

The use of the ConsoleHandler will log to the standard error output.

Then run your application with
`-Djava.util.logging.config.file=/path/to/logging.properties` (replace
/path/to with actual path or relative path from the current working
directory).

Mark
--
Mark Rotteveel

Hugo Larson

unread,

Jul 29, 2026, 10:31:30 AM (yesterday) Jul 29

to 'Mark Rotteveel' via firebird-java

Is this helpful?
Everytime all the time

26-07-29 16:28:54|org.firebirdsql.gds.ng.AbstractFbAttachment [Finalizer|]:org.firebirdsql.logging.JulLogger debug Exception on safely detach

java.sql.SQLException: Error writing data to the connection. [SQLState:08006, ISC error code:335544727]

at org.firebirdsql.gds.ng.FbExceptionBuilder$Type$1.createSQLException(FbExceptionBuilder.java:618)

at org.firebirdsql.gds.ng.FbExceptionBuilder$ExceptionInformation.toSQLException(FbExceptionBuilder.java:571)

at org.firebirdsql.gds.ng.FbExceptionBuilder.toSQLException(FbExceptionBuilder.java:309)

at org.firebirdsql.gds.ng.wire.version10.V10Database.internalDetach(V10Database.java:201)

at org.firebirdsql.gds.ng.AbstractFbDatabase.close(AbstractFbDatabase.java:190)

at org.firebirdsql.gds.ng.AbstractFbAttachment.safelyDetach(AbstractFbAttachment.java:176)

at org.firebirdsql.gds.ng.wire.AbstractFbWireDatabase.finalize(AbstractFbWireDatabase.java:372)

at java.lang.System$2.invokeFinalize(System.java:1270)

at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:102)

at java.lang.ref.Finalizer.access$100(Finalizer.java:34)

at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:217)

Caused by: java.net.SocketException: Socket closed

at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:118)

at java.net.SocketOutputStream.write(SocketOutputStream.java:155)

at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)

at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)

at org.firebirdsql.gds.ng.wire.version10.V10Database.internalDetach(V10Database.java:199)

--

Support the ongoing development of Firebird! Consider donating to the Firebird Foundation and help ensure its future. Every contribution makes a difference. Learn more and donate here:

https://www.firebirdsql.org/donate

---

You received this message because you are subscribed to the Google Groups "firebird-java" group.

To unsubscribe from this group and stop receiving emails from it, send an email to firebird-jav...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/firebird-java/4ab809e2-1d10-4f3c-8625-b57cd4a3576c%40lawinegevaar.nl.

Hugo Larson

unread,

Jul 29, 2026, 10:38:03 AM (yesterday) Jul 29

to 'Mark Rotteveel' via firebird-java

Three exeptions.

26-07-29 16:28:53|org.firebirdsql.gds.ng.wire.version13.V13WireOperations [Thread-7|]:org.firebirdsql.logging.JulLogger debug Could not load EncryptionPluginSpi: org.firebirdsql.gds.ng.wire.crypt.chacha.ChaChaEncryptionPluginSpi

java.lang.ClassNotFoundException: org.firebirdsql.gds.ng.wire.crypt.chacha.ChaChaEncryptionPluginSpi

at java.net.URLClassLoader.findClass(URLClassLoader.java:381)

at java.lang.ClassLoader.loadClass(ClassLoader.java:424)

at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)

at java.lang.ClassLoader.loadClass(ClassLoader.java:357)

at java.lang.Class.forName0(Native Method)

at java.lang.Class.forName(Class.java:264)

at org.firebirdsql.gds.ng.wire.version13.V13WireOperations.<clinit>(V13WireOperations.java:77)

at org.firebirdsql.gds.ng.wire.version19.Version19Descriptor.createWireOperations(Version19Descriptor.java:127)

at org.firebirdsql.gds.ng.wire.AbstractFbWireDatabase.<init>(AbstractFbWireDatabase.java:63)

at org.firebirdsql.gds.ng.wire.version10.V10Database.<init>(V10Database.java:68)

at org.firebirdsql.gds.ng.wire.version11.V11Database.<init>(V11Database.java:54)

at org.firebirdsql.gds.ng.wire.version12.V12Database.<init>(V12Database.java:55)

at org.firebirdsql.gds.ng.wire.version13.V13Database.<init>(V13Database.java:47)

at org.firebirdsql.gds.ng.wire.version15.V15Database.<init>(V15Database.java:44)

at org.firebirdsql.gds.ng.wire.version16.V16Database.<init>(V16Database.java:44)

at org.firebirdsql.gds.ng.wire.version18.V18Database.<init>(V18Database.java:43)

at org.firebirdsql.gds.ng.wire.version19.V19Database.<init>(V19Database.java:54)

at org.firebirdsql.gds.ng.wire.version19.Version19Descriptor.createDatabase(Version19Descriptor.java:64)

at org.firebirdsql.gds.ng.wire.WireDatabaseConnection.createConnectionHandle(WireDatabaseConnection.java:90)

at org.firebirdsql.gds.ng.wire.WireDatabaseConnection.createConnectionHandle(WireDatabaseConnection.java:36)

at org.firebirdsql.gds.ng.wire.WireConnection.identify(WireConnection.java:382)

at org.firebirdsql.gds.ng.wire.FbWireDatabaseFactory.performConnect(FbWireDatabaseFactory.java:51)

at org.firebirdsql.gds.ng.wire.FbWireDatabaseFactory.connect(FbWireDatabaseFactory.java:39)

at org.firebirdsql.gds.ng.wire.FbWireDatabaseFactory.connect(FbWireDatabaseFactory.java:32)

at org.firebirdsql.jaybird.xca.FBManagedConnection.<init>(FBManagedConnection.java:121)

at org.firebirdsql.jaybird.xca.FBManagedConnectionFactory.createManagedConnection(FBManagedConnectionFactory.java:375)

at org.firebirdsql.jaybird.xca.FBStandAloneConnectionManager.allocateConnection(FBStandAloneConnectionManager.java:48)

at org.firebirdsql.jdbc.FBDataSource.getConnection(FBDataSource.java:72)

at org.firebirdsql.jdbc.FBDriver.connect(FBDriver.java:137)

___________________________________________________________________________________________________________________________________________________

26-07-29 16:28:53|org.firebirdsql.gds.ng.AbstractFbAttachment [Finalizer|]:org.firebirdsql.logging.JulLogger debug Exception on safely detach