Vaalen
Member
Hi,
Sometimes (I think at least once every 14 days) the first user of the day (we restart the databases every night) hangs while connecting to one of the databases. When this happens, nobody is able to connect to the database anymore.
A lot of batch processing has been done between starting up the database and the first user trying to connect. Every Login matches a Logout in the .lg file.
Auditing is enabled.
We cannot find any error anywhere.
When we kill (Unix, RedHat) the user process (taking up around 100% CPU), everything is working perfectly and everybody can connect and start the application.
We once found an error (see title), but we are unsure if this is because we killed the process. Anyway, the user mentioned was indeed the first one trying to connect.
We use OpenEdge 10.2A on Unix RedHat. We use putty from our pc to start a unix session.
Any suggestion is welcome...
Sometimes (I think at least once every 14 days) the first user of the day (we restart the databases every night) hangs while connecting to one of the databases. When this happens, nobody is able to connect to the database anymore.
A lot of batch processing has been done between starting up the database and the first user trying to connect. Every Login matches a Logout in the .lg file.
Auditing is enabled.
We cannot find any error anywhere.
When we kill (Unix, RedHat) the user process (taking up around 100% CPU), everything is working perfectly and everybody can connect and start the application.
We once found an error (see title), but we are unsure if this is because we killed the process. Anyway, the user mentioned was indeed the first one trying to connect.
We use OpenEdge 10.2A on Unix RedHat. We use putty from our pc to start a unix session.
Any suggestion is welcome...