PROLM9103003: Large Message Server Out of Resource Problems

ID Number: Q70875

2.00b

OS/2

buglist2.00b

Summary:

PROBLEM ID: OLM9103003

SYMPTOMS

Under the following circumstances, when using PATCH 5, the server

can crash, or exhibit other strange behavior, if the server is

processing large message named pipe transactions and it runs out

of resources:

1. The Server machine crashes after error 71 is returned to the

client, while the client is attempting to retry a DosWrite()

call. No tombstone symbol is displayed; the system just crashes

and must be rebooted. CTRL+ALT+DEL does not work, and the mouse

does not track.

2. If a DosWrite() call made by a client fails and error 55 is

returned to the client (followed by error 240 on a subsequent

operation), the server's DosRead() call will still succeed with

error 0, but the call states that 0 bytes were read (actual write

size was 65510, and it was a message-mode operation).

3. A DosWrite() call made by a client never unblocks, and the

server's DosRead() call returns fewer bytes read than were in

the message-mode DosWrite() call (for example, 4092 bytes are

read instead of the requested 65530 bytes), and an

ERROR_MORE_DATA error message is returned. The DosRead() call

was used with a user buffer of 65535 bytes, so the

ERROR_MORE_DATA error message is not appropriate.

CAUSE

These problems only occur if the server runs out of resources.

STATUS

Microsoft has confirmed these to be problems in OS/2 LAN Manager

version 2.00b. We are researching these problems and will post new

information here as it becomes available.