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 » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » Deadlocks in Workflow 3.4

Post new topic  Reply to topic
 Deadlocks in Workflow 3.4 « View previous topic :: View next topic » 
Author Message
whizkid
PostPosted: Tue Mar 02, 2004 6:12 am    Post subject: Deadlocks in Workflow 3.4 Reply with quote

Newbie

Joined: 25 Jun 2003
Posts: 7
Location: India
We are encountering timeout issues related to database deadlock in our production system. We are using Workflow V 3.4 in solaris and are using oracle as our DB. Could you please extend me any suggestion to alleivate this problem.

The timeout occurs both during query of worklists and starting new processes. Is it due to large worklists or due to some MQ related issue? Furthur we are using a single ExecutionService object to start all the processes, Could this be a cause?. However we have tested it to be thread save too.

I can observe some errors of the form
FmcFMLException, MQReturnCode=2, MQReasonCode=2161, MQObjectName=FMC1.FMCGRP1.FMCSYS1.ADM, severe error logged in fmcsys.log while the server was being shutdown. Once the server is restarted the timeout occurs instantly and the message logged is
02/28/04 14:20:35 FMC31100W The message ChndTxnActImplComplete could not be processed because of a database deadlock or timeout. The message will be retried.

Is the premature termination of the admin server a possible cause for the deadlock issue. Any suggestions?
Back to top
View user's profile Send private message
vennela
PostPosted: Tue Mar 02, 2004 6:49 am    Post subject: Reply with quote

Jedi Knight

Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
Though your DB is Oracle, I am not sure if this doc helps but you may want to take a look at the rutime DB maintenance.

http://www-1.ibm.com/support/docview.wss?rs=203&uid=swg27001502&loc=en_US&cs=utf-8&lang=en

MQReasonCode=2161 means MQRC_Q_MGR_QUIESCING. Most likely there is an FDC cut in your error logs. See if there are any FDCs are anything in MQ error logs.
Back to top
View user's profile Send private message Send e-mail Visit poster's website
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » Deadlocks in Workflow 3.4
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.