Unsupported key or value

Question

Hi,
I'm getting the following error when I try to retreive an object from the cache:
11:10:47,835 ERROR [STDERR] java.lang.IllegalArgumentException: Unsupported key or value: Key=1391631, Value=PartyImpl[PartyImpl[PartyImpl[objectId=61
380,entityId=6763,entityVersion=2],partyId=1391631,name=SUNRISE PARTNERS LIMITED PARTNERSHIP],shortName=SUNRISE PARTNERS LP]
11:10:47,851 ERROR [STDERR]     at com.tangosol.net.cache.BinaryMemoryCalculator.calculateUnits(BinaryMemoryCalculator.java:43)
11:10:47,851 ERROR [STDERR]     at com.tangosol.net.cache.OldCache$Entry.calculateUnits(OldCache.java:2396)
11:10:47,866 ERROR [STDERR]     at com.tangosol.net.cache.OldCache$Entry.onAdd(OldCache.java:1990)
11:10:47,866 ERROR [STDERR]     at com.tangosol.util.SafeHashMap.put(SafeHashMap.java:244)
11:10:47,866 ERROR [STDERR]     at com.tangosol.net.cache.OldCache.put(OldCache.java:266)
11:10:47,882 ERROR [STDERR]     at com.tangosol.net.cache.OldCache.put(OldCache.java:234)
11:10:47,882 ERROR [STDERR]     at com.tangosol.net.cache.CachingMap.get(CachingMap.java:534)
11:10:47,882 ERROR [STDERR]     at com.jpm.ibt.primegps.repository.AbstractCoherenceRepository.get(AbstractCoherenceRepository.java:233)
11:10:47,898 ERROR [STDERR]     at com.jpm.ibt.primegps.bulkload.reference.PartyBulkLoader.populateCache(PartyBulkLoader.java:33)
11:10:47,898 ERROR [STDERR]     at com.jpm.ibt.primegps.bulkload.AbstractBulkLoader.run(AbstractBulkLoader.java:167)
11:10:47,945 ERROR [STDERR]     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
11:10:47,945 ERROR [STDERR]     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
11:10:47,945 ERROR [STDERR]     at java.lang.Thread.run(Thread.java:619)I found a similar thread that was seeing the same error but this was only for a replicated cache. My config is:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE cache-config SYSTEM "cache-config.dtd" >
<cache-config>
     <caching-scheme-mapping>
     <cache-mapping>
          <cache-name>PARTY_CACHE</cache-name>
          <scheme-name>party_cache</scheme-name>
     </cache-mapping>
     </caching-scheme-mapping>
     <caching-schemes>
          <near-scheme>
               <scheme-name>party_cache</scheme-name>
               <service-name>partyCacheService</service-name>
               <!-- a sensible default ? -->
               <thread-count>5</thread-count>
               <front-scheme>
                    <local-scheme>
                         <!-- up to 10Megabytes -->
                              <high-units>10485760</high-units>
                              <unit-calculator>BINARY</unit-calculator>
                    </local-scheme>
               </front-scheme>
               <back-scheme>
                    <distributed-scheme>
                         <backing-map-scheme>
                              <read-write-backing-map-scheme>
                                   <internal-cache-scheme>
                                        <local-scheme>
                                        </local-scheme>
                                   </internal-cache-scheme>
                                   <cachestore-scheme>
                                        <class-scheme>
                                             <class-name>spring-bean:partyCacheStore</class-name>
                                        </class-scheme>
                                   </cachestore-scheme>
                              </read-write-backing-map-scheme>
                         </backing-map-scheme>
                    </distributed-scheme>
               </back-scheme>
               <autostart>true</autostart>
          </near-scheme>
     </caching-schemes>
</cache-config>removing the BINARY units part of the config seems to fix the problem but what is the effect of this? As I understand it this leaves me open to memory issues should the cache grow too large.

Answer 1

Hi Willy,
You problem is because the front scheme of a near cache stores data in deserialized form so you cannot use the BINARY unit calculator.
JK