| Author |
Message
|
| satya2481 |
 Posted: Mon May 23, 2011 3:00 am Post subject: FileInput Node Issue WMBV61 |
 |
|
Disciple
Joined: 26 Apr 2007
Posts: 170
Location: Bengaluru
|
Hi All,
I am using WMB V6.1 FP8 Run time as well as Toolkit.
I have created a simple flow as shown below, with below configuration.
| Code: |
FileInputNode --> MQOutput Node
FileInputNode Configurations
InputDirectory = C:\FILE\Read
FileName or Pattern = *
Action on successful processing = Delete
InputMessage Parsing = BLOB
All other default values
MQOutputNode Configurations
QueueName = TEST.OUT |
The issue I am facing is that the FileInput node not picking up the messages. Once I deploy the flow to EG its creating mqsibackout folder in the directory mentioned in the InputDirectory property.
I have enabled the debug trace and checked. What I can see is that the FileInput node able to read the file from the directory and placing it in the mqsitranit folder but unable to process it after that. No clue in the log file.
If anyone has resolved such an issue please provide updates.
Thank You
Satya[/code] |
|
| Back to top |
|
 |
| Cogito-Ergo-Sum |
| Posted: Mon May 23, 2011 4:06 am Post subject: |
|
|
Master
Joined: 07 Feb 2006
Posts: 293
Location: Bengaluru, India
|
How about the queue ? Everything ok with it ? (If it were not, I would think, the file would be backed out to mqsibackout directory. But, that does not seem to be happening in your case .... )
_________________
ALL opinions are welcome.
-----------------------------
Debugging tip:When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
---Sherlock Holmes |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon May 23, 2011 4:24 am Post subject: Re: FileInput Node Issue WMBV61 |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| satya2481 wrote: |
| No clue in the log file. |
So in the user trace you see the file being picked up and then the trace stops dead? No reference to the MQOutput node at all? No other lines of any kind? Just stops dead and stares at you? Indicates a larger problem..... 
Exactly what is between the FileInput node and the MQOutput node? What happens if you put a Trace node with a ${Root} pattern between them and run a user trace?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon May 23, 2011 4:26 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Cogito-Ergo-Sum wrote: |
| If it were not, I would think, the file would be backed out to mqsibackout directory |
You'd also think the WMQ exception would be written into the OP's user trace and provide a clue. But as you correctly say, doesn't seem to be happening here.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| satya2481 |
| Posted: Mon May 23, 2011 7:42 pm Post subject: |
|
|
Disciple
Joined: 26 Apr 2007
Posts: 170
Location: Bengaluru
|
Hi All,
I have added a trace node in between the FileInput and MQOutput node. Trace file not getting created. Used mqsi commands also to capture the flow trace in Debug mode ( mqsichangetrace BRK61 -u -e default -l debug -c 1000 -r)
Below is the Trace file content
| Code: |
Timestamps are formatted in local time, 330 minutes past GMT.
Trace written by version 6108; formatter version 6108
2011-05-24 09:00:11.795105 4460 UserTrace BIP4040I: The Execution Group ''default'' has processed a configuration message successfully.
A configuration message has been processed successfully. Any configuration changes have been made and stored persistently.
No user action required.
2011-05-24 09:00:11.795349 4460 UserTrace BIP2638I: The MQ output node 'ConfigurationMessageFlow.outputNode' attempted to write a message to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' connected to queue manager ''BRK61.QM''. The MQCC was '0' and the MQRC was '0'.
2011-05-24 09:00:11.795365 4460 UserTrace BIP2622I: Message successfully output by output node 'ConfigurationMessageFlow.outputNode' to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' on queue manager ''BRK61.QM''.
2011-05-24 09:00:11.795533 4460 Information BIP2154I: Execution group finished with Configuration message.
A command response will be sent to the broker.
No user action required.
2011-05-24 09:00:16.709873 2884 UserTrace BIP3336I: File node ''FileInput'' in message flow ''MyFlow'' is moving file ''C:\InputFiles\Formatted.txt'' to directory ''C:\InputFiles\mqsitransitin''.
The file node is about to move a file to a different directory. The node will not change the file's name.
No user action is necessary.
2011-05-24 09:00:21.710668 2884 UserTrace BIP3336I: File node ''FileInput'' in message flow ''MyFlow'' is moving file ''C:\InputFiles\Formatted.txt'' to directory ''C:\InputFiles\mqsitransitin''.
The file node is about to move a file to a different directory. The node will not change the file's name.
No user action is necessary.
2011-05-24 09:00:26.711572 2884 UserTrace BIP3336I: File node ''FileInput'' in message flow ''MyFlow'' is moving file ''C:\InputFiles\Formatted.txt'' to directory ''C:\InputFiles\mqsitransitin''.
The file node is about to move a file to a different directory. The node will not change the file's name.
No user action is necessary.
2011-05-24 09:00:31.712375 2884 UserTrace BIP3336I: File node ''FileInput'' in message flow ''MyFlow'' is moving file ''C:\InputFiles\Formatted.txt'' to directory ''C:\InputFiles\mqsitransitin''.
The file node is about to move a file to a different directory. The node will not change the file's name.
No user action is necessary.
2011-05-24 09:00:36.713211 2884 UserTrace BIP3336I: File node ''FileInput'' in message flow ''MyFlow'' is moving file ''C:\InputFiles\Formatted.txt'' to directory ''C:\InputFiles\mqsitransitin''.
The file node is about to move a file to a different directory. The node will not change the file's name.
No user action is necessary.
2011-05-24 09:00:41.714004 2884 UserTrace BIP3336I: File node ''FileInput'' in message flow ''MyFlow'' is moving file ''C:\InputFiles\Formatted.txt'' to directory ''C:\InputFiles\mqsitransitin''.
The file node is about to move a file to a different directory. The node will not change the file's name.
No user action is necessary.
2011-05-24 09:00:46.714828 2884 UserTrace BIP3336I: File node ''FileInput'' in message flow ''MyFlow'' is moving file ''C:\InputFiles\Formatted.txt'' to directory ''C:\InputFiles\mqsitransitin''.
The file node is about to move a file to a different directory. The node will not change the file's name.
No user action is necessary.
2011-05-24 09:00:51.715625 2884 UserTrace BIP3336I: File node ''FileInput'' in message flow ''MyFlow'' is moving file ''C:\InputFiles\Formatted.txt'' to directory ''C:\InputFiles\mqsitransitin''.
The file node is about to move a file to a different directory. The node will not change the file's name.
No user action is necessary.
2011-05-24 09:00:56.716510 2884 UserTrace BIP3336I: File node ''FileInput'' in message flow ''MyFlow'' is moving file ''C:\InputFiles\Formatted.txt'' to directory ''C:\InputFiles\mqsitransitin''.
The file node is about to move a file to a different directory. The node will not change the file's name.
No user action is necessary.
2011-05-24 09:01:01.717442 2884 UserTrace BIP3336I: File node ''FileInput'' in message flow ''MyFlow'' is moving file ''C:\InputFiles\Formatted.txt'' to directory ''C:\InputFiles\mqsitransitin''.
The file node is about to move a file to a different directory. The node will not change the file's name.
No user action is necessary.
2011-05-24 09:01:06.718149 2884 UserTrace BIP3336I: File node ''FileInput'' in message flow ''MyFlow'' is moving file ''C:\InputFiles\Formatted.txt'' to directory ''C:\InputFiles\mqsitransitin''.
The file node is about to move a file to a different directory. The node will not change the file's name.
No user action is necessary.
2011-05-24 09:01:11.718918 2884 UserTrace BIP3336I: File node ''FileInput'' in message flow ''MyFlow'' is moving file ''C:\InputFiles\Formatted.txt'' to directory ''C:\InputFiles\mqsitransitin''.
The file node is about to move a file to a different directory. The node will not change the file's name.
No user action is necessary.
2011-05-24 09:01:16.719812 2884 UserTrace BIP3336I: File node ''FileInput'' in message flow ''MyFlow'' is moving file ''C:\InputFiles\Formatted.txt'' to directory ''C:\InputFiles\mqsitransitin''.
The file node is about to move a file to a different directory. The node will not change the file's name.
No user action is necessary.
2011-05-24 09:01:21.720632 2884 UserTrace BIP3336I: File node ''FileInput'' in message flow ''MyFlow'' is moving file ''C:\InputFiles\Formatted.txt'' to directory ''C:\InputFiles\mqsitransitin''.
The file node is about to move a file to a different directory. The node will not change the file's name.
No user action is necessary.
2011-05-24 09:01:26.721378 2884 UserTrace BIP3336I: File node ''FileInput'' in message flow ''MyFlow'' is moving file ''C:\InputFiles\Formatted.txt'' to directory ''C:\InputFiles\mqsitransitin''.
The file node is about to move a file to a different directory. The node will not change the file's name.
No user action is necessary.
2011-05-24 09:01:31.722322 2884 UserTrace BIP3336I: File node ''FileInput'' in message flow ''MyFlow'' is moving file ''C:\InputFiles\Formatted.txt'' to directory ''C:\InputFiles\mqsitransitin''.
The file node is about to move a file to a different directory. The node will not change the file's name.
No user action is necessary.
2011-05-24 09:01:36.723098 2884 UserTrace BIP3336I: File node ''FileInput'' in message flow ''MyFlow'' is moving file ''C:\InputFiles\Formatted.txt'' to directory ''C:\InputFiles\mqsitransitin''.
The file node is about to move a file to a different directory. The node will not change the file's name.
No user action is necessary.
2011-05-24 09:01:41.723964 2884 UserTrace BIP3336I: File node ''FileInput'' in message flow ''MyFlow'' is moving file ''C:\InputFiles\Formatted.txt'' to directory ''C:\InputFiles\mqsitransitin''.
The file node is about to move a file to a different directory. The node will not change the file's name.
No user action is necessary.
2011-05-24 09:01:46.724784 2884 UserTrace BIP3336I: File node ''FileInput'' in message flow ''MyFlow'' is moving file ''C:\InputFiles\Formatted.txt'' to directory ''C:\InputFiles\mqsitransitin''.
The file node is about to move a file to a different directory. The node will not change the file's name.
No user action is necessary.
2011-05-24 09:01:51.725582 2884 UserTrace BIP3336I: File node ''FileInput'' in message flow ''MyFlow'' is moving file ''C:\InputFiles\Formatted.txt'' to directory ''C:\InputFiles\mqsitransitin''.
The file node is about to move a file to a different directory. The node will not change the file's name.
No user action is necessary.
2011-05-24 09:01:56.726448 2884 UserTrace BIP3336I: File node ''FileInput'' in message flow ''MyFlow'' is moving file ''C:\InputFiles\Formatted.txt'' to directory ''C:\InputFiles\mqsitransitin''.
The file node is about to move a file to a different directory. The node will not change the file's name.
No user action is necessary.
2011-05-24 09:02:01.727282 2884 UserTrace BIP3336I: File node ''FileInput'' in message flow ''MyFlow'' is moving file ''C:\InputFiles\Formatted.txt'' to directory ''C:\InputFiles\mqsitransitin''.
The file node is about to move a file to a different directory. The node will not change the file's name.
No user action is necessary.
2011-05-24 09:02:06.523667 4460 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'ConfigurationMessageFlow.InputNode'.
2011-05-24 09:02:06.523760 4460 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2011-05-24 09:02:06.523790 4460 UserTrace BIP6061I: Parser type ''MQMD'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value ''MQHMD'' from previous parser.
2011-05-24 09:02:06.523838 4460 UserTrace BIP6061I: Parser type ''XMLS'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '347' bytes beginning at offset '364'. Parser type selected based on value ''XMLS'' from previous parser.
2011-05-24 09:02:06.527602 4460 Information BIP2152I: Configuration message received from broker.
An execution group received a command from the Broker.
No user action required.
2011-05-24 09:02:06.527701 4460 Information BIP2153I: About to ''change'' an execution group.
An execution group is about to perform an action.
No user action required.
Threads encountered in this trace:
2884 4460
|
Please note that the same flow works fine in other systems. Broker versions are different.
WMB V6.1 FP 4 --> Flow Works
WMB V6.1 FP 8 --> Flow not working
If the working broker version is at higher end then we could say that its due to lower version but that is not the case.
Tried to cross check whether the flow atleast getting initialised correctly or not, by deleting the folders mqsiarchive, mqsibackout and mqsitransitin from the input directory. They are getting created in the next poll.
Regards
Satya
_________________
IBM Certified Solution Developer WebSphere Message Broker V6.0
IBM Certified System Administrator WebSphere MQ V6.0 |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon May 23, 2011 8:18 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20697
Location: LI,NY
|
I'm surprised I didn't see any other errors like permission errors on moving the files. I'd just double check the permissions to make sure the broker user has all the needed permissions on the transitin directory and that such a directory does exist.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| agurrala |
| Posted: Mon Sep 15, 2014 3:17 am Post subject: |
|
|
Newbie
Joined: 28 Aug 2013
Posts: 4
|
| I recently faced the same type of issue in FUT where on placing the file & changing its permissions,it is getting placed in "mqsitransitin" folder but the flow is not picking the file.Then I placed another file in the source directory & removed the previous one in mqsitransitin folder.Then the flow started picking the file.I guess this is some network issue in Reflection FTP. |
|
| Back to top |
|
|
|
|
