Details
-
Fix
-
Status: Released (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
-
None
Description
Current Situation
- The JOC Cockpit includes a number of JDBC Drivers that ship with the product.
- If a users adds an individual JDBC Driver then there is no control of the priority of .jar files with the classpath in Jetty
Desired Behavior
- When specifying during setup that no internal connector should be used then the JOC Cockpit setup should not install the respective internal connectors.
Maintainer Note
- Internal JDBC drivers provided by the setup are no longer included in the war file (./jetty_base/webapps/joc.war), but are stored under ./jetty_base/lib/ext/joc.
- Only those JDBC drivers that are required are stored.
Workaround
- You can apply the attached patch file for use with Oracle databases:
- stop JOC Cockpit
- Download patch_20200210_Oracle.zip
- copy it to the directory ./jetty_base/patches/ of the JOC installation
- call java
jar ./jetty_base/patches/bin/patch-executor<version>.jar - start JOC Cockpit
- Check the article Apply Patches to JOC Cockpit for more information