Jasper Server errors on Tomcat

[aeaston]

Good day,

     I'm new to JasperReports and I just installed jasperserver ce 7.8 on a RHEL 7 VM with an existing Tomcat server and it's not working correctly (js-install-ce.sh minimal).  The Login button is greyed out and I'm getting the following errors in the catalina.out file on Tomcat.  I've brought up the page, https://<myserver>:8443/jasperserver/login.html,  in Chrome, FireFox, and Edge and the Login is disable in all of them.  I'm not sure if the two items are related.  I've been using the https://community.jaspersoft.com/system/files/restricted-docs/jasperreports-server-cp-install-guide_10.pdf instructions and searching the community website, but I'm not seeing anything that matches my issues. I did add the parameter of enablepooling to false to hopefully help with the memory errors.

ERROR JNDIResourceProvider,main:75 - error closing context javax.naming.OperationNotSupportedException: Context is read only
        at org.apache.naming.NamingContext.checkWritable(NamingContext.java:990)
        at org.apache.naming.NamingContext.close(NamingContext.java:759)
        at com.tonbeller.tbutils.res.JNDIResourceProvider.close(JNDIResourceProvider.java:72)
        at com.tonbeller.tbutils.res.CompositeResourceProvider.close(CompositeResourceProvider.java:56)
        at com.tonbeller.tbutils.res.ResourcesFactory.initialize(ResourcesFactory.java:163)

ERROR SystemErrorController,https-jsse-nio-8443-exec-7:86 - Internal server error java.lang.NullPointerException
    at com.jaspersoft.jasperserver.war.themes.ThemeResolverServlet.doGet(ThemeResolverServlet.java:115)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:634)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:741)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
    at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)

[vchiem]

The second error points to an issue with themes. A fresh install should not have this problem when it installs the default active theme. It is hard to tell where it may have gone wrong with the current information but it is best to check the js-install log that was generated when js-install script was ran. Before running this script, the tomcat appserver should have been stopped and post install, tomcat work and temp directory contents should have been cleared.

[aeaston]

I made sure that Tomcat was stopped before I ran the install, but that didn't help.  The only way I was able to get this working was to install the software with the bundled database and Tomcat.