RE: FW: IBM's RPG Strategy (was: Long Procedure Names)

Scott,

We've been running WebSphere since v1.0 and we have an application that has 
crashed the JVM on occasion the entire time. The problem with the JVM crashing 
is entirely related to resource leaks in that application. It's not really any 
different than allocating memory and never releasing it (which has been the 
bane of a Windows program we had written for us to enhance a package we 
purchased several years ago) -- you eventually run out and things go boom. On 
the other hand, we have Java apps that run without any problems. The JVM's do 
get restarted once a week but that's only because everything gets shut down for 
a full system save.

Matt

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Scott Klement
Sent: Friday, March 25, 2005 4:45 AM
To: RPG programming on the AS400 / iSeries
Subject: Re: FW: IBM's RPG Strategy (was: Long Procedure Names)



> Something is wrong if Java crashes frequently on your system. Is there
> a pattern?

Hmmm...  There's three problems that are relatively consistent:

<snip>

c) On the iSeries, there's a particular program that crashes the JVM. It's 
one that uses the HSSF classes to load a spreadsheet and update certain 
columns.  Sometimes it works fine.  Other times, it gets an error with 
memory access (illegal teraspace offset or something like that.) 
Considering that there aren't any pointers in Java, that's a little weird. 
After that happens, the next time I run it, the JVM comes crashing down, 
and won't run again until I sign off and back on again.

IMHO, an application should not be able to crash the JVM!
<snip>