Subject | Re: [IBO] ACCVIO loop in fbclient.dll during rundown, maybe related to TIB_EVENTS |
---|---|
Author | mspencewasunavailable |
Post date | 2008-04-30T01:45:10Z |
--- In IBObjects@yahoogroups.com, Helen Borrie <helebor@...> wrote:
remote interface mods on IBO yet. See my preceding postings.
and try that. But what would it mean if that fixed it? Would I
then have to upgrade everyone to FB211 and IBO 4.8? That would be
scary.
Michael D. Spence
Mockingbird Data Systems, Inc.
>server
> At 11:14 AM 30/04/2008, you wrote:
> >For some users where the client is physically on a different
> >than FB, my application goes into a loop (taking all of a singleand
> >CPU). I suspect that it's engaged in an Access Violation loop.
> >AFAICT, it's at offset 24413 of fbclient.dll (build 2.0.0.12855),
> >which is talking to Classic 2.0.1.12855. I'm using IBO 4.7.16
> >BDS 2006. The application connects to two different databases,and
> >uses TIB_Events with one of them.one
> >
> >When the application is in this error state, netstat shows two
> >connections to port 3050, usually in ESTABLISHED but sometimes
> >may be in TIME_WAIT, which, IIRC, means the port has already beensound
> >closed. Port 3051 (my auxport) is in CLOSE_WAIT. This makes me
> >wonder if the problem concerns Event rundown.
> >
> >I've noticed a few items in this group and in FB-Support that
> >similar, but they're mostly very old.We really don't know the whole scope of the effect of the Fb 2
> >
> >Does any of this sound familiar to anyone?
> >
> >I've got some ideas about things to look into, but the biggest
> >problem here is that I can't reproduce this at all on any of my
> >development systems.
>
> You could try the Fb211 client to see if this solves the problem.
remote interface mods on IBO yet. See my preceding postings.
>I'll have to see if I can get the client to let me use their machine
> Helen
>
and try that. But what would it mean if that fixed it? Would I
then have to upgrade everyone to FB211 and IBO 4.8? That would be
scary.
Michael D. Spence
Mockingbird Data Systems, Inc.