on NT system: command line too long

Tweet

Share

Java problem N°1

On windows NT machine, command line length is limited to 1024 characters!, clearly not enough for a distributed classpath with a lot of frameworks or 3rd party tools.

Solutions

• Reduce number of jar files, instead of having 10 jar files, you can try to build only one, use automatic build process, with jakarta ANT during the build and for your deployment. This is often not a good/verybad solution.
• Put the half classpath size in java ext classpath (if you use resin or tomcat)

• Use cygwin to start the java process, for example you can use a bash terminal. But do not use cygrunsrv as it was not designed for installing java process as NT service: it wil create a ghost program when you kill the service.
• Last chance, put the classpath in a .txt file and create a classloader which will read it and set the classpath (adaptative classloader). You must create your own classloader!

You might also like:

1284 days ago

Developer cartoons

Don't forget to click Read More ;-)

2820 days ago

Hierarchy of classloader

 Read this document about classloader (PDF)System classloader is the content of the system variabl

2820 days ago

java.lang.ClassNotFound and ClassNotDefFoundError are differ

 java.lang.ClassNotFound and ClassNotDefFoundError are different but what if my classes are in cla

2820 days ago

Parser incompatibility or Parser order in Classpath

Parser incompatibility or Parser order in Classpath, classloader, loading sequence in a highly compl