Skip to main content

Problem:

  • Product Name: BES
  • Product Version: 6.5
  • Product Component: iastool

When using the iastool to generate a deployable jar, we are receiving an erroneous and undescriptive error/exception message:

 [exec] The " characters around the executable and arguments are
 [exec] not part of the command.
 [exec] Generating deployable module
 [exec] java.io.IOException: No such file or directory
 [exec] at java.io.UnixFileSystem.createFileExclusively(Native Method)
 [exec] at java.io.File.checkAndCreate(File.java:1314)
 [exec] at java.io.File.createTempFile(File.java:1402)
 [exec] at com.borland.enterprise.util.FileUtil.createTempDir(FileUtil.java:597)
 [exec] at com.borland.enterprise.util.FileUtil.createTempDir(FileUtil.java:626)
 [exec] at com.borland.management.module.tools.ModuleAPI.generateDeployableJar(ModuleAPI.java:232)
 [exec] at com.borland.management.module.tools.GenDeployableCmd.execut
 .
 .
 .

The cause of the issue is that the "java.io.tmpdir" property is set to: /tmp/cmdtool/

I have tried numerous command-line incantations to no avail.

Resolution:

There are two ways to set the "java.io.tmpdir" for iastool:

1. The iastool picks up its settings from the "iastool.config" file under the same directory as iastool, i.e., <BES Install>/bin. Comment out the default setting in the config file:

"vmprop java.io.tmpdir=$var(installRoot)/tmp/$var(feature)"

and set it to be an absolute dir where you want.

2. The standard JVM options should be taken by iastool, as the following:

.../BES65_64/bin: ./iastool -Djava.io.tmpdir=xxx

 


#AppServer
#iastool
#ioexception
#VisiBroker
#Security
#tmpdir

Problem:

  • Product Name: BES
  • Product Version: 6.5
  • Product Component: iastool

When using the iastool to generate a deployable jar, we are receiving an erroneous and undescriptive error/exception message:

 [exec] The " characters around the executable and arguments are
 [exec] not part of the command.
 [exec] Generating deployable module
 [exec] java.io.IOException: No such file or directory
 [exec] at java.io.UnixFileSystem.createFileExclusively(Native Method)
 [exec] at java.io.File.checkAndCreate(File.java:1314)
 [exec] at java.io.File.createTempFile(File.java:1402)
 [exec] at com.borland.enterprise.util.FileUtil.createTempDir(FileUtil.java:597)
 [exec] at com.borland.enterprise.util.FileUtil.createTempDir(FileUtil.java:626)
 [exec] at com.borland.management.module.tools.ModuleAPI.generateDeployableJar(ModuleAPI.java:232)
 [exec] at com.borland.management.module.tools.GenDeployableCmd.execut
 .
 .
 .

The cause of the issue is that the "java.io.tmpdir" property is set to: /tmp/cmdtool/

I have tried numerous command-line incantations to no avail.

Resolution:

There are two ways to set the "java.io.tmpdir" for iastool:

1. The iastool picks up its settings from the "iastool.config" file under the same directory as iastool, i.e., <BES Install>/bin. Comment out the default setting in the config file:

"vmprop java.io.tmpdir=$var(installRoot)/tmp/$var(feature)"

and set it to be an absolute dir where you want.

2. The standard JVM options should be taken by iastool, as the following:

.../BES65_64/bin: ./iastool -Djava.io.tmpdir=xxx

 


#AppServer
#iastool
#ioexception
#VisiBroker
#Security
#tmpdir

How to change the Remote Access Logging in Administrative Tools? I've just checked the technet.microsoft.com/.../cc739394(v=ws.10).aspx and https://hireessaywriter.org/ tutorials on IAS Tools. What are the basic discrepancies between /tmp and /var/tmp in this case? They do have the same functionality and aims?

Thanks.