MESH Client Services is Not Releasing Lock

Message Exchange for Social Care and Health (MESH)
1

Hi,

We have been running a MESH client for a while. Lately it failed due to a change in Java environment. I have redirected the service to the new jvm.dll but now I find that, after the first run, the mesh.lck file never clears. I get errors like;

2026-02-18 16:24:56,131:[main                ]:WARN :MeshClient          :Failed to lock file: mesh.lck
2026-02-18 16:24:56,131:[main                ]:FATAL:MeshClient          :MESH Client failed to start.  Unable to lock file mesh.lck
2026-02-18 16:24:56,131:[main                ]:INFO :MeshClient          :Check that the MESH Client is not already running.
2

Hi Shaun,

Please can you delete the mesh.lck file from \MESH-APP-HOME\working\ and try restarting your MESH Client again.

Regards
Paddy

3

I have deleted it and started the service again. Only interesting thing to note (so far) is a bad checksum on MESH client update. Will post again when 30 mins have passed.

2026-02-18 17:11:31,647:[pool-3-thread-1     ]:INFO :SignalFileMonitor   :Starting SignalFileMonitor
2026-02-18 17:11:31,647:[Daily Housekeeper   ]:INFO :DailyHouseKeeper    :Starting MESH Client Housekeeping
2026-02-18 17:11:31,652:[Service Manager     ]:INFO :ServiceManager      :Creating Token Pool
2026-02-18 17:11:31,672:[Daily Housekeeper   ]:INFO :DailyHouseKeeper    :Finished MESH Client Housekeeping
2026-02-18 17:11:31,672:[MESH - AutoUpgrade  ]:INFO :UpdateHouseKeeper   :Performing scheduled check for MESH Client Upgrade
2026-02-18 17:11:31,672:[MESH - AutoUpgrade  ]:INFO :UpdateHouseKeeper   :Starting MESH Client Update Check
2026-02-18 17:11:32,097:[MESH - AutoUpgrade  ]:INFO :UpdateClientResponseHandler:Upgrade to client version=  is available for auto-upgrade
2026-02-18 17:11:32,097:[MESH - AutoUpgrade  ]:ERROR:ArchiveDetails      :Downloaded archive checksum is incorrect
2026-02-18 17:11:32,097:[MESH - AutoUpgrade  ]:WARN :UpdateHouseKeeper   :Unable to perform auto-upgrade download package is invalid
2026-02-18 17:11:32,107:[Mailbox:xxxx]:INFO :AuthenticationService:Successfully Authenticated Mailbox: xxxx
2026-02-18 17:11:32,112:[Mailbox:xxxx    ]:INFO :SendFilesService    :Sent 0 files for Mailbox:xxxx
2026-02-18 17:11:32,112:[Mailbox:xxxx    ]:INFO :MailboxProcessor    :Sent  0 files for Mailboxxxxx.
2026-02-18 17:11:32,263:[Mailbox:xxxx    ]:INFO :MailboxProcessor    :Received  0 files for Mailbox:xxxx
4

Hi Paddy,

No fatal error this time though the lock file has persisted since the service was started. I will let it run overnight and report in the morning.

Thanks,

Shaun

5

OK, that’s fixed it.

Thank you Paddy