В Втр, 07/11/2006 в 21:44 +0100, Julien Anguenot пишет: > I experienced other problems even after the tomcat configuration changes > I mentioned in a previous thread : the requests are really slow and I > got MemoryError exception after couple of requests.
Didn't met this behaviour before. > I don't know if whether or not this is related to the JCA connection and > the CachedConnectionManager of JBoss. I don't have time to check out > right now though... By going back on a 4.0.4 GA, I don't experienced > these problems anymore. > > Ruslan, have you been working on the JCA problem and / or Nuxeo5 > migration ? I traced web layer to see what happens there and it turns this way: DocumentManagerBusinessDelegate stateful session bean acquires connection (cast to DocumentManagerBean) and closes it when bean is destroyed. Obviously stateful bean is not always destroyed when request is finished, so we see this message about 'Closing connection...'. In this particular case it shouldn't be a problem because in code on bean's destruction connection will be released, so i think we can safely comment CachedConnectionValve in server.xml for this case. Another similar connection issue i met with SQLDirectory when logging with incorrect user/password, but in checkins i saw George did something about it. I'm updating currently and will try to deploy to see if i meet that memory error you met before. > > I'm afraid we will have to release Nuxeo 5.0 on a 4.0.4 GA considering > the time frame of ours... > Probably.. Ruslan _______________________________________________ ECM mailing list [email protected] http://lists.nuxeo.com/mailman/listinfo/ecm
