This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Hi all, I have a firewall which closes all the connections which are idle for 30 mins.So i have included the following connection pooling parameters inside my context file. timeBetweenEvictionRunsMillis=300000 numTestsPerEvictionRun=20 minEvictableIdleTimeMillis= 180000 I also have maxActive=50 maxIdle=100 maxWait=-1 But still its not working.Can anybody have any suggestion in this regard.
I'm curious: Is the firewall between the servers and the outside world, or is it between segments of the internal network? The former would imply that there's JDBC traffic coming in over the Internet - I'd be interested to hear what lead to that architectural choice. If the latter, where does the need for a firewall between internal systems come from?
Joined: May 06, 2005
I dont have any control on these issues(firewall between internal servers).Probably this kind of settings can save the data in case of any hack. But the problem is still there and not been fixed yet. regards, Ajse
Product companies always have problem like that. You can't dictate to customers how to configure firewall, otherwise they will get a product of your competitor which can manage such problems. I do not see lifetime for connection in your pool parameters. We used own pool and actually added this feature because met such requirements.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com