StatementCreatorUtils.setNull throws exception in Derby Client driver [SPR-6000]

[spring-projects-issues]

Norbert Schneider opened SPR-6000 and commented

If JdbcTemplate.update is executed with a null value it throws an exception in the Derby Client driver:

org.apache.derby.client.am.SqlException: Es wurde versucht, einen Datenwert des Typs '<UNKNOWN>' aus einem Datenwert des Typs 'BIGINT' abzurufen.
org.apache.derby.client.am.PreparedStatement$PossibleTypes.throw22005Exception(Unknown Source)
org.apache.derby.client.am.PreparedStatement.setNull(Unknown Source)
org.springframework.jdbc.core.StatementCreatorUtils.setNull(StatementCreatorUtils.java:247)
org.springframework.jdbc.core.StatementCreatorUtils.setParameterValueInternal(StatementCreatorUtils.java:214)
org.springframework.jdbc.core.StatementCreatorUtils.setParameterValue(StatementCreatorUtils.java:145)
org.springframework.jdbc.core.ArgPreparedStatementSetter.setValues(ArgPreparedStatementSetter.java:51)
org.springframework.jdbc.core.JdbcTemplate$2.doInPreparedStatement(JdbcTemplate.java:796)
org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:591)
org.springframework.jdbc.core.JdbcTemplate.update(JdbcTemplate.java:792)
org.springframework.jdbc.core.JdbcTemplate.update(JdbcTemplate.java:850)
org.springframework.jdbc.core.JdbcTemplate.update(JdbcTemplate.java:858)
org.springframework.security.acls.jdbc.JdbcMutableAclService.updateObjectIdentity(JdbcMutableAclService.java:376)
org.springframework.security.acls.jdbc.JdbcMutableAclService.updateAcl(JdbcMutableAclService.java:334)

In org.springframework.jdbc.core.StatementCreatorUtils.setNull, the current driver name get compared against some predefined names and the null value is set appropriately. There is already a comparison against "Apache Derby Embedded". I suggest changing it to "Apache Derby", this works fine in my case.

---

Affects: 2.5.6

Referenced from: commits 84c1b56

[spring-projects-issues]

Thomas Risberg commented

Maybe they changed the behavior in Derby 1.5. I'm pretty sure I tested this in 1.4 and the behavior was different between the client and the embedded drivers. Have you tried this using Derby 1.4?

[spring-projects-issues]

Norbert Schneider commented

I tested it a little further...
The behaviour can be verified in derby server versions 10.5.1.1 and 10.4.2.0 with derbyclient version 10.5.3.0, 10.5.1.1 and 10.4.2.0.
Every combination produces the described error.

I haven't tested the embedded version, it's behaviour could be different.

[spring-projects-issues]

Thomas Risberg commented

Thanks for doing some additional testing. If you could paste an example of the code you are using then I'll take a look at this in the next couple of days.

[spring-projects-issues]

Norbert Schneider commented

Sure, but, as you can see in the stacktrace, I don't use the JdbcTemplate directly.
Here is an example out of the involved service. It uses Spring Security's MutableAclService:

 
private void createAcl(ObjectIdentity oid) {
   MutableAcl acl = mutableAclService.createAcl(oid);

   // [...]
   acl.insertAce(0, WRITE, new GrantedAuthoritySid("PERM_Owner"), true);

   // [...]
   acl.insertAce(1, READ, new GrantedAuthoritySid("PERM_Member"), true);

   mutableAclService.updateAcl(acl);
}

The error occurs when the "updateAcl" method gets executed. I don't know what the MutableAclService exactly does, but I narrowed the error down to the described part.