Up Prev Next
From: sy50027 at milton dot sbi dot com (Simon Yaminian)
Subject: RE: out of sync message
Date: Jun 4 1998 8:52PM
> From owner-SYBPERL-L@listproc.net Thu Jun 4 16:47:32 1998
> From: Tim Holt
> To: SybPerl Discussion List
> Subject: RE: out of sync message
> Date: Thu, 4 Jun 1998 13:42:04 -0700
> Mime-Version: 1.0
> X-Listprocessor-Version: 8.2.06 -- ListProc(tm) by CREN
> Interesting to hear that!
> I really didn't solve the problem of the fork. In our
> case, the time spent to do the update was pretty small,
> and so it was not really necessary to do the fork'ed
> off task. Had it been necessary, I had contemplated
> actually having a second perl program that did the
> task that was to be forked. Then the main prog would just
> run the other prog when necessary.
> -----Original Message-----
> > You know, I've fought that same error pair...
> > Sybase error: Datastream processing out of sync.
> > Sybase error: DBPROCESS is dead or not enabled.
> > as well. I never figured out exactly what was causing the
> > problem, but it was centered in some code that was being
> > fork'ed off to do an update in the background. When I
> > finally tossed the fork method, the errors went away.
> > Don't ask me what fixed what, but the errors went away.
> > I've got my Sybperl error traps for our site set to email
> > me w/all the error info, perl call dumps, etc. and I was
> > getting tired of coming in to find 45 SQL/perl warnings
> > waiting for me in the mailbox!
> > Tim Holt, Rogue Wave Software
> Thank you for your insights regarding this problem. As it turns out, I
> also doing forks in the script. I am wondering what other alternatives
> used if any. I am also interested to know if you ever implemented a
> like cancel request for an ongoing Sybperl query or a batch of commands.
> Thank You
> Simon Yaminian
Thanks much for your reply.