Login as a user to QMS times out

There is a long pause while trying to log in as a user to QMS. The login eventually fails or a script error is returned.

QMS uses SMTP to authenticate users before they are given access to their quarantine. Because QMS uses SMTP to authenticate, receive threads must be available on the GWIA (SMTP Gateway) in order for the authentication to be successful. If all of the receive threads are being used there will be a long pause while trying to log in to QMS as a user.

Another characteristic of this issue is that the log in to QMS will work sometimes but not other times depending on how busy the GWIA is.

1) Check the number of GWIA receive threads available.

For NetWare:

Open your remote console to the GroupWise Internet agent screen and press F10 and then F9. The screen will look similar to the following:

The number of receive threads available is the number to the right of the colon. In the screenshot the number of receive threads available is 60, and the number being used is 4.

For Linux:

Open the GWIA web status program (default <ip_address>:9850). In the thread status section it will specify  how many threads are being used and how many are available.

a. If the number of available receive threads is anywhere near 0, you will want to increase the number of GWIA receive threads so that QMS will have open threads to authenticate users. Continue with step 2 below.

b. If the number of available receive threads is more than 10 then this is likely not the issue and you should go back to the knowledgebase and review some of the other articles that address user login issues.

2) Change the receive threads.

Usually you'll want to increase the number of receive threads by about double to make sure there are plenty of threads available. (example, if I have 16 receive threads total, I would set the receive threads to 32).

To increase the GWIA receive threads open up the gwia.cfg file (normally found in sys:\system) and modify the /rd switch at the bottom of the page to have a larger number. For more details please refer to the GroupWise 7 administration guide.

3) Restart the GWIA.

A restart of the GWIA is necessary in order for the changes to take affect.

This article was originally published in the GWAVA knowledgebase as article ID 378.