Hi Wolfgang,
Wolfgang Jeltsch schrieb:
Am Montag, 19. Mai 2008 11:27 schrieb Andreas Hartmann:
Hi Wolfgang,
Wolfgang Jeltsch schrieb:
some time ago I asked for help regarding an internal server error message
at the first Lenya 2.0 try. Meanwhile, I solved the problem by looking
into the logs (which were a bit hard to find). My Debian system used the
ISO-8859-15 character encoding by default and this wasn’t supported by
the JVM, I think. After having switched to UTF-8, it worked.
thanks a lot for reporting! I added an FAQ entry:
https://lenya.zones.apache.org/cms/docu/live/docu20/faq.html#faq-N1002E
-- Andreas
Thanks a lot!
I have some corrections to your entry, though.
thanks a lot too :)
I have updated the documentation accordingly.
BTW, in case you're interested in an account for editing the upcoming
website, check out this section:
https://lenya.zones.apache.org/cms/docu/live/community.html#N1007F
-- Andreas
First, I checked a second time
with ISO-8859-15, looked at the logs and detected that it’s probably not the
JVM having problems with this encoding but Cocoon. Second, I wouldn’t
mention Debian in this way in the FAQ entry. The problem is likely to occur
with other operating systems (especially other Linux distributions). In
addition, starting with the current stable version, Debian uses UTF-8 by
default. The ISO-8859-15 default was just a configuration of my server
provider (Hetzner Online AG).
So I would reformulate the FAQ text as follows:
1.3. When I request the web application, I get the error message "HTTP
ERROR: 500 Internal Server Error".
This problem might have something to do with the character encoding. Please
look in $LENYA_HOME/build/lenya/webapp/WEB-INF/logs/log4j.log for a line
like the following:
Caused by:
org.apache.cocoon.components.serializers.encoding.CharsetFactory$CharsetFactoryException:
The default encoding of this JVM "ISO8859_15" is not supported
If such a line exists, you might want to change the system’s default
character encoding to something different, e.g., UTF-8.
This solution worked on a Debian GNU/Linux 4.0 system where this problem
occured. In Debian, changing the default locale is done by running
dpkg-reconfigure locales as root.
Note that the “locales” belongs to the command line so that the command line
is “dpkg-reconfigure locales”. On the web, this should be marked up
properly, of course.
Best wishes,
Wolfgang
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
