Long living SyncProxy

[Bartosz Wilk]

Hello,

we use long-living ComputeServiceContext (which as I assume is not bad - https://groups.google.com/forum/#!msg/jclouds/3aMDPxY5L8w/DfGavkxYZ6oJ). After about 30 days of operation the LoadingCache<ClassMethodArgs, Object> delegateMap which is a field in org.jclouds.concurrent.internal.SyncProxy grows very big (about 400Megs which is unacceptable for us). Is there any method to limit the size of this cache? How to do it?

Thank in advance,
Bartosz Wilk

we use jclouds 1.5.7

[Adrian Cole]

Id switch to 1.6.0 as sync proxy had bad behavior and has been written out.

--
You received this message because you are subscribed to the Google Groups "jclouds" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jclouds+u...@googlegroups.com.
To post to this group, send email to jcl...@googlegroups.com.
Visit this group at http://groups.google.com/group/jclouds?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Andrew Phillips]

Hi Bartosz

> we use jclouds 1.5.7

This isn't an immediate solution to your problem, but as a result of
#1501 [1] you'll find that SyncProxy is disappearing ;-) Is there any
way you can try out the latest 1.6.0 release [2] to see if that makes
any difference?

ap

[1] https://github.com/jclouds/jclouds/issues/1501
[2] http://blog.jclouds.org/post/49146565342/jclouds-1-6-0-released

[Adrian Cole]

Ps I first read this subject as "long live sync proxy" a horrific thought :p

[Bartosz Wilk]

Adrian, Andrew,
thanks for replies. I'll try 1.6.0 and come back with effects. It may take some time to reproduce the problem so please be patient :)...

Bartosz