IBM Support

Troubleshooting the Domino Web Access 8 contact list (Buddy List)

Technote (troubleshooting)


Problem

You configure Sametime integration for Lotus Domino Web Access (DWA) 8. However, when you choose "Show Instant Contact List" in DWA 8, the contact list fails to load. Additionally, you may receive the following errors:

      "Bad http status: 404"
      "Buddy list servlet not logged into Sametime server"
      "Could not resolve the name on Sametime server".

Resolving the problem


1.
Confirm that awareness is working correctly

Check to confirm that awareness is working correctly.This will help isolate the problem to the Instant Contact List. Before proceeding, ensure that you see "I Am Active" when logged into DWA, indicating you are logged into Sametime.



Note: Instructions for setting up Domino Web Access 8 are available on IBM Lotus Domino and Notes Infocenter under the topic "Setting up Domino Web Access with Sametime".


2. Confirm that the DWA 8 contact list is enabled and properly configured
Confirm that the DWA 8 contact list is enabled and properly configured before proceeding to the next step. For additional detail on this topic, refer to the following document: "Error: "Bad HTTP status: 404" when accessing DWA IM Contact List (#1258358).

a. Enabling the Instant Contact List for DWA 8
To enable the DWA 8 Instant Contact List, open your DWA Server configuration document > Domino Web Access tab > Instant Messaging section. Set the "Prefer DWA 8 Contact List" setting to Enabled. Restart http for the setting to take effect.



b. Configuring the Instant Contact List for DWA 8
Note: The following information is available on IBM Lotus Domino and Notes Infocenter under the topic "Setting up Domino Web Access with Sametime". See "Part 5 - Set up the Instant Contact List in Domino Web Access".

  • Configure Java servlet support:
    1. From the Domino Administrator client, open the Server document for the Domino Web Access server in edit mode.
    2. Click "Internet Protocols" > Domino Web Engine tab.
    3. In the Java™ Servlets section, for the field Java servlet support, select "Domino Servlet Manager" from the list.
    4. Save and close the document and restart the server.

  • Edit the Sametime Configuration file:

    1. Open the Sametime Configuration application (stconfig.nsf) on the Sametime server.
    2. From the "By Form" view, open the ComunityConnectivity document.
    3. Add the IP address of the Domino Web Access server to Community Trusted IPs field.
    4. Save and close the document and restart the Sametime server.

  • Edit the Servlet Configuration file:

    1. Create a text file in the Domino Data directory on the Domino Web Access server called servlets.properties that includes the following line:
    servlet.DWABuddyList.code=com.lotus.dwa.stbuddy.DWABuddyList
    2. (Optional) If you are using reverse proxy servers in your environment, you may need to add the following line with the fully qualified domain name or IP address of the Sametime server in the servlets.properties file:
    servlet.DWABuddyList.initArgs=stserver=sametime.company.com

3. Troubleshooting "Buddy list servlet not logged in to Sametime server" errors



a. The Contact List servlet on the DWA 8 server communicates with the Sametime server over port 1516 (and passes the contact list information to the browser). Port 1516 must be open for this feature to work properly. Confirm you are able to telnet on port 1516 from your DWA server to your Sametime server. If you are unable to communicate on this port, you must correct this issue before proceeding.

b. You may need to determine if an additional IP address is missing from the "Community Trusted IPs" field in the Sametime Configuration application (stconfig.nsf) on the Sametime server.

  • One way to determine if a trusted IP is missing from stconfig.nsf is to review the Sametime.log file in the program directory of your Sametime server. Search for the word "trusted" to see if an IP address is not trusted. If so, you will see the following:

"Rejecting server component <ip address>, not in trusted ips list"

  • To correct this problem, follow these steps:

    1. Open the Sametime Configuration application (stconfig.nsf) on the Sametime server.
    2. From the "By Form" view, open the ComunityConnectivity document.
    3. Add the IP address mentioned in the sametime.log file to Community Trusted IPs field.
    4. Save and close the document and restart the Sametime server.

c. In some cases, the IP address mentioned in sametime.log may be different from the IP address of your actual DWA server. An example of this would be a multihomed server where DWA is running on an AIX platform and the IP address of the AIX machine is different from the IP address of the DWA server running on the machine. In such cases, it is necessary to add the IP address of the physical machine to the Community Trusted IPs field. A restart of the Sametime server is necessary for this change to take effect. By adding the IP address of the physical machine, all other servers running on the machine will be trusted by default. This behavior has been reported to Quality Engineering as SPR# MALZ7KLSLM.

d. If the Sametime server(s) are behind a standalone Community Services Multiplexer (MUX server), the DWA server has trouble pulling the buddylist. The problem is that the DWA 8 Buddy list is hard coded to connect to a Sametime server using port 1516 but the MUX server listens on port 1533.

