| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ 2255. |
« View previous topic :: View next topic » |
| Author |
Message
|
| matuwe |
 Posted: Tue Jul 26, 2011 5:23 am Post subject: MQ 2255. |
 |
|
Master
Joined: 05 Dec 2007
Posts: 296
|
Hi Please help
I am using circular logging, all my queue uses persistence, and I am using segmentation. My flows have been working super fine. All my Output MQ has segmetation allowed = Yes.
Now I seem to have a weird error, 2255 when a message is bigger than the queue size. I think my failing messages are from messages created from a PROPAGATE.
MQ INput >> JAVA Compute -- Propagate 15 messages >> MQ OUT
I have set transactionality to NO on the MQOUT, to try and let the propagated message committed and processed. I need persistence and cannot remove it.
I am using Broker 7.0.0.2 |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Jul 26, 2011 5:51 am Post subject: Re: MQ 2255. |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| matuwe wrote: |
| all my queue uses persistence |
Once again, queues are neither persistent nor non-persistent. Persistence is a message attribute, not a queue attribute.
| matuwe wrote: |
| I have set transactionality to NO on the MQOUT, to try and let the propagated message committed and processed. |
What's the transactionality of the flow?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| matuwe |
| Posted: Tue Jul 26, 2011 6:16 am Post subject: |
|
|
Master
Joined: 05 Dec 2007
Posts: 296
|
My Flow MQ Input Node has Transaction Mode = Yes.
Could that be causing my error?  |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jul 26, 2011 6:52 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| matuwe wrote: |
| Could that be causing my error? |
Erm...description of a 2255...
| Quote: |
An MQGET, MQPUT, or MQPUT1 call was issued to get or put a message outside a unit of work, but the options specified on the call required the queue manager to process the call within a unit of work. Because there is already a user-defined unit of work in existence, the queue manager was unable to create a temporary unit of work for the duration of the call.
This reason occurs in the following circumstances:
On an MQGET call, when the MQGMO_COMPLETE_MSG option is specified in MQGMO and the logical message to be retrieved is persistent and consists of two or more segments.
On an MQPUT or MQPUT1 call, when the MQMF_SEGMENTATION_ALLOWED flag is specified in MQMD and the message requires segmentation. |
You've coded the flow to start a unit of work. You've coded the MQOutput node to put outside that, and use segmentation. If it's not your problem, it's somewhere to start looking...
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| 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
|
|
|
|
