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 » USER exception perofmance impact

Post new topic  Reply to topic
 USER exception perofmance impact « View previous topic :: View next topic » 
Author Message
ANILK
PostPosted: Tue Aug 23, 2016 2:01 am    Post subject: USER exception perofmance impact Reply with quote

Acolyte

Joined: 01 May 2014
Posts: 61

Hi Friends,

I have a general question , Is there any performance or any other impact
if we use "THROW USER EXCEPTION MESSAGE" code frequently .
i mean If this code is getting executed every second, will it create any performance or another impact in the message flow . kindly share your valuable advice.

Thanks

Anil
Back to top
View user's profile Send private message
smdavies99
PostPosted: Tue Aug 23, 2016 3:00 am    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

It depends...

Why not do some simple tests and think about it?

As you already have the ESQL to do it, it can't be that hard to run some tests with a flow that does it to say every other message. Then compare the elapsed time for processing 1000 messages to a flow that does not do it.

The reason I say, 'it depends' is because we have no, zero, nada, nilch idea of what happens in your flow when toy execute the ESQL to throw the exception.

Apart from that, and IMHO the fewer number of times you use that ESQL per day, the better.
There are other ways to signify a non fatal error that does not need an exception raised. But again, it all depends upon your site and their philosiphy for error handling.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
Back to top
View user's profile Send private message
mqjeff
PostPosted: Tue Aug 23, 2016 3:57 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

I'm confused.

THROW USER EXCEPTION is used when, well, there was an error that occurs in your flow.

It's not clear what you would do with that error if you don't throw it. So how would the performance make a difference in how you code?

Do you want your flow to just stop because of some error, or produce an incorrect answer?

Or do you want to make sure the error is handled in the proper way for what you are trying to do?
_________________
chmod -R ugo-wx /
Back to top
View user's profile Send private message
Vitor
PostPosted: Tue Aug 23, 2016 4:38 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

I'm likewise confused.

The efficiency of an error reporting mechanism is usually not a consideration because in a well running system you don't call it that much. So why would you be calling it every second?

The performance impact is not so much the statement (generating an exception tree) but what it causes to happen. If (for example) you call it at the end of a medium sized flow then there's going to be a noticeable performance impact as the flow rolls back all the work it's done and resets the input. If it has to rollback a database as well, then that's more time.

But again, why the question?
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
ANILK
PostPosted: Tue Aug 23, 2016 6:35 am    Post subject: Reply with quote

Acolyte

Joined: 01 May 2014
Posts: 61

Hi Friends,

Thanks for the reply, this questions arrived because of a change in the business requirement. usually user exception use to happen 5 to 10 times in a day , but now because of a issue in the external system ,
this user exception code will be called 2 to 3 times in a second . and as per the current business scenario this cannot be treated as a error or exception.
so we are planing to remove this exception throw method from the code.

ANILK
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 » USER exception perofmance impact
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.