If you are using a generic JDBC account try adding “AUTO_SERVER” = “TRUE” to the Url properties.
You’ll also need to upload the h2 jar at ‘Jdbc jars’.
If you’ve explicitly specified the database URL try appending “;AUTO_SERVER=TRUE” to the URL everywhere you call it. You’ll want to do the same if you start the server with a script.
In any case you should start with a generic JDBC snap and account and verify that you can access the database with an existing snap. That lets you rule out any unexpected issues such as bad permissions, incompatible jars, etc., before you start developing your own code. That can save you a tremendous amount of effort down the road.
I have not open the snaplogic designer to make a connection, this issue is coming while doing configuration on groundplex, please refer below steps
I have modified – opt/snaplogic/etc/keys.properties file and /opt/snaplogic/etc/global.properties file after that while executing below commands got the exception.
cd ~/opt/snaplogic/run/lib
$ java -jar jcc.war jcc
For better understand my question, please go to this url Snap Development Documentation and seet the configuration section.
Exception:
2018-10-29T21:32:18,163 E main [ ] Error while loading web app configuration. Shutting down, please verify the jcc properties. javax.servlet.ServletException: JCC cannot be initialized properly [Failed to initialize pool: Database may be already in use: “C:/opt/snaplogic/run/bstore-Emirates_Training-sidekick-dev-1.mv.db”. Possible solutions: close all other connection(s); use the server mode [90020-182]]
at com.snaplogic.common.web.RequestFilter.init(RequestFilter.java:139) ~[jcc-4.0.jar:?]
at org.eclipse.jetty.servlet.FilterHolder.initialize(FilterHolder.java:139) ~[jetty-servlet-9.4.0.v20161208.jar:9.4.0.v20161208]
at org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:725) ~[jetty-servlet-9.4.0.v20161208.jar:9.4.0.v20161208]
at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:348)
@nagrajps, It would appear that an H2 file database was saved to the Groundplex installation directory. I would strongly recommend moving that database to a different location on the server, so that the it does not interfere with the operation of the plex.
If a JDBC Snap is using the file protocol to point to the old location, please update those Snap settings to reflect the new location.
I misunderstood the source of the H2 database. Redacting my answer.
