EMS server reports, "WARNING: owned lock not current, refreshing".
Article ID: KB0093666
Updated On:
| Products | Versions |
|---|---|
| TIBCO Enterprise Message Service | - |
| Not Applicable | - |
Description
Description:
Symptoms:
When configuring the EMS server using database store, if the ft_heartbeat is set to a value higher than 10 seconds, the EMS server will repeatedly report the warning message: "WARNING: owned lock not current, refreshing".
Cause:
The following JIRA issue was created to fix this unnecessary warning message in EMS future release:
EMS-4943
EMS server repeatedly reports "WARNING: owned lock not current, refreshing" warning messages when ft_heartbeat is higher than 10 second
Why does the EMS server repeatedly report: "WARNING: owned lock not current, refreshing" in the EMS server log?
Symptoms:
When configuring the EMS server using database store, if the ft_heartbeat is set to a value higher than 10 seconds, the EMS server will repeatedly report the warning message: "WARNING: owned lock not current, refreshing".
Cause:
The following JIRA issue was created to fix this unnecessary warning message in EMS future release:
EMS-4943
EMS server repeatedly reports "WARNING: owned lock not current, refreshing" warning messages when ft_heartbeat is higher than 10 second
Issue/Introduction
EMS server reports, "WARNING: owned lock not current, refreshing".
Resolution
To get rid of this warning message, you can set the ft_heartbeat to a smaller value than 10 seconds.
Feedback
Yes
No
Powered by
