[MAGNOLIA-2854] Cleanup obsolete Jackrabbit configuration from default webapp Created: 19/Aug/09 Updated: 23/Jan/13 Resolved: 23/Sep/09 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.1 |
| Type: | Task | Priority: | Major |
| Reporter: | Fabrizio Giustina | Assignee: | Magnolia International |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
The default webapp contains several jackrabbit sample configurations, but most of them are outdated and should not be suggested. this is the list of current files with proposed blacklist: jackrabbit-bundle-derby-search.xml -> ok jackrabbit-bundle-mysql-search.xml -> ok jackrabbit-derby-search.xml -> should be removed, non-bundle db persistence managers are not suggested jackrabbit-file-nosearch.xml -> to be removed: "nosearch" configurations doesn't work with magnolia anymore and the file persistence manager is definitively not suggested jackrabbit-file-search.xml -> remove: file persistence manager is definitively not suggested jackrabbit-memory-search.xml -> keep (if update to jackrabbit 1.6 we can modify this to add in memory search index configuration, new in 1.6 and useful for development) jackrabbit-mysql-search.xml -> remove, non-bundle db persistence managers are not suggested The dtd of surviving configuration file should also be updated (now it's 14, should be moved at least to 1.5 o 1.6 as soon as we upgrade the dependency); all the configurations are now missing a data store, which should be added. Mysql configuration should contain the "autoreconnect" parameter in urls. |
| Comments |
| Comment by Magnolia International [ 31/Aug/09 ] |
|
Removed obsolete files, added DataStore (doesn't seem to make sense with the in-memory config, does it?) and updated DTD references. Also, the mysql connection url should not use Mysql's autoreconnect; Jackrabbit has its own reconnection mechanism; it's not recommended to use this, even per MySQL: http://dev.mysql.com/doc/refman/5.0/en/connector-j-reference-configuration-properties.html As for upgrading to 1.6, we probably will not do it until 4.2/5.0 (whichever comes first), unless there's a good reason to do so. |
| Comment by Fabrizio Giustina [ 31/Aug/09 ] |
Never played so much with that parameter, I always left the 1024 default with no problems...
If you don't configure it you will end up with lot of errors logged by jackrabbit every time the connection times out... it can happen pretty frequently with the default timeout of mysql, jackrabbit recovers lost connections but the first operation seems to fail with an error, with this parameter it seems to happen less frequently |
| Comment by Magnolia International [ 01/Sep/09 ] |
|
In fact, the default is (according to docs) set to 100, which seemed unnecessarily low. The error JR logs should be harmless; and maybe we should document/recommend a longer timeout. |