Sun Java Communications Suite 5 Release Notes

Chapter 4 Sun Java System Instant Messaging 7.2 Release Notes

Version 7.2

These Release Notes contain important information available at the time of release of Sun JavaTM System Instant Messaging 7.2. New features and enhancements, known issues and limitations, and other information are addressed here. Read this document before you begin using Instant Messaging 7.2.

To ensure the best deployment with Instant Messaging, you should download the latest patches for this version of the product from SunSolve Online.

The most up-to-date version of these release notes can be found at the Sun Java System documentation web site. Check the web site prior to installing and setting up your software and then periodically thereafter to view the most up-to-date release notes and product documentation. These release notes contain the following sections:

Third-party URLs are referenced in this document and provide additional, related information.

Note –

Sun is not responsible for the availability of third-party Web sites mentioned in this document. Sun does not endorse and is not responsible or liable for any content, advertising, products, or other materials that are available on or through such sites or resources. Sun will not be responsible or liable for any actual or alleged damage or loss caused by or in connection with the use of or reliance on any such content, goods, or services that are available on or through such sites or resources.

Instant Messaging Release Notes Revision History

Table 4–1 Sun Java System Instant Messaging Revision History


Description of Changes 

Part Number 

September 2006 

Beta Release 


March 2007 

Final Release 


About Instant Messaging 7.2

Sun Java System Instant Messaging delivers secure presence and extended real-time messaging, enabling communities of users to communicate and collaborate instantly and securely. It combines instant messaging capabilities with conferences, alerts, news, polling, and file transfer to create a rich collaborative environment. It leverages an existing community, managed using LDAP, Sun Java System Access Manager, or Sun Java System Portal Server.

What’s New in This Release of Instant Messaging

This section includes the following topics:

Platform Support for Sun Java Communications Suite Server Products

The Instant Messaging server component is no longer supported on HP-UX or Windows platforms. For Instant Messenger supported platforms, see Instant Messaging Client Operating System Requirements.

Instant Messaging XMPP Redirect Server

The XMPP redirect server balances the load between servers in a server pool, increasing performance by decreasing the amount of communication required between servers in a single deployment. The XMPP redirect server increases the probability that two users who will likely share presence information and messages end up on the same node. You use a redirect service to optimize resource utilization. The redirect service directs client connections to specific hosts in the server pool.

Sun Java Enterprise System Monitoring Framework Support in Instant Messaging

This release of Instant Messaging supports version 2.0 of the monitoring framework. This monitoring framework provides information on the length of time for authentication, message delivery, the number of instant messages sent through the service, and other statistics.

Instant Messaging Redeploy Script Changes

The redeploy script used to redeploy Instant Messenger resource files has been renamed to iwadmin.

Highly Available Instant Messaging

(Issue Number: 6519754) This release of Instant Messaging does not support HA deployments with Sun Cluster.

Event Notification Service (ENS) Support in Instant Messaging

In this release there are two notification services for Calendar pop-ups: Sun Java System Message Queue (JMQ) and Event Notification Service (ENS). In a future release, the Communications Services products (Instant Messaging, Calendar Server, and Messaging Server) will use JMQ exclusively and ENS will be removed. However, for this release, you can continue to use ENS.

Legacy SSL and TLS Support for Instant Messaging

TLS support was added to Instant Messaging in the previous release; however, the Sun Java System Instant Messaging 7 2006Q1 Administration Guide did not adequately cover instructions for setting up TLS. TLS is used for communication between the server and clients, other servers, and Instant Messaging components such as the XMPP/HTTP Gateway. Legacy SSL is still supported for communication between clients and the multiplexor. Legacy SSL is no longer supported by the server and is not supported by the gateway. The Sun Java System Instant Messaging 7.2 Administration Guide now provides detailed information about setting up security for your deployment.

As a result of the implementation of TLS in Instant Messaging, you are no longer prompted to enter an SSL port for the server when you run configure.

The following iim.conf parameters are no longer used:

The following iim.conf parameters are new for this release:

Refer to the Sun Java System Instant Messaging 7.2 Administration Guide for information about using these parameters.

The Instant Messenger client uses imssl.html and imssl.jnlp only for legacy SSL connections. Instant Messenger supports TLS automatically when it connects to a server that is configured to use TLS.

Requirements for Instant Messaging

This section lists the requirements for installing Instant Messaging software. Before you install, ensure you have met the minimum hardware and operating system requirements. JRE 1.4 is supported by both server and client. In addition, check for any product patches before you install.

For the current list of required patches for Sun Java System Instant Messaging, go to the Patch Portal on SunSolve Online. As system patch requirements change and patches to Java Enterprise System components become available, updates will be made available on SunSolve, initially in the form of recommended patch clusters.

At the time of general release of Sun Java Communications Suite 5, the following Instant Messaging 7.2 upgrade patches are available:


Patch Number (English) 

Patch Number (Localized Languages) 

Solaris, SPARC 









In addition, the following Instant Messaging SDK 7.2 upgrade patches are available:


Patch Number 

Solaris, SPARC 






The hardware and software requirements for this release of Instant Messaging software are described in the following sections:

Instant Messaging Server Operating System Requirements

This release of Sun Java System Instant Messaging supports the following platforms:

A list of recommended patches for Solaris can be found at SunSolve Online.

Instant Messaging Server Software Requirements

This version of Instant Messaging is compatible with the following versions of other server software:

Instant Messaging Server Hardware Requirements

The minimum hardware requirements for installing Instant Messaging are as follows:

Instant Messaging Client Operating System Requirements

This release supports the following client platforms:

Instant Messaging Client Software Requirements

On Windows, you can run Instant Messenger using the browser’s Java Plug-in from the following browsers:

If the client machine has Java 1.4 or later version installed, there are no additional requirements to use either Java Plug-in or Java Web Start. Netscape Navigator v7 as well as the recent versions of the Mozilla browser include Java v1.4 or higher. Internet Explorer does not include the latest version of Java. If you experience problems using the client with Java 1.4, upgrade to 5.0. JDKTM 5.0 is included with Sun Java System Instant Messaging.

If the client machine does not have Java v1.4 or a higher version installed, you need to install Java Web Start. You can download and install Java v1.4. from the Java Technology website.

You can download and install Java Web Start from the Java Web Start Technology website.

HTML links can be exchanged over Instant Messenger and activated from the messenger by clicking them. When a link is activated, the messenger invokes a browser. Table 4–2 lists supported operating system and browser combinations.

Table 4–2 Supported Client OS and Browser Combinations for Instant Messaging

Operating System 


Solaris 10 JDS DesktopTM

Netscape Communicator, minimum 8.0, Mozilla minimum 1.7.12, Mozilla Firefox minimum 1.5.0 

Red Hat Linux Desktop, minimum 7.0 

Netscape Communicator, minimum 8.0, Mozilla minimum 1.7.12, Mozilla Firefox minimum 1.5.0 

Red Hat Linux Desktop, minimum 9.0 

Netscape Communicator, minimum 8.0, Mozilla minimum 1.7.12, Mozilla Firefox minimum 1.5.0 

Windows 98/ME/NT/2000/XP 

No restrictions 

Mac OS X 

No restrictions 

Instant Messaging Client Hardware Requirements

Instant Messenger uses between 20 and 40 MB of memory on most platforms. You should estimate the memory requirement by including the requirements of other applications (including operating systems) used on the client machine. In most cases, at least 128 MB RAM is recommended in order to run Instant Messenger and other applications comfortably. This number becomes higher when using memory-intensive operating systems.

Instant Messaging Installation and Uninstallation Notes

This section contains important information about installing and uninstalling Instant Messaging.

Instant Messaging Compatibility Issues

Table 4–3 lists the known incompatibilities in Instant Messaging 7.2.

Table 4–3 Instant Messaging 7.2 Compatibility Issues




Versions ofInstant Messenger prior to 2006Q1 do not support XMPP redirection. 

(Issue Number: 6401743) If you intend to use the Instant Messaging redirect server with Instant Messenger, you must use version 2006Q1 or later of Instant Messenger. 

If you use a third party client, ensure that it supports XMPP redirection before deploying the Instant Messaging redirect server. 

The Instant Messaging SDK Java packages were renamed in Sun Java System Instant Messaging 7 2005Q4 in order to match the open source community's naming conventions (org.netbeans.lib.collab). 

In a future release, Instant Messaging will use the new naming scheme exclusively and the old scheme will be deprecated. 


Instant Messaging 7.2 is incompatible with the 7 2005Q4 versions of Access Manager. 

When installing Access Manager, select “Legacy Mode (version 6 style)” instead of “Realm Mode (version 7 style)” on the Java Enterprise System installer. 


