You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Kristian Rink <kr...@zimmer428.net> on 2007/08/03 09:56:26 UTC
tomcat 6 and setenv.sh?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Folks,
after switching our production environment to tomcat 6.0.13, most of
the things work fine again by now. One thing, however, is still giving
me headaches: By now, I used to have something like
export CATALINA_OPTS="-server -Xmx512m ... "
in CATALINA_HOME/bin/setenv.sh (running Linux), which worked fine with
tc5.5.23. However, by now having settings like these in setenv.sh, I
just end up with this message...
WARNUNG: Dynamic setProperty(className,value) has been disabled, please
use explicit properties for the element you are trying to identify
03.08.2007 09:50:36 org.apache.catalina.core.AprLifecycleListener init
INFO: Loaded Apache Tomcat Native library 1.1.10. 03.08.2007 09:50:36
org.apache.catalina.core.AprLifecycleListener init INFO: APR
capabilities: IPv6 [true], sendfile [true], accept filters [false],
random [true].
... in catalina.out while tomcat refuses to start up correctly. Does
anyone have an idea what the problem is like? Is setenv.sh not
supported that way anymore in tc6.0? Is there a better way to do these
settings?
Environment:
- - Ubuntu 6.06.1 LTS
- - JDK 1.6.0-b105
- - tomcat 6.0.13, cluster-configured with two hosts
Thanks in advance for any hints and bye,
Kristian
- --
Kristian Rink * http://zimmer428.net * http://flickr.com/photos/z428/
jab: kawazu@jabber.ccc.de * icq: 48874445 * fon: ++49 176 2447 2771
"One dreaming alone, it will be only a dream; many dreaming together
is the beginning of a new reality." (Hundertwasser)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGst+xcxBAPOA1m6wRArfIAKCmMRY3GGc90o6q2NVHHAhyNxMUewCfQ9Yu
GdjSLPYqmAfRRMibc/VRXqg=
=s7UW
-----END PGP SIGNATURE-----
Re: tomcat 6 and setenv.sh?
Posted by Robert Casties <ca...@mpiwg-berlin.mpg.de>.
Kristian Rink wrote:
>
> Folks,
>
> after switching our production environment to tomcat 6.0.13, most of
> the things work fine again by now. One thing, however, is still giving
> me headaches: By now, I used to have something like
>
> export CATALINA_OPTS="-server -Xmx512m ... "
>
> in CATALINA_HOME/bin/setenv.sh (running Linux), which worked fine with
> tc5.5.23. However, by now having settings like these in setenv.sh, I
> just end up with this message...
It works fine for me with 6.0.13 (plain config, no cluster, no APR),
although I don't use "export" but just "CATALINA_OPTS=..." (the script
uses the variables itself and not the started executable).
Cheers
Robert
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: tomcat 6 and setenv.sh?
Posted by Johnny Kewl <jo...@kewlstuff.co.za>.
Hi, Kristian... listen I dont use Tomcats built in clustering, so I dont
know anything about it.
However below is the actual code that is giving you that error message and
it seems that clustering properties must not be set in CATALINA_OPTS.
Unfortunately you didnt post all your CATALINA_OPTS properties
.... however its definitely not CATALINA_OPTS or java Djava properties that
are not allowed... it seems JUST properties related to clustering will
generate this warning....
So now, you... like me, are probably wondering how one must set those
properties.... if I had to guess, I think they have to be set in the XML
configuration only.
I dont know how it works and how fancy it is, like whether one can set
properties in one manager and they propogated to members of the cluster, or
whether they have to be set for each tomcat. It seems they changed it
because one could screw clustering up thru JMX
Sorry couldnt help more... but at least you can see how the programmer is
thinking about it below.
Good luck...
----- Original Message -----
From: "Kristian Rink" <kr...@zimmer428.net>
To: "Tomcat Users List" <us...@tomcat.apache.org>
Sent: Friday, August 03, 2007 9:56 AM
Subject: tomcat 6 and setenv.sh?
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> Folks,
>
> after switching our production environment to tomcat 6.0.13, most of
> the things work fine again by now. One thing, however, is still giving
> me headaches: By now, I used to have something like
>
> export CATALINA_OPTS="-server -Xmx512m ... "
>
> in CATALINA_HOME/bin/setenv.sh (running Linux), which worked fine with
> tc5.5.23. However, by now having settings like these in setenv.sh, I
> just end up with this message...
>
>
> WARNUNG: Dynamic setProperty(className,value) has been disabled, please
> use explicit properties for the element you are trying to identify
> 03.08.2007 09:50:36 org.apache.catalina.core.AprLifecycleListener init
> INFO: Loaded Apache Tomcat Native library 1.1.10. 03.08.2007 09:50:36
> org.apache.catalina.core.AprLifecycleListener init INFO: APR
> capabilities: IPv6 [true], sendfile [true], accept filters [false],
> random [true].
HERE IS THE ACTUAL CODE IN SimpleTcpCluster
public void setProperty(String name, Object value) {
if (log.isTraceEnabled())
log.trace(sm.getString("SimpleTcpCluster.setProperty", name,
value,properties.get(name)));
properties.put(name, value);
//using a dynamic way of setting properties is nice, but a security
risk
//if exposed through JMX. This way you can sit and try to guess
property names,
//we will only allow explicit property names
log.warn("Dynamic setProperty("+name+",value) has been disabled,
please use explicit properties for the element you are trying to identify");
if(started) {
// FIXME Hmm, is that correct when some DeltaManagers are direct
configured inside Context?
// Why we not support it for other elements, like sender,
receiver or membership?
// Must we restart element after change?
// if (name.startsWith("manager")) {
// String key = name.substring("manager".length() + 1);
// String pvalue = value.toString();
// for (Iterator iter = managers.values().iterator();
iter.hasNext();) {
// Manager manager = (Manager) iter.next();
// if(manager instanceof DeltaManager &&
((ClusterManager) manager).isDefaultMode()) {
// IntrospectionUtils.setProperty(manager, key,
pvalue );
// }
// }
// }
}
}
> ... in catalina.out while tomcat refuses to start up correctly. Does
> anyone have an idea what the problem is like? Is setenv.sh not
> supported that way anymore in tc6.0? Is there a better way to do these
> settings?
>
> Environment:
> - - Ubuntu 6.06.1 LTS
> - - JDK 1.6.0-b105
> - - tomcat 6.0.13, cluster-configured with two hosts
>
>
> Thanks in advance for any hints and bye,
> Kristian
>
>
> - --
> Kristian Rink * http://zimmer428.net * http://flickr.com/photos/z428/
> jab: kawazu@jabber.ccc.de * icq: 48874445 * fon: ++49 176 2447 2771
> "One dreaming alone, it will be only a dream; many dreaming together
> is the beginning of a new reality." (Hundertwasser)
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFGst+xcxBAPOA1m6wRArfIAKCmMRY3GGc90o6q2NVHHAhyNxMUewCfQ9Yu
> GdjSLPYqmAfRRMibc/VRXqg=
> =s7UW
> -----END PGP SIGNATURE-----
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org