| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| MQSeries client chl tables : Calling MQ emergency services! |
« View previous topic :: View next topic » |
| Author |
Message
|
| shogan2003 |
 Posted: Sun May 23, 2004 3:23 am Post subject: |
 |
|
Centurion
Joined: 03 Jul 2003
Posts: 133
Location: London
|
Thanks for taking the trouble to suggested in a highly detailed fashion (as usual) a possible solution.
Just FYI, the error code is 2058, not 2059, though that distinction is largely academic.
I shall certainly experiment using the non-QM approach and if that fails, will see if I can workaround with a group of segmented messages, by setting MAXMSGL back to the default of 4Mb on the queue and letting the queue manager slice up the messages.
Many thanks.
_________________
MQSI2 certified specialist
MQSeries certified specialist |
|
| Back to top |
|
 |
| JasonE |
| Posted: Mon May 24, 2004 1:20 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
FYI I have emailed you a response regarding your traces....
Just for reference it appeared to be doing an MQCONN with the correct qmgr name but failing later on. As to the failure, I think either the trace file was truncated or the client conn table is corrupted. |
|
| Back to top |
|
|
| shogan2003 |
| Posted: Mon May 24, 2004 5:06 am Post subject: |
|
|
Centurion
Joined: 03 Jul 2003
Posts: 133
Location: London
|
OK thanks for your email, JasonE.
I simply ftp'd over the client channel table in binary as you suggested.
I was able to transfer an 8Mb message, which is evidence that the 4Mb threshold was overcome.
CASE CLOSED
_________________
MQSI2 certified specialist
MQSeries certified specialist |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
