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

Bug 1077407

Summary: When CMR is defined WARN message is shown in the log
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Ondrej Chaloupka <ochaloup>
Component: Transaction ManagerAssignee: Michael <mmusgrov>
Status: CLOSED CURRENTRELEASE QA Contact: Ondrej Chaloupka <ochaloup>
Severity: medium Docs Contact: Russell Dickenson <rdickens>
Priority: unspecified    
Version: 6.3.0CC: hhovsepy
Target Milestone: ER4   
Target Release: EAP 6.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-28 15:25: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:
Attachments:
Description Flags
Standalone xml with configured CMR none

Description Ondrej Chaloupka 2014-03-17 22:47:29 UTC 
Description of problem:
When commit markable resource is defined under transaction subsystem then warning message with content:
23:33:20,602 WARN  [com.arjuna.ats.arjuna] (Periodic Recovery) Could not lookup CommitMarkableResource: <jndi_name_of_configured_cmr>
is shown.

It's not clear what's happening. Whether there is  some trouble in loading CMR or what.

In fact this is not an issue as the datasource is bound after the TM is started. In time when Periodic Recovery checks the existence of the datasource the datasource is not yet bound and the warning message is shown. In the next round the ds is already bound and periodic recovery thread is satisfied.

But still the log contains warning messages which are not obvious for normal user.

This could be a bit problematic but could be possible to somelike better describe what's happening (that's not a problem) to the user?
Comment 1 Ondrej Chaloupka 2014-03-17 22:49:08 UTC 
Created attachment 875726 [details]
Standalone xml with configured CMR

For reproducing the warning it's necessary to take postgresql jdbc driver, name it dsdriver.jar and put it to eap deployments folder.

This was tested with EAP 6.3.0.DR4
Comment 2 tom.jenkinson 2014-05-07 15:12:13 UTC 
I wonder about maybe we could just not print a warning the very first pass of the recovery module, what do you think Mike?
Comment 3 Michael 2014-05-07 15:39:37 UTC 
We could do that quite easily but the issue is that the transaction subsystem starts before JCA starts so when we lookup the datasource it isn't registered. 

Will the resolution for https://bugzilla.redhat.com/show_bug.cgi?id=1091308 help here, if not then lets fix it by only printing the warning on the next recovery pass.
Comment 4 Ondrej Chaloupka 2014-05-07 15:51:09 UTC 
Just a note from me: if you test this on later EAP 6.3.0 version I can see that the message was moved from WARN to DEBUG log level.
Comment 5 Michael 2014-05-19 12:20:46 UTC 
I think Tom did that so the bug status should either be moved to POST or not a bug. What do you think Ondrej?
Comment 6 Ondrej Chaloupka 2014-05-19 13:55:00 UTC 
Yeap, I agree. It could be moved to POST (or to ON_QA) - I'm not sure what is the procedure - and it could be verified now for 6.3.0.ER4. 
Can you do so?
Comment 7 Ondrej Chaloupka 2014-05-29 11:36:50 UTC 
The log level was changed to debug so the error/warning message is not shown normally.
Verified for EAP 6.3.0.ER5.