"Bad file number" error for a very long command line

Asked Jun 09 '15 at 13:42

Active Jun 09 '15 at 15:35

Viewed 155 times

I have a particularly large java command to execute (lot's of parameters, long classpath, etc) - and when I run it like that (as I normally do in my Windows via git bash app, which tries to emulate linux bash):

java <classpath here> <params>

it returns me the weird message: sh.exe": /c/Windows/system32/java: Bad file number

BUT, whenever I decrease the command length (by removing any part of it - classpath, params) to about 32k symbols - it runs ok.

Is there any length limit in Windows/bash/java to a single executed command ?

edited Jun 09 '15 at 15:35

Nick Volynkin

14,023
6
43
67

asked Jun 09 '15 at 13:42

javagirl

1,635
6
27
43

2

http://stackoverflow.com/questions/3205027/maximum-length-of-command-line-string – gawi Jun 09 '15 at 13:52
@gawi thanks! so the limit in Win7 is 32768 – javagirl Jun 09 '15 at 13:54
Maybe this supports longer strings: http://cygwin.com/ – Nick Volynkin Jun 09 '15 at 14:14
For all Windows versions - https://www.google.com/#q=windows+command+line+maximum+length – lit Jun 09 '15 at 15:38

"Bad file number" error for a very long command line

0 Answers0