I just checked and running tomcat (normal) from the symlink
/home/ron/tomcat doesn't make any different... :(
?
Ron Piterman wrote:
well, thanx but I have still no clue.
Here are both commands, as listed by ps (i broke them to make reading
easier):
>> first the normal tomcat:
>>
/usr/java/jre/bin/java
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
-Djava.util.logging.config.file=/usr/java/tomcat/conf/logging.properties
-Djava.endorsed.dirs=/usr/java/tomcat/common/endorsed
-classpath
:/usr/java/tomcat/bin/bootstrap.jar
:/usr/java/tomcat/bin/commons-logging-api.jar
-Dcatalina.base=/usr/java/tomcat
-Dcatalina.home=/usr/java/tomcat
-Djava.io.tmpdir=/usr/java/tomcat/temp
org.apache.catalina.startup.Bootstrap
start
>> then in debug mode:
>>
/usr/java/jre/bin/java
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
-Djava.util.logging.config.file=/home/ron/tomcat/conf/logging.properties
-Xdebug
-Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=n
-Djava.endorsed.dirs=/home/ron/tomcat/common/endorsed
-classpath
:/home/ron/tomcat/bin/bootstrap.jar
:/home/ron/tomcat/bin/commons-logging-api.jar
-Dcatalina.base=/home/ron/tomcat
-Dcatalina.home=/home/ron/tomcat
-Djava.io.tmpdir=/home/ron/tomcat/temp
org.apache.catalina.startup.Bootstrap start
---
Now the only difference seems to be in the catalina.home and
catalina.base parameters -
/home/ron/tomcat is a symlink to /usr/java/tomcat/
why should that make a difference ?
will try to change that and see what happens...
(will be back after the commercials :) )
Cheers,
Ron
Thom Hehl wrote:
Here is a similar problem that I had with httpd.
I was running a CGI script that was creating an output file with
international characters (characters above 127). When I ran it from
the command prompt, it was fine. When I ran the same program from
httpd, it screwed up those characters.
It turns out that the default character set I was running from the
prompt was ISO-LATIN1, but httpd was running under whatever the
character set is for 127 and down. I fixed the problem by using the
Java output stream and always specifying the character set.
Beyond that, I can't help you. Hope this helps some.
Ron Piterman wrote:
Hi all,
I have this strange encoding problem with tomcat 5.5.12:
when I start it using the startup.sh script, my tapestry pages are
served with something wrong along the encoding pipeline, so some
"special" characters like ä or ß are encoded wrong.
when I start tomcat using the catalina.sh in debug mode, everything
is fine - does someone have a clue of what or where the problem might
be?
Cheers,
Ron
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thom Hehl
Heavyweight Software for Heavyweight Needs
www.heavyweightsoftware.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
