Hi, Tony.
At least the parsing issue is resolved.
The log you posted from April 10 shows you were using build 37 at that time. I assume you are still using the same build?
I suspect you are correct that the OOM has caused the other problems.
The OOM errors have come up in a number of ways and people have been discussing that in quite a few places in the forum. Some of the other threads have some things to try:
http://forums.java.net/jive/search.jspa?threadID=&q=outofmemoryerror&objID=f56&dateRange=lastyear&userID=&numResults=15&rankBy=10001
If I recall correctly (and someone set the record straight if I'm wrong) there were some bugs that were fixed that helped this but I don't remember in which build(s) the fixes would have appeared.
It's also possible that you may just need to increase the heap space settings for the JVM in the domain.xml.
You also asked about whether GlassFish should use its own ZipFile. No, GlassFish does not provide its own implementation of ZipFile. I think the reference to ZipFile in the top stack trace reflects that the ZipFile.open method was the unlucky code that happened to be running when the space became exhausted. I don't think that the ZipFile it was trying to open was overly large or anything like that.
- Tim
[Message sent by forum member 'tjquinn' (tjquinn)]
http://forums.java.net/jive/thread.jspa?messageID=212354