Sun Java Communications Suite 5 Release Notes

Known Issues and Limitations in Instant Messaging

This section contains a list of the more important known issues at the time of the Instant Messaging 7.2 release.

Patch updates are issued on a frequent basis. If you encounter a problem while installing or using Instant Messaging, contact Sun Support to enquire about the availability of a fix for this problem. Alternatively, you can consult SunSolve Online for patches.

This section covers the following product areas:

Instant Messaging Installation, Upgrade, and Uninstallation Issues


(Linux Only) When you upgrade to this release from Sun Java System Instant Messaging 7 2005Q4, the client resources will be undeployed from the web container.

Workaround: To avoid this problem, do one of the following:

  • Run the following command when applying the patch:

    "rpm -F --nopreun sun-im-client*"
  • Manually redeploy the client resources after applying the patch:


Server can't access user data after upgrading from Sun Java System Instant Messaging 7 2005Q4 to 7.2.


If you want to upgrade from Sun Java System Instant Messaging 7 2005Q4 to this release, and you are using a file to store user properties in the default location ( = "file"), you will need to copy the user data before you upgrade as follows:

Solaris: /var/opt/SUNWiim/db to /var/opt/SUNWiim/default/db

Linux: /var/opt/sun/im/db to /var/opt/sun/im/default/db


Customizations made to Instant Messaging resources are lost after patchrm

If you perform a patchrm on the Instant Messaging installation, all customizations to the client resources will be lost.

Workaround: Back up client resources before performing this action.


Server will not start after upgrade in a large deployment.

In a deployment where Instant Messaging conference information is stored in LDAP, and there are over 1,000 conferences stored, the server may not start after performing an upgrade. This is because at initial startup, the server checks to see if a migration has been performed. If none has, for example when upgrading from Sun Java System Instant Messaging 7 2005Q4 or 2005Q1 it isn't required, the server will not start. You need to manually add a flag to indicate that migration has been completed before starting the server.

Workaround: After upgrading, change to im_runtime_base and type the following commands at the command line to manually add a flag that indicates that migration has been completed:

touch db/muc/.ids_migrated_muc
touch db/muc/.ids_migrated

Upgrade rollback does not undeploy Instant Messenger components.

If you attempt to rollback this release to a previous version of Instant Messaging using patchrm, then run undeploy on the Instant Messenger resources, the undeploy command fails with the following error:

/im_svr_base/sbin/iwadmin: No such file or directory.

Workaround: None.

6440300, 6440340

Executing imadmin start command fails to start services after upgrading from 2005Q1 or 2005Q4 to 7.2.

A change was made to the watchdog in this release that causes imadmin from 2005Q1 or 2005Q4 to fail when used with the most recent version of the shared components and when the component is not also specified with the command.

Workaround: You must upgrade Instant Messaging components (server, etc.) to 7.2 if you upgrade the shared components to Sun Java Communications Suite 5. In addition, before you can upgrade Instant Messaging, you must update shared components.


(Solaris Only) Configure fails with error after rollback from Instant Messaging 7.2 to 2005Q4.

On Solaris, if you upgrade from Sun Java System Instant Messaging 7 2005Q4 to 7.2, then rollback to the 2005Q4 release, and then run the configure utility, configure fails with errors, but the rollback is successful.

Workaround: None.


The imadmin –migrate option is no longer supported.

Version 2005Q1 and earlier included a -migrate option for imadmin. This option is no longer supported.

Workaround: None.


The configure utility fails if you specify userid and groupid as anything other than root.

If you use any user other than root to install Instant Messaging, the user will not have permission by default to modify iim.conf. In this situation, when you run configure after installing, configure will fail.

Workaround: After installing, and before starting Instant Messaging components, you need to manually set permissions for imuser and imgroup as follows:

chown -R imuser:imgroup /var/opt/SUNWiim/default
chown -R imuser:imgroup /etc/opt/SUNWiim/default

Where imuser and imgroup are the user and group respectively, with which you installed Instant Messaging.

6516514, 6518514

(Linux Only) Upgrade to Instant Messaging 7.2 fails with file conflict error.