Instant Messaging 7.2 is incompatible with the 2004Q2 versions of Portal Server and Messaging Server. 

Upgrade Portal Server and Messaging Server when upgrading Instant Messaging 7.2. 


Due to a protocol change the Instant Messaging 7.2 server is not able to communicate with a server of an older version in federated deployments. 

Instant Messaging federated deployment sites will need to upgrade all the servers. The existing deployments who do not wish to upgrade the server will have to explicitly set the property of collaboration session factory object to use the legacy protocol implementation. 

You should coordinate the upgrade to limit the length of time during which servers will be unable to communicate with each other. 

Client - Server Communication 

Due to a protocol change the older versions of the client (2004Q2 and earlier) will not be able to communicate with the newer versions of the server and vice versa. 

You will need to upgrade both the client and server at the same time. 

Sun Java System Instant Messaging 7 2005Q4 and 2006Q1 are incompatible with shared components that ship with Sun Java System Instant Messaging 7.2. 

Instant Messaging has a hard dependency on the IM SDK. The IM SDK is installed with the shared components. 

You will need to upgrade shared components then upgrade Instant Messaging. See the Sun Java Communications Suite 5 Installation Guide for specific instructions.

The Instant Messaging SDK implementation of the Legacy Instant MessagingPresence protocol is now bundled. 

By default, the Instant Messaging SDK APIs use the implementation based on the XMPP protocol. Applications will have to explicitly set the property of collaboration session factory object to use the Legacy protocol implementation. 


The SDK component includes additional jar files: The Instant Messaging SDK uses the JSO (JABBER Stream Objects) libraries.

In order to take advantage of XMPP, you will need to modify the classpath for older applications using the Instant Messaging SDK.


The Instant Messaging 6 2004Q2 server is incompatible with the default behavior of the latest version of the SDK. 

In order to use the 6 2004Q2 server with the current Instant Messaging SDK you need to set the property of the collaboration session factory object to use the legacy protocol implementation. See Issue Number 6200472 under Known Issues and Limitations in Instant Messaging for instructions.


The Instant Messaging 7.2 multiplexor does not work with previous versions of the server. 

(Issue Number: 6396790) Due to a change in the internal protocol used between the multiplexor and the server, the multiplexor does not immediately detect when a previous version of the server goes down. Clients using a multiplexor connected to a previous version of the server that has gone down may not become aware of server failure within a reasonable amount of time. 

Use Instant Messaging 7.2 for both the multiplexor and server. You will need to upgrade or patch systems on which the server is installed and then upgrade systems on which only the multiplexor is enabled. 

Instant Messaging 7.2 server does not work with previous versions of the Instant Messaging SDK. 

(Issue Number: 6439781) You cannot start the Instant Messaging 7.2 server after upgrade if you do not also upgrade the Instant Messaging SDK. 

Use the 7.2 version of the server and the SDK. 

Changes to default codebase URL since release 6 2004Q2. 

(Issue Number: 6189921) The default URL for the codebase was changed from: 





Changes to default port numbers since release 6 2004Q2 

(Issue Number: 6189921) The server port was changed from 49999 to 45222 and the multiplexor port changed from 49909 to 5222. 


Performance, Scalability, and Sizing Considerations for Instant Messaging

This section describes some information useful for tuning and performance when deploying Instant Messaging in a server pooled configuration and for optimizing garbage collection in the following sections:

This information should be used with the Sun Java Communications Suite 5 Deployment Planning Guide.

Caution – Caution –

In a server pool deployment, you need to setup each Instant Messaging server in the server pool identically.

Tuning Instant Messaging Server Memory

Use the J2SE version 5 for running the Instant Messaging server, because it performs better and does not require command line tuning as it supports ergonomic features. More information on the use of this version of Java can be found in the following documents:

The Instant Messaging server uses the iim.jvm.maxmemorysize parameter in iim.conf to set the maximum size of the JVM heap to allocate. The default value of this parameter is 256 MB, but a large active deployment of Instant Messaging will need more memory. Determining how much memory to allocate for the Instant Messaging servers in the server pool is dependent on how many concurrent active users you need to support. Each Instant Messaging server in the server pool needs 256 MB along with 65 KB for each connected/active user with daily usage like the following:

