[jbosscache-issues] [JBoss JIRA] Commented: (JBCACHE-1426) Putting a null map in the cache when the node already contains data causes the JDBC Cache Loader to barf

[Manik Surtani (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBCACHE-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12433741#action_12433741 ] 

Manik Surtani commented on JBCACHE-1426:
----------------------------------------

I can also confirm that this is not a problem on 3.x (possibly due to JBCACHE-1368).

This also does not affect any of the other cache loaders - only the JDBCCacheLoader.

> Putting a null map in the cache when the node already contains data causes the JDBC Cache Loader to barf
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JBCACHE-1426
>                 URL: https://jira.jboss.org/jira/browse/JBCACHE-1426
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Cache loaders
>    Affects Versions: 2.2.0.GA, 2.2.1.CR1
>            Reporter: Manik Surtani
>            Assignee: Manik Surtani
>            Priority: Critical
>             Fix For: 2.2.1.CR2, 2.2.1.GA
>
>
> simple test:
> cache.put(fqn, key, value);
> cache.put(fqn, null); // causes the JDBC cache loader to barf.
> This is now in the test suite - CacheLoaderTestsBase.testPutNullDataMap() and CacheLoaderTestsBase.testPutNullDataMapNodeHasData().

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira