Submitted by: rcamposff
on Mon, 03/09/2015 - 14:00
Issues & Bugs
freeze
Engine start
Windows

Hi folks! I am a new user of YAWL, and have come across my first hiccup :(. After the installation (W7, 64 bits) I tru to start the engine, but the button "Engine is starting" simply stays for ages (apparently bringing it up).
I wonder whether there is a way to debug what is happening. Are there any quick hints, known issues... that I can try? IS there a check list I could go through?

Thanks in advance!

I just tried an install with the latest version on W7 64 bits in a virtual box.

After installation I start the control panel. There are some popups asking to allow some access through the firewall. You might watch out for those. Then there ist the console window:

I have Java version 8 running. Which one do you have?

Any other hints from the community?

 

Many thanks!

Mine, as it seems, was a simpler issue. For what it may help others, this is what I learn with a little help from my friends, as the song goes :).

(I checked first thing my AV settings, but everywhere YAWL was a trusted application, and I could not find any filters that could be preventing YAWL from working).

1) They suggested that I may need to have the JDK installed (I may be wrong, but I think this was not specified mong the requirements for installation), which I think is true (I installed it).

2) Another recommendation was to manually run (from the command line prompt) the startup.bat process under the tomcat \bin directory, so that the error messages thrown would be visible. As it happened, I did not have the JAVA_HOME and JRE_HOME environment variables set (although I did have JRE installed, used by several applications)

Once I fixed that, all seems to be working fine thus far :).

Michael Adams

Thu, 03/12/2015 - 00:28

Permalink

Your second point is the right one. The YAWL installer is supposed to set the JAVA_HOME env var if it does not already exist, but that is failing in some win 7 & 8 installs. It will be fixed in the next YAWL release.

In the meantime, to fix manually:
- create a new plain text file and add this line: JAVA_HOME=[path to your java directory]
- save it as 'setenv.bat' to [your yawl dir]\engine\apache-tomcat-7.0.55\bin\

replace the [path...] bit with your actual java path.