CreateProcess error 206 The filename or extension is too long when running main method

Question

I have this error in eclipse helios   Exception occurred executing command line  Cannot run program  C  Program Files  x86  Java jre6 bin javaw exe   in directory  C  Users motiver helios workspace TimeTracker    CreateProcess error 206  The filename or extension is too long  I researched a bit but most of the issues were related to DataNucleus when working on Google App Engine  But I am not using anything remotely related to Google App Engine  I am doing a small project with Servlet 3 0 on JBOSS 6  I am using Hibernate 4 1 2 for ORM and RESTEasy to expose a web service  I created a util file that has a main   method that basically drops and re-creates the schema  I run the main   methos when I need a clean database for testing purposes  It worked fine on Tomcat 7 but it stopped working when I moved to JBoss 6   Any hint or solution would be greatly appreciated

User · Answer

I ve had the same problem but I was using netbeans instead  I ve found a solution so i m sharing here because I haven t found this anywhere so if you have this problem on netbeans try this   names might be off since my netbeans is in portuguese  Right click project   properties   build   compiling   Uncheck run compilation on external VM

User · Answer

I got the error below when I run  ant deploy   Cannot run program  C  java jdk1 8 0 45 bin java exe   CreateProcess error 206  The filename or extension is too long   Fixed it by run  ant clean  before it

User · Answer

I have got same error  while invoking Maven  The root cause for my problem was the classpath was very huge  Updating the classpath fixed the problem  There are multiple ways to update the large classpath as mentioned in this  How to set a long Java classpath in Windows   Use wildcards Argument File Pathing jar  Since I am using Intellij  they provide the option to use Argument File that i used

User · Answer

In my case the error was showing because system java version was different from intellijj eclipse java version  System and user had diff java versions  If you compile your code using one version and tried to run using a different version  it will error out      The system java version is 1 7 131   java -version java version  1 7 0 131    Long story short  make sure your code is compiled and ran by the same java version

User · Answer

In bug report Bug 327193 it is considered fixed  but it happen to me recently with Eclipse Kepler 4 3 2   Please download patch for Eclipse Juno or newer   https   bugs eclipse org bugs attachment cgi id 216593   After download back up existing eclipse plugins org eclipse jdt launching 3   jar Copy and paste classes in the patch to org eclipse jdt launching JAR  replace existing files   Restart Eclipse

User · Answer

I am using legacy version of gradle plugins and this plugin solved the issue for me    Usage  check source for more details       Build script snippet for plugins DSL for Gradle 2 1 and later  plugins     id  com github ManifestClasspath  version  0 1 0-RELEASE          Build script snippet for use in older Gradle versions or where dynamic   configuration is required  buildscript     repositories       maven         url  https   plugins gradle org m2               dependencies       classpath  gradle plugin com github viswaramamoorthy gradle-util-plugins 0 1 0-RELEASE         apply plugin   com github ManifestClasspath

User · Answer

Try this       java -jar -Dserver port 8080 build libs APP NAME HERE jar

User · Answer

If you create your own build file rather than using Project - gt  Generate Javadocs you can add useexternalfile  yes  to the javadoc task  which is designed specifically to solve this problem

User · Answer

To fix this below error  I did enough research  not got any great solution  I prepared this script and it is working fine  thought to share to the public and make use of it and save there time      CreateProcess error 206  The filename or extension is too long   If you are using the Gradle build tool  and the executable file is placed in build libs directory of your application  run sh -  create this file in the root directory of your project  and copy below script in it  then go to git bash and type run sh then enter  Hope this helps      bin bash dir name  pwd  if         1    amp  amp     1     debug    then     port  RANDOM     quit 0     echo  Finding free port for debugging      while     quit  -ne 1    do         netstat -anp   grep  port  gt  gt   dev null         if      -gt 0    then             quit 1         else             port  expr  port   1          fi     done     echo  Starting in Debug Mode on   port     gradle clean bootjar     jar name  build libs   ls -l   build libs  grep jar grep -v grep awk   print  NF         java -jar -Xdebug -Xrunjdwp transport dt socket server y suspend n address  port  jar name  elif         1    amp  amp     1     help    then     echo  please use this commands      echo  ------------------------      echo  Start in Debug Mode  sh run sh debug          echo  Start in Run Mode  sh run sh       echo  ------------------------  else     gradle clean bootjar     word count  ls -l   build libs  grep jar grep -v grep wc -w      jar name  ls -l   build libs  grep jar grep -v grep awk   print  NF        jar path build libs  jar name     echo  jar name      java -jar  jar path fi  Hope this helps

User · Answer

This is because of your long project directory name  which gives you a very long CLASSPATH altogether  Either you need to reduce jars added at CLASSPATH  make sure removing unnecessary jars only  Or the best way is to reduce the project directory and import the project again  This will reduce the CLASSPATH  It worked for me

User · Answer

There is no simple  as in a couple of clicks or a simple command  solution to this issue  Quoting from some answers in this bug report in Eclipse org  these are the work-arounds  Pick the one that s the least painful to you   Reduce the classpath Use directories instead of jar files Use a packed jar files which contains all other jars  use the classpath variable inside the manifest file to point to the other jars Use a special class loader which reads the classpath from a config file Try to use one of the attached patches in the bug report document Use an own wrapper e g  ant  Update  After July 2014  there is a better way  thanks to  Brad-Mace s answer below  If you have created your own build file instead of using Project - gt  Generate Javadocs  then you can add useexternalfile  quot yes quot  to the Javadoc task  which is designed specifically to solve this problem

User · Answer

To solve it   If you are using Eclipse   Move  m2 repository to  c   Go to Eclipse   Windows Preferences Maven User Settings -  Create your own setting xml with its content    lt settings gt     lt localRepository gt c   m2 repository lt  localRepository gt   lt  settings gt    If you are using IntelliJ  Go to IntelliJ    clicking the right mouse button on  pom xml    maven   create  settings xml   with its content    lt settings gt        xmlns  yourcontent        xmlns xsi  yourcontent        xsi schemaLocation  yourcontent xsd  gt     lt localRepository gt c   m2 repository lt  localRepository gt   lt  settings gt

User · Answer

I was running into this issue trying to execute a JPQL query in the Hibernate   JPA console of IntelliJ 2020 2 Adding this to my  idea workspace xml fixed it  lt component name  quot PropertiesComponent quot  gt              lt property name  quot dynamic classpath quot  value  quot true quot   gt           lt  component gt   Origin of the solution  https   youtrack jetbrains com issue IDEA-166929  ga 2 167622078 1290412178 1604511702-23036228 1574844686

User · Answer

Valid answer from this thread was the right answer for my special case  Specify the ORM folder path for datanucleus certainly reduce the java path compile   https   stackoverflow com a 1219427 1469481

User · Answer

I faced this problem today and I was able to solve it using this Gradle plugin  It s github url is this  IF you  like me  have no idea what Gradle is but need to run a backend to do your front end work  what you need to do is find the build gradle file that is being called to start your BE server and add this to the top   plugins     id  ua eshepelyuk ManifestClasspath  version  1 0 0

User · Answer

Try adding this in build gradle  gradle version 4 10 x  file and check it out com xxx MainClass this is the class where your main method resides  plugins     id  quot ua eshepelyuk ManifestClasspath quot  version  quot 1 0 0 quot    apply plugin   application  application       mainClassName    quot com xxx MainClass quot     The above change must resolve the issue  there is another way using script run sh below could fix this issue  but it will be more of command-line fix  not in IntelliJ to launch gradle bootRun

User · Answer

This is not specifically for eclipse  but the way I got around this was by creating a symbolic link to my maven repository and pointing it to something like  C  R   Then I added the following to my settings xml file    lt localRepository gt C  R lt  localRepository gt    The maven repository path was contributing to the length problems in my windows machine

User · Answer

I got the same error in android studio   I was able to resolve it by running Build- Clean Project in the IDE

User · Answer

Question is old  but still valid  I come across this situation often whenever a new member joins my team or a new code segment is added to existing code  Simple workaround we follow is to  Reduce the classpath  by moving up the directories    As question mentioned  this is not specific to eclipse  I came across this issue in IntelliJ Idea 14 and 2018 as well    After a long research  I found the solution is to set the      fork   false   in javc of ant build file     lt javac destdir    build dir   fork  false  debug  on  gt       lt classpath      gt       lt src       gt       lt patternset       gt   lt  javac gt    This is how my ant build javac looks now  To learn about more on fork  please refer ant documentation

User · Answer

Add below to your gradle file  plugins    id  quot com github ManifestClasspath quot  version  quot 0 1 0-RELEASE quot            See https   plugins gradle org plugin com github ManifestClasspath

User · Answer

Answering my own question here so that the solution doesn t get buried in comments  I exported the project as a runnable jar from within eclipse and did a command line  java -jar MyJar jar  and it works perfectly fine

User · Answer

In intellij there is an option to  shorten command line   select  JAR manifest  or   argFiles  would solve the problem  basically it will put your lengthy class path into a jar file or a temp file

User · Answer

In a Windows machine  there is a limitation of the jar file name path length in the command-line  due to which you see the below error message  I tried searching a lot  even I tried applying the above solution  some reason  it didn t work  I found the working snippet for Gradle  gradle-4 10 2-all zip  Error  CreateProcess error 206  The filename or extension is too long Use this below gradle build code snippet to fix the above problem in IntelliJ or STS  or eclipse anything  Gradle Code Fix  apply plugin   application   task pathingJar type  Jar        dependsOn configurations runtime     appendix    pathing       doFirst           manifest               attributes  quot Class-Path quot   configurations runtimeClasspath files collect   it getName     join                         task copyToLib type  Copy        into  quot  buildDir libs quot      from configurations runtime    bootRun       systemProperties   System properties       This below line is for if you have different profiles prod  dev etc          systemProperty  spring profiles active    dev      jvmArgs  -Djava util logging config file none       mainClassName    quot com xxxx Main quot      dependsOn pathingJar     dependsOn copyToLib     doFirst           classpath   files  quot  buildDir classes java main quot    quot  buildDir resources main quot   pathingJar archivePath

User · Answer

How many people sad above  there are a lot of plugins to gradle execute a by pass in this problem like  plugins     id  quot ua eshepelyuk ManifestClasspath quot  version  quot 1 0 0 quot     or plugins     id  quot com github ManifestClasspath quot  version  quot 0 1 0-RELEASE quot     But the better solution that I found was kill the JVM process and everything is done

User · Answer

it happens due to DataNucleus sometimes overwrite the Arguments with many paths   You have to overwrite them with this   -enhancerName ASM -api JDO -pu MediaToGo  Hope help you

User · Answer

Try updating your Eclipse version  the issue was closed recently  2013-03-12   Check the bug report https   bugs eclipse org bugs show bug cgi id 327193

User · Answer

I got the same error  Tried solutions like cleaning  rebuild  invalidateCache  retart etc but nothing works   I just have created a new folder with short name and copied all the files app folder  gradle files etc  in new folder  Opened application in android studio and its working fine

[java] CreateProcess error=206, The filename or extension is too long when running main() method

Examples related to java

Examples related to eclipse