Apache Tomcat crashing...

[Stefan Ziegler]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Hi
after running Apache Tomcat for a whole month without problems, it crashes now too often (after approx. 2 days). The error I get: "java.lang.OutOfMemoryError: requested 140 bytes for CHeapObj-new. Out of swap space?"

My JVM options:
export MALLOC_CHECK_=0
JAVA_OPTS="-Djava.awt.headless=true"
JAVA_OPTS="$JAVA_OPTS -server "
JAVA_OPTS="$JAVA_OPTS -XX:SoftRefLRUPolicyMSPerMB=36000 "
JAVA_OPTS="$JAVA_OPTS -Xms128m -Xmx768m "
JAVA_OPTS="$JAVA_OPTS -XX:PermSize=128m "
JAVA_OPTS="$JAVA_OPTS -XX:MaxPermSize=256m "

Is there a way to find out which process makes Tomcat crashing? (I have two other servlets running in Tomcat) And how to avoid crashing Tomcat this often? [GeoServer 1.6.4b, Apache Tomcat 5.5.25 on a Red Hat Enterprise Linux ES release 4 (Nahant Update 6)]

regards
Stefan

Mit freundlichem Gruss
Stefan Ziegler
Leiter Aufsicht

Kanton Solothurn
Bau- und Justizdepartement
Amt für Geoinformation
Rötistrasse 4
4501 Solothurn
Telefon [phone]
Telefax 032 627 75 98
stefan.ziegler@...
http://www.so.ch

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@...
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Arne Kepp]

I don't have a clear answer, but you may be able to peak into the
process by running visualvm: https://visualvm.dev.java.net/

We have several GeoServer instances that have been up for extended
periods of time, so I'd be surprised if there are major memory leaks in
the WMS / Shapefile / Postgis context.

Other relevant questions
1) What version of Java are you running?
2) How much physical memory does the machine actually have? Try setting
both Xms and Xmx to 512
3) Alternatively, move GeoServer to it's own application server (can be
on the same machine), see what eats memory.

-Arne

Ziegler Stefan wrote:

> Hi
> after running Apache Tomcat for a whole month without problems, it
> crashes now too often (after approx. 2 days). The error I get:
> "java.lang.OutOfMemoryError: requested 140 bytes for CHeapObj-new. Out
> of swap space?"
>
> My JVM options:
> export MALLOC_CHECK_=0
> JAVA_OPTS="-Djava.awt.headless=true"
> JAVA_OPTS="$JAVA_OPTS -server "
> JAVA_OPTS="$JAVA_OPTS -XX:SoftRefLRUPolicyMSPerMB=36000 "
> JAVA_OPTS="$JAVA_OPTS -Xms128m -Xmx768m "
> JAVA_OPTS="$JAVA_OPTS -XX:PermSize=128m "
> JAVA_OPTS="$JAVA_OPTS -XX:MaxPermSize=256m "
>
> Is there a way to find out which process makes Tomcat crashing? (I
> have two other servlets running in Tomcat) And how to avoid crashing
> Tomcat this often? [GeoServer 1.6.4b, Apache Tomcat 5.5.25 on a Red
> Hat Enterprise Linux ES release 4 (Nahant Update 6)]
>
> regards
> Stefan
>
> Mit freundlichem Gruss
> Stefan Ziegler
> Leiter Aufsicht
>
> Kanton Solothurn
> Bau- und Justizdepartement
> Amt für Geoinformation
> Rötistrasse 4
> 4501 Solothurn
> Telefon [phone]
> Telefax 032 627 75 98
> stefan.ziegler@...
> http://www.so.ch
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> ------------------------------------------------------------------------
>
> _______________________________________________
> Geoserver-users mailing list
> Geoserver-users@...
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>  

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@...
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Stefan Ziegler]

Some parts of this message have been removed. Learn more about Nabble's security policy.

> 1) What version of Java are you running?
vm_info: Java HotSpot(TM) Server VM (1.6.0_03-b05) for linux-x86, built on Sep 24 2007 22:32:39 by "java_re" with gcc 3.2.1-7a (J2SE release)

> 2) How much physical memory does the machine actually have?
8 gigs

> Try setting
> both Xms and Xmx to 512
Done.

> 3) Alternatively, move GeoServer to it's own application
> server (can be
> on the same machine), see what eats memory.
Will discuss it with the admin...

Thanks so far!
Stefan

>
> -Arne
>
> Ziegler Stefan wrote:
> > Hi
> > after running Apache Tomcat for a whole month without problems, it
> > crashes now too often (after approx. 2 days). The error I get:
> > "java.lang.OutOfMemoryError: requested 140 bytes for
> CHeapObj-new. Out
> > of swap space?"
> >
> > My JVM options:
> > export MALLOC_CHECK_=0
> > JAVA_OPTS="-Djava.awt.headless=true"
> > JAVA_OPTS="$JAVA_OPTS -server "
> > JAVA_OPTS="$JAVA_OPTS -XX:SoftRefLRUPolicyMSPerMB=36000 "
> > JAVA_OPTS="$JAVA_OPTS -Xms128m -Xmx768m "
> > JAVA_OPTS="$JAVA_OPTS -XX:PermSize=128m "
> > JAVA_OPTS="$JAVA_OPTS -XX:MaxPermSize=256m "
> >

> > Is there a way to find out which process makes Tomcat crashing? (I
> > have two other servlets running in Tomcat) And how to avoid
> crashing
> > Tomcat this often? [GeoServer 1.6.4b, Apache Tomcat 5.5.25 on a Red
> > Hat Enterprise Linux ES release 4 (Nahant Update 6)]
> >
> > regards
> > Stefan
> >
> > Mit freundlichem Gruss
> > Stefan Ziegler
> > Leiter Aufsicht
> >
> > Kanton Solothurn
> > Bau- und Justizdepartement
> > Amt für Geoinformation
> > Rötistrasse 4
> > 4501 Solothurn
> > Telefon [phone]
> > Telefax 032 627 75 98
> > stefan.ziegler@...
> > http://www.so.ch
> >
> --------------------------------------------------------------
> ----------
> >
> >
> --------------------------------------------------------------
> -----------
> > This SF.Net email is sponsored by the Moblin Your Move
> Developer's challenge
> > Build the coolest Linux based applications with Moblin SDK
> & win great prizes
> > Grand prize is a trip for two to an Open Source event
> anywhere in the world
> > http://moblin-contest.org/redirect.php?banner_id=100&url=/
> >
> --------------------------------------------------------------
> ----------
> >
> > _______________________________________________
> > Geoserver-users mailing list
> > Geoserver-users@...
> > https://lists.sourceforge.net/lists/listinfo/geoserver-users
> >
>
>

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@...
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Mika Lehtonen]

Hi Stefan,

I found this:

The next improvement is visible when the system is almost out of swap
space and an allocation from the native heap fails in the VM. In that
case the VM aborts and you get a one-line error such as the following:

  Exception java.lang.OutOfMemoryError: requested 16 bytes for CHeapObj-new. Out of swap space?

This message has been known to confuse a lot of developers. At first
glance it might it might look like that the java heap is full. Of course
if you increase the size of the heap with the -mx option it might make
the problem worse as the larger java heap means there is less native
memory available.

from: http://blogs.sun.com/alanb/entry/outofmemoryerror_looks_a_bit_better


I don't know whether it will help but maybe you can give it a try. Could
there really be problems with the swap space? You'd better check it.

- mika -


Ziegler Stefan kirjoitti:

> Hi
> after running Apache Tomcat for a whole month without problems, it
> crashes now too often (after approx. 2 days). The error I get:
> "java.lang.OutOfMemoryError: requested 140 bytes for CHeapObj-new. Out
> of swap space?"
>
> My JVM options:
> export MALLOC_CHECK_=0
> JAVA_OPTS="-Djava.awt.headless=true"
> JAVA_OPTS="$JAVA_OPTS -server "
> JAVA_OPTS="$JAVA_OPTS -XX:SoftRefLRUPolicyMSPerMB=36000 "
> JAVA_OPTS="$JAVA_OPTS -Xms128m -Xmx768m "
> JAVA_OPTS="$JAVA_OPTS -XX:PermSize=128m "
> JAVA_OPTS="$JAVA_OPTS -XX:MaxPermSize=256m "
>
> Is there a way to find out which process makes Tomcat crashing? (I
> have two other servlets running in Tomcat) And how to avoid crashing
> Tomcat this often? [GeoServer 1.6.4b, Apache Tomcat 5.5.25 on a Red
> Hat Enterprise Linux ES release 4 (Nahant Update 6)]
>
> regards
> Stefan
>
> Mit freundlichem Gruss
> Stefan Ziegler
> Leiter Aufsicht
>
> Kanton Solothurn
> Bau- und Justizdepartement
> Amt für Geoinformation
> Rötistrasse 4
> 4501 Solothurn
> Telefon [phone]
> Telefax 032 627 75 98
> stefan.ziegler@...
> http://www.so.ch
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> ------------------------------------------------------------------------
>
> _______________________________________________
> Geoserver-users mailing list
> Geoserver-users@...
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>  

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@...
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Stefan Ziegler]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Swap space looks like this:
total used free shared buffers cached
Mem: 8306064 6183208 2122856 0 60492 5620972
-/+ buffers/cache: 501744 7804320
Swap: 4096532 656 4095876

Thanks for the link. The "Troubleshooting and Diagnostic Guide" seems to be full of information but it's getting a little bit late for this hardcore java action (and a new episode of "Californication" will be aired in half an hour ;)).

I almost forgot: There was an older trunk version of GeoServer 1.7 (with the GeoSearch module) and GeoWebCache running in Tomcat.

regards
Stefan

> -----Ursprüngliche Nachricht-----
> Von: Lehtonen, Mika [mailto:mika@...]
> Gesendet am: Donnerstag, 14. August 2008 22:29
> An: geoserver-users
> Betreff: Re: [Geoserver-users] Apache Tomcat crashing...
>
> Hi Stefan,
>
> I found this:
>
> The next improvement is visible when the system is almost out of swap
> space and an allocation from the native heap fails in the VM. In that
> case the VM aborts and you get a one-line error such as the following:
>
> Exception java.lang.OutOfMemoryError: requested 16 bytes
> for CHeapObj-new. Out of swap space?
>
> This message has been known to confuse a lot of developers. At first
> glance it might it might look like that the java heap is
> full. Of course
> if you increase the size of the heap with the -mx option it
> might make
> the problem worse as the larger java heap means there is less native
> memory available.
>
> from:
> http://blogs.sun.com/alanb/entry/outofmemoryerror_looks_a_bit_better
>
>
> I don't know whether it will help but maybe you can give it a
> try. Could
> there really be problems with the swap space? You'd better check it.
>
> - mika -
>
>
> Ziegler Stefan kirjoitti:
> > Hi
> > after running Apache Tomcat for a whole month without problems, it
> > crashes now too often (after approx. 2 days). The error I get:
> > "java.lang.OutOfMemoryError: requested 140 bytes for
> CHeapObj-new. Out
> > of swap space?"
> >
> > My JVM options:
> > export MALLOC_CHECK_=0
> > JAVA_OPTS="-Djava.awt.headless=true"
> > JAVA_OPTS="$JAVA_OPTS -server "
> > JAVA_OPTS="$JAVA_OPTS -XX:SoftRefLRUPolicyMSPerMB=36000 "
> > JAVA_OPTS="$JAVA_OPTS -Xms128m -Xmx768m "
> > JAVA_OPTS="$JAVA_OPTS -XX:PermSize=128m "
> > JAVA_OPTS="$JAVA_OPTS -XX:MaxPermSize=256m "
> >
> > Is there a way to find out which process makes Tomcat crashing? (I
> > have two other servlets running in Tomcat) And how to avoid
> crashing
> > Tomcat this often? [GeoServer 1.6.4b, Apache Tomcat 5.5.25 on a Red
> > Hat Enterprise Linux ES release 4 (Nahant Update 6)]
> >
> > regards
> > Stefan
> >
> > Mit freundlichem Gruss
> > Stefan Ziegler
> > Leiter Aufsicht
> >
> > Kanton Solothurn
> > Bau- und Justizdepartement
> > Amt für Geoinformation
> > Rötistrasse 4
> > 4501 Solothurn
> > Telefon [phone]
> > Telefax 032 627 75 98
> > stefan.ziegler@...
> > http://www.so.ch
> >
> --------------------------------------------------------------
> ----------
> >
> >
> --------------------------------------------------------------
> -----------
> > This SF.Net email is sponsored by the Moblin Your Move
> Developer's challenge
> > Build the coolest Linux based applications with Moblin SDK
> & win great prizes
> > Grand prize is a trip for two to an Open Source event
> anywhere in the world
> > http://moblin-contest.org/redirect.php?banner_id=100&url=/
> >
> --------------------------------------------------------------
> ----------
> >
> > _______________________________________________
> > Geoserver-users mailing list
> > Geoserver-users@...
> > https://lists.sourceforge.net/lists/listinfo/geoserver-users
> >
>
>
> --------------------------------------------------------------
> -----------
> This SF.Net email is sponsored by the Moblin Your Move
> Developer's challenge
> Build the coolest Linux based applications with Moblin SDK &
> win great prizes
> Grand prize is a trip for two to an Open Source event
> anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Geoserver-users mailing list
> Geoserver-users@...
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@...
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Arne Kepp]

