Re: library cache load lock - major problems

norman.dunbar_at_lfs.co.uk wrote:
>and that's the last time I trust anything I'm told
> around here :o)

"Trust - but verify"

>
> Just thought I'd let you know what the solution was - reconfigure the
> application. Of course,this raises the question of why they need this
> limit in the application in the first place !

Could there be licensing issues?

I had an app once that was squiggly about the licensing - you could have many sessions open from one IP, but would count licenses with the same login or different login from many IP's. Anyways, some bug would randomly kill sessions, leaving the tcp cleanup to the timeouts, and long running SQL running. And apparently X'ing Windows (as opposed to cleanly exiting the app) would sometimes do the same thing. The licensing was from another party added into the app by the app vendor.

>
>
> Cheers,
> Norm. (Slipping back behind the firewall yet again)
>
> PS. Gravity sucks.

jg

-- 
@home.com is bogus.
And Winblows.