Bug 1152774

Summary: When CMR is used WARN message "Could not lookup CommitMarkableResource" appears in log
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Ondrej Chaloupka <ochaloup>
Component: Transaction ManagerAssignee: tom.jenkinson
Status: CLOSED CURRENTRELEASE QA Contact: Ondrej Chaloupka <ochaloup>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.4.0CC: hhovsepy, kkhan
Target Milestone: DR11   
Target Release: EAP 6.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-19 12:43:19 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:    
Bug Blocks: 1165728    
Attachments:
Description Flags
server.log with warning message none

Description Ondrej Chaloupka 2014-10-14 22:51:56 UTC 
Created attachment 947053 [details]
server.log with warning message

This is the same issue as: https://bugzilla.redhat.com/show_bug.cgi?id=1077407

It's quite strange that this issue disappear on EAP 6.3.0 but during test of EAP 6.3.0.DR5 appears again.

Symptoms:
if CMR datasource is defined then warning message 
WARN  [com.arjuna.ats.arjuna] (Periodic Recovery) Could not lookup CommitMarkableResource: ...
is shown in the log.
It seems that the CMR recovery module tries to use the datasource before it's bound. 

Would be possible to move the message from WARN to DEBUG level?
Comment 2 tom.jenkinson 2014-10-15 10:00:32 UTC 
https://github.com/jbosstm/narayana/pull/743
Comment 3 tom.jenkinson 2014-11-04 10:31:37 UTC 
Resolved upstream: https://github.com/jbosstm/narayana/commit/7cd36d7b9c35df05f6b7bc4130c46973e80aa222
Comment 4 Ondrej Chaloupka 2014-11-26 11:40:26 UTC 
The message was moved to DEBUG. Verified for EAP 6.4.0.DR11.