Yeah, our setup is pretty similar, except I use Tomcat 6.x, so that
sounds good. Java 6 lets you use tools like visualvm remotely, so that
simplifies things a bit.

I would probably increase Xms and Xmx to at least 1024 Mb (unless you
really need it for other applications). Rendering big WMS images with 32
bit color depth is not cheap, but people run GeoServer with much less.

-Arne



Ziegler Stefan wrote:

> > 1) What version of Java are you running?
> vm_info: Java HotSpot(TM) Server VM (1.6.0_03-b05) for linux-x86,
> built on Sep 24 2007 22:32:39 by "java_re" with gcc 3.2.1-7a (J2SE
> release)
>
> > 2) How much physical memory does the machine actually have?
> 8 gigs
>
> > Try setting
> > both Xms and Xmx to 512
> Done.
>
> > 3) Alternatively, move GeoServer to it's own application
> > server (can be
> > on the same machine), see what eats memory.
> Will discuss it with the admin...
>
> Thanks so far!
> Stefan
>
> >
> > -Arne
> >
> > Ziegler Stefan wrote:
> > > Hi
> > > after running Apache Tomcat for a whole month without problems, it
> > > crashes now too often (after approx. 2 days). The error I get:
> > > "java.lang.OutOfMemoryError: requested 140 bytes for
> > CHeapObj-new. Out
> > > of swap space?"
> > >
> > > My JVM options:
> > > export MALLOC_CHECK_=0
> > > JAVA_OPTS="-Djava.awt.headless=true"
> > > JAVA_OPTS="$JAVA_OPTS -server "
> > > JAVA_OPTS="$JAVA_OPTS -XX:SoftRefLRUPolicyMSPerMB=36000 "
> > > JAVA_OPTS="$JAVA_OPTS -Xms128m -Xmx768m "
> > > JAVA_OPTS="$JAVA_OPTS -XX:PermSize=128m "
> > > JAVA_OPTS="$JAVA_OPTS -XX:MaxPermSize=256m "
> > >
>
> > > Is there a way to find out which process makes Tomcat crashing? (I
> > > have two other servlets running in Tomcat) And how to avoid
> > crashing
> > > Tomcat this often? [GeoServer 1.6.4b, Apache Tomcat 5.5.25 on a Red
> > > Hat Enterprise Linux ES release 4 (Nahant Update 6)]
> > >
> > > regards
> > > Stefan
> > >
> > > Mit freundlichem Gruss
> > > Stefan Ziegler
> > > Leiter Aufsicht
> > >
> > > Kanton Solothurn
> > > Bau- und Justizdepartement
> > > Amt für Geoinformation
> > > Rötistrasse 4
> > > 4501 Solothurn
> > > Telefon [phone]
> > > Telefax 032 627 75 98
> > > stefan.ziegler@...
> > > http://www.so.ch
> > >
> > --------------------------------------------------------------
> > ----------
> > >
> > >
> > --------------------------------------------------------------
> > -----------
> > > This SF.Net email is sponsored by the Moblin Your Move
> > Developer's challenge
> > > Build the coolest Linux based applications with Moblin SDK
> > & win great prizes
> > > Grand prize is a trip for two to an Open Source event
> > anywhere in the world
> > > http://moblin-contest.org/redirect.php?banner_id=100&url=/
> > >
> > --------------------------------------------------------------
> > ----------
> > >
> > > _______________________________________________
> > > Geoserver-users mailing list
> > > Geoserver-users@...
> > > https://lists.sourceforge.net/lists/listinfo/geoserver-users
> > >
> >
> >

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@...
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Andrea Aime-4]

Ziegler Stefan ha scritto:

> Swap space looks like this:
> total used free shared buffers cached
> Mem: 8306064 6183208 2122856 0 60492 5620972
> -/+ buffers/cache: 501744 7804320
> Swap: 4096532 656 4095876
>
> Thanks for the link. The "Troubleshooting and Diagnostic Guide" seems to
> be full of information but it's getting a little bit late for this
> hardcore java action (and a new episode of "Californication" will be
> aired in half an hour ;)).

