org.mule.MuleException: Failed to read payload data

Mirth Project | Bruno MARTIN | 5 years ago
  1. 0

    ftp inbound connector problem: (using check file age option) (the problem occurs on short files - few ko) When a file is being written by the source application and mirth ftp inbound connector read the file, the mirth channel is then blocked althrough remaining started in the dashboard. All the following files created by the application in the source directory, are not integrated by the Mirth connector. Although the connector is started in the state, the following log is produced: 2011-10-17 15:36:31,463] ERROR (com.mirth.connect.connectors.file.FileMessageReceiver:250): Error reading file //C53871.hst Could not completely read file C53871.hst [2011-10-17 15:36:31,700] ERROR (org.mule.impl.DefaultComponentExceptionStrategy:95): Caught exception in Exception Strategy for: 21699d00-746e-47fc-8745-ae8c4ef6a62d: org.mule.MuleException: Failed to read payload data org.mule.MuleException: Failed to read payload data at com.mirth.connect.connectors.file.FileMessageReceiver.processFile(FileMessageReceiver.java:251) at com.mirth.connect.connectors.file.FileMessageReceiver.poll(FileMessageReceiver.java:118) at org.mule.providers.PollingMessageReceiver.run(PollingMessageReceiver.java:97) at org.mule.impl.work.WorkerContext.run(WorkerContext.java:290) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575) at java.lang.Thread.run(Thread.java:662)

    Mirth Project | 5 years ago | Bruno MARTIN
    org.mule.MuleException: Failed to read payload data
  2. 0

    ftp inbound connector problem: (using check file age option) (the problem occurs on short files - few ko) When a file is being written by the source application and mirth ftp inbound connector read the file, the mirth channel is then blocked althrough remaining started in the dashboard. All the following files created by the application in the source directory, are not integrated by the Mirth connector. Although the connector is started in the state, the following log is produced: 2011-10-17 15:36:31,463] ERROR (com.mirth.connect.connectors.file.FileMessageReceiver:250): Error reading file //C53871.hst Could not completely read file C53871.hst [2011-10-17 15:36:31,700] ERROR (org.mule.impl.DefaultComponentExceptionStrategy:95): Caught exception in Exception Strategy for: 21699d00-746e-47fc-8745-ae8c4ef6a62d: org.mule.MuleException: Failed to read payload data org.mule.MuleException: Failed to read payload data at com.mirth.connect.connectors.file.FileMessageReceiver.processFile(FileMessageReceiver.java:251) at com.mirth.connect.connectors.file.FileMessageReceiver.poll(FileMessageReceiver.java:118) at org.mule.providers.PollingMessageReceiver.run(PollingMessageReceiver.java:97) at org.mule.impl.work.WorkerContext.run(WorkerContext.java:290) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575) at java.lang.Thread.run(Thread.java:662)

    Mirth Project | 5 years ago | Bruno MARTIN
    org.mule.MuleException: Failed to read payload data
  3. 0

    Error happened while listing files - Mirth Community

    mirthcorp.com | 8 months ago
    org.mule.MuleException: Error happened while listing files
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Mirth Community - Error happened while listing files

    mirthcorp.com | 5 months ago
    org.mule.MuleException: Error happened while listing files
  6. 0

    I set up a new channel this morning and didn't check my source connection before deploying. I was running test messages through manually so I didn't notice a huge number of errors coming through. The error message indicated an smb connection problem, which allowed me to reduce my search, but I do have quite a few of those. I finally managed to trace the issue back to this channel's source connector. Once I corrected the issue and re-deployed the channel things were fine: The problem is that the error messages didn't tell me what channel the problem was in. These are the two I was getting: [2011-10-27 12:52:37,172] FATAL (org.mule.impl.DefaultComponentExceptionStrategy:83): The Default Component Exception Strategy has been invoked but there is no current event on the context and: [2011-10-27 12:52:37,173] FATAL (org.mule.impl.DefaultComponentExceptionStrategy:84): The error is: org.mule.MuleException: Error happened while listing files java.lang.Exception: org.mule.MuleException: Error happened while listing files at com.mirth.connect.connectors.file.FileMessageReceiver.poll(FileMessageReceiver.java:124) at org.mule.providers.PollingMessageReceiver.run(PollingMessageReceiver.java:97) at org.mule.impl.work.WorkerContext.run(WorkerContext.java:290) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575) at java.lang.Thread.run(Thread.java:662)Caused by: org.mule.MuleException: Error happened while listing files at com.mirth.connect.connectors.file.filesystems.SmbFileConnection.listFiles(SmbFileConnection.java:147) at com.mirth.connect.connectors.file.FileMessageReceiver.listFiles(FileMessageReceiver.java:416) at com.mirth.connect.connectors.file.FileMessageReceiver.poll(FileMessageReceiver.java:104) ... 5 moreCaused by: jcifs.smb.SmbAuthException: Logon failure: unknown user name or bad password. at jcifs.smb.SmbTransport.checkStatus(SmbTransport.java:515) at jcifs.smb.SmbTransport.send(SmbTransport.java:629) at jcifs.smb.SmbSession.sessionSetup(SmbSession.java:288) at jcifs.smb.SmbSession.send(SmbSession.java:233) at jcifs.smb.SmbTree.treeConnect(SmbTree.java:154) at jcifs.smb.SmbFile.doConnect(SmbFile.java:847) at jcifs.smb.SmbFile.connect(SmbFile.java:890) at jcifs.smb.SmbFile.connect0(SmbFile.java:816) at jcifs.smb.SmbFile.resolveDfs(SmbFile.java:665) at jcifs.smb.SmbFile.send(SmbFile.java:716) at jcifs.smb.SmbFile.doFindFirstNext(SmbFile.java:1920) at jcifs.smb.SmbFile.doEnum(SmbFile.java:1672) at jcifs.smb.SmbFile.listFiles(SmbFile.java:1649) at jcifs.smb.SmbFile.listFiles(SmbFile.java:1627) at com.mirth.connect.connectors.file.filesystems.SmbFileConnection.listFiles(SmbFileConnection.java:133) ... 7 more

    Mirth Project | 5 years ago | David Rothbauer
    org.mule.MuleException: Error happened while listing files

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. org.mule.MuleException

      Failed to read payload data

      at com.mirth.connect.connectors.file.FileMessageReceiver.processFile()
    2. com.mirth.connect
      FileMessageReceiver.poll
      1. com.mirth.connect.connectors.file.FileMessageReceiver.processFile(FileMessageReceiver.java:251)
      2. com.mirth.connect.connectors.file.FileMessageReceiver.poll(FileMessageReceiver.java:118)
      2 frames
    3. org.mule.providers
      PollingMessageReceiver.run
      1. org.mule.providers.PollingMessageReceiver.run(PollingMessageReceiver.java:97)
      1 frame
    4. org.mule.impl
      WorkerContext.run
      1. org.mule.impl.work.WorkerContext.run(WorkerContext.java:290)
      1 frame
    5. Backport of JSR 166
      ThreadPoolExecutor$Worker.run
      1. edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
      2. edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
      2 frames
    6. Java RT
      Thread.run
      1. java.lang.Thread.run(Thread.java:662)
      1 frame