This section contains a list of the more important known issues at the time of the Instant Messaging 7 2005Q4 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.
Table 3–6 lists the known issues and limitations.
Table 3–6 Known Issues and Limitations
ID |
Summary |
|
---|---|---|
4609599 |
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. |
|
4632723 |
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. |
|
4806791 |
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. |
|
4841572 |
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. |
|
4846542 |
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. |
|
4852882 |
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". |
|
4858320 |
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. |
|
4860906 |
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. |
|
4871150 |
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. |
|
4922347 |
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. |
|
4929247 |
Users cannot send messages when a moderator has denied presence access for the user. |
|
4929295 |
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. |
|
4944558 |
The Web Poll tab on the Alert window doesn’t display some web pages correctly. This is a limitation of the Java HTML renderer. Workaround: Send URLs using Message Creation tab instead of the Web Poll tab. |
|
4960933 |
Windows task bar menu labels are not rendered properly in some locales with multibyte characters. The menu functionality is not affected. |
|
4978293 |
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. |
|
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:
Configure should still work as expected, as no error really occurs. |
|
5042884 |
A problem with the archive provider enables end users to view archived data in search results. |
|
5050973 |
News message properties are not sent with news messages. As a result, the following client capabilities might be affected:
|
|
5051299 |
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. |
|
5051369 |
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. |
|
5051371 |
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. |
|
5071025 |
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. |
|
5082579 |
User status remains online even after the network connection is lost. |
|
5087303 |
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. Workaround:
|
|
5104840 |
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. |
|
6186465 |
An additional carriage return might be added when cutting and pasting text in Instant Messenger. |
|
6195180 |
The title and sender might not be displayed in the News window. |
|
6200472 |
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:
|
|
6203957 |
On Linux, if the openLDAP client RPM is not installed, imServiceConfigure might fail when trying to run ldapmodify. |
|
6205657 |
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. |
|
6213365 |
Instant Messaging service fails to start after upgrade. Workaround: Remove SUNWiimdv package before upgrading. |
|
6217627 |
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 |
|
6244099 |
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. |
|
6271708 |
Problems using SSL in a server-to-server environment. Workaround: Download the product patch from SunSolve Online. |
|
6282401 |
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. |
|
6282887 |
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). |
|
6286776, 6288533 |
Problems running Instant Messenger in a server-to-server environment. Workaround: Download the product patch from SunSolve Online. |
|
6291159 |
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. |
|
6302273 |
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. |
|
6302312 |
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. |