Looking at the page Jukka linked I see this:

"In Mustang this condition will trigger the VM to invoke the fatal error
handling mechanism. This means you should get a fatal error log as you
would get with a normal (abnormal?) crash. The fatal error log is named
hs_err_<pid>.log and contains useful information about the thread,
process, and system at the time of the crash. In the case of native heap
exhaustion then the heap memory and memory map information in the log
can be useful. The exact format is version and platform specific and you
will get more information in the J2SE Troubleshooting Guide."

Mumble, can we see the contents of that hs_err_<pid>.log file?
Cheers
Andrea

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@...
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Stefan Ziegler]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Hi Andrea
see the attached files. It just happened again on a different server. After taking a look at the log files, it seems that it happened during the same process. I stumbled across "org.geotools.renderer.shape.ShapefileRenderer.paint" which makes me think of some shapefiles I'm using (besides postgis). One of it are dissolved streets (some 10000 lines into one. I've done it with ArcView so I think it's actually a multiline with a lot of lines). Ogrinfo output looks ok. But that's all just guessing...

regards
Stefan

> -----Ursprüngliche Nachricht-----
> Von: Andrea Aime [mailto:aaime@...]
> Gesendet am: Montag, 18. August 2008 12:01
> An: Ziegler Stefan
> Cc: geoserver-users; mika
> Betreff: Re: [Geoserver-users] Apache Tomcat crashing...
>
> Ziegler Stefan ha scritto:
> > Swap space looks like this:
> > total used free shared buffers cached
> > Mem: 8306064 6183208 2122856 0 60492 5620972
> > -/+ buffers/cache: 501744 7804320
> > Swap: 4096532 656 4095876
> >
> > Thanks for the link. The "Troubleshooting and Diagnostic
> Guide" seems to
> > be full of information but it's getting a little bit late for this
> > hardcore java action (and a new episode of
> "Californication" will be
> > aired in half an hour ;)).
>
> Looking at the page Jukka linked I see this:
>
> "In Mustang this condition will trigger the VM to invoke the
> fatal error
> handling mechanism. This means you should get a fatal error
> log as you
> would get with a normal (abnormal?) crash. The fatal error
> log is named
> hs_err_<pid>.log and contains useful information about the thread,
> process, and system at the time of the crash. In the case of
> native heap
> exhaustion then the heap memory and memory map information in the log
> can be useful. The exact format is version and platform
> specific and you
> will get more information in the J2SE Troubleshooting Guide."
>
> Mumble, can we see the contents of that hs_err_<pid>.log file?
> Cheers
> Andrea
>

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@...
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Stefan Ziegler]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Hi Andrea
I sent the logfiles to the mailinglist, they're awaiting moderator approval. Or should I send you the files in a different way? (Internet) Tomcat crashed again in this very moment (after 4 days). Exactly same errors in the hs_err_<pid>.log file.

regards
Stefan

> -----Ursprüngliche Nachricht-----
> Von: Andrea Aime [mailto:aaime@...]
> Gesendet am: Montag, 18. August 2008 12:01
> An: Ziegler Stefan
> Cc: geoserver-users; mika
> Betreff: Re: [Geoserver-users] Apache Tomcat crashing...
>
> Ziegler Stefan ha scritto:
> > Swap space looks like this:
> > total used free shared buffers cached
> > Mem: 8306064 6183208 2122856 0 60492 5620972
> > -/+ buffers/cache: 501744 7804320
> > Swap: 4096532 656 4095876
> >
> > Thanks for the link. The "Troubleshooting and Diagnostic
> Guide" seems to
> > be full of information but it's getting a little bit late for this
> > hardcore java action (and a new episode of
> "Californication" will be
> > aired in half an hour ;)).
>
> Looking at the page Jukka linked I see this:
>
> "In Mustang this condition will trigger the VM to invoke the
> fatal error
> handling mechanism. This means you should get a fatal error
> log as you
> would get with a normal (abnormal?) crash. The fatal error
> log is named
> hs_err_<pid>.log and contains useful information about the thread,
> process, and system at the time of the crash. In the case of
> native heap
> exhaustion then the heap memory and memory map information in the log
> can be useful. The exact format is version and platform
> specific and you
> will get more information in the J2SE Troubleshooting Guide."
>
> Mumble, can we see the contents of that hs_err_<pid>.log file?
> Cheers
> Andrea
>

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@...
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Stefan Ziegler]

