Name: jl125535 Date: 08/20/2003


A DESCRIPTION OF THE REQUEST :
With our application we are loading huge datasets from a SQL database. These datasets canNOT be split. This means the client software uses a lot of memory. I already tried to use the maximum- heap- size property that is specified for the jnlp files, but this does not help. When I start load those datasets javaw.exe is not able to use more than around 80 megs of memory.
When I run the application with the debugger or on my machine and pass the
-Xmx265M to the VM it's working fine and without any problem!

JUSTIFICATION :
I need this modification, because I must make sure that our software can be easily installed and used in all possible networks (is'nt that the reason why one uses Java?)- and it has got to be runnable without any restrictions.

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
I'd like to have the possibility to specify an additional parameter in the jnlp file that passes data to the VM (that is used on the local machine). I personally cannot see how this could be a security problem.
ACTUAL -
Actually the java shows the message java.lang.outofmemory though the machines got quite enough!


CUSTOMER SUBMITTED WORKAROUND :
I only could imagine a workaround by writing two jars. A small one that starts the real application by using the commandline. (But this is not very professional!)
(Incident Review ID: 190994)
======================================================================