ClassCastException in JdbcMessageStore.getMessageGroup() with Oracle DB

[piercemar]

In what version(s) of Spring Integration are you seeing this issue?

5.5.0

Describe the bug

When running the latest 5.5.0 with an Oracle DB, calls to JdbcMessageStore.getMessageGroup(String) throw a ClassCastException on line 509.
groupInfo.get("COMPLETE") returns a java.math.BigDecimal under Oracle, which cannot be cast to Long.

java.lang.ClassCastException: class java.math.BigDecimal cannot be cast to class java.lang.Long (java.math.BigDecimal and java.lang.Long are in module java.base of loader 'bootstrap')
	at org.springframework.integration.jdbc.store.JdbcMessageStore.getMessageGroup(JdbcMessageStore.java:409)
	at org.springframework.integration.store.AbstractMessageGroupStore.addMessageToGroup(AbstractMessageGroupStore.java:190)
	at org.springframework.integration.aggregator.AbstractCorrelatingMessageHandler.store(AbstractCorrelatingMessageHandler.java:856)
	at org.springframework.integration.aggregator.AbstractCorrelatingMessageHandler.processMessageForGroup(AbstractCorrelatingMessageHandler.java:566)
	at org.springframework.integration.aggregator.AbstractCorrelatingMessageHandler.handleMessageInternal(AbstractCorrelatingMessageHandler.java:546)
	at org.springframework.integration.handler.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:56)
	... 113 common frames omitted

Expected behavior

Correct handling of the BigDecimal value.
5.4.7 leverages the driver conversion feature by calling rs.getInt() on the ResultSet.

[artembilan]

Confirmed.

Interesting that I made a cast to Long because our H2 and Derby tests have failed for Integer. That BIGINT in the table is really mapped to Long for them. Meanwhile Oracle's NUMBER(19,0) is just that BigDecimal, which is neither Long nor Integer "castable".

We probably don't have choice unless come back to the ResultSetExtractor to call the mentioned rs.getInt()...