You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Ognjen Blagojevic (JIRA)" <ji...@apache.org> on 2011/04/04 14:53:06 UTC
[jira] [Created] (DAEMON-202) Add JSVC_OPT (options for JSVC
executable) into Tomcat7.sh
Add JSVC_OPT (options for JSVC executable) into Tomcat7.sh
----------------------------------------------------------
Key: DAEMON-202
URL: https://issues.apache.org/jira/browse/DAEMON-202
Project: Commons Daemon
Issue Type: Improvement
Components: Jsvc
Affects Versions: 1.0.5
Environment: Linux
Reporter: Ognjen Blagojevic
Priority: Minor
Out-of-the box, Tomcat7.sh script runs on default JVM, which is for 32-bit Sun Java equal to 'Client' JVM.
I assume that starting tomcat on 'Server' JVM is generally better then 'Client' JVM.
Adding '$JSVC_JVM' into run, start and version actions of that script, would allow user to add e.g. "export JSVC_JVM='-jvm server'" into setenv.sh to use appropriate JVM, without need to modify the example script.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DAEMON-202) Add JSVC_OPT (options for JSVC
executable) into Tomcat7.sh
Posted by "Ognjen Blagojevic (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DAEMON-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ognjen Blagojevic updated DAEMON-202:
-------------------------------------
Attachment: tomcat7-jsvc_opts.patch
> Add JSVC_OPT (options for JSVC executable) into Tomcat7.sh
> ----------------------------------------------------------
>
> Key: DAEMON-202
> URL: https://issues.apache.org/jira/browse/DAEMON-202
> Project: Commons Daemon
> Issue Type: Improvement
> Components: Jsvc
> Affects Versions: 1.0.5
> Environment: Linux
> Reporter: Ognjen Blagojevic
> Priority: Minor
> Attachments: tomcat7-jsvc_opts.patch
>
>
> Out-of-the box, Tomcat7.sh script runs on default JVM, which is for 32-bit Sun Java equal to 'Client' JVM.
> I assume that starting tomcat on 'Server' JVM is generally better then 'Client' JVM.
> Adding '$JSVC_JVM' into run, start and version actions of that script, would allow user to add e.g. "export JSVC_JVM='-jvm server'" into setenv.sh to use appropriate JVM, without need to modify the example script.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (DAEMON-202) Add JSVC_OPT (options for JSVC
executable) into Tomcat7.sh
Posted by "Mladen Turk (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DAEMON-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mladen Turk resolved DAEMON-202.
--------------------------------
Resolution: Fixed
Fix Version/s: 1.0.6
Patch applied. Thanks!
> Add JSVC_OPT (options for JSVC executable) into Tomcat7.sh
> ----------------------------------------------------------
>
> Key: DAEMON-202
> URL: https://issues.apache.org/jira/browse/DAEMON-202
> Project: Commons Daemon
> Issue Type: Improvement
> Components: Jsvc
> Affects Versions: 1.0.5
> Environment: Linux
> Reporter: Ognjen Blagojevic
> Assignee: Mladen Turk
> Priority: Minor
> Fix For: 1.0.6
>
> Attachments: tomcat7-jsvc_opts.patch
>
>
> Out-of-the box, Tomcat7.sh script runs on default JVM, which is for 32-bit Sun Java equal to 'Client' JVM.
> I assume that starting tomcat on 'Server' JVM is generally better then 'Client' JVM.
> Adding '$JSVC_JVM' into run, start and version actions of that script, would allow user to add e.g. "export JSVC_JVM='-jvm server'" into setenv.sh to use appropriate JVM, without need to modify the example script.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira