Bug in XA Recovery implementation: java.sql.SQLException: ORA-00932: inconsistent datatypes: expected BLOB got NUMBER

This class is found in the error stack trace:
Caused by: java.sql.SQLException: ORA-00932: inconsistent datatypes: expected BLOB got NUMBER

at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:743)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:216)
at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:955)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1168)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3285)
at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3368)
at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeUpdate(WrappedPreparedStatement.java:227)
at org.jboss.mq.pm.jdbc2.PersistenceManager.addTXRecord(PersistenceManager.java:913)
at org.jboss.mq.pm.jdbc2.PersistenceManager.insertPersistentTx(PersistenceManager.java:1030)
... 21 more

The method addTXRecord(Connection c, Tx txid) does
905 if (xaRecovery)
906

{ 907 Xid xid = txid.getXid(); 908 if (xid != null) 909 setBlob(stmt, 2, xid); 910 else 911 stmt.setNull(2, java.sql.Types.BIGINT); 912 }

913 stmt.executeUpdate();

So if the xid is NULL then it tries to insert a NULL number as opposed a BLOB.