Some parts of this message have been removed. Learn more about Nabble's security policy.

A short update: I think I was able to reproduce the crash. It happened after trying to reproject the data from the native srs to epgs:4326. The requested wms layer is cascaded in MapServer with aerial photographs (to obtain a google like appearance). It does not seem to crash with requests in the native srs.

Stefan

> -----Ursprüngliche Nachricht-----
> Von: Andrea Aime [mailto:aaime@...]
> Gesendet am: Montag, 18. August 2008 12:01
> An: Ziegler Stefan
> Cc: geoserver-users; mika
> Betreff: Re: [Geoserver-users] Apache Tomcat crashing...
>
> Ziegler Stefan ha scritto:
> > Swap space looks like this:
> > total used free shared buffers cached
> > Mem: 8306064 6183208 2122856 0 60492 5620972
> > -/+ buffers/cache: 501744 7804320
> > Swap: 4096532 656 4095876
> >
> > Thanks for the link. The "Troubleshooting and Diagnostic
> Guide" seems to
> > be full of information but it's getting a little bit late for this
> > hardcore java action (and a new episode of
> "Californication" will be
> > aired in half an hour ;)).
>
> Looking at the page Jukka linked I see this:
>
> "In Mustang this condition will trigger the VM to invoke the
> fatal error
> handling mechanism. This means you should get a fatal error
> log as you
> would get with a normal (abnormal?) crash. The fatal error
> log is named
> hs_err_<pid>.log and contains useful information about the thread,
> process, and system at the time of the crash. In the case of
> native heap
> exhaustion then the heap memory and memory map information in the log
> can be useful. The exact format is version and platform
> specific and you
> will get more information in the J2SE Troubleshooting Guide."
>
> Mumble, can we see the contents of that hs_err_<pid>.log file?
> Cheers
> Andrea
>

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@...
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Andrea Aime-4]

Ziegler Stefan ha scritto:
> A short update: I think I was able to reproduce the crash. It happened
> after trying to reproject the data from the native srs to epgs:4326. The
> requested wms layer is cascaded in MapServer with aerial photographs (to
> obtain a google like appearance). It does not seem to crash with
> requests in the native srs.

There are probably two things at work here. The first is a solid bug
in the Sun JVM, if the shape is problematic, it should report an
error, not crash like this. Trying to upgrade the JVM _might_ solve
the issue.

Besides this, maybe the shapefile renderer is being too aggressive in
trying to simplify the geometry before rendering it. I've fixed
a related issue recently (mid July), you might want to grab a
nightly here: http://gridlock.openplans.org/geoserver/1.6.x/
and see if that fixes your issue.

That release is quite close to being turned into 1.6.5.
Cheers
Andrea

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@...
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Stefan Ziegler]

Some parts of this message have been removed. Learn more about Nabble's security policy.

If I can prevent crashing Tomcat by not providing reprojecting I'm going to wait for 1.6.5 (and test a nightly build now). Updating JWM will definitely be done.
Thanks.
Stefan

> -----Ursprüngliche Nachricht-----
> Von: Andrea Aime [mailto:aaime@...]
> Gesendet am: Montag, 18. August 2008 17:23
> An: Ziegler Stefan
> Cc: geoserver-users
> Betreff: Re: AW: Re: [Geoserver-users] Apache Tomcat crashing...
>
> Ziegler Stefan ha scritto:
> > A short update: I think I was able to reproduce the crash.
> It happened
> > after trying to reproject the data from the native srs to
> epgs:4326. The
> > requested wms layer is cascaded in MapServer with aerial
> photographs (to
> > obtain a google like appearance). It does not seem to crash with
> > requests in the native srs.
>
> There are probably two things at work here. The first is a solid bug
> in the Sun JVM, if the shape is problematic, it should report an
> error, not crash like this. Trying to upgrade the JVM _might_ solve
> the issue.
>
> Besides this, maybe the shapefile renderer is being too aggressive in
> trying to simplify the geometry before rendering it. I've fixed
> a related issue recently (mid July), you might want to grab a
> nightly here: http://gridlock.openplans.org/geoserver/1.6.x/
> and see if that fixes your issue.
>
> That release is quite close to being turned into 1.6.5.
> Cheers
> Andrea
>

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@...
https://lists.sourceforge.net/lists/listinfo/geoserver-users