PHSS_25662 required to fix iPlanet

[David Connolly]

I'm seeing the following error in my iPlanet server 4.1 sp11 on HPUX 11.11

"Error accepting connection -5974, oserr=233 (Insufficient resources)"

I did a search on the web, and found the article http://www.experts-exchange.com/Operating_Systems/Unix/Q_20268608.html which says that I need PHSS_25662.

Yet when I search for this patch on itrc, I can't find it.

Has anyone come across a similar error, or know where the patch is?

Thanks

Dave

[Ramkumar Devanathan · Accepted solution]

Dave,

Probably you should look for its replacement patch - PHSS_28198.

-- without much knowledge of the problem. --

- ramd.

[Alex Glennie]

Looks like it's been superceeded by PHSS_28198 Virtual Vaults 4.0 NES libproxy fix patch

[Robert-Jan Goossens]

Hi Dave,

http://www5.itrc.hp.com/service/patch/patchDetail.do?patchid=PHSS_25662&context=hpux:800:11:04

the link above is for yor patch,

Alex + Ramkumar gave you the latest patch,

http://www5.itrc.hp.com/service/patch/patchDetail.do?patchid=PHSS_28198&context=hpux:800:11:04

Hope it helps,

Robert-Jan.

[David Connolly]

Thanks folks,

This patch appears specific to this "VirtualVault" package which I don't have installed! I have libproxy.so, which is patched by this fileset, but that's provided by BEA as part of WLS6.1.

I'll raise with BEA, but I'm wondering has anyone else seen this error? I have iPlanet Webserver 4.1 sp11 talking to BEA Weblogic6.1 sp3 (on the same machine).

[Ramkumar Devanathan]

Dave,

The error message says insufficient resources - why don't you increase some kernel parameters -

here are some we used for iplanet 4.1 SP2 -

max_thread_proc maximum threads per process 8192
nkthread maximum threads in system 32768
maxdsiz max data segment size limit, heap memory use 1 GB (0x040000000)
maxtsiz max text size use 64 MB (0x04000000)
maxfiles_lim max number of open files per process 32768
nfile max number of files system wide 65536
ninode max number inodes in memory 32768

- ramd.

[Gary Yu]

Hi Dave,

We had similar problems before, and resolved it by increasing some kernel parameters, like max_thread_proc...

thanks,
Gary