-
Bug
-
Resolution: Won't Fix
-
Critical
-
None
-
6.1.1, 6.1.2, 6.1.3, 6.1.4, 6.1.5, 6.2, 6.2.1, 6.2.2
-
Windows & Ubuntu local startup using H2-PM and having more than one NIC.
Situation:
- Using H2 PM on Windows (or Ubuntu) AND having more than one NIC
- H2-PM is configured using the value 'AUTO_SERVER=FALSE' in:
WEB-INF/config/repo-conf/jackrabbit-bundle-h2-search.xml
<PersistenceManager class="org.apache.jackrabbit.core.persistence.bundle.H2PersistenceManager"> <param name="url" value="jdbc:h2:${rep.home}/version/db;AUTO_SERVER=FALSE" /> <param name="schemaObjectPrefix" value="version_" /> </PersistenceManager>
Problem:
Startup when reading the H2 data it takes around 5-10 minutes (!!) to load all workspaces.
Root couse:
http://www.h2database.com/html/features.html -> Automatic Mixed Mode
The 'Automatic Mixed Mode' opens a port and would allow multiple connections into the PM/DB.
This seems to cause severe problems on Windows when having more than one NIC on the machine, for example when being plugged into a docking-station.
It seems that on any file access/change in the H2-FS it waits for a time out of the second NIC which doesn't serve any response as no tomcat is running/responding on it.
Solution:
- Set the value to 'AUTO_SERVER=FALSE' before first deployment. Otherwise this value is persisted in each workspace.xml.
- Magnolia should set that value in our webapp and bundle to 'AUTO_SERVER=FALSE'
Acceptance criteria