Eviction it was not in my configuration i added, but i could not restart tomee yet because i have users in the webapp
2014-02-13 16:28 GMT-06:00 Romain Manni-Bucau <[email protected]>: > Hmm with validation query and eviction configured it should wirk, maybe > screenshit the jmx config > Le 13 févr. 2014 21:48, "José Luis Cetina" <[email protected]> a écrit > : > > > Sorry i copy/paste the same values, here are again > > > > Now: 14:46 > > In server 1, now is in 95 > > In server 2, now is in 63 lets see if after a while it decrease. > > > > At: 13:08 hrs > > > > In server 1, now is in 77 > > In server 2, now is in 40 lets see if after a while it decrease. > > > > What could be happening? > > > > > > 2014-02-13 14:47 GMT-06:00 José Luis Cetina <[email protected]>: > > > > > @Romain the size of the datasource still growing: > > > > > > > > > Now: 14:46 > > > In server 1, now is in 77 > > > In server 2, now is in 40 lets see if after a while it decrease. > > > > > > At: 13:08 hrs > > > > > > In server 1, now is in 77 > > > In server 2, now is in 40 lets see if after a while it decrease. > > > > > > What could be happening? > > > > > > > > > > > > 2014-02-13 14:42 GMT-06:00 José Luis Cetina <[email protected]>: > > > > > > The apps are running GREAT!! i will share what is my infraestructure: > > >> > > >> 1 Apache Server at front (configure with workers for tomee instances) > > >> 1 Database server with mysql (All the resources are available just for > > >> mysql) > > >> 2 Tomee server for production (they do DB operations to database > server, > > >> here i have all the available resource just for TomEE) > > >> 1 Tomee server for testing and jira issue tracker > > >> > > >> All of them running great, my server are intel i5 with 16gb of ram > with > > >> debian 6. > > >> > > >> My app is an ear, with 6 webapps and 3 own libraries + 1 ejb module, > > >> today i reach to 450 users from only 1 weeek. The app has more than > 650 > > >> user's, by the way the mainly app has only 1 week at the web and is > > >> responding well, the only problem that i had is that the pull get > > empty, i > > >> get that error just today. From yesterday to today we get just 200 new > > >> users and they are interacting with any other issue. > > >> > > >> What i can see is that the active connections still growing it just > time > > >> to reach the limite (500) but im monitoring, i will let you know. > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> 2014-02-13 14:29 GMT-06:00 Howard W. Smith, Jr. < > [email protected] > > >: > > >> > > >> 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. > > >>> > > >> > > >> > > >> > > >> -- > > >> ------------------------------------------------------------------- > > >> *José Luis Cetina* > > >> ------------------------------------------------------------------- > > >> > > > > > > > > > > > > -- > > > ------------------------------------------------------------------- > > > *José Luis Cetina* > > > ------------------------------------------------------------------- > > > > > > > > > > > -- > > ------------------------------------------------------------------- > > *José Luis Cetina* > > ------------------------------------------------------------------- > > > -- ------------------------------------------------------------------- *José Luis Cetina* -------------------------------------------------------------------