If you upgrade the sun-im-install-7.2–24 package before the sun-im-ident-7.2–24 package, the old versions of the packages are not overwritten. The old versions are sun-im-install-7.0–13 and sun-im-ident-7.0–13This results in the following error:

file /opt/sun/im/lib/imService.ldif from    \
install of sun-im-install-7.2-24 conflicts with    \
file from package sun-im-ident-7.0-13

The versions of these packages that should be installed with Instant Messaging 7.2 are sun-im-ident-7.2–24 and sun-im-install-7.2–24 .

Workaround: Uninstall the sun-im-ident-7.0–13 package, then upgrade Instant Messaging. Ensure that you apply sun-im-ident-7.0–24 before applying the sun-im-install-7.2–24 patch when applying patches during upgrade.

Instant Messaging Performance Issues


Memory performance degradation occurs with default garbage collection used by JRE 1.4.2 on the server's host.

Workaround: See Performance, Scalability, and Sizing Considerations for Instant Messaging for instructions.

Instant Messaging Server-to-Server Communication Issues


In server-to-server communications, news channel access rights might not work for end users.

For example, a user whose access is set to NONE is able to have READ access.

Workaround: None.


In server-to-server communications, an end user subscribed to a news channel on a different server is unable to chat with the message creator of the news channel.

Workaround: None.


In server-to-server communications, access rights for end users do not function properly in conference rooms.

For example, access rights such as NONE, READ, and WRITE.

Workaround: None.

Instant Messaging Configure Issues

6400572, 6431614

Command-line help for configure utility is incorrect

You must preface whole-word options with two hyphens when using the configure utility. For example, configure --nodisplay will work while configure –nodisplay will not. The command line help for the configure utility incorrectly states that you only need to use a single hyphen.


Configuration of multiplexor appears to fail due to an incorrect LDAP connection.

If you are installing an instance that will be only a multiplexor, and you select the option that stores user properties in LDAP, you will receive an error when you run configure stating that configuration failed.

Workaround: Do not choose to store user properties in LDAP if you are only installing a multiplexor.


Configure shows options for configuring the Access Manager SDK even if it is not installed.

After successful installation of Instant Messaging without Access Manager SDK, the “User Management Options” panel incorrectly allows you to choose settings for using Access Manager for SSO and policy.

Workaround: None.

Instant Messaging High Availability (HA) Issues


This release of Instant Messaging does not support HA deployments with Sun Cluster.

Workaround: None.

Instant Messaging XMPP/HTTP Gateway Issues


Log file location for the XMPP/HTTP gateway is incorrect after install

On Solaris, if you choose to use a location for logs other than the default, or if you are running on Linux, regardless of the path you choose, you need to modify the location of the default log file for the XMPP/HTTP gateway in httpbind_log4j.conf.

Workaround: In httpbind_log4j.conf , set the value of the log4.appender.appender_ID.file parameter to the location where log files are stored. By default, on Linux, this value is /var/opt/sun/im/default/log. If you chose another location for log files when you ran configure, enter that path as the value for the parameter.

Instant Messaging Server Pooling Issues

There are no known server pooling issues in this release.

Instant Messaging Redirect Server Issues


Cannot use Instant Messenger 2005Q4 or earlier with redirect server.

Older versions of Instant Messenger do not support XMPP redirection.

Workaround: Upgrade Instant Messenger to 2006Q1 or later

Instant Messaging Virtual and Hosted Domain Issues

6425755, 6431267

Searching for conference rooms and news channels in another hosted domain fails from the default domain.

Workaround: None.


Users in a non-default domain in a server pool are unable to join conferences created by users in the default domain.

In a server pool in a hosted domain environment, if a user in the default domain sets up a conference and invites users from a non-default domain to participate, the invited users cannot join the conference even though they are listed in the conference participant's list.

Workaround: None.

Instant Messaging News Channel Issues


News message properties are not sent with news messages.

As a result, the following client capabilities might be affected:

  • Subject is not displayed along with the news message.

  • Cannot change lines in the news message so that everything appears collapsed.

  • The formatting of the news messages might be lost.

  • Unable to send attachments.

  • Unable to send images.

