Sun Java System Instant Messaging 7 2006Q1 Release Notes

Known Issues and Limitations

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

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

Known Issues and Limitations lists the known problems and limitations.

Table 4 Known Problems and Limitations




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


Idle detection is not implemented on Mac OS. 

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


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


Alerts with embedded images are not rendered faithfully. 

When a recipient receives an alert with embedded images, the images are not centered and font information present in the accompanying text is lost. 


Custom statuses cannot be removed. 


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


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


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


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. 


Set this field to "text/calendar".


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. 


Can’t create conf_room/news using certain gb18030 characters

Since conference and news ACL file names are written using names fed from Instant Messenger, there is a problem creating ACLs when the names contain Tibetan or Arabic characters.


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. 


Read-only users and fully privileged users within a chat room are indistinguishable. This might be confusing if a user attempts to send a message to a user with read-only privileges. The read-only user will not receive the message. 


Users cannot send messages when a moderator has denied presence access for the user. 


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. 


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


The Web Poll tab on the Alert window doesn’t display some web pages correctly. This is a limitation of the Java HTML renderer.


Send URLs using Message Creation tab instead of the Web Poll tab. 


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


In zh_HK locales, Instant Messenger displays English.


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. 

5004449, 5084745 

On Linux, warning messages might be displayed on screen when you run the configure utility. Typically, these warning messages begin with the following text: 

WARNING: Cannot parse rpm files
by running "/bin/rpm -qp --queryformat

Configure should still work as expected, as no error really occurs. 


The documentation should state that the multiplexor queries DNS directly and does not use getbyhostname.

Workaround: If you are not using DNS for hostname resolution, you can use IP addresses instead of hostnames in iim.conf. If you are using DNS, change hosts in nsswitch.conf as follows:

hosts: files dns


A problem with the archive provider enables end users to view archived data in search results. 


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.


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.


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. 


In server-to-server communications, access rights for end users, such as NONE, READ, and WRITE, do not function properly in conference rooms.

5065241, 5080586 

Users are given the option to change presence status while Instant Messenger is not connected to the server. Any modifications made to status while disconnected do not take effect. 


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. 


User status remains online even after the network connection is lost. 


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.


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. 


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


The title and sender might not be displayed in the News window. 


If you intend to run the Sun Java System Instant Messaging 6 2004Q2 server with the SDK from this release, you will need to explicitly set the property of the collaboration session factory object to use the legacy protocol implementation. The SDK for this release supports the legacy protocol implementation; however, the default is to use the new protocol implementation (XMPP). To use the legacy protocol implementation, you need to use the following constructor to create a CollaborationSessionFactory in the API:

CollaborationSessionFactory factory=new


On Linux, if the openLDAP client RPM is not installed, imServiceConfigure might fail when trying to run ldapmodify.


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. 

6213223, 6217766 

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 service fails to start after upgrade. 

Workaround: Remove SUNWiimdv package before upgrading.


On a machine with less than the required memory, the configure utility might complete configuration of Instant Messaging, but also throw exceptions. 

Workaround: Ensure that your system meets the minimum memory requirements before installing or running the configure utility. If you still encounter this problem, run the following:

Solaris: /opt/SUNWiim/lib/imServiceConfigure

Linux: /opt/sun/im/lib/imServiceConfigure


The Administration Guide contains confusing information for enabling the Instant Messenger Archive Control component for the Java Plug-in. This component is not present in this release. 


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 instructions.


The online help does not mention that if you remove all contacts from a contact group, then logout and back in, the contact group will be deleted. 


Sun Java System Instant Messaging 6 2004Q2 is not compatible with the shared components that ship with this release. 

Workaround: If you must upgrade the shared components, then upgrade all Instant Messaging components to the current version. 


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.” 

6286776, 6288533 

Problems running Instant Messenger in a server-to-server environment. 

Workaround: Download the product patch from SunSolve Online.


Instant Messenger disconnects from the server after a time period different from the value set for the iim_server.clienttimeout parameter in iim.conf.

Workaround: Specify the following system property using the -D option:

Set the value to the number of seconds after which you want Instant Messenger to start sending bytes to the server. These bytes are only used to prevent the time out and subsequent disconnect. 


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


The online help incorrectly states that conference moderators can edit messages before accepting them. Conference moderators cannot edit messages. 


In deployments with Sun Java System Access Manager, if Sun Java System 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.


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.


If the server is configured to use text/xml format for Calendar pop-ups, task pop-ups received by users do not contain the expected reminder message. Reminder messages are received as expected when using text/calendar format.


(Linux Only) The location for Java may be incorrectly recorded in redeployApp after upgrade.

Workaround: Manually modify the path for Java in /opt/sun/im/html/redeployApp.


The XMPP/HTTP Gateway only supports StartTLS for secure communications. If the multiplexor is configured to use SSL, you need to ensure that the gateway connects directly to the server over StartTLS.  


(Linux Only) When you apply the patch to upgrade to this release, 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:



(Linux Only) In a deployment with Sun Java System Application Server, you must accept the default URI when prompted when you run configure.


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 on to Instant Messenger after making changes. 


A ConnectException may appear after redeploying the XMPP/HTTP Gateway. The exception can be ignored.


When Instant Messaging is the only component installed on a system, the file ldajpjdk.jar may not be present in /usr/share/lib (Solaris) or /opt/sun/share/lib (Linux). In this case, if you choose to store user properties in LDAP when you run the configure utility, you will receive an exception.

Workaround: On the command-line, go to the following location: 


Add the ljdk package manually using one of the following commands: 


pkgadd SUNWljdk


rpm -i sun-ljdk-4.18-4.i386.rpm

Run the configure utility again.


(Linux Only) 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 from /var/opt/sun/im/db to /var/opt/sun/im/default/db before you upgrade.


If you configure a proxy, but disable SSL in iim.conf, you can still log in through the proxy. In addition, the console will show that Instant Messenger is securely logged in when it is not.


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


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


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.

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.


By default, the Instant Messaging new user registration facility does not enable users for other Sun Java Enterprise System 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. 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.


If you deploy the XMPP/HTTP gateway, you need to set the iim_agent.httpbind.enable parameter in iim.conf to true. By default, this parameter is set to false.


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. 


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

Workaround: Edit each %-encoded name through the edit news channel windows in Instant Messenger. 


If you will be storing user properties in LDAP, you must install the Sun Java System Access Manager SDK before you run the configure utility.


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


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


Instant Messenger may throw an exception if timeouts, for example httpbind.polling, are set too high.


The Sun Java Enterprise System 2005Q4 Upgrade and Migration Guide incorrectly instructs you to use the deployHTML script to redeploy Instant Messaging resources. Instead, you need to use redeploy. See Redeploying Resource Files in Sun Java System Instant Messaging 7 2006Q1 Administration Guide for instructions.