Re: Connection timeout

Hi Eric,
I fixed the issue. I had a typical deadlock, with two transaction working on
the same objects, where each one was waiting the other one finishing his
job. Anyway I'm working with just one database.
I don't think we're talking about the same problem, anyway try telling
something more about your problem, sure you will be helped.
greetings
Alessandro


On 2/27/07, Ferrer, Eric <[email protected]> wrote:
>
> Alessandro,
>
> Did you code around your stall or did you fix the issue causing the
> stall.  Sometimes I swear I notice connectivity issues between 3 of the
> external database I talk to.  Sometimes the problem self fixes as
> connectivity improves but other times we have a dead process that is
> waiting on its transaction to complete and is literally stalled on the
> query execution remotely.
>
> Thanks
> -Eric
>
> -----Original Message-----
> From: Alessandro Colantoni [mailto:[email protected]]
> Sent: Wednesday, February 07, 2007 4:29 AM
> To: OJB Users List
> Subject: Re: Connection timeout
>
> Hi Armin,
> thanks the same.
>
> I asked that because in an application I made a mistake that got in a
> stall
> :-(
> Of course I solved the problem, but I thought that a mistake can occur,
> and some resource can keep blocked.
> So I thought that if I could set some timeout, at rollback the resource
> will
> be available again , and the problem could be solved later (for example
> during the night) without affecting the user. My application is in
> test phase, and I'm sure that now stall are impossible, but you know...
> Anyway thanks again for the excellent support you do.
>
> Greetings
> Alessandro
>
>
> On 2/6/07, Armin Waibel <[email protected]> wrote:
> >
> > Hi Alessandro,
> >
> > Alessandro Colantoni wrote:
> > > Hi all.
> > > I'm using ojb1.4 with persistence broker.
> > > I would know if there is any way to set a timeout for the broker, so
> if
> > it
> > > doesn't end his job in the timeout limit a rollback is done and an
> > > exception
> > > thrown.
> >
> > Sorry no. OJB expects that all PB instances/PB-tx are closed/handled
> by
> > the user.
> >
> > regards,
> > Armin
> >
> > > Thanks in advance for the help.
> > >
> > > Alessandro
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>