[ACE-1405] SOLR 4 checks for Quartz update Created: 27-Mar-14  Updated: 03-Mar-16  Resolved: 18-Aug-15

Status: Closed
Project: Alfresco One Platform
Component/s: Search and Indexing (non-UI)
Affects Version/s: 4.2.f Community
Fix Version/s: Community Edition 201508 EA, 5.1

Type: Bug Priority: Unprioritized
Reporter: Charles Le Seac'h (Inactive) Assignee: Closed Issues
Resolution: Fixed Votes: 0
Labels: K2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File solr.diff    
Issue Links:
Related
is related to by MNT-12313 Repo sends data to terracotta.org on ... Closed
Build Location: https://bamboo.alfresco.com/bamboo/browse/ALF-EREPO0-234
Story Points: 3
Epic Link: SOLR 4 in 5.1

 Description   

Quartz is used in SOLR (bundled with Alfresco) to schedule Alfresco polling.
When SOLR starts, Quartz checks Terracotta server for an update. That shouldn't happen.

The problem comes from the non-definition of the property "org.quartz.scheduler.skipUpdateCheck" (should be set to true).
This property can be set in java options, but it would be better if we have, by default, a correct configuration.

Provided diff file is for Alfresco project SOLR (source code used is https://svn.alfresco.com/repos/alfresco-open-mirror/alfresco/COMMUNITYTAGS/V4.2f/root/projects/solr).
It sets by default the property org.quartz.scheduler.skipUpdateCheck to "true" :
properties.setProperty("org.quartz.scheduler.skipUpdateCheck","true");

But it also adds the use of quartz.properties file in order to set the scheduler properties.
Warning : quartz.properties has to be available either in solrHome, or in classpath.



 Comments   
Comment by Andrew Hind [X] (Inactive) [ 10-Apr-14 ]

Add property to remove warning.

Comment by Andrew Hind [X] (Inactive) [ 03-Aug-15 ]

Charles Le Seac'h What do you need to set via properties that is not exposed already?

Comment by Andrew Hind [X] (Inactive) [ 18-Aug-15 ]

Additional configuration does not show logging of this check.

Generated at Fri Jul 10 04:15:44 BST 2020 using JIRA 7.6.3#76005-sha1:8a4e38d34af948780dbf52044e7aafb13a7cae58.