| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Strange behaviour with fileinput node |
« View previous topic :: View next topic » |
| Author |
Message
|
| issis |
 Posted: Thu Oct 28, 2010 1:03 am Post subject: Strange behaviour with fileinput node |
 |
|
Novice
Joined: 20 Aug 2004
Posts: 17
Location: Finland
|
Hello,
We have a simple message flow that reads a file using FTP and writes it to a queue. I have tried this flow in two environments: test and production. The weird thing is that the exactly same flow works ok in test environment but not in production.
I have tested the ftp connection from command line and it works fine from both servers. The directory and file access rights are ok. I can upload, download and delete the files in question and create subdirectories.
Both are running on Aix (oslevel 5.3.0.0) and the product binaries are on the same level, 6.1.0.5 plus an ifix.
| Code: |
Oct 28 09:51:07 upmqsip01 user:info WebSphere Broker v6105[938062]: (BROKER.prdeg)[9024]BIP3332E: File node 'testftpin' in message flow 'FILE_IN' cannot continue executing. See the following message number '3301' for details of the problem preventing execution. : BROKER.841f9eae-2b01-0000-0080-dc0ba2945552: /build/S610_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp: 739: com.ibm.broker.nodes.filenodes.ComIbmFileInputNode.checkDirectory: :
Oct 28 09:51:07 upmqsip01 user:info WebSphere Broker v6105[938062]: (BROKER.prdeg)[9024]BIP3301E: File node 'testftpin' in message flow 'FILE_IN' is unable to process files in the input directory '/usr/local/interface'. : BROKER.841f9eae-2b01-0000-0080-dc0ba2945552: /build/S610_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp: 739: com.ibm.broker.nodes.filenodes.ComIbmFileInputNode.checkDirectory: : |
Another interesting find is this: adding a level to the file path causes the flow to fail. Note that the error message below says that the file "/usr/local/interface/output.files/TESTOUT_MSG" does not exist. It does and the broker even knows about it. It sould have suffucient access rights as I have uploaded the files to the directory using the same userid as the broker is using.
This behaviour applies to both environments described above and was produced by the same message flow.
| Code: |
Oct 28 08:55:03 upmqsit01 user:err|error WebSphere Broker v6105[3698802]: (BROKER.testeg)[7968]BIP2628E: Exception condition detected on input node 'FILE_IN.testftpin'. : BROKER.ba641ed1-2a01-0000-0080-8c28d9b02f9f: /build/S610_P/src/DataFlowEngine/TemplateNodes/ImbInputTemplateNode.cpp: 509: ImbInputTemplateNode::run: ComIbmFileInputNode: FILE_IN#FCMComposite_1_7
Oct 28 08:55:03 upmqsit01 user:info WebSphere Broker v6105[3698802]: (BROKER.testeg)[7968]BIP3385E: File node 'testftpin' in message flow 'FILE_IN'. Unexpected I/O exception occurred in communication with FTP server 'FtpService[xxx.xxx.xxx.xxx,CWD '/usr/local/interface/output.files']'. I/O exception text is '/usr/local/interface/output.files/TESTOUT_MSG (No such file or directory)'. : BROKER.ba641ed1-2a01-0000-0080-8c28d9b02f9f: ComIbmFileInputNode.java: 1251: transferFromRemoteServer(): :
|
Any ideas? Have I forgotten something incredibly simple? 
We will be upgrading to version 7 within a few months anyway and I can give these a spin with it very soon. However, if this is an OS -level thing, we'l have to call Ghostb, I mean IBM. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Thu Oct 28, 2010 2:15 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Talk to the network and FTP server team. That unexpected I/O exception is something funny going on that isn't broker. |
|
| Back to top |
|
|
| issis |
| Posted: Thu Oct 28, 2010 2:22 am Post subject: |
|
|
Novice
Joined: 20 Aug 2004
Posts: 17
Location: Finland
|
The first problem could be a network issue. It is going to be hard to describe as command line ftp works and broker does not. The production broker runs in a cluster so the network arrangements are a bit different compared to the test server.
The second... well, of course anything is possible. First I think I'll try to access a totally different ftp server just to see if there are differences with the number of directories in the file path... (This must sound stupid)
In both cases the debug level user trace was as informative as those entries from syslog. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Oct 28, 2010 3:18 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
There have been some fixes in this area in 6.1.0.7/6.1.0.8.
"unable to process files in the input directory '/usr/local/interface' " likely means that Broker is unable to create the necessary mqsi subdirectories it wants to create in that location. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
