Am 27.08.2007 um 07:48 schrieb Jayan Chirayath Kurian: > In tomcat 6.0 configure, I have java options > > (1) > > -Djava.endorsed.dirs=C:\Program Files\Apache Software Foundation > \Tomcat 6.0\common\endorsed > > -Djava.io.tmpdir=C:\Program Files\Apache Software Foundation\Tomcat > 6.0\temp > > -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager > > -Djava.util.logging.config.file=C:\Program Files\Apache Software > Foundation\Tomcat 6.0\conf\logging.properties > > The interface also has options for > > (2) Internal Memory pool > > (3) Maximum Memory pool > > (4) Thread stack size > > Would it be better to give memory value at (2) ….(4) or in java > options given in (1). One will take precedence over the other. I bet (2) - (4) takes precedence if set explicitly, but ... I would advise to set either the one *or* the other.
Tomcat probably wont mind you to set both and follow only one of them, but it is yourself who gets screwed up, if you try both at once. Precedence order should be documented in the official docs, but you can certainly find out yourself by try and error (which would take more time for me, so I would search the docs). (2) - (4) are probably easier to rediscover in case you fail to document your final solution properly and are asking yourself what you actually did one day in the future, so I would choose this approach. Bye, Christian ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
