From af5096f89d3220f63d63dd0737d37808aaa0af4e Mon Sep 17 00:00:00 2001
From: Steve Ebersole <steve@hibernate.org>
Date: Thu, 18 Apr 2024 14:18:16 -0500
Subject: [PATCH] txn timeout migration note

---
 migration-guide.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/migration-guide.adoc b/migration-guide.adoc
index 7f54c64e6a..f54bb31af6 100644
--- a/migration-guide.adoc
+++ b/migration-guide.adoc
@@ -29,7 +29,7 @@ earlier versions, see any other pertinent migration guides as well.
         But that is a bytecode incompatibility.
   ** JPA has added support in its Graph API for things Hibernate has supported for some time.  Some of those are collisions
         requiring changes to the Hibernate API.
-  ** `Transaction#getTimeout`.  JPA 3.2 adds `#getTimeout` but uses `Integer` whereas Hibernate has historically used `int`
+  ** `Transaction#getTimeout`.  JPA 3.2 adds `#getTimeout` but uses `Integer` whereas Hibernate has historically used `int`.  Note that this raises the possibility of a `NullPointerException` during migration if, e.g., performing direct comparisons on the timeout value against an in (auto unboxing).
 
 See this https://in.relation.to/2024/04/01/jakarta-persistence-3/[blog post] for a good discussion of the changes in Jakarta Persistence 3.2.