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 Process Server (WID/WPS/WAS+) » Long Running Transaction - How long????

Post new topic  Reply to topic
 Long Running Transaction - How long???? « View previous topic :: View next topic » 
Author Message
wilsonjohn24
PostPosted: Mon Aug 18, 2008 12:14 pm    Post subject: Long Running Transaction - How long???? Reply with quote

Voyager

Joined: 02 Feb 2007
Posts: 93
Location: Scotland

Has any one any commercial experience/good working practices on long running transactions...

Especially around how long is a long running transaction?

1)Is a 40 second transaction a long running transaction- inhuman terms it is unlikely to be synchronous-so does this make it long running?

2) Back end fufilment process last around 4 minutes - 1 hour etc?

3) A fufilment procedure that last a year?

4) NHS ( or the american equalivent ???) transaction cradle to grave stuff?

I personally think 2 is more realistic as a long running transaction!

But would like to hear from those in the know

thanks

John
Back to top
View user's profile Send private message
gbaddeley
PostPosted: Mon Aug 18, 2008 7:14 pm    Post subject: Reply with quote

Jedi

Joined: 25 Mar 2003
Posts: 2495
Location: Melbourne, Australia

'Long running' UOW usually implies that it is causing issues for MQ regarding the number of recovery logs that messages in the UOW span. This is typically anything from minutes to hours, depending on the volume of persistent message traffic through MQ and the size / number of logs.

The general advice is that apps should commit the UOW as soon as practical. The UOW should only span one logical transaction. The longer a UOW runs the more exposure there is to unexpected failure and so the more likely it may need to roll back. YMMV.
_________________
Glenn
Back to top
View user's profile Send private message
wilsonjohn24
PostPosted: Mon Aug 18, 2008 8:53 pm    Post subject: Reply with quote

Voyager

Joined: 02 Feb 2007
Posts: 93
Location: Scotland

thanks for that.

So basically running long is measured in a sort of Technical TX level/Rollback ability/Transaction Save points rather than a Business Process being long term.


cheers


John
Back to top
View user's profile Send private message
JLRowe
PostPosted: Tue Aug 19, 2008 2:23 am    Post subject: Reply with quote

Yatiri

Joined: 25 May 2002
Posts: 664
Location: South East London

the shorter the better generally, I would expect a maximum of a few seconds but possibly longer during peak periods.

In J2EE you can set the timeout, if you do not complete within the time it is rolled back and an exception is thrown.

http://java.sun.com/j2ee/sdk_1.3/techdocs/api/javax/transaction/UserTransaction.html#setTransactionTimeout(int)

I think the default for WAS is 120 - not certain though.
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Process Server (WID/WPS/WAS+) » Long Running Transaction - How long????
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.