Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1073397

Summary: Error in server log on business central deployment: Cannot create directory: .index/repository1
Product: [Retired] JBoss BRMS Platform 6 Reporter: Jiri Svitak <jsvitak>
Component: Business CentralAssignee: Alexandre Porcelli <porcelli>
Status: CLOSED DUPLICATE QA Contact: Jiri Locker <jlocker>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0.1CC: kverlaen, mbaluch, rrajasek
Target Milestone: CR2   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-04-10 09:32:36 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:
Bug Depends On: 1064212    
Bug Blocks:    
Attachments:
Description Flags
server.log none

Description Jiri Svitak 2014-03-06 10:53:12 UTC
Created attachment 871334 [details]
server.log

The following error is thrown when deploying standalone business central on a physical server in a lab:

05:25:15,568 ERROR [org.uberfire.metadata.io.BatchIndex] (Thread-77) Index fails. [@/readme.md]: java.lang.RuntimeException: java.io.IOException: Cannot create directory: /mnt/hudson_workspace/bpms-perf/bpms-6.0.1.ER2/jboss-eap-bpms/.index/repository1
	at org.uberfire.metadata.backend.lucene.index.directory.DirectoryLuceneIndex.<init>(DirectoryLuceneIndex.java:53) [uberfire-metadata-backend-lucene-0.3.2-redhat-3.jar:0.3.2-redhat-3]

See the attached server.log.

It appears that everything works fine. Even the erroneous directory exists there:

[hudson@brmsperf02 bpms-perf]$ ls -l bpms-6.0.1.ER2/jboss-eap-bpms/.index/repository1/
total 184
-rw-rw-r--. 1 hudson hudson  293 Mar  6 05:25 _0.fdt
-rw-rw-r--. 1 hudson hudson   42 Mar  6 05:25 _0.fdx
...

The product shouldn't produce no such error messages, if they do not block other functionality.

My env:
BPMS 6.0.1.ER2
EAP 6.1.1
Oracle11gR2

Comment 1 Alexandre Porcelli 2014-03-06 11:55:58 UTC
This was reported and fixed on #1064212 - need to check if those commits are on ER2.

Comment 2 Rajesh Rajasekaran 2014-04-04 21:40:00 UTC
Setting to ON_QA to verify on 6.0.1 as this seems to be the same issue as BZ#1064212

Comment 3 Jiri Locker 2014-04-10 09:32:36 UTC
Can't reproduce with ER2. Looking at the attached server log I can see some 6.0.2-redhat-3 artifacts, suggesting this was either tested with 6.0.1.ER1 or the first 6.0.1.ER2 build that was rejected and.

Closing as duplicate of bz 1064212.

*** This bug has been marked as a duplicate of bug 1064212 ***