Guido,

Reading the comments on that pull request, I get the feeling that pcl is
suggesting that upgrading to 4.2.2 is another way to solve the problem. I
dont think that route was taken to resolve the issue. Quoting his comment...

 upgrading your dependency to 4.2.2 once it becomes available will
*also*resolve the issue
>


I dont see a change to pom.xml during this pull. I tried the riak-client
1.0.6 and it still depends on 4.1.x. So the upgrade would be necessary to
fix the memory leak.

Thanks
Deepak Bala

On Tue, Sep 25, 2012 at 12:35 AM, Guido Medina <[email protected]>wrote:

>  Deepak,
>
>   I think that was fixed on the following pull request but, you would have
> to compile your own client from github which is easy; or, did you get the
> new 1.0.6? I'm not sure if it is already available at maven repos, anyways,
> there is a lot going on in the riak client in java, I would suggest you to
> keep an eye on the github, many good bugs getting fixed quickly.
>
> https://github.com/basho/riak-java-client/pull/159
>
> Best regards,
>
> Guido
>
>
>
> On 24/09/12 19:45, Deepak Balasubramanyam wrote:
>
> Hi,
>
>  My servers complain about a leaky apache DateUtils class during hot
> deployments. This is a known 
> bug<https://issues.apache.org/jira/browse/HTTPCLIENT-1216>in http 4.1.x and 
> has been fixed in 4.2.x. Can the next version of
> riak-client be updated to include the newer HTTP client (the
> current version is 4.1.1 ) ? Is the riak-client compatible with httpclient
> 4.2.x as it is ?
>
>  Thanks
> Deepak Bala
>
>
> _______________________________________________
> riak-users mailing 
> [email protected]http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>
>
>
> _______________________________________________
> riak-users mailing list
> [email protected]
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>
>
_______________________________________________
riak-users mailing list
[email protected]
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Reply via email to