Announcement

Collapse

NextGen (Mirth) Connect 3.9.1 Released!

NextGen (Mirth) Connect 3.9.1 is now available as an appliance update and on our GitHub page. This release contains bug fixes and adds support for eHealth Exchange UDDI providers in the Interoperability plugin. See the release notes for the list of fixes and updates.

Download | See What's New | Upgrade Guide | Release Notes

For discussion on this release, see this thread.
See more
See less

Error - Wrapper.log - org.mule.MuleException: Failed to delete file

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • #1

    Error - Wrapper.log - org.mule.MuleException: Failed to delete file

    =======================
    Environment:

    Mirth 1.3.1 running as service on Windows XP Professional
    Channel: File Reader to Database
    =======================

    I see following errors (repeated with different file names) in wrapper.log file.

    Any help to resolve this would be appreciated.

    Thanks
    ==================================

    INFO | jvm 1 | 2007/01/08 17:28:45 | ERROR 2007-01-08 17:28:44,982 [d3922ef8-5c92-4f40-8f6c-0db562d25184_source_connector._fileEndpoint#205922 0050.receiver.1] org.mule.impl.DefaultComponentExceptionStrategy: Caught exception in Exception Strategy for: d3922ef8-5c92-4f40-8f6c-0db562d25184: org.mule.MuleException: Failed to delete file "C:\CembexMirthHL7\CembexMirthHL7Inbound\0CFDF F97-B6AC-48ca-A7C8-39C41EEFD565.HL7" as part of the file move operation
    INFO | jvm 1 | 2007/01/08 17:28:45 | org.mule.MuleException: Failed to delete file "C:\CembexMirthHL7\CembexMirthHL7Inbound\0CFDF F97-B6AC-48ca-A7C8-39C41EEFD565.HL7" as part of the file move operation
    INFO | jvm 1 | 2007/01/08 17:28:45 | at org.mule.providers.file.FileMessageReceiver.proces sFile(FileMessageReceiver.java:217)
    INFO | jvm 1 | 2007/01/08 17:28:45 | at org.mule.providers.file.FileMessageReceiver.poll(F ileMessageReceiver.java:111)
    INFO | jvm 1 | 2007/01/08 17:28:45 | at org.mule.providers.PollingMessageReceiver.run(Poll ingMessageReceiver.java:73)
    INFO | jvm 1 | 2007/01/08 17:28:45 | at org.mule.impl.work.WorkerContext.run(WorkerContext .java:290)
    INFO | jvm 1 | 2007/01/08 17:28:45 | at edu.emory.mathcs.backport.java.util.concurrent.Thr eadPoolExecutor$Worker.runTask(ThreadPoolExecutor. java:650)
    INFO | jvm 1 | 2007/01/08 17:28:45 | at edu.emory.mathcs.backport.java.util.concurrent.Thr eadPoolExecutor$Worker.run(ThreadPoolExecutor.java :675)
    INFO | jvm 1 | 2007/01/08 17:28:45 | at java.lang.Thread.run(Unknown Source)

    ==================================
    Tags: None
  • #2
    Re: Error - Wrapper.log - org.mule.MuleException: Failed to delete file

    If Mirth is running as a service, the service must run as an administer account to access files on the file system.

    -Chris
    Chris Lang

    Comment

    • #3
      Re: Error - Wrapper.log - org.mule.MuleException: Failed to delete file

      The logon account used to run Mirth service has full access to INBOUND folder (directory on the local drive).

      Also, this error does not happen for all the files but does happen in random. Out of more than 24,000 messages processed, there are less than 10 such errors in the wrapper.log file.

      Comment

      • #4
        Re: Error - Wrapper.log - org.mule.MuleException: Failed to delete file

        Hmm, interesting - do you have "process messages in order received/synchronized" checked on the channel? This seems like an issue with multiple threads trying to process the messages...
        Chris Lang

        Comment

        • #5
          Re: Error - Wrapper.log - org.mule.MuleException: Failed to delete file

          Yes, "Process messages in order received" is checked (it is a requirement). The messages are getting processed and the Administrator does not show any errors.

          Comment

          • #6
            Re: Error - Wrapper.log - org.mule.MuleException: Failed to delete file

            After changing the the "Polling Frequency" to 5000 ms (5 seconds), the number of times this error occurs has come down. But it does happen at random.

            This error is not causing any problem in processing the messages. Since Mirth continues to process all inbound messages and does delete the file, I would like to suppress this message for now just to keep the log "clean".

            How do I suppress this error from getting logged into mirth.log and wrapper.log?

            ========= ERROR MESSAGE IN mirth.log =============
            ERROR 2007-01-11 09:46:46,641 [d3922ef8-5c92-4f40-8f6c-0db562d25184_source_connector._fileEndpoint#210442 3684.receiver.1] org.mule.impl.DefaultComponentExceptionStrategy: Caught exception in Exception Strategy for: d3922ef8-5c92-4f40-8f6c-0db562d25184: org.mule.MuleException: Failed to delete file "C:\MirthHL7\MirthHL7Inbound\E3E12F5A-A523-4c3e-BAFC-F70A7B6082FB.HL7" as part of the file move operation
            org.mule.MuleException: Failed to delete file "C:\MirthHL7\MirthHL7Inbound\E3E12F5A-A523-4c3e-BAFC-F70A7B6082FB.HL7" as part of the file move operation
            at org.mule.providers.file.FileMessageReceiver.proces sFile(FileMessageReceiver.java:217)
            at org.mule.providers.file.FileMessageReceiver.poll(F ileMessageReceiver.java:111)
            at org.mule.providers.PollingMessageReceiver.run(Poll ingMessageReceiver.java:73)
            at org.mule.impl.work.WorkerContext.run(WorkerContext .java:290)
            at edu.emory.mathcs.backport.java.util.concurrent.Thr eadPoolExecutor$Worker.runTask(ThreadPoolExecutor. java:650)
            at edu.emory.mathcs.backport.java.util.concurrent.Thr eadPoolExecutor$Worker.run(ThreadPoolExecutor.java :675)
            at java.lang.Thread.run(Unknown Source)

            ========== SAME ERROR MESSAGE IN Wrapper.log ===========

            ERROR 2007-01-11 09:46:46,641 [d3922ef8-5c92-4f40-8f6c-0db562d25184_source_connector._fileEndpoint#210442 3684.receiver.1] org.mule.impl.DefaultComponentExceptionStrategy: Caught exception in Exception Strategy for: d3922ef8-5c92-4f40-8f6c-0db562d25184: org.mule.MuleException: Failed to delete file "C:\MirthHL7\MirthHL7Inbound\E3E12F5A-A523-4c3e-BAFC-F70A7B6082FB.HL7" as part of the file move operation
            INFO | jvm 1 | 2007/01/11 09:46:46 | org.mule.MuleException: Failed to delete file "C:\MirthHL7\MirthHL7Inbound\E3E12F5A-A523-4c3e-BAFC-F70A7B6082FB.HL7" as part of the file move operation
            INFO | jvm 1 | 2007/01/11 09:46:46 | at org.mule.providers.file.FileMessageReceiver.proces sFile(FileMessageReceiver.java:217)
            INFO | jvm 1 | 2007/01/11 09:46:46 | at org.mule.providers.file.FileMessageReceiver.poll(F ileMessageReceiver.java:111)
            INFO | jvm 1 | 2007/01/11 09:46:46 | at org.mule.providers.PollingMessageReceiver.run(Poll ingMessageReceiver.java:73)
            INFO | jvm 1 | 2007/01/11 09:46:46 | at org.mule.impl.work.WorkerContext.run(WorkerContext .java:290)
            INFO | jvm 1 | 2007/01/11 09:46:46 | at edu.emory.mathcs.backport.java.util.concurrent.Thr eadPoolExecutor$Worker.runTask(ThreadPoolExecutor. java:650)
            INFO | jvm 1 | 2007/01/11 09:46:46 | at edu.emory.mathcs.backport.java.util.concurrent.Thr eadPoolExecutor$Worker.run(ThreadPoolExecutor.java :675)
            INFO | jvm 1 | 2007/01/11 09:46:46 | at java.lang.Thread.run(Unknown Source)
            =====================

            Thanks in advance.

            Comment

            • #7
              Same Issue

              I notice there has been no posted resolution to this topic, but I am having the same issue. It seems restarting Mirth Connect will resolve this issue for a time. Other that bumping all of my polling times up to 5-10 seconds, is there any way to prevent this?

              Comment

              Previous template Next
              Working...
              X

              We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.

              By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.

              I Agree