FTP returncode 250

, ,
1

Hello,

We are having problem while invoking service pub.client.ftp:put service.

Partner is returning 250 as the return code and put service is returning back with ABORT.

After that, put is exiting with null exception.

Can anyone give us any idea, how webMethods handles ftp return code 250? where I can find the list of return codes webemthods supports?

Any other ideas?

Thanks.

2

250 is a success code. It should be returned to the caller of the service.

Your post is a little confusing.

"…put service is returning back with ABORT.

After that, put is exiting with null exception."

Which is it doing? I suspect that the remote FTP server is not returning 250 but is instead returning a code > 300.

Can you post the details of the inputs to the put?

3

Hello Reamon,

Here is the server log info:

First login is successful. then the log follows as below.

2010-12-15 13:20:44 CST [ISC.0064.0026T] → STOR xxxxxxxxx.csv^M

2010-12-15 13:20:44 CST [ISC.0064.0024T] ← 150 Opening data connection for transfer.
2010-12-15 13:20:49 CST [ISC.0064.0024T] ← 250

2010-12-15 13:21:19 CST [ISC.0064.0026T] → ABOR^M

2010-12-15 13:21:19 CST [ISC.0049.0008D] Sequence : index=5 depth=2
2010-12-15 13:21:19 CST [ISC.0049.0008D] Sequence : index=2 depth=1
2010-12-15 13:21:19 CST [ISC.0049.0008D] Sequence : index=1 depth=2
2010-12-15 13:21:19 CST [ISC.0049.0005D] Invoke : index=1 depth=3
2010-12-15 13:21:19 CST [ISS.0014.0016T] Invoking service pub.flow:getLastError

From the log above, it clearly shows that put is getting return code 250 back but sending ABORT. after that it exiting with null exception.

Any ideas?

Thanks.

4

remote FTP server returning 250 return code.

we are using the below sequence of flow steps.

  1. ftp:login
  2. ftp:put
  3. ftp:logout

Login is successful.

put results:
Put is able to successfully write the file on remote server. Remote server responding with return code 250.

Right after that, webMethods is sending ABORT and then put is going to catch block and the result is null exception.

I strongly doubt that ftp having trouble understanding 250 return code.

Any Ideas?

Thanks.

5

You have some good debugging info there. I would suggest opening a ticket with wM support.