Chris laments............
>
>Sorry - there's no hope. You gotta reboot the box. Take it from an unhappy
>site here that has to reboot our 9x7 box about every other week because of
>this problem... And we have our max# set to 2048!!
>
>We're getting close as we speak... *sigh*
>
>TCP_CUR_CONNS = 1663
>TCP_MAX_CONNS = 2048
>
>(It does appear to be fixed in 5.5 however...Our 5.5 box doesn't have the
>problem.)

I added these two little lines to the Websock Cobol just before the
IXCLOSE calls.

    CALL "SHUTDOWN" USING WS6-SD-1 SHUTDOWN WS6-CALL-STAT.
    CALL "SHUTDOWN" USING WS6-SD-2 SHUTDOWN WS6-CALL-STAT.

and made sure that the Visual Basic socket client also did this
(SHUTDOWN has a value of 2),
and it seems that MPE/iX is releasing Sockets pretty quickly, or at
least quicker than before.

It's not a scientific test, but after a full day, lots of web activity,
and therefore socket calls to Websock.cobx,

TCP_CUR_CONNS = 4
TCP_MAX_CONNS = 1024

(Notice how I bumped up the max from 256 to 1024 - <nervous grin>)

If I do serious web stuff, it rises alarmingly, but seems to stabilise
at a certain point (140 - 150), and then if I stop, it sinks fast.

Oh well, well be on 5.5 on Saturday.

Regards

Neil