Workaround: None.

6213223, 6217766

Lost messages in news channel.

If you post a message to a news channel then log out without viewing the message you just posted, the message appears to be lost. The messages are there, just not visible.

Workaround: View any messages you post to news channels before logging out of Instant Messenger, or unsubscribe and resubscribe to the news channel.

Instant Messaging Localization and Globalization Issues


Problems with customizing font for multibyte characters.

Workaround: In order to customize the font of multibyte characters, you need to type in your text first, then highlight the text and apply the font customization.


Printing errors occur with Instant Messenger in some locales.

Workaround: Cut and paste the text you want to print to another application that can print.


Windows task bar menu labels are not rendered properly in some locales with multibyte characters.

The menu functionality is not affected.

Workaround: None.


In zh_HK locales, Instant Messenger displays English.

Workaround: In order to see traditional Chinese (zh_TW) messages on a machine that uses a zh_HK locale for login, you need to create a symbolic link to zh_TW.


On Windows 2000, in localized versions of Instant Messenger, the first item in the folder pop-up menu does not display correctly.

The text should say “Collapse.”

Workaround: On client systems, use JDK 1.4.2 instead of JDK 1.5 (5.0).


An additional invalid character may be appended to the contents in email archive messages that contain multibyte characters.

Workaround: None.

Instant Messenger Issues

This section describes issues known to exist in Instant Messenger at the time of release in the following sections:

Instant Messenger General and Usability Issues


Idle detection is not implemented on Mac OS.

If a user leaves an Instant Messenger session, the absence is not automatically detected.

Workaround: Mac OS users need to explicitly set their presence status as AWAY, prior to leaving.


Custom statuses cannot be removed.

Workaround: The least used statuses are eventually removed. To remove one immediately, add five new customized statuses and the oldest one will disappear.


Changes users make on the Settings dialog box Privacy tab are saved as the changes are made, not when the user clicks OK.

For this reason, if you click Cancel after making changes on this tab, the changes are saved anyway.

Workaround: None.


Users cannot set priority for Idle or Away status when Instant Messenger is launched from the Java plug-in

The options for setting priority for idle and away status are not displayed in the user interface when Instant Messenger is launched using the Java plug-in. This does not occur when launching Instant Messenger from Java Web Start.


  1. Launch Instant Messenger using Java Web Start.

  2. Select Tools|Settings to bring up the Settings dialog box.

  3. Select the Advanced Tab.

  4. Set priority for Idle and Away as desired. More information for these options is available from the online help.


Cannot use Instant Messenger 2005Q4 or earlier with redirect server.

Older versions of Instant Messenger do not support XMPP redirection.

Workaround: Upgrade Instant Messenger to 2006Q1 or later


(Windows Only) Desktop Integration Settings option is missing when the client is launched from the Java plug-in on Windows

The Java plug-in does not support desktop integration. As a result, the Desktop Integration Settings option is missing from the General tab of the Settings dialog box.

Workaround: Invoke the application from Java Web Start.

Instant Messenger Log in/out and Connectivity Issues


The Instant Messenger Login dialog box does not necessarily display the server the end user last successfully logged into.

This behavior is inconsistent with the behavior for username, where the last successfully used username is displayed in the Login dialog box.


  1. On the Login dialog box, click More Detail.

  2. Select the appropriate server from the Server drop-down list.


If a client connected over SSL becomes disconnected and attempts to reconnect, the user will be prompted to accept the certificate again.

Workaround: None.


Instant Messenger unexpectedly disconnects.

In deployments with Access Manager, if Access Manager times out, Instant Messenger disconnects and cannot reconnect until the Instant Messaging server is restarted.

Workaround: Download the product patch from SunSolve Online.


Problems with Instant Messenger after reconnecting to server.

If Instant Messenger becomes disconnected from the server, it may not function properly when it reconnects. For example, presence information may not be displayed correctly, and conference rooms will not work.

Workaround: To join a conference room after a disconnect occurs, click the chat icon instead of double-clicking the conference on the Conferences tab. In addition, you can download the product patch from SunSolve Online.


