Highlighted
Respected Contributor.
Respected Contributor.
561 views

JRTE E LockHandler: failed to lock, it might be database failure

Jump to solution

Hi experts,

   I just found the following disturbing line in our production sm.log:

4504( 6932) 09/04/2018 11:47:26 JRTE E LockHandler: failed to lock, it might be database failure, rc=-1, lock = Key:schedule:sla, IP:<XXXXXXXXXXX>, PID:4504, TID: 6648, SID: 57, Retry: 0

   Obviously went on googling it but haven't found anything. We haven't noticed any error. Should I be worried?

BR,

Dávid

0 Likes
1 Solution

Accepted Solutions
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..

Re: JRTE E LockHandler: failed to lock, it might be database failure

Jump to solution

How frequently this log is appearing?

If it is recurring, please try killing the sla process and restart the sla scheduler.

View solution in original post

1 Reply
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..

Re: JRTE E LockHandler: failed to lock, it might be database failure

Jump to solution

How frequently this log is appearing?

If it is recurring, please try killing the sla process and restart the sla scheduler.

View solution in original post

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.