To clarify, should read;

...
"There are no other threads accessing this OBJECT(Hashtable) within the cache."
...

....but there was other threads writing to other objects within the cache.

Specifically the problem seems to be this;

public void aSessionBeanMethod(){
Map<String,String> map = (Map<String,String>)getPojoCache().find("XXX");
for(int i=0; i < 100; i++){
map.put(i+"",i+"");
}
}

In this scenario the writes to the Map get steadily slower. I assume because they are batched up into the session beans method transaction, to the point where the last few puts into the Map take nearly a second each.

So my questions are;

1. Why is the above so code so slow and how should I make it faster without moving the code outside of session bean method?
2. Why is the above code locking all writes to all objects stored in the pojocache? how do I set the locking to be per instance, I used to have the following in my pojocache-aop.xml, but the version in the latest download doesn't have this, and adding this back in didn't seem to help;

<!-- Perform parent level node locking -->



Thanks in advance

regards

James

Forgot to add CODE tags :)
... the default pojocache-aop.xml used to have the following for locking;

<!-- Perform parent level node locking -->
<interceptor name="TxLock" class="org.jboss.cache.pojo.interceptors.PojoTxLockInterceptor"
 scope="PER_INSTANCE"/>

<?xml version="1.0" encoding="UTF-8"?>
<!--
 This is a variant of jboss-aop.xml.
-->
<aop>
 <!-- If a POJO has a Replicable annotation, it will be asepectized. -->

 <!--
 Supports inheritance and polymorphism. It can either be a concrete class
 or an interface. All sub-classes or interface implementors will be instrumeneted.
 -->
 <prepare expr="field(* $instanceof{@org.jboss.cache.pojo.annotation.Replicable}->*)" />

 <!-- Work around that ensures annotated classes which do not access fields are instrumented -->
 <introduction expr="class($instanceof{@org.jboss.cache.pojo.annotation.Replicable})"/>

 <!-- Array support -->
 <!-- Comment entire section to disable -->
 <arrayreplacement expr="class($instanceof{@org.jboss.cache.pojo.annotation.Replicable})"/>
 <interceptor name="pojocache-array" class="org.jboss.cache.pojo.interceptors.dynamic.ArrayInterceptor"/>
 <introduction expr="class($instanceof{@org.jboss.cache.pojo.annotation.Replicable})">
 <interfaces>org.jboss.cache.pojo.impl.ArrayInterceptable</interfaces>
 </introduction>
 <arraybind name="pojocache-array" type="READ_WRITE">
 <interceptor-ref name="pojocache-array"/>
 </arraybind>
</aop>

By the way this used to work fine on Cache 1.4 on Jboss4.2.

To clarify in the code above each call of; map.put(i+"",i+""); get slower and slower with the last few taking over 1 second each.

As the map get bigger things get progressively slower, so the next time the loop is called it's even slower.
Note this isn't due to excessive logging, the same happens when level is INFO.

In production I do something similar but I write about 500 different entries to a few different lists. By the end this takes over 10 seconds per write causing timeout from other thread that try to write to (different) objects in the cache during that time.

Note - I notice that the session bean in question is being instrumented during (compile time) weaving, I assume because it contains references and accesses some other Replicable objects, but the session bean method I've used for testing I use a Map.