Hi,

I am currently looking at the various options for exception handling. I am
having a problem at the moment finding out what kind of exception has
occurred. I have set up an orchestration to call a stored procedure - I then
renamed the stored procedure to cause an error. I tried to catch what I
thought would be a SqlException, but I guess it is not.

Does anybody know how to find out what kind of message is thrown?

Cheers,
Gary

[ Post a follow-up to this message ]

Gary,

>
> I am currently looking at the various options for exception handling. I am
> having a problem at the moment finding out what kind of exception has
> occurred. I have set up an orchestration to call a stored procedure - I
> then
> renamed the stored procedure to cause an error. I tried to catch what I
> thought would be a SqlException, but I guess it is not.
>
> Does anybody know how to find out what kind of message is thrown?

Are you calling the SP through the SQL Adapter, or through a custom
component?

If it is the SQL Adapter, then you have to take into account retries (so the
exception might not pop up right now), and then you need to be aware of
things like delivery notifications and catching exceptions from adapters
(they usually through a SoapException or DeliveryFailureException, btw).

You can always put a System.Exception handler and then check the exception
object to see what exact exception type it is.


--
Tomas Restrepo
tomasr@mvps.org
http://www.winterdom.com/

[ Post a follow-up to this message ]

Hi Tomas,

I am calling the stored procedure through the SQL Adapter. I'll have a look
at catching a SOAPException, so thanks for that.

Is there any documentation about what kind of exceptions can be thrown as
oppose to me just having a stab in the dark or trial and error?

Cheers,
Gary

"Tomas Restrepo (MVP)" wrote:

> Gary,
> 
>
> Are you calling the SP through the SQL Adapter, or through a custom
> component?
>
> If it is the SQL Adapter, then you have to take into account retries (so t
he
> exception might not pop up right now), and then you need to be aware of
> things like delivery notifications and catching exceptions from adapters
> (they usually through a SoapException or DeliveryFailureException, btw).
>
> You can always put a System.Exception handler and then check the exception
> object to see what exact exception type it is.
>
>
> --
> Tomas Restrepo
> tomasr@mvps.org
> http://www.winterdom.com/
>
>
>

[ Post a follow-up to this message ]

Gary,

> I am calling the stored procedure through the SQL Adapter. I'll have a
> look
> at catching a SOAPException, so thanks for that.
>
> Is there any documentation about what kind of exceptions can be thrown as
> oppose to me just having a stab in the dark or trial and error?

I don't think it is all that documented. However, in general, the exceptions
aren't all that many because you never see the real exception thrown by the
adapter directly, but rather a wrapper the messaging engine puts on top of
it.

You might want to read this, as well....
http://thearchhacker.blogspot.com/2...cations-in.html
http://blogs.msdn.com/kevinsmi/arch.../03/172574.aspx


--
Tomas Restrepo
tomasr@mvps.org
http://www.winterdom.com/

[ Post a follow-up to this message ]

Hi Tomas,

Thanks for that, those links were a good read. It will help me quite a bit.

Cheers,
Gary

"Tomas Restrepo (MVP)" wrote:

> Gary,
> 
>
> I don't think it is all that documented. However, in general, the exceptio
ns
> aren't all that many because you never see the real exception thrown by th
e
> adapter directly, but rather a wrapper the messaging engine puts on top of
> it.
>
> You might want to read this, as well....
> http://thearchhacker.blogspot.com/2...cations-in.html
> http://blogs.msdn.com/kevinsmi/arch.../03/172574.aspx
>
>
> --
> Tomas Restrepo
> tomasr@mvps.org
> http://www.winterdom.com/
>
>
>

[ Post a follow-up to this message ]