Hi,
We are using the Service Broker External Activator Service and we've come across an error involving runtime checkpointing and the process not being able to access the EARecovery.rlog file.. it goes like this:
2014/06/09 10:15VERBOSECheckpointing recovery log C:\Program Files\Service Broker\External Activator\log\EARecovery.rlog ...2014/06/09 10:15ERRORThe External Activator service is aborting ...
2014/06/09 10:15EXCEPTIONERROR = 90, Internal exceptions have occurred when External Activator is runtime checkpointing.
2014/06/09 10:15EXCEPTIONDETAILSInner Exception:
2014/06/09 10:15EXCEPTIONDETAILSSystem.IO.IOException: The process cannot access the file 'C:\Program Files\Service Broker\External Activator\log\EARecovery.rlog' because it is being used by another process.
2014/06/09 10:15EXCEPTIONDETAILS at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
2014/06/09 10:15EXCEPTIONDETAILS at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy)
2014/06/09 10:15EXCEPTIONDETAILS at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
2014/06/09 10:15EXCEPTIONDETAILS at ExternalActivator.LogManager.CompressRecoveryLog(LogRecoveryContext recoveryContext)
2014/06/09 10:15EXCEPTIONDETAILS at ExternalActivator.LogManager.Checkpoint(LogRecoveryContext recoveryContext)
2014/06/09 10:15EXCEPTIONDETAILS at ExternalActivator.LogManager.Log(LogRecord recoveryLogRec)
2014/06/09 10:15EXCEPTIONDETAILS at ExternalActivator.ApplicationMonitor.OnProcessExited(ProcessMonitor processMonitor)
2014/06/09 10:15EXCEPTIONDETAILS at ExternalActivator.ProcessMonitor.NotifySubscriber()
2014/06/09 10:15EXCEPTIONDETAILS at ExternalActivator.ProcessMonitor.OnProcessExited(Object a, EventArgs b)
2014/06/09 10:15VERBOSEHeartbeat-Thread is exiting...
2014/06/09 10:15VERBOSEWaiting for worker threads to finish...
2014/06/09 14:13======================================================================================
2014/06/09 14:13======================================================================================
This happened a few days ago and we are pretty sure nobody was using the file as this is a production application server... and then it happened again several days later...
We have to kill the process and restart the service to get things going again.
Any help would be greatly appreciated as this is not a viable way of doing things for us.
Thanks
Gabriel