Hi Chamila,
Seems this happens from the cassandra side. You can solve this issue up to
some level by tuning Garbage Collector for Cassandra. Please look at
this[1] blog post. Hope it would be helpful
1.
http://malinthas.blogspot.com/2014/01/how-to-tune-apache-cassandra-garbage.html
Regards,
This is a requirement for connector implementations.
On Fri, Feb 21, 2014 at 2:36 PM, Isuru Udana isu...@wso2.com wrote:
Hi,
Setting the endpoint timeout values dynamically is not supported.
What is the actual requirement to make it dynamic ? In typical integration
scenarios, endpoint
There seem to be a registry issue. And I am using Windows, so I wonder if
this is a Windows issue.
Thanks,
Samisa...
Samisa Abeysinghe
Vice President Developer Evangelism
WSO2 Inc.
http://wso2.com
On Fri, Feb 21, 2014 at 10:26 PM, Evanthika Amarasiri evanth...@wso2.comwrote:
Hi Samisa,
Hi Samisa,
I tried this with having ESB4.8.1 on a windows7 machine and BAM2.4.1
AS5.2.1 on Ubuntu. It worked for me, expected message properties (company
name volume) received to BAM side. Since the windows machine is very low
in performance, couldn't try all three on it.
Thanks,
Pandula
