VM Could not reserve enough space for object heap (Windows slave)

[morty]

I have just upgraded to Jenkins 1.500 on a windows machine. I have a windows
slave with 8GB RAM. I have made a remote connection to this slave and
started it from the Jenkins webinterface (using the JNLP launch button). The
slave starts fine and the machine/slave only uses approx 1.6GB out of the 8
GB available RAM.

I start a job (assigned to the windows slave) on the jenkins master which
calls a java application with the following vm args:

-XX:MaxPermSize=512m -Xmx1024m


but the job fails with this error:

Error occurred during initialization of VM Could not reserve enough
space for object heap Could not create the Java virtual machine.

If I run the job locally on the slave it works fine. Any ideas why the build
fails on the windows slave when triggered through the jenkins master?

The job ran fine on the slave BEFORE the upgrade.

The slave is running:
java version "1.6.0_34"
Java(TM) SE Runtime Environment (build 1.6.0_34-b04)
Java HotSpot(TM) 64-Bit Server VM (build 20.9-b04, mixed mode)



--
View this message in context: http://jenkins.361315.n4.nabble.com/VM-Could-not-reserve-enough-space-for-object-heap-Windows-slave-tp4653961.html
Sent from the Jenkins users mailing list archive at Nabble.com.

[morty]

It seems to work with the second approach described where the slave.jar is
launched from cmd. Remain a mystery why it gives mem errors when launching
the slave with the jnlp file.



--
View this message in context: http://jenkins.361315.n4.nabble.com/VM-Could-not-reserve-enough-space-for-object-heap-Windows-slave-tp4653961p4653964.html