Consultor Eletrônico

Status: Verified

SYMPTOM(s):

Unconditional shutdown takes minutes when database is not started as root

Database is shutdown by user whom started the database

Another user than who started the database is connected self-service at the time of shutdown

Connected self-service user is not doing any transactional activity at the time of normal shutdown request

FACT(s) (Environment):

Database is not started as root
Client-server connections do not cause the shutdown delay
In previous versions proshut -by takes seconds under these conditions eg OE10.1x
OpenEdge 10.2A
OpenEdge 10.2A01
UNIX

CAUSE:

Bug# OE00183967

CAUSE:

This is a regression issue introduced in OpenEdge 10.2A to disallow client access to files that the user does not have permission to read/write etc. During exit the user id of the process is downgraded to the real user for the process. This code is also used by the broker, which causes the broker process to be downgraded immediatly before the broker performs database shutdown.

The user therefore does not have the permissions to kill the client for other self-service connected users. As the client cannot be signalled it never disconnected from the database, which forces the broker to continue to shutdown for up tp 6 min 30 seconds. Once the 6:30 mark is reached the broker attempts to perform an immediate shutdown on the database.

FIX:

Apply OpenEdge 10.2A02 Service Pack, or upgrade to OpenEdge 10.2B+ where this issue has been fixed.

Workaround:

Disconnect current connections with

$ proshut dbname -connect <userid>

Then issue the normal shutdown

Alternatively, issue an emergency shutdown after issuing the normal shutdown request:

$ proshut dbname -byF