From: Adam R. <ad...@ex...> - 2011-12-20 09:08:17
|
I doubt this is a Tomcat issue. What we need is a thread dump from the JVM so we can wee where the brokers are locked. kill -3 will give you that... On Dec 20, 2011 8:14 AM, "Chris Tomlinson" <chr...@gm...> wrote: > Hello Dannes, > > Thank you for the comment. FWIW, we've had no problem running trunk in > tomcat 7.0.11 for around a year now. I think that the questions that I'm > asking are likely pretty much internal to eXist-db but I could be way off. > > What sorts of things are you aware of not working? > > Regards, > Chris > > > On Dec 20, 2011, at 1:24 PM, Dannes Wessels wrote: > > Hi Chris, > > On Tue, Dec 20, 2011 at 4:17 AM, Chris Tomlinson < > chr...@gm...> wrote: > >> Running eXist trunk rev 15568 in tomcat 7.0.11. The tomcat is run with >> -Xmx6144m. The eXist cacheSize is 768M. The other parameters in conf.xml >> are at their defaults. After running under a normal load for some hours we >> are seeing and of course things eventually go downhill from there: >> > > I just want to note that no effort has been put jet in qualifiying > eXistdb-trunk in tomcat (6,7). Please be aware of that.... I know that some > things do not work. > > cheers > > Dannes > > > -- > eXist-db Native XML Database - http://exist-db.org > Join us on linked-in: http://www.linkedin.com/groups?gid=35624 > > > > > ------------------------------------------------------------------------------ > Write once. Port to many. > Get the SDK and tools to simplify cross-platform app development. Create > new or port existing apps to sell to consumers worldwide. Explore the > Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join > http://p.sf.net/sfu/intel-appdev > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > > |