A problem occurred starting process 'command 'C:\Java\jdk1.8.0_101\bin\java.exe''


#1

Hi Everyone

After running the command gradlew --no-daemon run on Window 10 The following error is displayed in the terminal :

FAILURE: Build failed with an exception.

  • What went wrong:
    Execution failed for task ‘:run’.

A problem occurred starting process ‘command ‘C:\Java\jdk1.8.0_101\bin\java.exe’’

  • Try:
    Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

  • Get more help at https://help.gradle.org

BUILD FAILED in 2m 44s
116 actionable tasks: 115 executed, 1 up-to-date

any suggestion is welcome


CreateProcess error=206, filename or extension is too long
#2

Hi

Which project are u trying to compile (abs, adk, webapp… ?)

Regards


#3

Hi,

I try to run the abs

I think the problem is about the path long in the classpath

C:\Java\jdk1.8.0_101\bin\java.exe -Dfile.encoding=windows-1252 -Duser.country=FR -Duser.language=fr -Duser.variant -cp E:\workspaces\nawar\gold-tools\abs-webapp\b
uild\classes\java\main;E:\workspaces\nawar\gold-tools\abs-webapp\build\resources\main;E:\workspaces\nawar\gold-tools\abs-webapp\modules\abs\axelor-business-production\build\libs\axel
or-business-production-5.0.0-rc1.jar;E:\workspaces\nawar\gold-tools\abs-webapp\modules\abs\axelor-business-project\build\libs\axelor-business-project-5.0.0-rc1.jar;E:\workspaces\nawa
r\gold-tools\abs-webapp\modules\abs\axelor-cash-management\build\libs\axelor-cash-management-5.0.0-rc1.jar;E:\workspaces\nawar\gold-tools\abs-webapp\modules\abs\axelor-quality\build
libs\axelor-quality-5.0.0-rc1.jar;E:\workspaces\nawar\gold-tools\abs-webapp\modules\abs\axelor-talent\build\libs\axelor-talent-5.0.0-rc1.jar;E:\workspaces\nawar\gold-tools\abs-webapp
\modules\abs\axelor-human-resource\build\libs\axelor-human-resource-5.0.0-rc1.jar … > >
C:\Users\HORRI.gradle\caches\m
odules-2\files-2.1\org.apache.httpcomponents\httpcore\4.4.4\b31526a230871fbe285fbcbe2813f9c0839ae9b0\httpcore-4.4.4.jar com.axelor.app.internal.AppRunner --port 8080 --config build\t
omcat\axelor-tomcat.properties

Then the command generate this error : "Createprocess error=206; the filename or extension is too long"


#4

Hello

I’m also having the same issue while trying to run “gradlew --no-daemon run”.

Config: abs, adk & webapp 5.0.0-rc1. jdk1.8.0_71

I’m trying to see if the issue is on my end while waiting for a reply.

Thank you


#5

Hi,

It seems that Windows has a command length limit or 8192 bytes so if u run the java command under the “E:\workspaces\nawar\gold-tools\abs-webapp” directory maybe you can try to replace this path by “./” and thus reduce the length of the command. You can use the online tool https://mothereff.in/byte-counter to check it.

What is your goal, compile the ADK itself or the WEBAPP ?

Regards


#6

Hi,

From my point of view, the best way to run the ABS is to:

  1. download, install and configure the lastest tomcat releaser
  2. Sync the git repository:
    2.1 git clone https://github.com/axelor/abs-webapp.git
    2.2 cd abs-webapp
    2.3 edit the .gitmodules and replace the url by https://github.com/axelor/axelor-business-suite.git
    2.4 sync submodules: git submodule init; git submodule update; git submodule foreach git checkout master; git submodule foreach git pull origin master
    3 edit the \abs-webapp\src\resources\main\application.properties
    4 execute gradlew war
    5 put the war files into the webapps dir of tomcat and wait for complete deployement (see catalina.out)

Regards


CreateProcess error=206 && A problem occurred starting process 'command 'PATH\java.exe''
#7

Hi,
I dont need abs juste for use, but I want to make some modifications and add others modules and I want to profit from the hot redeployment in the version 5.
Like I say the problem is about the length of the class path, So I want to know if is there any way to reduce the class path, for example why not creating un empty jar with Manifest File contening all jars, then run the command with one jar?


#8

I check for the axelor-demo and I found the same problem, I think it depends on gradle configuration


#9

Please if any one has suggestion we are blocked


#10

do you still have the issue ?

We fix an issue with long command lin on windows. The run command now uses manifest jar to avoid long classpath
causing too long command line which is not supported on windows.

Regards


CreateProcess error=206 && A problem occurred starting process 'command 'PATH\java.exe''
#15

WTF !!! get out of there