MQSeries.net :: View topic - multithreading (mqje001 completion code '2' reason '2195')

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » IBM MQ Java / JMS » multithreading (mqje001 completion code '2' reason '2195')

multithreading (mqje001 completion code '2' reason '2195')

« View previous topic :: View next topic »

Author

Message

alexeimail

Posted: Thu May 23, 2013 10:20 pm Post subject: multithreading (mqje001 completion code '2' reason '2195')

Newbie

Joined: 28 Apr 2013
Posts: 3

Hello. I'm cofused. I have class wmqUtil implements Runnable where i'm creating MQQueueManager and geting message from queue.

Code:

MQGetMessageOptions getOptions = new MQGetMessageOptions();
getOptions.options = MQC.MQGMO_WAIT + MQC.MQGMO_FAIL_IF_QUIESCING + MQC.MQGMO_LOGICAL_ORDER + MQC.MQGMO_ALL_SEGMENTS_AVAILABLE + MQC.MQGMO_COMPLETE_MSG + MQC.MQGMO_SYNCPOINT;

Every instance of wmqUtil i'm run in separate thread.
When i creating one or two thread all ok. But when i'm creating three threads - throw exeption:
mqje001 completion code '2' reason '2195'
MQJE005: TSH eyecatcher not found. Eyecatcher was 1950000
Error occured during API call - reason code0
MQJE001: èÂ«ñ ºáóÑÓÞÑ¡¿´ 2, Â»Ó¿þ¿¡á 2009.....

The message length 11 mb, max message length in queue 4194304.
That's problem?

P.S. NetBeans 7.1, Websphere MQ 6.2.

alexeimail

Posted: Thu May 23, 2013 10:31 pm Post subject:

Newbie

Joined: 28 Apr 2013
Posts: 3

I forget: it's standalone app. And was a out of memory exception.

An important addition: when i'm set parametr of VM to -Xmx256m, errors have disappeared.

But it is a strange relationship

mqjeff

Posted: Fri May 24, 2013 4:13 am Post subject:

Grand Master

Joined: 25 Jun 2008
Posts: 17447

alexeimail wrote:

I forget: it's standalone app. And was a out of memory exception.

An important addition: when i'm set parametr of VM to -Xmx256m, errors have disappeared.

But it is a strange relationship

It's a strange enough relationship that it seems clear that the two are mostly unrelated.

Debug the fact that your app is failing to release objects first. Once you're sure that your app no longer runs out of memory in general, then see if the MQ thread/segmentation issue occurs.

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » IBM MQ Java / JMS » multithreading (mqje001 completion code '2' reason '2195')

Jump to:

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

Protected by Anti-Spam ACP