| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| .NET remote queue reason code 2030 |
« View previous topic :: View next topic » |
| Author |
Message
|
| tnse |
 Posted: Wed Sep 28, 2005 3:59 am Post subject: .NET remote queue reason code 2030 |
 |
|
Newbie
Joined: 25 Oct 2002
Posts: 5
|
Hi,
I hope someone can help me on following problem:
An application (written is VB.NET, using amqmdnet.dll) has to put a message on a remote queue manager. Although the length of the message is very small (and lower then the maximum message length for the queues, channels etc), I still got an error message with reason code 2030 (message to long)
In fact executing the application and putting the same message on the local queue manager gives no problem at all.
As I have no idea where to look for, any suggestion/help is welcome.
Regards |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Sep 28, 2005 4:08 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
2030 is always an issue with the queue max depth being smaller than the size of the message.
If you can successfully put to a local queue, then likely the problem is with the size on the Transmission Queue.
Or possibly, it is a problem with the size of the queue or qmgr on the other end, but I would think then that your message would end up on a DLQ somewhere with the 2030, rather than giving your program an RC of 2030.
_________________
I am *not* the model of the modern major general. |
|
| 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
|
|
|
|
