All,
Well, it's happening again. This message writes to the logs, over and over
every few milliseconds, and the log files quickly become many GIGS in size:
535035713 [WARNING] WeakCollection - NullPointerException
java.lang.NullPointerException
at
org.geotools.util.WeakCollectionCleaner.run(WeakCollectionCleaner.java:76)
I've narrowed it down to happening when I try to shutdown Tomcat to update
files/settings/etc. The proccess never shuts down unless we kill it. Once
killed, I remove the log files, start Tomcat, and it all works fine....but
that's not the best way to restart Tomcat.
Running GS 1.4.0. The problem seems to have started when I upgraded from
the last release candidate, though it's hard to pinpoint because I didn't
notice for a week or so.
Any ideas?
Thanks,
Steve
Stephen Crawford
Center for Environmental Informatics
GeoVISTA Center
The Pennsylvania State University
814.865.9905
src176@anonymised.com
Let's ping GeoTools, as I remember some discussions about such things there.
Do you have a longer stack trace at all? And what was the last release candidate that was working for you?
thanks,
Chris
Stephen Crawford wrote:
All,
Well, it's happening again. This message writes to the logs, over and over
every few milliseconds, and the log files quickly become many GIGS in size:
535035713 [WARNING] WeakCollection - NullPointerException
java.lang.NullPointerException
at
org.geotools.util.WeakCollectionCleaner.run(WeakCollectionCleaner.java:76)
I've narrowed it down to happening when I try to shutdown Tomcat to update
files/settings/etc. The proccess never shuts down unless we kill it. Once
killed, I remove the log files, start Tomcat, and it all works fine....but
that's not the best way to restart Tomcat.
Running GS 1.4.0. The problem seems to have started when I upgraded from
the last release candidate, though it's hard to pinpoint because I didn't
notice for a week or so.
Any ideas?
Thanks,
Steve
Stephen Crawford
Center for Environmental Informatics
GeoVISTA Center
The Pennsylvania State University
814.865.9905
src176@anonymised.com
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
!DSPAM:1003,45b7c4b6215341804284693!
--
Chris Holmes
The Open Planning Project
http://topp.openplans.org
Chris Holmes ha scritto:
Let's ping GeoTools, as I remember some discussions about such things there.
Do you have a longer stack trace at all? And what was the last release candidate that was working for you?
thanks,
Chris
Stephen Crawford wrote:
All,
Well, it's happening again. This message writes to the logs, over and over
every few milliseconds, and the log files quickly become many GIGS in size:
535035713 [WARNING] WeakCollection - NullPointerException
java.lang.NullPointerException
at
org.geotools.util.WeakCollectionCleaner.run(WeakCollectionCleaner.java:76) I've narrowed it down to happening when I try to shutdown Tomcat to update
files/settings/etc. The proccess never shuts down unless we kill it.
I see... somehow the java runtime is no more behaving properly during shutdown. If the call in weakcollectioncleaner does not block anymore as
stated in the javadoc ("Removes the next reference object in this queue, blocking until one becomes available.") the weak collection cleaner
thread runs an infinite loop without ever blocking, no wonder it generates a ton of logs...
Can you give me some more details on the operating system and jdk (minor version too)?
I know we have had issues with the jdk distributed along with Gentoo
(apparently it's not a normal Sun jdk).
Cheers
Andrea
Hi Andrea,
Running Tomcat 5.5.15 with jdk 1_5_0_06 on Red Hat Linux, on two
load-balanced servers. The postGIS db currently resides on a single desktop
machine in our network; we just this week have postgreSQL/postGIS on our
production db servers and will be moving the db's soon.
I don't really have more of an error log since it was so huge last time I
just deleted it instead of trying to open it.
Thanks,
Steve
-----Original Message-----
From: geoserver-users-bounces@lists.sourceforge.net
[mailto:geoserver-users-bounces@lists.sourceforge.net] On Behalf Of Andrea
Aime
Sent: Thursday, January 25, 2007 3:37 AM
To: Chris Holmes
Cc: Stephen Crawford; geoserver-users@lists.sourceforge.net;
geotools-devel@lists.sourceforge.net
Subject: Re: [Geoserver-users] Null pointer exception
Chris Holmes ha scritto:
Let's ping GeoTools, as I remember some discussions about such things
there.
Do you have a longer stack trace at all? And what was the last
release candidate that was working for you?
thanks,
Chris
Stephen Crawford wrote:
All,
Well, it's happening again. This message writes to the logs, over
and over every few milliseconds, and the log files quickly become
many GIGS in
size:
535035713 [WARNING] WeakCollection - NullPointerException
java.lang.NullPointerException
at
org.geotools.util.WeakCollectionCleaner.run(WeakCollectionCleaner.jav
a:76) I've narrowed it down to happening when I try to shutdown
Tomcat to update files/settings/etc. The proccess never shuts down
unless we kill it.
I see... somehow the java runtime is no more behaving properly during
shutdown. If the call in weakcollectioncleaner does not block anymore as
stated in the javadoc ("Removes the next reference object in this queue,
blocking until one becomes available.") the weak collection cleaner thread
runs an infinite loop without ever blocking, no wonder it generates a ton of
logs...
Can you give me some more details on the operating system and jdk (minor
version too)?
I know we have had issues with the jdk distributed along with Gentoo
(apparently it's not a normal Sun jdk).
Cheers
Andrea
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's
Techsay panel and you'll get the chance to share your opinions on IT &
business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Stephen Crawford ha scritto:
Hi Andrea,
Running Tomcat 5.5.15 with jdk 1_5_0_06 on Red Hat Linux, on two
load-balanced servers. The postGIS db currently resides on a single desktop
machine in our network; we just this week have postgreSQL/postGIS on our
production db servers and will be moving the db's soon.
I see... well, it seems to me the only way is to implement a workaround
to this jdk misbehaviour. I would like to talk with Martin first, but he's going to be away for a couple of days, and I'm not working on Geoserver tomorrow.
Is this compatible with your time frames?
Cheers
Andrea
Andrea Aime ha scritto:
Stephen Crawford ha scritto:
Hi Andrea,
Running Tomcat 5.5.15 with jdk 1_5_0_06 on Red Hat Linux, on two
load-balanced servers. The postGIS db currently resides on a single desktop
machine in our network; we just this week have postgreSQL/postGIS on our
production db servers and will be moving the db's soon.
I see... well, it seems to me the only way is to implement a workaround
to this jdk misbehaviour. I would like to talk with Martin first, but he's going to be away for a couple of days, and I'm not working on Geoserver tomorrow.
Opened http://jira.codehaus.org/browse/GEOT-1138, now we have to wait a little for Martin to consider the issue.
Cheers
Andrea
Andrea Aime ha scritto:
Andrea Aime ha scritto:
Stephen Crawford ha scritto:
Hi Andrea,
Running Tomcat 5.5.15 with jdk 1_5_0_06 on Red Hat Linux, on two
load-balanced servers. The postGIS db currently resides on a single desktop
machine in our network; we just this week have postgreSQL/postGIS on our
production db servers and will be moving the db's soon.
I see... well, it seems to me the only way is to implement a workaround
to this jdk misbehaviour. I would like to talk with Martin first, but he's going to be away for a couple of days, and I'm not working on Geoserver tomorrow.
Opened http://jira.codehaus.org/browse/GEOT-1138, now we have to wait a little for Martin to consider the issue.
Ok, Martin provided us with a patch. I backported it to Geotools 2.2.x and built a new 1.4.x test Geoserver. You can download it from:
http://geo.openplans.org/aaime/geoserver.war
Let me know if it works fine.
Cheers
Andrea