This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: AIX: launch command classpath truncated
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jul 17, 2007
03:35 PM
AIX: launch command classpath truncated
Has anyone encountered the following problem?
When using ISMP 11.5 MP Dynamic suite installer, when doing a jvm search or bundling your own jvm, the launch command that is used to launch the installer gets truncated at certain number of characters.
In this case, the classpath is long because a number of jar files were added to be embedded with the installer:
As you can see here is the launch command when launching it on an AIX machine:
LAUNCH_COMMAND="/tmp/istemp634956197225919/_bundledJRE_/bin/java" -cp .:::::"#CLASSPATH#":.:"/tmp/istemp634956197225919/suite.jar"::"/tmp/istemp634956197225919/com.tibco.neo.launch_1.2.0.003.jar":"/tmp/istemp634956197225919/org.eclipse.osgi3.2.2.R32x_v20070118.jar":"/tmp/istemp634956197225919/com.tibco.corona.installation.machine.model_1.0.0.006.jar":"/tmp/istemp634956197225919/org.eclipse.emf.common_2.2.1.v200705141058.jar":"/tmp/istemp634956197225919/com.tibco.neo.osgi.tools_1.0.0.006.jar":"/tmp/istemp634956197225919/org.e:"/tmp/istemp634956197225919/org.eclipse.emf.ecore.xmi_2.2.3.v200705141058.jar":::: -Djava.io.tmpdir="/tmp" -Dtemp.dir="/tmp" -Dis.jvm.home="/tmp/istemp634956197225919/_bundledJRE_" -Dis.jvm.temp="1" -Dis.media.home="/tmp/istemp634956197225919/suite.jar" -Dis.launcher.file="/rv/home/smathur/universalinstaller/aix/./TIBCOUniversalInstaller.bin" -Dis.jvm.file="/tmp/istemp634956197225919/_bundledJRE_/jvm" -Dis.external.home="/rv/home/smathur/universalinstaller/aix/." run "-console" 1>&1 2>>/tmp/istemp634956197225919/APP_STDERR
Here is the launch command when launching it on a Solaris machine:
LAUNCH_COMMAND="/tmp/istemp3505197232401/_bundledJRE_/bin/java" -cp .:::::"/tmp/istemp3505197232401/suite.jar"::"/tmp/istemp3505197232401/com.tibco.neo.launch_1.2.0.003.jar":"/tmp/istemp3505197232401/org.eclipse.osgi3.2.2.R32x_v20070118.jar":"/tmp/istemp3505197232401/com.tibco.corona.installation.machine.model_1.0.0.006.jar":"/tmp/istemp3505197232401/org.eclipse.emf.common_2.2.1.v200705141058.jar":"/tmp/istemp3505197232401/com.tibco.neo.osgi.tools_1.0.0.006.jar":"/tmp/istemp3505197232401/org.eclipse.emf.ecore_2.2.3.v200705141058.jar":"/tmp/istemp3505197232401/com.tibco.neo.common.util_2.2.0.005.jar":"/tmp/istemp3505197232401/com.tibco.neo.model.base_2.2.0.007.jar":"/tmp/istemp3505197232401/com.tibco.neo.osgi.launch_1.0.0.009.jar":"/tmp/istemp3505197232401/slf4j-api-1.3.1.jar":"/tmp/istemp3505197232401/slf4j-jdk14-1.3.1.jar":"/tmp/istemp3505197232401/org.eclipse.emf.ecore.xmi_2.2.3.v200705141058.jar":::: -Djava.io.tmpdir="/tmp" -Dtemp.dir="/tmp" -Dis.jvm.home="/tmp/istemp3505197232401/_bundledJRE_" -Dis.jvm.temp="1" -Dis.media.home="/tmp/istemp3505197232401/suite.jar" -Dis.launcher.file="/rv/home/smathur/universalinstaller/sol-sparc/disk1/./TIBCOUniversalInstaller.bin" -Dis.jvm.file="/tmp/istemp3505197232401/_bundledJRE_/jvm" -Dis.external.home="/rv/home/smathur/universalinstaller/sol-sparc/disk1/." run "-console" 1>&1 2>>/tmp/istemp3505197232401/APP_STDERR
As you can see, the classpath gets cut off on AIX as where is Solaris, it does not. The cutting off of the classpath causes the java usage output to be outputted and the launch of the installer fails. This is a serious issue since we cannot launch the installer on AIX in both the case where we are doing a jvm search or if we are bundling a jvm. It is to note that the jvm used in both cases is 1.5.
When using ISMP 11.5 MP Dynamic suite installer, when doing a jvm search or bundling your own jvm, the launch command that is used to launch the installer gets truncated at certain number of characters.
In this case, the classpath is long because a number of jar files were added to be embedded with the installer:
As you can see here is the launch command when launching it on an AIX machine:
LAUNCH_COMMAND="/tmp/istemp634956197225919/_bundledJRE_/bin/java" -cp .:::::"#CLASSPATH#":.:"/tmp/istemp634956197225919/suite.jar"::"/tmp/istemp634956197225919/com.tibco.neo.launch_1.2.0.003.jar":"/tmp/istemp634956197225919/org.eclipse.osgi3.2.2.R32x_v20070118.jar":"/tmp/istemp634956197225919/com.tibco.corona.installation.machine.model_1.0.0.006.jar":"/tmp/istemp634956197225919/org.eclipse.emf.common_2.2.1.v200705141058.jar":"/tmp/istemp634956197225919/com.tibco.neo.osgi.tools_1.0.0.006.jar":"/tmp/istemp634956197225919/org.e:"/tmp/istemp634956197225919/org.eclipse.emf.ecore.xmi_2.2.3.v200705141058.jar":::: -Djava.io.tmpdir="/tmp" -Dtemp.dir="/tmp" -Dis.jvm.home="/tmp/istemp634956197225919/_bundledJRE_" -Dis.jvm.temp="1" -Dis.media.home="/tmp/istemp634956197225919/suite.jar" -Dis.launcher.file="/rv/home/smathur/universalinstaller/aix/./TIBCOUniversalInstaller.bin" -Dis.jvm.file="/tmp/istemp634956197225919/_bundledJRE_/jvm" -Dis.external.home="/rv/home/smathur/universalinstaller/aix/." run "-console" 1>&1 2>>/tmp/istemp634956197225919/APP_STDERR
Here is the launch command when launching it on a Solaris machine:
LAUNCH_COMMAND="/tmp/istemp3505197232401/_bundledJRE_/bin/java" -cp .:::::"/tmp/istemp3505197232401/suite.jar"::"/tmp/istemp3505197232401/com.tibco.neo.launch_1.2.0.003.jar":"/tmp/istemp3505197232401/org.eclipse.osgi3.2.2.R32x_v20070118.jar":"/tmp/istemp3505197232401/com.tibco.corona.installation.machine.model_1.0.0.006.jar":"/tmp/istemp3505197232401/org.eclipse.emf.common_2.2.1.v200705141058.jar":"/tmp/istemp3505197232401/com.tibco.neo.osgi.tools_1.0.0.006.jar":"/tmp/istemp3505197232401/org.eclipse.emf.ecore_2.2.3.v200705141058.jar":"/tmp/istemp3505197232401/com.tibco.neo.common.util_2.2.0.005.jar":"/tmp/istemp3505197232401/com.tibco.neo.model.base_2.2.0.007.jar":"/tmp/istemp3505197232401/com.tibco.neo.osgi.launch_1.0.0.009.jar":"/tmp/istemp3505197232401/slf4j-api-1.3.1.jar":"/tmp/istemp3505197232401/slf4j-jdk14-1.3.1.jar":"/tmp/istemp3505197232401/org.eclipse.emf.ecore.xmi_2.2.3.v200705141058.jar":::: -Djava.io.tmpdir="/tmp" -Dtemp.dir="/tmp" -Dis.jvm.home="/tmp/istemp3505197232401/_bundledJRE_" -Dis.jvm.temp="1" -Dis.media.home="/tmp/istemp3505197232401/suite.jar" -Dis.launcher.file="/rv/home/smathur/universalinstaller/sol-sparc/disk1/./TIBCOUniversalInstaller.bin" -Dis.jvm.file="/tmp/istemp3505197232401/_bundledJRE_/jvm" -Dis.external.home="/rv/home/smathur/universalinstaller/sol-sparc/disk1/." run "-console" 1>&1 2>>/tmp/istemp3505197232401/APP_STDERR
As you can see, the classpath gets cut off on AIX as where is Solaris, it does not. The cutting off of the classpath causes the java usage output to be outputted and the launch of the installer fails. This is a serious issue since we cannot launch the installer on AIX in both the case where we are doing a jvm search or if we are bundling a jvm. It is to note that the jvm used in both cases is 1.5.
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jul 17, 2007
03:37 PM
Please ignore the #CLASSPATH# value in the AIX launch command. The same thing happens without this value being there so this is not the issue.
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)