Bug 1288132

Summary: Same 'Completed indexing' message 3 times in the server log
Product: [Retired] JBoss BRMS Platform 6 Reporter: Zuzana Krejčová <zkrejcov>
Component: Business CentralAssignee: manstis
Status: CLOSED EOL QA Contact: Lukáš Petrovický <lpetrovi>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: lpetrovi
Target Milestone: DR1   
Target Release: 6.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-27 19:42:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Zuzana Krejčová 2015-12-03 15:57:40 UTC
Description of problem:
See summary and steps to reproduce/actual result.


Version-Release number of selected component (if applicable):
6.2 CR2


Steps to Reproduce:
1. Start clean business central with enabled example repository.
2. Wait until deployment and initial indexing finishes,
3. Look into server log.


Actual results:
'Completed indexing of default://master@repository1/' is logged 3 times:
16:51:30,929 INFO  [org.uberfire.ext.metadata.io.BatchIndex] (EJB default - 8) Completed indexing of default://master@datasets/
16:51:31,578 INFO  [org.uberfire.ext.metadata.io.BatchIndex] (EJB default - 7) Completed indexing of default://master@repository1/
16:51:31,600 INFO  [org.uberfire.ext.metadata.io.BatchIndex] (EJB default - 10) Completed indexing of default://master@repository1/
16:51:36,539 INFO  [org.uberfire.ext.metadata.io.BatchIndex] (EJB default - 1) Completed indexing of default://master@repository1/


Expected results:
Once would be enough.


Additional info:
There are no problems resulting from this, as far as I can tell, it is just a minor annoyance.

Comment 1 manstis 2015-12-03 16:22:49 UTC
Business Central is actually indexing 'repository1' three times:-

16:11:25,028 INFO  [org.uberfire.ext.metadata.io.BatchIndex] (EJB default - 8) Starting indexing of default://master@repository1/ ...
16:11:25,030 INFO  [org.uberfire.ext.metadata.io.BatchIndex] (EJB default - 5) Starting indexing of default://master@datasets/ ...
16:11:25,030 INFO  [org.uberfire.ext.metadata.io.BatchIndex] (EJB default - 7) Starting indexing of default://master@repository1/ ...
16:11:25,034 INFO  [org.uberfire.ext.metadata.io.BatchIndex] (EJB default - 4) Starting indexing of default://master@repository1/ ...
...
16:11:27,004 INFO  [org.uberfire.ext.metadata.io.BatchIndex] (EJB default - 4) Completed indexing of default://master@repository1/
16:11:27,004 INFO  [org.uberfire.ext.metadata.io.BatchIndex] (EJB default - 8) Completed indexing of default://master@repository1/
16:11:27,183 INFO  [org.uberfire.ext.metadata.io.BatchIndex] (EJB default - 7) Completed indexing of default://master@repository1/

This should not be happening!

Comment 2 Zuzana Krejčová 2015-12-03 16:41:34 UTC
(In reply to manstis from comment #1)
> Business Central is actually indexing 'repository1' three times:-
> 
> 16:11:25,028 INFO  [org.uberfire.ext.metadata.io.BatchIndex] (EJB default -
> 8) Starting indexing of default://master@repository1/ ...
> 16:11:25,030 INFO  [org.uberfire.ext.metadata.io.BatchIndex] (EJB default -
> 5) Starting indexing of default://master@datasets/ ...
> 16:11:25,030 INFO  [org.uberfire.ext.metadata.io.BatchIndex] (EJB default -
> 7) Starting indexing of default://master@repository1/ ...
> 16:11:25,034 INFO  [org.uberfire.ext.metadata.io.BatchIndex] (EJB default -
> 4) Starting indexing of default://master@repository1/ ...
> ...
> 16:11:27,004 INFO  [org.uberfire.ext.metadata.io.BatchIndex] (EJB default -
> 4) Completed indexing of default://master@repository1/
> 16:11:27,004 INFO  [org.uberfire.ext.metadata.io.BatchIndex] (EJB default -
> 8) Completed indexing of default://master@repository1/
> 16:11:27,183 INFO  [org.uberfire.ext.metadata.io.BatchIndex] (EJB default -
> 7) Completed indexing of default://master@repository1/
> 
> This should not be happening!

Hmm, I didn't even see that in all the server log noise. Luckily it doesn't change the fact that it seems to not cause any problems. And the repo is pretty much empty at that time. I also haven't seen this happen for any other repository.

Comment 3 manstis 2015-12-04 11:29:06 UTC
The cause is that multiple requests are made for the "repository1" FileSystem before the batch indexing has flagged that batch indexing is "in progress"; hence multiple batch indexing takes place. There is little risk running multiple batch indexing of the same FileSystem; it's just wasteful.

The three batch indexing observed are caused by:-

1 - Creating "repository1" repository.
2 - jBPM Designer writing a "global" folder to "repository1".
3 - system.git changed (as a result of "repository1" being added).

Comment 6 Zuzana Krejčová 2016-03-30 11:41:03 UTC
Now I see the repository1 indexing just 2 times instead of 3.