On Thu, Feb 13, 2014 at 10:21 AM, José Luis Cetina <[email protected]>wrote:
> I use 2 servers with this configuration and tomee and both of them read to > other server where the database is (2 webapp server + 1 db server). > with your current config, have (180) endusers reported performance feedback? web page (database) transactions seems to be fast/responsive, no-wait, few seconds wait for most transactions? when you changed max active from 250 to 500, any better (or different) feedback from endusers of your app? i don't have 180 (concurrent) users (or connections), but i have tweaked those jdbc resource settings a few times. I think, my last change was from higher number to lower number, and app performs well. app always performed well, but i don't think i've seen difference in performance when jdbc resource settings were tweaked. there is something that I recognized recently. for some time, there was one page that retrieved data from database via @Stateless, and the data was not the latest-and-greatest data. Recently, I did some transactions in the app (on other pages), and opened that page, and it seems to work-as-expected 'now' (finally). I think the latest change to my app was tomee 1.6.1 snapshot, but i think it had something to do with @Stateless EJBs and the jdbc connections. seem as though app was reusing a pooled connection and it did not get the latest data, but glad it's working as expected now.
