ws_open_domain_client_socket: CreateFile Error 2

[Guest_imported]

Hi, our webapp suddenly returned an 'error 500-internal server error' page for a page which had been working fine all along. The whole webapp could not be accessed even though the websphere service was still running.

Here is the error we got in our trace files for the day:

Sat Feb 02 20:52:46 2002 - 00000308 00000414 - Error - ws_open_domain_client_socket: CreateFile Error 2
Sat Feb 02 20:52:46 2002 - 00000308 00000414 - Error - mediate_service_to_clone: Error 8 from clone 0, uri /sba/index.jsp
Sat Feb 02 20:52:46 2002 - 00000308 00000414 - Error - router_service : Failed 8

this happened for some time, for another page 404.jsp which is displayed upon 404 error.

the next string of errors is just a repetition of

Sat Feb 02 21:01:58 2002 - 00000308 000003e8 - Error - sysmgmt_queue_for_uri : Error returned from sysmgmt_vhost_for_aliasport rc=9
Sat Feb 02 21:01:58 2002 - 00000308 000003e8 - Error - sysmgmt_is_servlet_uri : failure in sysmgmt_queue_for_uri rc=9
Sat Feb 02 21:01:58 2002 - 00000308 00000380 - Error - sysmgmt_queue_for_uri : Error returned from sysmgmt_vhost_for_aliasport rc=9
Sat Feb 02 21:01:58 2002 - 00000308 00000380 - Error - sysmgmt_is_servlet_uri : failure in sysmgmt_queue_for_uri rc=9

we had to reboot the server for it to resume serving out pages.

does anybody have any idea about this?
we are using v 3.5.4 with fixpack 5 installed.
the file-serving enabler is disabled, doc root is set to a dir under IBM Http Server

 

[fearo]

Hi,

You have not mentioned what your OS is but under AIX client_socket files get created in the /tmp directory. If the file system is full then the files cannot be created causing a problem. Rebooting could clean up a number of temporary files thereby solving the short term problem.

Worth a try?

fearo