You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This property behaves differently between native and non-native modes.
In non-native mode, the default time unit of spring.transaction.default-timeout is seconds.
In native mode, the default time unit of spring.transaction.default-timeout is milliseconds.
The text was updated successfully, but these errors were encountered:
wilkinsona
changed the title
Bug with spring.transaction.default-timeout
Default duration unit is ignored when binding properties in a native image
May 1, 2025
wilkinsona
changed the title
Default duration unit is ignored when binding properties in a native image
Custom default units are ignored when binding properties in a native image
May 1, 2025
wilkinsona
changed the title
Custom default units are ignored when binding properties in a native image
Custom default units on a field are ignored when binding properties in a native image
May 1, 2025
wilkinsona
changed the title
Custom default units on a field are ignored when binding properties in a native image
Custom default units declared on a field are ignored when binding properties in a native image
May 1, 2025
Thanks for reporting this, @ldwqh0. It affected any JavaBean configuration property binding where the property's field was annotated. As I think you've already realised, you can avoid the problem by specifying a unit in your configuration property. Alternatively, you could add a reflection hint for the field backing the affected property. Neither will be necessary after the next round of maintenance releases later this month.
This property behaves differently between native and non-native modes.
In non-native mode, the default time unit of spring.transaction.default-timeout is seconds.
In native mode, the default time unit of spring.transaction.default-timeout is milliseconds.
The text was updated successfully, but these errors were encountered: