#88 NT Service not obeying wrapper.java.maxmemory

[Anonymous]

I have these properties set in wrapper.conf, for an NT
service, running on Windows Server 2003.

# Java Additional Parameters
#wrapper.java.additional.1=

# Initial Java Heap Size (in MB)
#wrapper.java.initmemory=64

# Maximum Java Heap Size (in MB)
#wrapper.java.maxmemory=512

The application will take up not more than 64MB of
heap, and then throws an out of memory exception. I
would just pass -Xmx512m as a java parameter, but I'm
not sure how that would interact with initmemory and
maxmemory. Have you seen this behavior before? Can I
set heap size as a java parameter myself?

Thanks,
David Berkman

[Nobody/Anonymous]

Logged In: NO

Forget this. Stupidity reigns supreme. I think I'll remove
the # comments...