Try removing the AS_JAVA variable from the asenv.bat file, and setting
up the PATH on each machine to point to the right location of the JVM.
Tom
On 1/10/2011 12:40 PM, rockxwre_at_live.nl wrote:
> Hi,
>
> I'm experimenting with a cluster using GF 3.1 with the 'DAS managed'
> approach (SSH). The setup is based on a few windows (Windows 7, 2003)
> machines.
> As expected, when installing an instance
> (install-node/create-node-ssh/create-instance), a Glassfish setup is
> installed on the remote machine. However, the asenv.bat of the remote
> machine contains a AS_JAVA variabele with the value of the path to java
> version of the DAS and not the path of java version of the remote
> machine. For example, the DAS path to java is D:\Java\jdk1.6.0_23 and
> the path to java on the remote system is C:\Java\jdk1.6.0_23. Result:
> the remote instance can not be started properly, because asadmin tries
> to use the wrong java path. How can I avoid this, is there a way to
> pass the local JDK location as an argument when installing an instance?
>
> Regards,
> Ramon