The -javahome flag in all MQ Solaris/Microsoft
Windows scripts does not work if the value has a space.
The command-line utilities in Sun Java System Message Queue have a -javahome option that allows you to specify an alternate Java runtime. Using
this option exposes a limitation where the path of the specified alternate
Java runtime must not contain spaces. Examples of paths that have spaces are:
-
Microsoft Windows: C:\jdk 1.4
-
Solaris: /work/java 1.4
This
problem occurs at Sun Java System Application Server instance startup. When a Sun Java System Application
Server instance is started, by default its corresponding Sun Java System Message Queue
broker instance is also started. The broker always starts using the -javahome command-line option to ensure that it uses the same Java runtime
used by the Sun Java System Application Server. If the Java runtime that is configured for
use by the Sun Java System Application Server (and therefore passed on for use
by the broker) is located at a path that contains spaces, broker startup fails,
which also causes the Sun Java System Application Server instance startup to fail.
Solution
Make sure that the Java runtime used by the Sun Java System Application Server is
located at a path that does not contain spaces.
|