| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| First Message in batch fails with BIP2635E |
« View previous topic :: View next topic » |
| Author |
Message
|
| MikeC |
 Posted: Thu Jan 29, 2004 11:07 am Post subject: First Message in batch fails with BIP2635E |
 |
|
Acolyte
Joined: 30 Jun 2003
Posts: 55
Location: Toronto, Canada
|
Hello,
I have a situation where the first message in a batch fails with error message..
BIP2635E: Exception during destination list processing
When it's sent again, it goes through OK.
The error message is preceeded by..
BIP2230E: Error detected whilst processing a message in node ***
and followed by..
BIP2620E: Unable to write message to queue ***
Has anyone seen this before? .. or know why it happens or how to fix it?
I'm running WMQI 2.1 with DB2 7.1 on AIX.
Cheers,
-Mike.
_________________
-Mike. |
|
| Back to top |
|
 |
| CoolDude |
| Posted: Thu Jan 29, 2004 11:40 am Post subject: |
|
|
Apprentice
Joined: 17 Jan 2004
Posts: 39
|
Have you made sure that your Destination lists are set properly. and you have set destination list in your MQOutput node.
what does your trace files say?
Try:
remove the destination list and give a queue name.
submit the same batch and see what happens.
Hope you havenot tried this already.
thanks
_________________
Correct Me from Wrong  . If i am correct Appreciate Me  |
|
| Back to top |
|
|
| MikeC |
| Posted: Thu Jan 29, 2004 1:30 pm Post subject: |
|
|
Acolyte
Joined: 30 Jun 2003
Posts: 55
Location: Toronto, Canada
|
Thanks. .. Good ideas, but that's not the problem. The output node is set to destination list and it (the list) is set correctly.
As for the trace, I can't run one because it's our production system. (I can't leave one running there.) And since the problem is sporadic, I'd never know when to start the trace so I could catch it.
Thanks though. .... Any other thoughts?
-Mike.
_________________
-Mike. |
|
| Back to top |
|
|
| MikeC |
| Posted: Fri Feb 20, 2004 7:21 am Post subject: |
|
|
Acolyte
Joined: 30 Jun 2003
Posts: 55
Location: Toronto, Canada
|
OK, I figured out the problem. (If anyone's interested.)
It's actually an MQSeries logging issue. The queue manager log was running out of space. So the message was rolled back to release log space.
_________________
-Mike. |
|
| 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
|
|
|
|