This issue was reported to Quality Engineering as SPR # HMAI7KF83L and is fixed in Notes and Domino 8.5.1. Refer to the Upgrade Central site for details on upgrading Notes/Domino.

Note: The fix allows for the default port to be set to the desired value, by adding the following line to the servlets.properties file on the DWA server:

servlet.DWABuddyList.initArgs=logging=1,stport=1533


5. Troubleshooting "Could not resolve name on Sametime server" errors
  • In more than one case, the error "Could not resolve name on Sametime Server" was caused by duplicate LDAP documents existing in stconfig.nsf on the Sametime server. Removing the duplicate document(s) resolved the error and the contact list loaded successfully.
  • In another case, the error "Could not resolve name on Sametime Server" was caused because the LDAP task was loading automatically as a service on a Lotus Domino administrative server, even though the administrator had not configured the server to use LDAP. Removing the LDAP task from the server's notes.ini did not stop LDAP from loading. Disabling the LDAP Listener task in the 'TCP/IP port status' and 'SSL port status' fields on the Server document (Ports -> Internet Ports -> Directory tabs and restarting the staddin task on the Sametime server resolved this issue.
  • In another case, the error "Could not resolve name on Sametime Server" was caused because the LDAP server was overloaded with requests from a WebSphere server. The LDAP server was running at over 70% CPU in this case. The issue was resolved by implementing a designated LDAP server specifically to handle requests from the Sametime server.

6. Configure servlet logging to gather additional data

In the event that none of the above steps resolve the issue, it may be helpful to configure servlet logging to gather additional data to send to Lotus Support.


To gather servlet logging data, follow these steps:

    1. Append ,logging=1 to the end of the following line in your servlets.properties file in the Domino Data directory on your DWA server: (If this line does not already exist, simply add it in)
    servlet.DWABuddyList.initArgs=stserver=sametime.company.com
    Here's an example of a servlets.properties file with servlet logging configured:
servlet.DWABuddyList.code=com.lotus.dwa.stbuddy.DWABuddyList
    servlet.DWABuddyList.initArgs=stserver=sametimeone.acme.com,logging=1
    2. Restart HTTP on your DWA server.
    3. Reproduce the problem and take note of the time the problem (or error) occurs.
    4. Open log.nsf in the Domino Data directory of your DWA server.
    5. Under "Miscellaneous events", open the document which corresponds to the time the problem occurred. For very large log files, it is helpful to use CTRL + F to search for "JVM:".

Below is an example of server log output:

---------------------------------
01/30/2008 09:15:28 AM HTTP JVM: com.lotus.dwa.stbuddy.DWABuddyList: init
01/30/2008 09:15:29 AM HTTP JVM: TRACE: Creating STBuddyListService for srsdim.srsd.ca class=com.lotus.dwa.stbuddy.DWABuddyList, method=createBLService
01/30/2008 09:15:29 AM HTTP JVM: TRACE: Logging in to sametime.acme.com class=com.lotus.dwa.stbuddy.STBuddyListSA, method=login
01/30/2008 09:15:29 AM HTTP JVM: TRACE: Going to resolve user: CN=Jane Doe/O=ACME class=com.lotus.dwa.stbuddy.DWABuddyList, method=doPost
01/30/2008 09:15:29 AM HTTP JVM: TRACE: Wait for lookup service to be ready class=com.lotus.dwa.stbuddy.STBuddyListService, method=resolve

01/30/2008 09:15:48 AM HTTP JVM: TRACE: Got logged out event before login, reason = -2147483129 class=com.lotus.dwa.stbuddy.STBuddyListSA, method=loggedOut
01/30/2008 09:15:48 AM HTTP JVM: TRACE: Try to relogin class=com.lotus.dwa.stbuddy.STBuddyListSA, method=loggedOut
01/30/2008 09:16:16 AM HTTP JVM: TRACE: Going to resolve user: CN=Jane Doe/O=ACME class=com.lotus.dwa.stbuddy.DWABuddyList, method=doPost
01/30/2008 09:16:16 AM HTTP JVM: TRACE: Wait for lookup service to be ready class=com.lotus.dwa.stbuddy.STBuddyListService, method=resolve
01/30/2008 09:16:16 AM HTTP JVM: ERROR: Could not login class=com.lotus.dwa.stbuddy.STBuddyListService, method=waitForResolveToBeReady
01/30/2008 09:16:18 AM HTTP JVM: TRACE: Logging in to sametime.acme.com class=com.lotus.dwa.stbuddy.STBuddyListSA, method=login

---------------------------------

Copy the log output into a text file and send the text file to Lotus Support for analysis. In the example above, Support was able to translate the highlighted decimal error code -2147483129 to its text description "The host is unreachable".



Document information

More support for: Lotus Domino Web Access
Chat

Software version: 8.0

Operating system(s): Linux, Windows

Reference #: 1317895

Modified date: 10 February 2012


Translate this page: