[GeoNetwork-devel] java.lang.OutOfMemoryError on Geonetwork 2.4.3

GeoNetwork GeoNetwork Developer
1

Dear list,

I suspect there’s a memory leak problem on geonetwork 2.4.3: I did the upgrade from 2.2.0 and I keep getting java.lang.OutOfMemoryError some time after tomcat startup.

My VM configuration is:

-Xms48m -Xmx1500m -XX:MaxPermSize=256m -XX:PermSize=128m

(I increased -Xmx to 1500m see if the new version was just RAM demanding).

I also fixed some problems in Lucene indexing, should I checkin? On branches/2.4.3?

Thanks for your help

Stefano

2

Hi
I dont know if this is related to your issue

I was getting a Tomcat died on "java.lang.OutOfMemoryError: requested
2147483664 bytes for Chunk. Out of swap space?" error message last week
when running 2.4.3.

But this was just after I upgraded my jvm on linux. There appears to be a
bug in the hotspot compilation in latest sun jvm. .

I added -Xint (Operate in interpreted-only mode) to startup params. to
confirm that this bug was affecting my setup.
No more out of memory problems as soon as I added -Xint.

I then had to downgrade to my previous version of the jvm.
Cheers
Murray
--
View this message in context: http://osgeo-org.1803224.n2.nabble.com/java-lang-OutOfMemoryError-on-Geonetwork-2-4-3-tp5203547p5203637.html
Sent from the GeoNetwork developer mailing list archive at Nabble.com.

3

Hi Stefano

In 2.4.3 is included a fix for saxon and java 1.6 that produced an OutOfMemory exception:

http://osgeo-org.1803224.n2.nabble.com/SF-net-SVN-geonetwork-5999-branches-2-4-x-bin-td4937268.html#a4937268

The fix commited is for jetty, but is similar for tomcat. Please check next url to verify for tomcat statup script is fixed:

http://osgeo-org.1803224.n2.nabble.com/Re-GeoNetwork-users-Java-updates-td4935064.html

If not using java 1.6 then should be caused by other new problem. In that case is an option for you to use YourKit profiler to make a memory profiling session so can analyze the results? Other option is if you can post the geonetwork.log file to check, but please verify first if is caused by java 1.6 and saxon issue.

Regards,
Jose Garcia

On Mon, Jun 21, 2010 at 11:27 AM, Stefano Giaccio <Stefano.Giaccio@anonymised.com> wrote:

Dear list,

I suspect there’s a memory leak problem on geonetwork 2.4.3: I did the upgrade from 2.2.0 and I keep getting java.lang.OutOfMemoryError some time after tomcat startup.

My VM configuration is:

-Xms48m -Xmx1500m -XX:MaxPermSize=256m -XX:PermSize=128m

(I increased -Xmx to 1500m see if the new version was just RAM demanding).

I also fixed some problems in Lucene indexing, should I checkin? On branches/2.4.3?

Thanks for your help

Stefano

ThinkGeek and WIRED’s GeekDad team up for the Ultimate
GeekDad Father’s Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo

GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

4

Hi Murray,

Add the following to your JAVA_OPTS env variable and restart tomcat - then only the method (from Saxon XSLT) that is causing the problem will be run in interpreted mode:

-XX:CompileCommand=exclude,net/sf/saxon/event/ReceivingContentHandler.startElement

Cheers,
Simon

________________________________________
From: murray king [murray.king@anonymised.com]
Sent: Monday, 21 June 2010 7:51 PM
To: geonetwork-devel@lists.sourceforge.net
Subject: Re: [GeoNetwork-devel] java.lang.OutOfMemoryError on Geonetwork 2.4.3

Hi
I dont know if this is related to your issue

I was getting a Tomcat died on "java.lang.OutOfMemoryError: requested
2147483664 bytes for Chunk. Out of swap space?" error message last week
when running 2.4.3.

But this was just after I upgraded my jvm on linux. There appears to be a
bug in the hotspot compilation in latest sun jvm. .

I added -Xint (Operate in interpreted-only mode) to startup params. to
confirm that this bug was affecting my setup.
No more out of memory problems as soon as I added -Xint.

I then had to downgrade to my previous version of the jvm.
Cheers
Murray
--
View this message in context: http://osgeo-org.1803224.n2.nabble.com/java-lang-OutOfMemoryError-on-Geonetwork-2-4-3-tp5203547p5203637.html
Sent from the GeoNetwork developer mailing list archive at Nabble.com.

------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:

_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net

GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

5

A better solution appears to be patch the method in saxon (9.1.0.8) to remove some code required for jdk1.4 and replace it with code that works only with jdk1.5 (from 9.2HE) - this is fine for us as GN assumes 1.5 as a minimum. I'm testing this at the moment. If it proves ok then we should be able to do away with this exclusion.

Cheers,
Simon

Simon.Pigot@anonymised.com wrote:

Hi Murray,

Add the following to your JAVA_OPTS env variable and restart tomcat - then only the method (from Saxon XSLT) that is causing the problem will be run in interpreted mode:
-XX:CompileCommand=exclude,net/sf/saxon/event/ReceivingContentHandler.startElement

Cheers,
Simon

________________________________________
From: murray king [murray.king@anonymised.com]
Sent: Monday, 21 June 2010 7:51 PM
To: geonetwork-devel@lists.sourceforge.net
Subject: Re: [GeoNetwork-devel] java.lang.OutOfMemoryError on Geonetwork 2.4.3

Hi
I dont know if this is related to your issue

I was getting a Tomcat died on "java.lang.OutOfMemoryError: requested
2147483664 bytes for Chunk. Out of swap space?" error message last week
when running 2.4.3.

But this was just after I upgraded my jvm on linux. There appears to be a
bug in the hotspot compilation in latest sun jvm. .

I added -Xint (Operate in interpreted-only mode) to startup params. to
confirm that this bug was affecting my setup.
No more out of memory problems as soon as I added -Xint.

I then had to downgrade to my previous version of the jvm.
Cheers
Murray
--
View this message in context: http://osgeo-org.1803224.n2.nabble.com/java-lang-OutOfMemoryError-on-Geonetwork-2-4-3-tp5203547p5203637.html
Sent from the GeoNetwork developer mailing list archive at Nabble.com.

------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
geonetwork-devel List Signup and Options
GeoNetwork OpenSource is maintained at GeoNetwork - Geographic Metadata Catalog download | SourceForge.net

6

Thanks for your help, I'll try with the solutions that you suggested (I just got the messages as my mail server promptly stopped working yesterday) and let you know how it goes.

Cheers
Stefano

On Jun 22, 2010, at 10:15 AM, Simon Pigot wrote:

A better solution appears to be patch the method in saxon (9.1.0.8) to
remove some code required for jdk1.4 and replace it with code that works
only with jdk1.5 (from 9.2HE) - this is fine for us as GN assumes 1.5 as
a minimum. I'm testing this at the moment. If it proves ok then we
should be able to do away with this exclusion.

Cheers,
Simon

Simon.Pigot@anonymised.com wrote:

Hi Murray,

Add the following to your JAVA_OPTS env variable and restart tomcat - then only the method (from Saxon XSLT) that is causing the problem will be run in interpreted mode:

-XX:CompileCommand=exclude,net/sf/saxon/event/ReceivingContentHandler.startElement

Cheers,
Simon

________________________________________
From: murray king [murray.king@anonymised.com]
Sent: Monday, 21 June 2010 7:51 PM
To: geonetwork-devel@lists.sourceforge.net
Subject: Re: [GeoNetwork-devel] java.lang.OutOfMemoryError on Geonetwork 2.4.3

Hi
I dont know if this is related to your issue

I was getting a Tomcat died on "java.lang.OutOfMemoryError: requested
2147483664 bytes for Chunk. Out of swap space?" error message last week
when running 2.4.3.

But this was just after I upgraded my jvm on linux. There appears to be a
bug in the hotspot compilation in latest sun jvm. .

I added -Xint (Operate in interpreted-only mode) to startup params. to
confirm that this bug was affecting my setup.
No more out of memory problems as soon as I added -Xint.

I then had to downgrade to my previous version of the jvm.
Cheers
Murray
--
View this message in context: http://osgeo-org.1803224.n2.nabble.com/java-lang-OutOfMemoryError-on-Geonetwork-2-4-3-tp5203547p5203637.html
Sent from the GeoNetwork developer mailing list archive at Nabble.com.

------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork