Mango 3.0 Server Error

[larry]

Mango 3.0 New install (Windows 10) Loads fine. Runs When the data source page is opened it gives me the Server Error in the page. All the rest of the pages seem to open fine.????????

[JoelHaggar]

You might have a corrupted jsp file. Try deleting your "work" folder in the Mango directory and then refreshing the page. Mango will recreate the work folder with newly compiled jsp pages.

If that doesn't fix it you'll have to post the specific error message you see in your log files

[larry]

Here is the error from the log file:

startup date [Fri Dec 29 11:14:11 EST 2017]; parent: Root WebApplicationContext
instanceDescription=My Mango Automation
NEW_ID=-1
org.springframework.web.servlet.HandlerMapping.pathWithinHandlerMapping=/data_sources.shtm
org.springframework.security.web.csrf.CsrfToken=org.springframework.security.web.csrf.DefaultCsrfToken@e81be6d
javax.servlet.error.request_uri=/data_sources.shtm
org.springframework.web.servlet.DispatcherServlet.THEME_RESOLVER=org.springframework.web.servlet.theme.FixedThemeResolver@5a55c20
javax.servlet.jsp.jstl.fmt.locale.request=en_US
javax.servlet.error.exception=org.apache.jasper.JasperException: /WEB-INF/jsp/dataSource.jsp (line: 5, column: 0) The absolute uri: http://java.sun.com/jsp/jstl/core cannot be resolved in either web.xml or the jar files deployed with this application

[JoelHaggar]

Did deleting the "work" folder help?

[larry]

No When I restarted that is when I got those errors.

[terrypacker]

Make sure you are using the correct java runtime, a JDK not a JRE. Also make sure your {ma.home}/lib directory is readable by the user starting Mango and has not been altered. It sounds like that folder is missing a library or can’t read the file.

[johnykab]

I have the same problem under fresh installation of Mango 3.3.0 on fresh Ubuntu 16.04 64 bit server. None of the above mentioned solution doesn't work for me. After that I decided to lower the version of the Oracle's JDK (it was jdk-9.0.4) to jdk1.8.0_162 and everything goes fine and smoothly. Maybe there is some incompatibility with the latest version of JDK?!

[Jared Wiltshire]

@johnykab said in Mango 3.0 Server Error:

After that I decided to lower the version of the Oracle's JDK (it was jdk-9.0.4) to jdk1.8.0_162 and everything goes fine and smoothly. May be there is some incompatibility with the latest version of JDK?!

Yep Mango will not currently run on Java 9, its a known issue which we will try and resolve for the next major core release.

[anmont]

@jared-wiltshire This continues to be a problem in JDK 10. Also rather than suggesting at least version 1.8 or higher, maybe explicitly stating Oracle JDK 8 is required may save people the time of discovering this known issue for themselves.

[phildunlap]

@anmont

You are not wrong, it probably should have said that. It does say we recommend JDK 8 on the store's download page, but it doesn't say the others wouldn't have worked.

However, we are actively addressing compatibility issues. If you click the like to the known issue you will see that it's ready for testing. Mango 3.4, the beta of which is released, can be launched on Java 9 without encountering that illegal access exception. There may be lingering issues yet undiscovered, but you can definitely use Java 9 now! I haven't tested JDK 10 with it.