Additional load per user, use of additional Instant Messaging services like news or file transfer, and use of features such as message filters, archiving, or SSL will consume more memory. You should perform load profiling of typical user activity before deploying Instant Messaging into a production environment. Contact Sun Support Services for more information about load profiling an Instant Messaging deployment.

Instant Messaging Thread Pooling and Service Port Configuration

Instant Messaging provides a set of configuration options to tailor the size and behavior of thread pools used to service client to server and server to server requests. These thread pools combined with associated service ports can improve the throughput of an Instant Messaging server.

Option Name 


Default Value 


Maximum number of threads for the default threadpool. 



List of independent thread pools. 

(Everything uses the default thread pool.) 


Capacity(*) of the default threadpool. 

10 * maxthreads

Maximum threads for named threadpool aaa:


Capacity of named threadpool aaa.

10 * maxthreads(aaa) 

Table 4–4 Defined Thread Pools for Sun Java Communications Suite




All server to server inbound communications. If the port allows server to server, this thread pool is used. 


All server to server outbound communications. If the port allows server to server, this thread pool is used. 


All server to server communications; the union of s2s-in and s2s-out. 

Defined threadpools can be specified and used with an associated server only service port, as described in Service Port Configuration . You edit thread and port configurations in iim.conf. You need to restart the server after making changes to thread and port configurations.

When a threadpool's capacity is exceeded, a message is output to standard error. The Instant Messaging server will not accept any additional requests for the threadpool until the number of requests is lower than the value of the threadpool's capacity. If this condition occurs in a server pooled environment, you may need to:

Example 4–1 Using the Defined Threadpool to Reserve Five Threads for Server to Server Inbound Communications for Instant Messaging

!s2s thread pool

Service Port Configuration

There are a number of service port configuration options as described in this section.



Default Value 


Open normal ports (allow for StartTLS). 



Open SSL ports (non-negotiable TLS) 



Open multiplexor ports 



List of normal ports 



List of SSL ports 



List of multiplexor ports 


iim_server.port.port .sndbuf

Socket send buffer size


iim_server.port.port .rcvbuf

Socket recv buffer size


iim_server.port.port .interface

List of specific network interfaces to bind to 

none (Indicates any) 

iim_server.port.port .protocol

List protocols are permitted on this port (client, server, component, peer) 


iim_server.port.port .nodelay

Enables the Nagles algorithm 


Throughput of a service port may be improved by adjusting the size of a port's send of receive buffer sizes.

Example 4–2 Service Ports Configuration for Instant Messaging

iim_server.port = 5269, 45269, 15222
iim_server.port.5269.protocol = server
iim_server.port.45269.protocol = peer, component
iim_server.port.45269.sndbuf= 512000
iim_server.port.45269.recvbuf= 512000
iim_server.port.15222.protocol = client 

Tuning Garbage Collection for Instant Messaging

(Issue Number: 6279277) Due to differences in the way the 1.4.2 and 1.5 versions of the JRE handle garbage collection, you may experience less than optimal performance using the default garbage collector with version 1.4.2 on the server's host. To fix this, you can either upgrade to version 1.5 of the JRE, or include the following command line option when you invoke the server:


For more information about JRE garbage collection, see the following:

Problems Fixed in This Release of Instant Messaging

This section describes problems fixed in this Instant Messaging 7.2 release.


(Linux Only) The location for Java is now correctly recorded in redeployApp after upgrade. You no longer need to manually modify the path for Java in /opt/sun/im/html/redeployApp.


Previously, if you configured a proxy, but disabled SSL in iim.conf, you could still log in through the proxy. In addition, the console showed that Instant Messenger was securely logged in when it was not. These errors no longer occur.


After upgrading, in a deployment with Sun Java System Access Manager, where user properties are stored in LDAP, existing multibyte news channel names no longer appear as %-encoded.


Instant Messenger no longer throws an exception if timeouts, for example httpbind.polling, are set too high.


The rdadmin generate command no longer overwrites the existing redirect database redirect.db.

6425667, 6465631

Users with read access are no longer able to attach files in moderated conferences.


Searching for users in another hosted domain from the default domain no longer fails.


In a virtual domain deployment, users can now receive presence information and send messages to contacts in other domains hosted by the same LDAP server.


Online help now displays the correct release number.


In a server pool deployment, single messages are no longer sent multiple times.

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.

Redistributable Files for Instant Messaging

Sun Java System Instant Messaging 7.2 does not contain any files which you can redistribute.