The editors do not start, and I get the following three lines in the 'Output' tab of the EJS console:
RMI registry started at port: 2008 EjsConsole server is ready to listen at port: 2008 The program selected is NOT running
My setup: Windows 7 Professsional 32-bit Java JRE 1.7 update 17
I have kept a number of previous versions of EJS, so that I can make comparisons. EJS 4.3.7_121014 starts correctly, by the looks of it. (The editor starts up. I have not verified whether the editor can actually open a file)
In the hope of finding out more I enabled logging in the following way: I opened the Java Control Panel, opened the last tab, Advanced, and I placed checkboxes at 'Enable tracing' and 'Enable logging'.
First I ran EJS 4.3.7_130310. After a minute or so a log file appeared in Sun\Java\Deployment\log 6 lines or so, with no apparent connection with EJS (Only mention of JFX)
I disabled logging, saved a copy of the log, then enabled logging once again. Then I ran EJS 4.3.7_121014 (the one that starts correctly) Likewise, after a minute or so a log file appeared. The content was identical to the one before.
My conclusion: nothing of EJS is logged by Java.
Since there is no log to give any clue I don't know how to proceed. Are there other EJS users with the same setup (W7, JRE 1.7 update 17)?
UPDATE: I fired up another PC, one that still has the version of JRE from when I last used it. JRE 1.6 update 31. In that JRE-1.6_31 environment I did not encounter problems; EJS 4.3.7_130310 started correctly.
The latest version of the 1.6 branch is 1.6 update 43. Oracle has announced last february that the Java 1.6 branch will no longer receive security updates. So going back from JRE 1.7 to JRE 1.6 is not an option.
I just tested with Java 1.7 release 10 and then updated to the latest (21) to do the test again. No problem at all with EJS 4.3.7 130310 just downloaded from the EJS web page. I tested both in a 64 bits Mac OS X Mountain Lion and a 32 bits Windows 7 (running in a VM in my Mac with Parallel Desktop). You are right that EJS does not use the Java logging mechanism, though. But errors shoudl show in the EJS console.
I am running my EJS in 1.7 regularly since it appeared. And I have found no problems.
You mention: 'errors should show in the EJS console'. Unfortunately, what I get in the output tab of the EJS console is devoid of clues. The usual output in the EJS console consists of three lines, and the first two are as follows:
RMI registry started at port: 2008 EjsConsole server is ready to listen at port: 2008
And the third line with all the technical information.
On my setup (W7 Pro, JRE 1.7 update 21) the output in the EJS console output tab reads as follows:
RMI registry started at port: 2008 EjsConsole server is ready to listen at port: 2008 The Program selected is NOT running
That is all. So there is no clue.
My best guess is that the Oracle Java Virtual Machine behaves differently on different platforms. I assume that running a VM in a Mac is not the same as running Windows directly.
EDIT: I forgot to mention: I also tried the same setup with the Internet Firewall program that I use shut down, to see if maybe the problem was due to some sort of firewall interference. Same error.
The only thing I can think of is that you start the console from a command window using: C:\> java -jar EjsConsole.jar and see if this command window shows any error message. If so, please , send this message to me or post it here.
Trying java -jar EjsConsole.jar (in the appropriate directory) seemed to indicate a Windows permission problem.
I re-downloaded and unzipped, and that version started correctly. (As always on first use of software Comodo Defense+ software prompted me whether to allow the program to proceed.)
But later with the same EJS the editors didn't start anymore. It occurred to me I had renamed the directory (Defense+ identification includes the path).
Often when I want to test I open the Comodo Security menu, and I click 'exit', to exclude security software interference. Did that, and then checked, and I saw this time Comodo was still running. Apparently, when I click 'exit', Comodo doesn't actually exit (or not always). So I tried setting Defence+ to 'disabled'. Then EJS started normally.
I opened a Comodo configurator window, and added an explicit 'allow' rule for EJS and everything in its subdirectories. After that EJS started normally.
Conclusion: Comodo Security was the cause of the denial of permission, it wasn't an EJS error. Paco, I owe you an apology. I failed in making sure it wasn't Security software interference.
