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 » Rethrowing an Exception

Post new topic  Reply to topic
 Rethrowing an Exception « View previous topic :: View next topic » 
Author Message
john01
PostPosted: Fri Mar 11, 2011 6:13 am    Post subject: Rethrowing an Exception Reply with quote

Novice

Joined: 16 Jun 2010
Posts: 21
Location: PT

Hi everyone,

I have this sequencial nodes in my sample flow:

SoapInput > TryCatch1 > (...) > TryCatch2 > (...)

Well, I want to handle some types of errors in Catch Flow 2 and all the others in Catch Flow1.
So, catch flow 2 rethrows every exception that doesn't know how to handle, to be caught at TryCatch1 . However, when I rethrow an exception, broker logs in event log an error mentioning: "broker has detected an error in node '...' whilst handling a previous error".
In the end, the Catch Flow1 finish its job correctly.

My question is, is there anyway to do a rethrow without getting an event log error?

Thx.
Back to top
View user's profile Send private message
smdavies99
PostPosted: Fri Mar 11, 2011 6:39 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.

You don't say what version of broker or what platform you are on.

There is a fix in 7.0.0.2 and due in 6.1.0.9 (any day now I hope....) to make SOAP nodes work the same way in this are as WMQ nodes.
_________________
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
john01
PostPosted: Fri Mar 11, 2011 7:00 am    Post subject: Reply with quote

Novice

Joined: 16 Jun 2010
Posts: 21
Location: PT

smdavies99 wrote:
You don't say what version of broker or what platform you are on.

There is a fix in 7.0.0.2 and due in 6.1.0.9 (any day now I hope....) to make SOAP nodes work the same way in this are as WMQ nodes.


Ups... sorry.

I'm using the 7.0.0.2 version on windows.
Btw, I've tried the MqInput node and I've got the same behavior. So, my problem remains.
Back to top
View user's profile Send private message
john01
PostPosted: Fri Mar 11, 2011 6:54 pm    Post subject: Reply with quote

Novice

Joined: 16 Jun 2010
Posts: 21
Location: PT

Anyone can help?

I guess that my error handling approach is in theory correct, however is not pretty, for a system administrator, getting treated errors in event log.

Thanks again.
Back to top
View user's profile Send private message
smdavies99
PostPosted: Fri Mar 11, 2011 11:36 pm    Post subject: Reply with quote

Jedi Council

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

sorry. I should have looked at your flow details more closely.

As you are using cascaded Try-Catch nodes then you are indeed going to experience different behavious from the model I was thinking of.

In our common error handling we don't use a cascaded TRy-Catch model.
We throw an exception.
The exception Handler does its stuff
Then it re-throws and the Input node tidies up.
_________________
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
john01
PostPosted: Mon Mar 14, 2011 3:45 am    Post subject: Reply with quote

Novice

Joined: 16 Jun 2010
Posts: 21
Location: PT

smdavies99 wrote:
sorry. I should have looked at your flow details more closely.

As you are using cascaded Try-Catch nodes then you are indeed going to experience different behavious from the model I was thinking of.

In our common error handling we don't use a cascaded TRy-Catch model.
We throw an exception.
The exception Handler does its stuff
Then it re-throws and the Input node tidies up.


Hi,
Tks for your reply.

I guess that I've tried your common error handling but I've got the same problem, that is, get an error in event log when exception handler re-throws.
Well, I've assumed when you said exception handler you've used a try-catch and "Input node tidies up" means that you've used the catch output provided by the input node.

Let me know if I've understood it correcty.
Back to top
View user's profile Send private message
john01
PostPosted: Tue Mar 15, 2011 1:58 pm    Post subject: Reply with quote

Novice

Joined: 16 Jun 2010
Posts: 21
Location: PT

Any other suggestions?

thx.
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 » Rethrowing an Exception
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.