REST API job runs in studio but not in CMD or Linux machine
The job I created runs perfectly in Studio. Even crested another job to test the REST API and everything looks good in my Studio. When I do build a job and then try to run the REST API from CMD or from Linux machine it doesn't run.
Tried all the options given in different posts in de community (point windows to JDK, add CLASSPATH, PATH and JAVA_HOME) and now I have an additional problem when I try to build the job from Studio (Error line: 451. Detail message syntax error on token ":",;expected. There may be some other errors caused by JVM compatibility.Make sure your JVM setup is similar to the studio)
I tried several different ways to resolve the problem with the job, with no success.
Tried to fix the issue through:
Updated packages – more than 12 hours update
Download and Install Java JDK
Set CLASSPATH, PATH, JAVA_HOME vars
Change IP ports – in all the cases the same response “web server failed to start. Port 80.. was already in use”
When I run the .bat from CMD as administrator, the response is “web server failed to start. Port 80.. was already in use”
Found here and here the issue is caused due to “The IP specified is not own interface. Socket is not able to bind to that IP”.
Also found in application properties file that server.port: 8065 - that was automatically defined - is the port CMD is pointing to and not port 8088 defined by me.
Tried changing server.port to the same port defined in REST_endpoint but received the same response “web server failed to start. Port 80.. was already in use”.
Ensure proper version of JDK is installed. If that requirement is met, ensure JDK bin is included in your PATH environment variable and is being reached.
doesn't work. Tried with JDK Oracle, JDK zulu, changing PATH, CLASSPATH, JAVA_HOME, Installed JRE... Nothing has changed, same response "Web server failed to start. Port 8065 was already in use" but that port wasn't defined by me. That's the port defined in server.port (in properties file) not in REST endpoint (trestrequest). Cannot understand why those ports are different and why CMD points to server.port - that is the port that fails to connect - and not to REST endpoint.
The job is still running well within studio? Did you build it as a standalone one? Would you mind posting your job design screenshots here which will be helpful for us to address your issue?
