Help coderanch get a
new server
by contributing to the fundraiser
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

can't run commands from application

 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi All,
I am customizing iPlanet's BillerXpert and within the packaged code is a call to Runtime.exec() to run a conversion program. When the code runs I get a 'java.io.IOException: Not enough space' message, but when I println the command, copy it from the log, and run it at the command line it works. Here is the code:

I have replaced the command with others but get the same error, and iPlanet insists it is not a code problem, so there must be something wrong with my environment. The application is running on a Sun Ultra 10 box with Solaris 8. The servers are iPlanet web server 6 and iPlanet application server 6.5. Any ideas of what to try, or alternatives to Runtime.exec() are greatly appreciated.
Thanks in advance.
[ August 13, 2003: Message edited by: Michelle L Botic ]
 
author and iconoclast
Posts: 24207
46
Mac OS X Eclipse IDE Chrome
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The JDC Bug Parade is your friend:
http://developer.java.sun.com/developer/bugParade/bugs/4337885.html
There are quite a few similar bugs, all now closed. If you look at them all, in general, the resolution seems to be that the cause is that the JDK version was inappropriate for the OS, or the OS wasn't at the right patch level for the JDK. Make sure your OS has all the recommended patches, and make sure you're using the newest JDK you can, and the problem should clear up.
 
Michelle L Botic
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks. My network admin is out today, so I'll have him look into patches tomorrow. Also, I looked at some of the bugs in the bug database and one of them (4391042) said the problem was solved by limiting the size of the JVM. How is this done?
 
Chicken Farmer ()
Posts: 1932
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I believe you need to do a java -Xmx (and possibly java -Xms).
If you type java -X, you get non-standard options, of which the two above allow you to control heap size.
 
Ernest Friedman-Hill
author and iconoclast
Posts: 24207
46
Mac OS X Eclipse IDE Chrome
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Probably meaning the heap size. I think that ws only referring to the case where the external program was a JVM too. But you can fiddle with the Java heap size using the -Xmx switch to the "java" command. -Xmx32m limits the heap to 32 megabytes.
 
Die Fledermaus does not fear such a tiny ad:
We need your help - Coderanch server fundraiser
https://coderanch.com/t/782867/Coderanch-server-fundraiser
reply
    Bookmark Topic Watch Topic
  • New Topic