Hi, It seems that AS 5.2.0 is not patched with the issue with JMS transport where the services with JMS enabled repeatedly try to establish a connection with the message broker. This results in GBs of logs in a matter of minutes filling up the disk.
As I got to know from Shammi, the solution is to exponentially increase the waiting time for the connection. Something like, trying in 1sec, 2sec, 4sec, 8, 16, 32 etc. This fix is already impelemented but it seems that it didn't get in to AS packs that is about to be released. I tried a setup with ActiveMQ, and I can see that it tries to establish a connection with the broker every second or so. Can the MB team look in to this ASAP please? Carbon 4.2.0 is due on coming Thursday. Thanks, KasunG -- *Kasun Gajasinghe* Software Engineer; Development Technologies Team, WSO2 Inc.; http://wso2.com , *email: **kasung AT spamfree wso2.com ** cell: **+94 (77) 678-0813* *linked-in: *http://lk.linkedin.com/in/gajasinghe * * *blog: **http://kasunbg.org* <http://kasunbg.org> * twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg> * *
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
