1.8 RC2 not processing?

[dugjohnson]

I have a pretty straight forward channel with a file in and a couple of file outs.
The input is being grabbed and transferred to the output directory, but the Administrator is not marking any reads or writes and the translated files are not appearing where expected.
I will try building a VERY simple channel from scratch, but this channel worked in 1.7.
Don't know if the getting it back problem caused the change to the channel, but it all looks OK in the transformers and there are no errors.
It is as if it is grabbing it and deciding not to process it for no good reason.

[jacobb]

Re:1.8 RC2 not processing?

There were very extensive changes done to the File Reader/Writer. Please post a sample channel of it not working, and we will resolve it.

[dugjohnson]

Re:1.8 RC2 not processing?

The attached isn't "simple" but it is what isn't working. And the basics are pretty straight forward. I'm not a complex person... MessagesOut.xml (288240 bytes)

[dugjohnson]

Re:1.8 RC2 not processing?

I'm also attaching the XML that is being "processed".

PAT20081020161017.xml (2912 bytes)

[dugjohnson]

Re:1.8 RC2 not processing?

Panic is off, but you will need to look at the problem.

I was able to uninstall 1.8, delete the Mirth directory, reinstall 1.7.1.3422, import the channels, and everything is working as expected.

I am now going to concentrate on the connectathon and will not be installing 1.8 for a few weeks (we have a demonstration in November and we are not to touch our installation once approved) so pressure's off for me.

Thanks for your prompt follow-up yesterday. You gave me what I needed to get out of the hole I threw myself into.

Doug

[jacobb]

Re:1.8 RC2 not processing?

You need to turn off Batch Processing on your File Reader. Batch is not supported for XML files. It was an error that it worked in the previous version of Mirth, but I will fix the next RC so that it has a notable exception for this error.

[dugjohnson]

Re:1.8 RC2 not processing?

Thanks. Probably occurred when copying from one type to another.
Makes sense that it WOULDN'T work with XML.