|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
About problem of TCP/IP on MQ V5.2 |
« View previous topic :: View next topic » |
Author |
Message
|
hyZhou |
Posted: Thu Jun 19, 2003 2:39 am Post subject: About problem of TCP/IP on MQ V5.2 |
|
|
Newbie
Joined: 18 Jun 2003 Posts: 2 Location: china
|
every friend:
hello,we have one problem now.when I send message in local_net,My application may send sucessfully very much, the same time,the receiver also may receive normally;but when I send message by dialing,if I send a message that is more than 1M,the MQ channel is in_doubt,the error is "TCP/IP (select) [TIMEOUT] return code 0 (X'0')".
thank you!!! |
|
Back to top |
|
 |
mqonnet |
Posted: Thu Jun 19, 2003 5:31 am Post subject: |
|
|
 Grand Master
Joined: 18 Feb 2002 Posts: 1114 Location: Boston, Ma, Usa.
|
I would think this is the typical case of sending 1M attachment using hotmail or some other service on a 56k connection. The chances that your session timesout are more compared to successfully sending this attachment.
Guess this is what you are experiencing. Messages are sent in chuncks when it is so large and when MQ doesnt receive all of them, you get errors from some or the other participant in this whole process. In this case it was tcp/ip who complained.
The alternative would be to break the message yourself, group all of them and send them individually. Just a suggestion.
Cheers
Kumar |
|
Back to top |
|
 |
hyZhou |
Posted: Fri Jun 27, 2003 1:00 am Post subject: about TCP/IP |
|
|
Newbie
Joined: 18 Jun 2003 Posts: 2 Location: china
|
friend:
hi,I am glad to see your reply.But I don't konw what you tell me yet.I have partitioned segment,I guess that this is associated with TCP/IP configration.At the same time, I send messge by ADSL,Receiver may receive message that is more than 1 MB.Is this problem associated with TCP/IP? |
|
Back to top |
|
 |
mqonnet |
Posted: Fri Jun 27, 2003 5:30 am Post subject: |
|
|
 Grand Master
Joined: 18 Feb 2002 Posts: 1114 Location: Boston, Ma, Usa.
|
In simple words let me give you an example.
Say in your local network at the office you have a FTP server running. When you try to upload a file to the server from within the network, it would more likely than not, uploaded without any problems and within a matter of seconds or at most a minute or 2.
But if you go home and wish to upload the same file to the same FTP server, this time of course from outside your LAN, it would be very very slow. Irrespective of whether you have ADSL or 56K.
The same is the case with MQ as well. It is the underlying Tcp/ip layer that is transmitting this huge file in bits and pieces and this takes quite a lot of time.
Hence as i suggested earlier, you must use GROUPING of messages as an alternative to get this working.
You might be lucky at times sending this big file accross using MQ, but if you want consistency then you have to break this file into bits and send it yourself through your application.
Cheers
Kumar |
|
Back to top |
|
 |
psanders |
Posted: Fri Jun 27, 2003 11:09 am Post subject: Another try |
|
|
Apprentice
Joined: 02 Apr 2002 Posts: 27
|
Over slower connections the transmission takes longer. Because the durration of the transmision is longer there is a much higher probability that an error may occur. When this happens the block is re-transmitted.
So, the every time an error occurs, you start over. Because the message is big the odds of an error occuring are increased.
The long durration and the starting over make the odds of actually getting the data there unlikely. |
|
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
|
|
|
|