| Author |
Message
|
| Ash_MB |
 Posted: Fri Jan 18, 2013 2:11 am Post subject: Unable to capture Messages from FileInput Node |
 |
|
Novice
Joined: 10 Sep 2012
Posts: 12
|
Hi,
I'm using fileinput node with Fixed length as record detection since the file contains 188bytes of 100k messages.
I used a Message set to capture the 188byte of message from fileinput node.
But still i do not see the message coming out of end of data terminal.
It will be great if someone could explain me how to capture this.
 |
|
| Back to top |
|
 |
| marko.pitkanen |
| Posted: Fri Jan 18, 2013 2:30 am Post subject: |
|
|
Chevalier
Joined: 23 Jul 2008
Posts: 440
Location: Jamsa, Finland
|
Hi,
What is the version of the broker you are using. Have you read the FileInput node documentation from the corresponded InfoCenter?
--
Marko |
|
| Back to top |
|
|
| Ash_MB |
| Posted: Fri Jan 18, 2013 3:08 am Post subject: |
|
|
Novice
Joined: 10 Sep 2012
Posts: 12
|
Broker Version 7.0.03 i'm using.
Yes i read about the node and used it as mentioned. |
|
| Back to top |
|
|
| marko.pitkanen |
| Posted: Fri Jan 18, 2013 3:16 am Post subject: |
|
|
Chevalier
Joined: 23 Jul 2008
Posts: 440
Location: Jamsa, Finland
|
So what is the exactly phenomenon you are suffering. Does the 188 bytes length record(s) be propagated to out terminal? And you are missing aknowledgement be propagated to EOD terminal?
Have you examined debug user trace yet?
--
Marko |
|
| Back to top |
|
|
| Ash_MB |
| Posted: Fri Jan 18, 2013 3:29 am Post subject: |
|
|
Novice
Joined: 10 Sep 2012
Posts: 12
|
1) I'm Connecting compute node to EOD terminal.
2) I tested with FileInput Node and Queue output to see if messages are coming out as required.
Here when i used Out terminal, I got first message corerctly as expected (188bytes)
Second message onwards it added .. in front of the message which is affecting the message.
When i used EOD terminal, i saw no message coming out of it.
So please tell me whether i should connect my Compute node to EOD terminal or out teminal ? |
|
| Back to top |
|
|
| marko.pitkanen |
| Posted: Fri Jan 18, 2013 4:30 am Post subject: |
|
|
Chevalier
Joined: 23 Jul 2008
Posts: 440
Location: Jamsa, Finland
|
If I understand processing files record (in this case 188 bytes) by record with FileInput node, you should be getting n times whole record + 1 time rest or bytes propagated to out terminal as individual messages and one empty message as an acknowledgement to end of data terminal.
--
Marko |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Jan 18, 2013 6:23 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| marko.pitkanen wrote: |
| If I understand processing files record (in this case 188 bytes) by record with FileInput node, you should be getting n times whole record + 1 time rest or bytes propagated to out terminal as individual messages and one empty message as an acknowledgement to end of data terminal. |
You understand correctly
| Ash_MB wrote: |
I got first message corerctly as expected (188bytes)
Second message onwards it added .. in front of the message which is affecting the message |
If by this you mean that for the second and subsequent messages the out terminal was propagrating 2 additional characters in front of the message payload then I would theorise that the file you're reading has records of 188 bytes one record to a line. So the file actually has 2 hex bytes x'0A' & x'0D' as CR/LF which are being displayed as '..' in whatever you're using to view the payload.
You either need to account for these characters in your message set or better still switch the FileInput records & elements property from FixedLength to Delimited.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Ash_MB |
| Posted: Mon Jan 21, 2013 2:31 am Post subject: |
|
|
Novice
Joined: 10 Sep 2012
Posts: 12
|
Thank you. 
I used Delimited as <cr><lf> adn i'm getting the messages as expected. |
|
| Back to top |
|
|
|
|
