Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Catching exceptions over TransactionServer context

4 posts in General Discussion (old) Last posting was on 2000-03-09 03:18:40.0Z
Brian P. Surratt Posted on 2000-03-07 15:04:57.0Z
Newsgroups: sybase.public.easerver
From: "Brian P. Surratt" <brian.surratt@bigfoot.com>
Subject: Catching exceptions over TransactionServer context
Date: Tue, 7 Mar 2000 10:04:57 -0500
Lines: 17
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
NNTP-Posting-Host: surratt88.ft89.upmc.edu 128.147.89.88
Message-ID: <347_CnLz0cEi$GA.74@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:26988
Article PK: 157930

We have a JavaBean component in EAS 3.5 that is being called from a PB 7.0
component on the sma eserver. The PB component is using the
TransactionServer context object to access the server.

When the bean throws an exception, it seems to be blowing away the PB
component. We would like to interrogate the exception and possible resume
the routine that called the bean.

I know you can catch exceptions in a connection object, but how do you catch
them if you're using the TransactionServer context? Or will we be forced to
open a new connection object?

Thanks in advance,
Brian


Dave Wolf [Sybase] Posted on 2000-03-07 23:30:01.0Z
Newsgroups: sybase.public.easerver
From: "Dave Wolf [Sybase]" <dwolf@sybase.com>
Subject: Re: Catching exceptions over TransactionServer context
Date: Tue, 7 Mar 2000 18:30:01 -0500
Lines: 35
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
NNTP-Posting-Host: vpn-eme-060.sybase.com 130.214.8.60
Message-ID: <347_e#BWj2Ii$GA.285@forums.sybase.com>
References: <347_CnLz0cEi$GA.74@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:26933
Article PK: 154465

Go to the Jaguar Manager. Open the properties for the component. Go to All
properties. Find the property

com.sybase.jaguar.component.tx_outcome

Set its value to

failed

Dave Wolf
Internet Applications Division

"Brian P. Surratt" <brian.surratt@bigfoot.com> wrote in message
news:CnLz0cEi$GA.74@forums.sybase.com...
> We have a JavaBean component in EAS 3.5 that is being called from a PB 7.0
> component on the sma eserver. The PB component is using the
> TransactionServer context object to access the server.
>
> When the bean throws an exception, it seems to be blowing away the PB
> component. We would like to interrogate the exception and possible resume
> the routine that called the bean.
>
> I know you can catch exceptions in a connection object, but how do you
catch
> them if you're using the TransactionServer context? Or will we be forced
to
> open a new connection object?
>
> Thanks in advance,
> Brian
>
>
>


Brian P. Surratt Posted on 2000-03-08 20:03:53.0Z
Newsgroups: sybase.public.easerver
From: "Brian P. Surratt" <brian.surratt@bigfoot.com>
Subject: Re: Catching exceptions over TransactionServer context
Date: Wed, 8 Mar 2000 15:03:53 -0500
Lines: 59
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
NNTP-Posting-Host: surratt88.ft89.upmc.edu 128.147.89.88
Message-ID: <347_wCWtjoTi$GA.201@forums.sybase.com>
References: <347_CnLz0cEi$GA.74@forums.sybase.com> <347_e#BWj2Ii$GA.285@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:26867
Article PK: 157832

Dave,

I'm not sure this is the answer to what I asked..... isn't "tx_outcome" the
property to disable the exception thrown when a transaction rolls back?

In a PB component, I'm trying to catch exceptions thrown by other components
when I'm get my session handle from a TransactionServer context object. So
I'm doing an intercomponent call, not a call over a normal connection
object. On the connection object there is the Error event where the
exceptions can be caught and processed. There is no error event on the
TransactionServer object, which is my problem.

Thanks,
Brian

Dave Wolf [Sybase] <dwolf@sybase.com> wrote in message
news:e#BWj2Ii$GA.285@forums.sybase.com...
> Go to the Jaguar Manager. Open the properties for the component. Go to
All
> properties. Find the property
>
> com.sybase.jaguar.component.tx_outcome
>
> Set its value to
>
> failed
>
> Dave Wolf
> Internet Applications Division
>
> "Brian P. Surratt" <brian.surratt@bigfoot.com> wrote in message
> news:CnLz0cEi$GA.74@forums.sybase.com...
> > We have a JavaBean component in EAS 3.5 that is being called from a PB
7.0
> > component on the sma eserver. The PB component is using the
> > TransactionServer context object to access the server.
> >
> > When the bean throws an exception, it seems to be blowing away the PB
> > component. We would like to interrogate the exception and possible
resume
> > the routine that called the bean.
> >
> > I know you can catch exceptions in a connection object, but how do you
> catch
> > them if you're using the TransactionServer context? Or will we be
forced
> to
> > open a new connection object?
> >
> > Thanks in advance,
> > Brian
> >
> >
> >
>
>


Dave Wolf [Sybase] Posted on 2000-03-09 03:18:40.0Z
Newsgroups: sybase.public.easerver
From: "Dave Wolf [Sybase]" <dwolf@sybase.com>
Subject: Re: Catching exceptions over TransactionServer context
Date: Wed, 8 Mar 2000 22:18:40 -0500
Lines: 71
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
NNTP-Posting-Host: vpn-eme-033.sybase.com 130.214.8.33
Message-ID: <347_uaSp$aXi$GA.74@forums.sybase.com>
References: <347_CnLz0cEi$GA.74@forums.sybase.com> <347_e#BWj2Ii$GA.285@forums.sybase.com> <347_wCWtjoTi$GA.201@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:26837
Article PK: 157807

Oh ok sorry. I dont know PB so good. :)

Dave Wolf
Internet Applications Division

"Brian P. Surratt" <brian.surratt@bigfoot.com> wrote in message
news:wCWtjoTi$GA.201@forums.sybase.com...
> Dave,
>
> I'm not sure this is the answer to what I asked..... isn't "tx_outcome"
the
> property to disable the exception thrown when a transaction rolls back?
>
> In a PB component, I'm trying to catch exceptions thrown by other
components
> when I'm get my session handle from a TransactionServer context object.
So
> I'm doing an intercomponent call, not a call over a normal connection
> object. On the connection object there is the Error event where the
> exceptions can be caught and processed. There is no error event on the
> TransactionServer object, which is my problem.
>
> Thanks,
> Brian
>
>
> Dave Wolf [Sybase] <dwolf@sybase.com> wrote in message
> news:e#BWj2Ii$GA.285@forums.sybase.com...
> > Go to the Jaguar Manager. Open the properties for the component. Go to
> All
> > properties. Find the property
> >
> > com.sybase.jaguar.component.tx_outcome
> >
> > Set its value to
> >
> > failed
> >
> > Dave Wolf
> > Internet Applications Division
> >
> > "Brian P. Surratt" <brian.surratt@bigfoot.com> wrote in message
> > news:CnLz0cEi$GA.74@forums.sybase.com...
> > > We have a JavaBean component in EAS 3.5 that is being called from a PB
> 7.0
> > > component on the sma eserver. The PB component is using the
> > > TransactionServer context object to access the server.
> > >
> > > When the bean throws an exception, it seems to be blowing away the PB
> > > component. We would like to interrogate the exception and possible
> resume
> > > the routine that called the bean.
> > >
> > > I know you can catch exceptions in a connection object, but how do you
> > catch
> > > them if you're using the TransactionServer context? Or will we be
> forced
> > to
> > > open a new connection object?
> > >
> > > Thanks in advance,
> > > Brian
> > >
> > >
> > >
> >
> >
>
>