Hey guys. Brand new Mirth user here.
I've been experimenting with different connection options over the past few days and just noticed that I have 70 GB .dat file in the /mirthdb/seg0 folder. I think this happened because i had my file reader set for batch processing but didn't configure mirth to move processed messages to another folder and the file reader was set to append the file if it already exists...So it seems i created a loop.
Whats puzzling is the channel was only enabled less than a minute so how did such a small txt file grow so quickly? ...and does Mirth have any way to protect against this sort of error? Clearly I need to be protected against myself.
I've been experimenting with different connection options over the past few days and just noticed that I have 70 GB .dat file in the /mirthdb/seg0 folder. I think this happened because i had my file reader set for batch processing but didn't configure mirth to move processed messages to another folder and the file reader was set to append the file if it already exists...So it seems i created a loop.
Whats puzzling is the channel was only enabled less than a minute so how did such a small txt file grow so quickly? ...and does Mirth have any way to protect against this sort of error? Clearly I need to be protected against myself.
70GB .dat file?
0 commentaires:
Enregistrer un commentaire