User connections terminated by Access Manager do not log users out of Instant Messenger.

If Access Manager terminates a user's current session, the user is still logged in to Instant Messenger.

Workaround: None.


Users cannot log in to Instant Messaging if the user's password contains a leading or trailing space.

Workaround: None.

Instant Messenger Chat Issues


An additional carriage return might be added when cutting and pasting text in Instant Messenger.

Workaround: None.

Instant Messenger Printing Issues


On MAC OS, trying to print from the Java Web Start client hangs Instant Messenger.

Workaround: Copy the message and paste it in some other application, then print.

Instant Messenger Policy Management Issues


When multiple Instant Messaging policies are applied to a user, the policies can contradict one another.

For example, when the “Regular” and “Conference Room Administrator” policies are attributed to a user, the user is unable to manage conference rooms.

Workaround: Edit the regular user policy by clearing the “Ability to manage conference rooms” checkbox. This will ensure that the two policies do not conflict.

Instant Messenger Contact Management Issues


Empty contact groups disappear in Instant Messenger

If you create a new contact group in Instant Messenger but do not assign any contacts to the group, then logout and log back in, the contact group no longer appears in the contact list.

Workaround: Add a contact to the contact group before logging out of Instant Messenger.


Privacy profile not enforced on contacts when added to a group.


In a deployment with a pool of servers, if you move a contact from one contact group to another, the privacy profile for that group does not take effect on the recently moved contact.

Workaround: Sign off and back in to Instant Messenger after making changes.


If you import a contact list that contains entries from multiple domains, only those entries in your domain are imported.

Workaround: None.

Instant Messenger Calendar Pop-Up Issues

4852882, 6303248

Calendar reminder is blank.

If the Calendar server alarm type is set to text/xml, that is:

caldb.serveralarms.contenttype = "text/xml"

The Reminder field in the Instant Messenger Task Due Reminder alert window is blank.

Workaround: Set this field to "text/calendar" .

Instant Messenger Conference Room Issues


Confusing behavior occurs when inviting a user to a conference when that user does not have the correct permissions to join the conference.

It appears as if you invited the user, when in fact, the user never received the invitation.

Workaround: None.


Access permission changes do not take effect in conference rooms.

If you change access permissions for users already in a conference room, the changes do not take effect until you relaunch the conference room window.

Workaround: Close and relaunch the conference room window to update access permissions.


You cannot enter the same conference room from multiple concurrent Instant Messaging sessions.

Workaround: None.

Instant Messenger Alerts Issues


Alerts with embedded images are not rendered faithfully.

Workaround: None.

Instant Messaging Single Sign-On Issues


Multiple session validation fails.

An issue in the SSO provider interface causes it to only allow a single session per user.

Workaround: None.

Instant Messaging Documentation Updates and Issues

This section contains information about changes to and errors in the documentation in the following sections:

Instant Messaging Administration Guide

This section lists information that is not described in the Administration Guide


Adding new users to Instant Messaging does not provision them for other Sun Java Enterprise System products

By default, theInstant Messaging new user registration facility does not enable users for other components, such as email or calendar. As a result, a user entry which has been provisioned using the Instant Messaging new user registration facility does not contain objectclasses and attributes required for these other services and will, therefore, not receive archive emails or calendar pop-ups.

Workaround: You can manually modify the user entries or registration.ldif to provide this additional information for the user entries added through the new user registration facility. Alternatively, use the provisioning tools supplied with the other Sun Java Enterprise System products.

Instant Messaging Online Help and Quick Reference

The following information is not described in either the product online help or the quick reference.


Start screen

The Start Screen launches Instant Messenger. If you are using Java Web Start, press the Start button in the middle of the screen. If you are using Java Plug-in (for Windows users only), click the Java Plug-in button at the top of the screen. The Online Help and Quick Reference buttons display end user product help.

Workaround: N/A.


Procedure for creating and managing conference rooms in the Quick Reference points to wrong menu

The Quick Reference incorrectly states that to create and manage a conference room, you need to select Manage Conferences from the File menu. The Manage Conferences menu option is under the Tools menu, not the File menu.

Workaround: None.