ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » ResourceManager, eventid 5347

Post new topic  Reply to topic
 ResourceManager, eventid 5347 « View previous topic :: View next topic » 
Author Message
sorn73
PostPosted: Tue Feb 22, 2005 8:54 am    Post subject: ResourceManager, eventid 5347 Reply with quote

Novice

Joined: 24 Mar 2004
Posts: 24
Location: Sweden

One of my customers is suddenly having problems with a message flow that has worked fine for weeks. It processes a single message each day. The first day it goes OK, but the next day we get an exception with eventID 5347 , which means "MtiImbParser2: RM has thrown an unknown exception.". If we restart the broker, which is the proposed action, and resubmit the message, it goes through ok, but the next day it's the same thing again. If we submit two or more in a short timeframe it also goes through OK, so there is some dependency on time here. It seems from my trace file that the exception occurs in an ESQL node processing a CARDINALITY statement.

Has anyone else experienced this? What is the "resource manager"? Is there any way I can monitor the "resource manager" and understand what resource is failing?

I do have a full trace of the Environment tree, which also says something about "'rmLoadDictionary'", which I guess is where this error occurs.

This is a broker V 5.0 fixpack 2 on AIX 5.2.
Back to top
View user's profile Send private message
chenulu
PostPosted: Tue Feb 22, 2005 9:08 am    Post subject: Reply with quote

Voyager

Joined: 27 Mar 2002
Posts: 87
Location: Research Triangle Park, NC

Hi,

There are two ways around this:
1. Set EXTSHM=ON in the environment for all users that use DB2 (e.g. by
setting it in .profile).
The implementation is relatively simple.
Type the following commands:
a. db2stop
b. export EXTSHM=ON
c. db2set DB2ENVLIST=EXTSHM
d. db2start
(please ensure that the export command is also included in your .profile,in case you need to restart DB2 at some point)

2. Catalog a TCPIP connection to the database over loopback, which will
mean that you can use TCPIP rather than shared memory to connect to the database.
Please check the following weblink for details on implementing the
LOOPBACK node :
http://www-1.ibm.com/support/docview.wss?rs=0&uid=swg21154603

Regards, Chenulu
Back to top
View user's profile Send private message Send e-mail
sorn73
PostPosted: Wed Nov 09, 2005 2:31 am    Post subject: Reply with quote

Novice

Joined: 24 Mar 2004
Posts: 24
Location: Sweden

We have already done that, the broker won't start without it. The problem was fixed in FP4 or FP6. After an upgrade we stopped having this problem.

For some reason you could not have more than 2 MessageSets deployed to the broker.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » ResourceManager, eventid 5347
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
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.