Re: A pool question
On Mon, Feb 25, 2013 at 09:33:28AM -0500, Daniel Mikusa wrote: > Personally, what would worry me the most about this setup is configuring > and tuning each of the pools. Since they are all going to the same DB, I > wouldn't want to overload the system with too many connection, but at the > same time there has to be enough in each pool to service the needs of the > application. Plus getting this right, would seem to get trickier as you > add more pools into the mix. I concur. But on the other hand, this granularity offers clear benefits, provided that one can identify the low rates and heavy hitters. The usual concerns related to tuning apply of course, as you noted. We'll see. On a related note, it seems that there is some also ambiguity in the standars with respect to pooled getConnecton() vs. getConnection(user, pw). Thanks for the comments, Jukka. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
A pool question
Hello. A question related to pools. Background: a big application in which it is preferable to enforce different roles for different databases and tables. This implies that there are different user names and passwords for different connections. As I understand, there are two options for connection pooling in a scheme like this: A. Create different resources for the different roles, each having the user names and passwords defined as constants in the Tomcat configuration files. B. Group the different roles into a bigger scheme and use the option 'alternateUsernameAllowed' to obtain the connections with the specific user names and passwords. Both were tested to work. But I wonder: 1. The first option seems intuitively more efficient. But on the other hand, does each Resource define its own cleaner thread? I wouldn't want to overburden the setup with too many threads. 2. Are there any benchmarks on the option B? The plain FIFO seems rather inefficient if there are many different users/passwords. Any additional thoughts? - Jukka. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: can't start tomcat on port 80
On Tue, Feb 05, 2013 at 04:37:42PM +0200, Karolis Monkus wrote: > I use fedora 17 and from yum downloaded tomcat-7.0.33 version. I changed > port from 8080 to 80 in server.xml, restarted tomcat and got the following > error in catalina.out file: How are you (re)starting Tomcat? As far as I know, Fedora is still in the process of migrating to the new init-system known as systemd. As others have noted, I believe this mandates patching some of the stock scripts. -Jukka. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 6.0.18 Caching Question
On Thu, Nov 22, 2012 at 04:49:42PM +, Pid wrote: > > Have you read the security vulnerability pages? > > Maybe he's emailing us from the year 2008. Maybe. That said, I am not too keen to see every other question on this list being turned into a question about upgrading. Most of the questions are valid regardless of the used version. Signal to noise, and all that. - Jukka. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
