i patched the released version 2.3.0 with the second patchset ( not the first one for WeakMap), refactored the code to use the new requestfactory package (which is now in gwt.web.bindary...), i dont get OutOfMemoryException anymore but the load test leads to jvm-crashed (with 100%cpu load).
anaylyse the dump: 412286 instances of class com.google.web.bindery.autobean.vm.impl.ProxyAutoBean 412286 instances of class com.google.web.bindery.autobean.vm.impl.ShimHandler 343638 instances of class com.google.gwt.core.client.impl.WeakMapping$IdentityWeakReference 279948 instances of class com.google.web.bindery.autobean.vm.impl.JsonSplittable 143060 instances of class $Proxy9 112000 instances of class org.json.JSONObject 106798 instances of class $Proxy8 86704 instances of class $Proxy25 78455 instances of class org.json.JSONArray 68648 instances of class com.google.web.bindery.autobean.vm.impl.SimpleBeanHandler 55446 instances of class org.eclipse.persistence.indirection.IndirectList 50428 instances of class $Proxy27 43352 instances of class $Proxy26 35434 instances of class com.google.web.bindery.autobean.shared.impl.AutoBeanCodexImpl$EncodeState 35433 instances of class com.google.web.bindery.autobean.shared.impl.SplittableList 29575 instances of class org.eclipse.persistence.internal.identitymaps.UnitOfWorkCacheKey any hints ? if i cannot manage to resolve this issue i may need to reimplement it with traditional rpc with dto thanx -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
