Rich Bair

Sorry, a Windows service.

Is there a new process to launch Jtrac as a service in 2.2.2? I do not see the wrapper tool. Thanks, -Rich

Thanks. I'm not sure how to fix this so will just use server:8888/jtrac for now.

Maybe it's more of an alias issue? I just don't know why the 8888 is now required whereas before it was not. I don't think I can use a different WAR file as I used the special one you made to work with older databases from https://sourceforge.net/projects/j-trac/files/jtrac/2.2.1/hsqldb-1810/ Thanks, -Rich

Prior to my 2.2.2 update I used to server from /server/jtrac but now its /server:8888/jtrac. I added -Djetty.port=80 to start.bat but no change. How can I get back to server/jtrac? Thanks, -Rich

I'm unable to upgrade to 2.2.1 and after trying I now am unable to launch 2.1.0. I was able to launch 2.2.1 on port 8888 checking on the server side but not using my old database just a new one. It appears my HSQLDB is too old. At this point, I really need to get 2.1.0 running as I have valuable data so I'm focused on the errors below. Java upgraded to below as part of getting ready for 2.2.1: C:\Users\xxxxxxx>java -version java version "1.8.0_341" Java(TM) SE Runtime Environment (build 1.8.0_341-b10)...

Hang on...I think I'm up. I now copied the jtrac.war file above into the webapps folder and changed the root.war to root.war1. I'm testing but it looks like it's serving up and showing 2.2.2

I've also tried this process on a database started in ~2007 or so. I copied the special jtrac.war file above into c:\jtrac-2.2.1 and have updated Java. I copied the entire data folder from my 2.1.0 in the 2.2.1 folder and I see the below errors early in the file and serve up a 503. Now realize (in my other thread) 503 also serves up in my 2.10 case due to an unknow issue; however, the errors are quite different. I'm just looking for anyway to get my jtrac database back presently using 2.2.1 or 2.1.0....