| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| V6.1 File Output using FTP problems |
« View previous topic :: View next topic » |
| Author |
Message
|
| smdavies99 |
 Posted: Wed Nov 19, 2008 4:59 am Post subject: V6.1 File Output using FTP problems |
 |
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
I'm seeing an issue with the V6.1 File output node when FTP is configured
System: Windows Server 2003
Broker runtime 6.1.0.2
If I put a message through the flow and trace it, the file gets put into a 'mqsitransit' directory.
A short time later, the DataflowEngine process goes to 100% CPU and stays there. After 5 mins I have to kill it
The mqsisetdbparms & mqsicreateconfigurableservice commands were setup using a script on the dev box and everything is hunky dory.
When we move to prod where the target System is accessed using a domain based account/password things go wrong.
I can FTP into the target account from the command line and the user that is runing broker can write to the target directory using command line FTP.
But as I said above, broker seems to go into aloop and sits there.
No error messages nothing.
Has anyone experienced this type of behaviour?javascript:emoticon(' ')
Stephen D
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Wed Nov 19, 2008 5:43 am Post subject: Some more details |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
When I send a message though the flow, the user trace indicated that the UOW has completed ok and the message disappears from the input queue.
However when I kill the EG and it restarts, the original message appears again and it put on the BOQ as it should do if there is a problem.
But still there are no event lot messages indicating why the FTP failed.
/S
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| mqpaul |
| Posted: Wed Nov 19, 2008 6:27 am Post subject: You need to open a PMR. You should collect a service trace. |
|
|
Acolyte
Joined: 14 Jan 2008
Posts: 66
Location: Hursley, UK
|
I have not encountered this problem, but that probably just means I've not used a sufficiently similar environment. It looks like something's failing during the FTP transfer - connection setup, the transfer itself - and the node is retrying. If the file got to the transit directory, the flow logic and local file handling have completed successfully.
You'll need to collect a service trace - the FileOutput node's FTP component doesn't write anything to the user trace, as you've seen. The instructions for using "mqsichangetrace <broker name> -t -r -l debug", "mqsireadlog <broker name> -t -f -o trace.xml" and "mqsiformatlog -i trace.xml -o trace.log" are in the broker Information Centre. Try to keep the trace enabled for only the shortest time around the FTP transfer/backout; trace files grow very quickly. Then you'll need to open a PMR with the support center; at least you'll have the trace when they ask for one !
_________________
Paul |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Wed Nov 19, 2008 7:52 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Thanks for the hint 'mqpaul'
I had taken a service trace and have found the cause of the problem.
It is down to the Inherited Properties in the Bar file for the FTP Address not overriding the address you put in when specifying the configurable service.
You have to put an address in the FTP Node Properties. This address is not overwritten by the serverName property valuse of the configurable service which I think should be the desired result. After all, you don't really have to edit the flow or bar file ( and redeploy it) if you want to change the destination address. But somehow, the value defined in the mqsicreateconfigurableservice command does not get used instead of the value n the flow.
I will have to do some more research into the matter.
Anyway, the files are being written to the right server so everyone is happy.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| 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
|
|
|
|
