6.1 and 6.1.1 upgrades fail!

[dgphelps]

Ok... I saw the 6.1 release and then the 6.1.1 release and thought I would upgrade.

I am running a Windows 7 system and have had Subsonic running on it for several years. When I attempt to upgrade to version 6.1 or 6.1.1 it proceeds like all previous upgrades, but when the server restarts I get a 503 error when connecting to Subsonic. I attempted all the fixes I have read here for clearing the Database with no success. I ended up uninstalling Subsonic and trying a straight 6.1.1 install (no upgrade) and it failed giving the same 503 server error. I then tried to uninstall 6.1.1 and install 6.0 and it failed with the same error. I got the system back working, by going back to 5.3 and then upgrading to 6.0. Once I got that working I again tried to upgrade to 6.1 and 6.1.1 and both again failed with the 503 server error. I am now back running with 6.0 again and no path to 6.1 or 6.1.1 I can see.

I have been running the same version of Java since I first installed Subsonic because early on if I let Sun update Java, Subsonic would quit. Has this changed? ( java 1.6.0_37)

Has anyone else run into this and found a solution?

[dgphelps]

I thought I would post an update. I finally got this to work this morning by upgrading to the latest version of Java. I had been avoiding trying that since everytime I upgraded Java in the past something else failed...

So all is good!

Version 6.1.1 (build fc853b) – May 31, 2017
Server jetty-6.1.x, java 1.7.0_79, HSQLDB, Windows 7 (95.5 MB / 123.2 MB)

[acroyear]

I agree on the Java thing. Java upgrades are causing my Eclipse to not run on my OSX box now.