The browser periodically reads /proc/meminfo and checks MemTotal and MemAvailable entries there. Once MemAvailable drops less than browser.low_commit_space_threshold_percent (5% by default) of MemTotal or MemAvailable falls below browser.low_commit_space_threshold_mb (200 MiB by default), the tab unloading mechanism is notified to do its job
After navigate in several articles I found the real reason of the issue. It is not a JDBC driver error but a configuration needed for Oracle database instance running inside a Docker container.
You need to change $ORACLE_HOME/network/admin/sqlnet.ora append DISABLE_OOB=ON at end of file. So, you can try to connect again. It is not necessary restart database or listener.
Set gfx.color_management.mode to 1 to enable colormanagement. The parameter changes to bold text which indicates that it is now user-defined.
Below are all parameters which can be altered:
gfx.color_management.display_profile
The Full Path to you monitor’s color profile. For example: C:\colorprofiles\HP Z27x\HP Z27x sRGB D65 ICC Profile.icm
gfx.color_management.enablev4
Set to true (doubleclick the entry) to enable colormanagement v4 (Recommended).
gfx.color_management.mode
0 – Disable color management.
1 – Enable color management for all rendered graphics. (Recommended)
2 – Enable color management only for tagged images only. (Default)
gfx.color_management.rendering_intent
-1 Honor the rendering intent specified in the image file.
0 Perceptual (Default) (Recomended)
1 Relative colorimetric
2 Saturation
3 Absolute colorimetric
To finaly enable color management you have to restart firefox.
There are two ways to specify how GET parameters are interpreted:
Set the URIEncoding attribute on the <Connector> element in server.xml to something specific (e.g. URIEncoding="UTF-8").
Set the useBodyEncodingForURI attribute on the <Connector> element in server.xml to true. This will cause the Connector to use the request body's encoding for GET parameters.
Log4j will inspect the "log4j.configurationFile" system property and, if set, will attempt to load the configuration using the ConfigurationFactory that matches the file extension.
If no system property is set the properties ConfigurationFactory will look for log4j2-test.properties in the classpath.
If no such file is found the YAML ConfigurationFactory will look for log4j2-test.yaml or log4j2-test.yml in the classpath.
If no such file is found the JSON ConfigurationFactory will look for log4j2-test.json or log4j2-test.jsn in the classpath.
If no such file is found the XML ConfigurationFactory will look for log4j2-test.xml in the classpath.
If a test file cannot be located the properties ConfigurationFactory will look for log4j2.properties on the classpath.
If a properties file cannot be located the YAML ConfigurationFactory will look for log4j2.yaml or log4j2.yml on the classpath.
If a YAML file cannot be located the JSON ConfigurationFactory will look for log4j2.json or log4j2.jsn on the classpath.
If a JSON file cannot be located the XML ConfigurationFactory will try to locate log4j2.xml on the classpath.
If no configuration file could be located the DefaultConfiguration will be used. This will cause logging output to go to the console.