Embedded Tomcat in Openboxes war?

general
1

Hi All,

I am following the steps mentioned in Application - OpenBoxes till the step when I have to start stop tomcat service.

I get an error message tomcat.service not found.

For the Ubuntu 1804-grails3 installation, there is no tomcat installation. It mentioned the tomcat is embedded in the war. I’m puzzled how this is going to work.

  1. May I know whether there is a need to install tomcat ?

  2. Would it be Tomcat version 8 since the java is using version 8?

Thanks.

2

I’ll have to run through the instructions myself to troubleshoot. Unfortunately I probably don’t have time today but I’ll investigate as soon as I can.

  1. You do not need to install Tomcat. The WAR file has its own embedded Tomcat that is included as a dependency during the build process. When we run java -jar on the WAR, Spring Boot will boot up Tomcat and launch the application.

  2. It doesn’t really matter which version of Tomcat we use. Tomcat 7, 8, and 9 are all probably compiled with Java 8. The reason we use Tomcat 7 is to ensure consistency as we continue to debug issues related to the Grails 3 migration.

3

Thanks for the response.

Your response gave me the clue to know what to do.

Since the Tomcat is built in and will boot up when the application is run, there is no need to stop and start the Tomcat.

I only stop and start the application, and I confirmed the Tomcat is launched from looking at the logs.

Thank you.

4

Is the WAR file for the Grails 3 different from the WAR file found on github (https://github.com/openboxes/openboxes/releases/download/v0.8.16-hotfix3/openboxes.war)

I have followed the directions for installing the Grails 3 version and ran into the following error

Feb 23 01:07:06 openboxes-grails systemd[1]: Stopped OpenBoxes app.
Feb 23 01:07:06 openboxes-grails systemd[1]: Started OpenBoxes app.
Feb 23 01:07:06 openboxes-grails java[26245]: no main manifest attribute, in /opt/openboxes/openboxes.war
Feb 23 01:07:06 openboxes-grails systemd[1]: openboxes.service: Main process exited, code=exited, status=1/FAILURE
Feb 23 01:07:06 openboxes-grails systemd[1]: openboxes.service: Failed with result 'exit-code'.
Feb 23 01:07:16 openboxes-grails systemd[1]: Stopped OpenBoxes app.
Feb 23 01:08:39 openboxes-grails systemd[1]: Started OpenBoxes app.
Feb 23 01:08:39 openboxes-grails java[26312]: no main manifest attribute, in /opt/openboxes/openboxes.war
Feb 23 01:08:39 openboxes-grails systemd[1]: openboxes.service: Main process exited, code=exited, status=1/FAILURE
Feb 23 01:08:39 openboxes-grails systemd[1]: openboxes.service: Failed with result 'exit-code'.
Feb 23 01:08:49 openboxes-grails systemd[1]: openboxes.service: Service hold-off time over, scheduling restart.
Feb 23 01:08:49 openboxes-grails systemd[1]: openboxes.service: Scheduled restart job, restart counter is at 322.
Feb 23 01:08:49 openboxes-grails systemd[1]: Stopped OpenBoxes app.
Feb 23 01:08:49 openboxes-grails systemd[1]: Started OpenBoxes app.
Feb 23 01:08:49 openboxes-grails java[26327]: no main manifest attribute, in /opt/openboxes/openboxes.war
Feb 23 01:08:49 openboxes-grails systemd[1]: openboxes.service: Main process exited, code=exited, status=1/FAILURE
Feb 23 01:08:49 openboxes-grails systemd[1]: openboxes.service: Failed with result 'exit-code'.

Java 8

openjdk version "1.8.0_322"
OpenJDK Runtime Environment (Zulu 8.60.0.21-CA-linux64) (build 1.8.0_322-b06)
OpenJDK 64-Bit Server VM (Zulu 8.60.0.21-CA-linux64) (build 25.322-b06, mixed mode)

MySQL 5.7
mysql Ver 14.14 Distrib 5.7.37, for Linux (x86_64) using EditLine wrapper

Ubuntu

Distributor ID: Ubuntu
Description:    Ubuntu 18.04.6 LTS
Release:        18.04
Codename:       bionic
5

Yes. Grails 3 refers to a branch of the software that is being migrated to Grails 3. We haven’t finished the migration (it’s been stalled for at least a year or more) so there’s no stable release at the moment. When it’s done it’ll become the default branch.