Instant Messaging 7.3 Release Notes

Chapter 5 Sun Java System Instant Messaging Software Version 7.3 Release Notes

This chapter contains important release information about Sun Java System Instant Messaging Software version 7.3. The release notes contain the following sections:

About Instant Messaging Version 7.3

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

What's New in This Release of Instant Messaging

See the What's New in This Release of Communications Suite 6 document.

Deprecated and Removed Features for Instant Messaging 7.3

Instant Messaging 7.3 does not have any deprecated features or removed features for this release.

Requirements for Instant Messaging 7.3

See Requirements for Communications Suite 6 and Requirements for Instant Messaging.

Instant Messaging Installation and Uninstallation Notes

This section contains important information about installing and uninstalling Sun Java System Instant Messaging software. If you are using Sun Java System Access Manager with Instant Messaging, install the Legacy (version 6 style) Access Manager by using the Sun Java Enterprise System installer. This version of Instant Messaging is not compatible with the Realm (version 7 style) Access Manager.
If you use Access Manager to store policies when configuring Instant Messaging, the following policies are created:

  • Ability to administer Instant Messaging and Presence Services
  • Ability to change your own Instant Messaging settings
  • Ability to manage Instant Messaging Conference Rooms
  • Ability to manage Instant Messaging news channels
  • Ability to send Instant Messaging alerts
  • Ability to watch changes on other Instant Messaging users
  • Default Instant Messaging and presence access

Instant Messaging Documentation Issues

This section contains information about known issues in the documentation.

Instant Messaging Administration Guide

This section lists information that is not documented in the Administration Guide.

6357162

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

By default, Instant Messaging new user registration facility does not enable users to access other components such as email or calendar. As a result, a user entry that has been provisioned by using the Instant Messaging new user registration facility does not contain object classes and attributes. As email and calendar services require object classes and attributes, a new user entry does not receive archive emails or calendar pop-ups.

Workaround: Modify the user entries or the registration.ldif file manually to specify information for user entries that you add by using 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 the product online help or the quick reference guide.

No ID

Help page for the Instant Messaging Start screen.

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

6480136

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. Select the Manage Conferences menu option from the Tools menu and not from the File menu.

Instant Messaging Compatibility Issues

The following table lists the compatibilities issues in Instant Messaging 7.3.

Table 5-1 Instant Messaging 7.3 Compatibility Issues

Incompatibility Impact Comments
Versions of Instant Messenger prior to 2006Q1 do not support XMPP redirection. Issue Number: 6401743. If you use the Instant Messaging redirect server with Instant Messenger, use version 2006Q1 or later of Instant Messenger. If you use a third-party client, ensure that the client supports XMPP redirection before deploying the Instant Messaging redirect server.
The Instant Messaging SDK Java packages are renamed in Sun Java System Instant Messaging software 7 2005Q4 to match the open source community naming conventions. For example, org.netbeans.lib.collab. Instant Messaging will use the new naming scheme exclusively and deprecate the old scheme.  
Instant Messaging 7.3 is incompatible with Sun Java System Access Manager version 7 2005Q4. The supported version of Sun Java System Access Manager is version 7.1  
Instant Messaging 7.3 is incompatible with the 2004Q2 versions of Portal Server and Messaging Server. The supported version of Sun Java System Portal Server are versions 7.1 and 7.1 update 1. The supported version of Sun Java System Messaging Server is version 7.0.  
Due to a protocol change the Instant Messaging 7.3 server cannot communicate with a server of a version older than 7.2 in federated deployments. Instant Messaging federated deployment sites should upgrade all the servers. The existing deployments who do not wish to upgrade the server should explicitly set the property of collaboration session factory object to use the legacy protocol implementation. Perform the upgrade to limit the length of time during which the servers cannot communicate with each other.
Client-Server Communication Due to a protocol change the older versions of the client and server (2004Q2 and earlier) cannot communicate with the new versions of client and server. Upgrade both the client and server at the same time.
Sun Java System Instant Messaging software 7 2005Q4 and 2006Q1 are incompatible with the shared components that ship with Sun Java System Instant Messaging software 7.3. Instant Messaging depends on the Instant Messaging SDK. The Instant Messaging SDK is installed with the shared components. Upgrade the shared components and then upgrade Instant Messaging. The Communication suite installer upgrades Instant Messaging SDK before installing Instant Messaging version 7.3.
The Instant Messaging SDK implementation of the legacy Instant Messaging Presence protocol is now co-packaged. By default, the Instant Messaging SDK APIs use the implementation based on the XMPP protocol. Applications should explicitly set the property of the collaboration session factory object to use the legacy Instant Messaging Presence protocol implementation.  
The SDK component includes additional JAR files. The Instant Messaging SDK uses the JSO (JABBER Stream Objects) libraries. To use the XMPP protocol effectively, modify the classpath parameter for older applications that use the Instant Messaging SDK.  
The Instant Messaging 6 2004Q2 server is incompatible with the default behavior of the latest version of the SDK. To use the 6 2004Q2 server with the current Instant Messaging SDK, 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.3 Multiplexor does not work with the older 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 the failure of a previous version of the server. Clients that use a Multiplexor connected to a previous version of the server that has failed might not be aware of server failure within a reasonable amount of time. Use Instant Messaging 7.3 for both the Multiplexor and server. Upgrade or patch systems on which the server is installed and then upgrade systems on which only the Multiplexor is enabled.
Instant Messaging 7.3 server does not work with the previous versions of the Instant Messaging SDK. Issue Number: 6439781. You cannot start the Instant Messaging 7.3 server after upgrade if you do not upgrade the Instant Messaging SDK. Use the 7.3 version of the server and the SDK.
Require URL to the default codebase URL since release 6 2004Q2. The default URL for the codebase is http://server:port/im.  
Require default port numbers since release 6 2004Q2 The default server port number is 45222 and the default Multiplexor port number is 5222.  
Instant Messaging 7.3 server does not support Multiplexor version 7.2.   Upgrade the Multiplexor to version 7.3.
Although the 7.2 client is supported on 7.3 server, all functionalities might not work.   Upgrade the client to version 7.3.

Problems Fixed in This Release of Instant Messaging

This section describes the problems fixed in the Instant Messaging version 7.3 release.

6531861

Server loses channels if different Multiplexors are configured to use different maximum session values.

2150967

The JUD search returns all attributes of a user, including the roster and private settings of the user.

6534319

The certificate used to sign-in the Instant Messaging client has expired.

6635378

Presence of an online contact is not sent to a new resource after bind and First Available Presence (FAP).

6470399

Instant Messaging sends invalid presence packets when joining a multiuser chat.

2150966

The XMPPPersonalContact.getPrincipal() function does a JUD search each time.

6358741

An option to change password using the GAIM client should be supported.

6553653

The Instant Messaging server does not handle password expiry warning with Access Manager correctly.

6504585

The Instant Messaging client should rejoin all existing open chats on client reconnection.

6487570

An option to completely turn off the emoticon conversion should be provided.

6649478

The file transfer feature does not work in the Alert window.

6477227

Client does not display time stamps that the server provides with history.

6577636

All client sessions hosted on a proxy component session should be terminated when the proxy server fails.

6577729

When a user copies text from a web page or any other source and paste the text in a chat window, the font settings of any subsequent text that is typed in the chat window changes drastically.

Known Issues and Limitations in Instant Messaging

This section contains a list of known issues at the time of release of Instant Messaging version 7.3.

Instant Messaging Installation, Upgrade, and Uninstallation Issues

6440300

Executing the imadmin start command fails to start services after upgrading from Java Enterprise Server version 4 to Instant Messaging 7.2.
A change was made to the watchdog in this release that causes the imadmin functionality from Java Enterprise Server version 4 to fail when used with the most recent version of the shared components.

Workaround: You must upgrade the Instant Messaging server and components to version 7.2 if you upgrade the shared components to Sun Java Communications Suite 5. In addition, before upgrading Instant Messaging, update the shared components.

6493939

The -migrate option of the imadmin utility is no longer supported.

6498428

The Configurator tool fails if you specify any userid and groupid other than root.
If you use any user ID other than root to install Instant Messaging, the user does not have permission to modify the iim.conf file. In this situation, when you invoke the Configurator tool after installing the Instant Messaging components, the tool fails.

Workaround: After installing and before starting the Instant Messaging components, you need to manually set permissions for imuser and imgroup. To do this, type:

chown -R imuser:imgroup /var/opt/sun/comms/im/default
chown -R imuser:imgroup /etc/opt/sun/comms/im/default

imuser and imgroup are the user and group respectively that you use to install Instant Messaging.

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 existing versions of the packages are not overwritten. The existing versions are sun-im-install-7.0-13 and sun-im-ident-7.0-13. This upgrade 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 and then upgrade Instant Messaging. During upgrade, ensure that you apply sun-im-ident-7.0-24 before applying sun-im-install-7.2-24.

6729367

(Linux Only) Upgrading or uninstalling Instant Messaging version 7.2 by using the Communication Suite 6 installer does not remove older Instant Messaging L10N RPM Package Manager (RPMs).

Workaround:
To upgrade to Instant Messaging 7.3 by using the Communication Suite 6 installer commpkg upgrade command, perform the following steps:

  1. Remove the previous L10N RPMs from the system manually.
    The following L10N RPMs exist in the system if you have installed Instant Messaging using the Communication Suite 5 installer. Use the rpm -e command to remove the L10N RPMs.
    sun-im-client-l10n-<version>
    sun-im-ident-l10n-<version>
    sun-im-install-l10n-<version>
    sun-im-olh-l10n-<version>
    
  2. Invoke the commpkg upgrade command.

To uninstall the previous version of Instant Messaging, perform the following steps:

  1. Remove the previous L10N RPMs from the system manually.
    The following L10N RPMs exist in the system if you have installed Instant Messaging using the Communication Suite 5 installer. Use the rpm -e command to remove the L10N RPMs.
    sun-im-client-l10n-<version>
    sun-im-ident-l10n-<version>
    sun-im-install-l10n-<version>
    sun-im-olh-l10n-<version>
    

Instant Messaging Server-to-Server Communication Issues

5051299

News channel access rights do not work in a server-to-server setup.
In a server-to-server communication, news channel access rights do not work for end users. For example, a user whose access is set to none has read access.

5051369

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

Instant Messaging Configurator Tool Issues

6431614

Command-line help for the Configurator tool is incorrect.
When using the Configurator tool, prefix the long options with two hyphens. For example, type configure --nodisplay and not configure -nodisplay. The command-line help for the Configurator tool incorrectly states that you need to use a single hyphen.

6444431

The Configurator tool shows options for configuring Access Manager even though it is not installed.
After successful installation of Instant Messaging without Access Manager, the User Management Options panel incorrectly enables you to choose settings for using Access Manager for single sign on and policy.

Instant Messaging XMPP/HTTP Gateway Issues

6354757

The location of the httpbind log is not correct in the httpbind_log4j.conf file.Log file.
On the Solaris OS or on the Linux platform, if you choose to use a location for log files other than the default location and regardless of the path you choose, modify the location of the default log file for the XMPP or HTTP gateway in the httpbind_log4j.conf file.

Workaround: In the httpbind_log4j.conf file, set the value of the log4.appender.appender_ID.file parameter to the location where the log files are stored. On Linux, the default value is /var/opt/sun/im/default/log. If you choose another location for the log files when you invoke the Configurator tool, type that path as the value for the parameter.

Instant Messaging Redirect Server Issues

6401743

Cannot use Instant Messenger 2005Q4 or earlier with the redirect server.
Previous versions of Instant Messenger do not support XMPP redirection.

Workaround: Upgrade Instant Messenger to 2006 Q1.

Instant Messaging News Channel Issues

5050973

News message properties are not sent with the 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 the message appears collapsed.
  • Format of news messages might be lost.
  • Unable to send attachments.
  • Unable to send images.

6213223

Messages appear to be lost in news channel.
If a user posts a message to a news channel and then log out without viewing the message that is posted, the message appears to be lost. The messages exist but are not visible.

Workaround: User should view any messages that is posted to news channels before logging out of Instant Messenger or unsubscribe and resubscribe to the news channel.

6217766

Alerts and news channel messages not displayed on relogin.
If the user sends an alert and then logs out without viewing the alert that is posted, the alert appears to be lost. The alerts exist but are not visible.

Instant Messenger Issues

This section contains a list of known issues at the time of release of Instant Messenger version 7.3.

Instant Messenger General and Usability Issues

4632723

Idle detection is not implemented on the Mac operating system.
If a user stops or terminates an Instant Messenger chat session, the absence of the user is not automatically detected.

Workaround: Prior to terminating the chat session, Mac operating system users should explicitly set their presence status as Away.

4841572

Custom statuses cannot be removed.

Workaround: The least used statuses are eventually removed. To remove a status, add five new customized statuses and the oldest status is automatically removed.

5104840

Canceling changes for the Privacy tab should not save the changes to settings.
The changes that users make on the Settings dialog box Privacy tab are saved as the changes are made and not when the user clicks OK. For this reason, if a user clicks Cancel after making changes on this tab, the changes are still saved.

6192611

Users cannot set priority for Idle or Away status when Instant Messenger is invoked 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 invoked using the Java plug-in. However, the options are displayed when Instant Messenger is invoked by using Java Web Start.

Workaround: To set the priority, perform the following steps:

  1. Start Instant Messenger by using Java Web Start.
  2. Select Tools->Settings.
    The Settings dialog box appears.
  3. Select the Advanced tab.
  4. Set priority for Idle and Away.
    For more information about these options, see the Instant Messaging online help.

6477618

(Windows only) The Desktop Integration Settings option is missing when the client is invoked by using the Java plug-in on the Windows operating system.
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 by using Java Web Start.

Instant Messenger Login, Logout, and Connectivity Issues

5087303

The Instant Messenger Login dialog box does not display the name of the end user who last successfully logged in to the server.
This behavior is inconsistent with the behavior for username, where the last successfully used username is displayed in the Login dialog box.

Workaround:

  1. Click the More Detail button on the Login dialog box.
  2. Select the appropriate server from the Server drop-down list.

6292212

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

6302273

Instant Messenger disconnects unexpectedly.
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 http://sunsolve.

6419542

User connections that are 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.

Instant Messenger Chat Issues

6186465

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

Instant Messenger Printing Issues

4846542

On the Mac operating system, trying to print from the Java Web Start client hangs Instant Messenger.

Workaround: Copy the message that needs to be printed, paste it in any other application, and print the information.

Instant Messenger Policy Management Issues

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 unchecking the Ability to manage conference rooms check box to ensure that the two policies do not conflict.

Instant Messenger Conference Room Issues

6205657

Changes made to the access permission do not take effect in conference rooms.
If you change access permissions for users who are present in a conference room, the changes do not take effect until you restart the conference room window.

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

6354184

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

Instant Messenger Alerts Issues

4806791

Alerts with embedded images are not displayed correctly.

Instant Messaging Single Sign-On (SSO) Issues

6536721

Multiple session validation fails.
Due to an issue in the SSO provider interface, Instant Messenger allows only a single session per user.

Other Known Issues

6643628

The Configurator tool does not connect to the Directory Server SSL port 636.

Workaround: Add the configuration values directly to the iim.conf file.

6661405

The Configurator tool checks for Application Server packages even though the container is Web Server. Similarly, the tool checks for Web Server packages even though the container is Application Server.

6664693

The Configurator tool displays the Application Server Administration port (4849) even though the container is Web Server.

6665839

Voice chat status shows Connected even after the server shuts down.

6652740

When a third user joins a group of two users in a group chat, the voice chat option is not inactivated. That is, a group of more than two users can start a voice chat, which is not the expected behavior.

6665277

Chat messages are not delivered in a sequence when CIR is restarted.

6646341

Voice chat is enabled after inviting other users to chat although the user is able to chat.

6665258

The roster subscription does not function correctly between the Instant Messaging and Presence Service (IMPS) clients.

6667139

User status shows online in others' contact list even when the user logs out.

6592012

Users are added twice in the recipient list of the Add Recipients dialog box.

6664744

Chat window is not updated when the other users log out.

6661538

User is unable to stop the voice chat once the chat session enters a group chat.

Workaround: To close the voice chat, close the Chat window.

6647520

The termination information query is not displayed correctly if a voice chat session terminates when the user status is busy.
The log entry corresponding to a termination information query is not generated correctly when a voice chat session is initiated. For example, if a user has initiated a voice chat with another user and receives a voice chat request, the new chat session is not initiated as the user is busy. The reason code parameter in the log file does not show the termination information query for this action.

6652192

Moderate conference does not work when httpbind is configured and the user logs in without httpbind.
The HTTP bind feature does not work as expected when a users create a moderated conference. Even though the conference is moderated, the message is sent to all the users without being accepted by the conference owner.

6576575

Authorize Contact is not sent to the added user when a user is added from Alert or Chat.
The authorization of contacts does not work when users try to add other users by sending an alert from the chat window. To add other users, choose Tools->Alert or select Tools from the Add to Contact list. The contacts are displayed in the user's roster with a status of Authorization Pending. However, the authorization is not sent to the invited user.

6667213

The Manage news channel online help shows the incorrect version of Instant Messenger.

6536165

Unable to close the chat window when the start multiple chats in new windows option is selected and deselected.
When a user enables and disables the option start multiple chats in new windows, multiple chat sessions are started in the same window. Every chat session appears in a separate tab. Users cannot close the chat window by clicking on the cross button on the chat window.

Workaround: Close the chat window by using the File->close or File->Leave option.

6635211

Consolidated Issues in News.
The Instant Messaging client enables users to subscribe to various news channels created by the news administrator. This feature has the following list of issues.

  • Scenario: Instant Messaging is configured by using httpbind.
    • When a news channel is subscribed, the news tab contains special characters when it appears for the first time. An exclamation mark is prefixed in the window that displays the news.
    • News channel subscription exists only for the session when it is subscribed to.
    • The order in which the news items are displayed does not match the order in which they are created.
    • The news window does not appear when a user with no contacts tries to view the news channel.
  • Scenario: Instant Messenger is configured in a hosted domain setup.
    • New news channels are not displayed immediately in the New Channel Administration window for users in both the default and non default domains.
    • New news channels that are created are not displayed in manage news channels.

6543861

Invited users do not get calendar reminder alerts.
When users enable the calendar reminder feature that is provided by Instant Messenger, the reminder is sent to the user who has created the event and not to the users who are invited for the event. Reminder alerts for the events are not sent to all the recipients of the event.

6545003

Stream error sent through httpbind has a blank error condition value.

6628423

Conference search fails with third party client in server-to-server setup.
When Instant Messengers are configured in a server-to-server setup, and third-party clients such as GAIM, Pidgin, and Exodus are used, a "Remote server or component not reachable" error appears when users try to search for a conference room.

6519053

Instant Messaging server allows the user to specify an invalid domain.
If a client is configured to the wrong domain, Instant Messaging server allows the client to log in. Subsequently, at resource binding, the server sends the correct domain to the client.

6634719

Fatal error is displayed on a terminal when Instant Messaging server is started.
When the Instant Messaging server is started on a command line terminal, the following errors appear.

Starting Server                      [OK]
Starting Multiplexor                 [OK]
[Fatal Error] :1:1: Premature end of file.
[Fatal Error] :1:1: Premature end of file.
[Fatal Error] :1:1: Premature end of file.
[Fatal Error] :1:1: Premature end of file.
[Fatal Error] :1:1: Premature end of file.
[Fatal Error] :1:1: Premature end of file.

6649550

Status Unknown is displayed for offline users after relogin in a server-to-server setup.
In a server-to-server setup users add contacts from different domains. After logging in and reloging in, Instant Messenger displays the status of the contacts from the same domain correctly. However, the status of the offline contacts for different domains are displayed as Status Unknown.

6302312

Instant Messaging client is not completely functional after reconnecting to server.

6626931

Authorization pending issues with client for self-jid.
The Instant Messenger client enables adding self-jid for a new user who logs in for the first time with no contacts in the user's roster. The self-jid user status is Online with Authorization Pending. The Instant Messenger server should not enable the user to add a self-jid.

6628502

Usage of the imadmin migratepropstore command is incorrect in the CLI help.
The command-line usage help for the migratepropstore command is incorrectly displayed. When the migratepropstore command is executed with the -h help option, the help is displayed as follows:

/opt/sun/comms/im/sbin/imadmin [options] migratepropstore \\
[error_log]

The correct usage is:

/opt/sun/comms/im/sbin/imadmin migratepropstore \\
[options] [error_log]

6632080

Unable to join conference rooms on another server in a server-to-server setup with TLS enabled.
In a server-to-server setup with Transport Layer Security (TLS) enabled, when users try to invite users in another domain to a conference, the invitation is not sent. Users are unable to invite users from other domains to a conference.

6644703

User status is not updated when a two-side subscription occurs in a server pool setup.
When Instant Messenger is configured in a server-to-server setup in server redirect mode and users try to subscribe to each other's roster, the subscription request is performed correctly. The subscription process also performs the authorization. The server requests for a reauthorization, in spite of the subscription performed successfully.

Workaround: Set the subscription after a reauthorization.

6646034

The imadmin assign_services command fails when Instant Messenger interacts with LDAP in the SSL mode.
When users try to use the imadmin command with the assign_services subcommand, an error is displayed when Instant Messenger is configured to interact with the LDAP server in the SSL mode.

Workaround:

  1. Edit the iim.conf file and set the LDAP port to a non SSL mode.
  2. Type the imadmin command and assign services.
  3. Reset the LDAP port to SSL mode in the iim.conf file.

6646048

New users can register even if a new user registration is not enabled on the server-side schema 1 and schema 2.

6620273

Migration fails for user IDs with uppercase characters.
The imadmin migratepropstore command does not migrate user IDs with uppercase characters.

6540801

Calendar pop-ups are sent even when the sysSendAlerts.acl parameter is set to false.

6531502

The imadmin command fails to bind and takes the Directory Manager password as input.

Workaround:

  1. Include the iim_ldap.usergroupbindcred = password parameter in the iim.conf file.
  2. Type the ./imadmin assign_services command to assign services to users in the LDAP directory.

6641777

Stop Moderating conference room does not remove the moderate conference pane.

4868028

Users cannot easily change their status in the Mac operating system.
Users cannot change their status by using the status bar of the Instant Messenger client when using JDK software version 1.5.0_09, in the Mac operating system Safari. This issue, however, does not exist in JRE implementation, version 1.4.2_03 and on Mac version 10.3.4.

Workaround: To change the status, select the File->Change Status option from the client menu.

4960933

On Windows, the task bar menu labels that contain multibyte characters are not displayed correctly in some locales. The menu functionality is not affected.

5080586

The status text should not be displayed in the label for the status button.
Users are given the option to change the current status when Instant Messenger is not connected to the server. Any modifications made to status when Instant Messenger is disconnected do not take effect.

5097513

Outstanding issues in Calendar and Instant Messenger integration.
Integration of Instant Messenger and Calendar messages has the following issues:

  • The from attribute of the Calendar reminder messages appends the domain name to the calendar Instant Messenger bot.
  • The server stores the calendar reminders messages of users whose status is offline.

5107645

Client cannot add the LDAP group to the privacy list.
Users can create a privacy profile on the client by selecting Tools-> Settings. For example, if users try to add an LDAP group to the profile for Show My User Status to: -> Only These Users, the LDAP group is displayed in the recipient's list. However, after clicking OK, the LDAP group is not displayed in the New Profile screen. This error occurs when the LDAP group is not in the user's roster.

6319382

Emoticons cannot be pasted in the horizontal line.

6482265

While upgrading from Sun Java Enterprise Server version 4 with Access Manager to Sun Java Enterprise Server version 5, Access Manager policies do not get reflected in the Instant Messaging client.
When users are granted the administrator permission to manage conference rooms in a Sun Java Enterprise Server version 4 setup, the permission does not get reflected when Instant Messenger is upgraded. Though Access Manager indicates that the users have administrator permission for conference, Instant Messenger does not recognize the permission.

6506541

Unable to choose a different user ID or group ID during configuration by using the state file.
The Instant Messenger Configuration tool enters a loop when configuring as root with a non root group ID. This situation occurs if the Configuration tool is executed using the configure command with a state file. This happens when Instant Messenger is configured with Access Manager or when Instant Messenger is configured with LDAP.

6463394

The Format menu options do not work as expected.

6663115

A user who is logged in to a chat for the first time is unable to post messages to the moderator of the conference.

Workaround: Close the conference window and reinvite the user.

6646374

MSN Web Messenger user ID is shown as xxx%hotmail.com@<jid> in the Instant Messaging client.

6665277

Chat messages are not delivered in a sequence when CIR shuts down and restarts.

6631538

If a user name contains the Ñ character, the user name is displayed incorrectly when the users logs in through a gateway.

6626943

The Tools->News->Subscribe news channel option displays an error in a hosted domain schema 2 setup.

6671892

Instant Messaging does not work through the portal gateway.

6676055

Single Sign On (SSO) cannot be enabled unless the policy is identity.
The Configurator tool enables users to select SSO even if the policy is non identity. This selection causes a conflict in the configuration. Even if the Configurator tool shows a successful configuration, the server does not start and user gets the following log message: SSO Configurations are conflicting.

Workaround: When SSO is selected, select identity as the policy.

6646394

In IMPS, the Client Capability Response should support any content type but the supported content type is text/plain.
When a file is transferred between an IMPS client and an XMPP client, the content type in the IMPS logs (sender) says it as "image/jpeg" while the Instant Messenger console logs (receiver) says it as "text/plain".

6698101

Event message is not displayed in the client pop-up window. Instant Messenger alerts the user to check the Calendar instead.

Workaround:

  1. Add the following line in the iim.conf file:
    agent-calendar.serveralarms.contenttype="text/plain"
  2. Restart the server.

6688458

Unable to start the Instant Messaging client using Firefox on a Solaris platform Sun Ray machine.

Workaround: If the Instant Messaging client is deployed on a Solaris platform by using Sun Java System Application Server 9.1 Update 1 as the web container, the client machines must have JDK software version 1.6.0.

6646704

Offline alerts functionality does not work when alerts are sent from the Instant Messaging client to users on the MSN and AOL Instant Messenger (AIM) clients
Sending an offline alert from the Instant Messaging client to users on MSN and AIM clients does not result in the message display when the users on MSN and AIM are back online.

6646722

The AIM contact group does not show up in the Instant Messaging client.

6688131

The Participation list option does not work from the View menu of the chat window.

6689323

The redeploy command gives an error after upgrade.

6676559

Null pointer exception is displayed when a JWChat user subscribes to an Instant Messenger user.

6651540

Unable to get import the roster information with a JWChat client.

6688472

The imadmin migratecerts command does not migrate the certificate chain.
The imadmin migratecerts command should migrate the certificate from the NSS store cert8.db/key3.db to the JKS (Java Key Store) file. When the command migrates the certificate key, it does not migrate the certificate with its chain. The SSL service does not send the proper SSL chain when users connect.

Workaround:

  1. Export the certificate from the keystore.
  2. Append the Certificate Authority (CA) chain.
  3. Reimport to the same server-cert name.

6671297

Service Management Facility (SMF) does not support starting or stopping of multiple Instant Messaging instances.

6673225

The imadmin start server and imadmin stop server commands starts and stops the server and the Multiplexor.

Workaround: Disable SMF if not required by typing the following command:
svccfg delete application/sunim

6661426

The stack trace should not be displayed in the INFO level log.

6693804

The uninstaller does not remove the SMF related files. The status is shown as online even though the product is uninstalled.

Workaround: Type the following command:
svccfg delete svc:/application/sunim:default

6691049

Instant Messaging server sends conference history timestamps with its own timezone rather than the universal time clock.

6678951

Voice chat does not work correctly when users do a side chat in a conference.

6677110

The Configurator tool should not provide an option to specify the SSO and the property store as ldap/file.

6686494

The Instant Messaging Configurator tool does not have an option to provide the default domain name for the server.

6686514

The Instant Messaging Configurator tool should have an option to configure voice for hosted domains.

6688466

Web Container configuration issues.

  • Webcontainer Path should be changed to Web Container Path. Note the space between the words Web and Container.
  • The default web container path should not be /opt. The path should use the default path /var/opt/SUNWwbsvr7/https-<HOSTNAME> or should not contain any value

6684303

The File attachment button is inactive or is disabled.
The File attachment button in the chat window of Instant Messaging client is inactive or is disabled in the following scenario.

  • User 1, a Instant Messenger user, sends a message to another user, User 2 who is another user on the Instant Messenger client.
  • User 1 closes the chat window.
  • User 2 sends a message to User 1 through the chat window that is open.
  • The file attachment button in User 2's client is inactive.

6685534

Issues with chat session.
Issue 1 - Consider the following:

  1. Log in to the Instant Messaging client as User1 and User2.
  2. User1 starts a chat session with User2 and User1 closes the chat window. In User2 chat window participation list, User1 still exists. A message "User2 has left" is displayed.
  3. User2 sends a chat message to User1 by using the original chat window that is open.

If User1 closes the chat window once again, User1 is added one more time in the participation list of the User2 chat window. The message "User1 has left" is not displayed.

Issue 2: Consider the following.

  1. Two users, User1 and User2, log in to the Instant Messaging client.
  2. User1 starts chat session with User2 and User2 closes the chat window. Before sending any text message User1 sends a VoIP initiation request to User2.
  3. The User2 chat window displays the VoIP status "Incoming call from User1".
  4. User2 accepts the VoIP call and send the text message.

In the User1 chat window, the client opens a new tab for text messages.

6672605

The migratepropstore command takes the source only from the iim.conf file and not from the command-line interface.

6685874

Error while inviting the user to join the openfire conference.

6656388

An error "Cannot get the default privilege" is displayed when the Instant Messaging client connects to openfire.

6684713

A new chat tab is opened during chat initiation while chatting with any third-party client.

6687295

An incorrect and incomplete user status change alert message is displayed when the MSN user logs off the MSN client.

6697992

Some handsets that use IMPS version 1.2 might not work correctly with the IMPS service.

6689918

Voice chat does not work correctly on a Sun Ray machine.

6514509

L10N: Apostrophes missing in four pages of the Configurator tool online help.

6649450

If the Instant Messaging client is invoked with a plug-in, the client does not enable the user to log out by using the Close button.

6634660

Redirect Server displays an resource constraint error even if another node instance exists.

6626366

After making changes to properties in the iim.conf file, the user is able to add a contact only once.

6653020

Authorized contact does not exist after changes are made to the sysWatch.acl policy.

6687284

User status alerts in the Instant Messenger client does not reflect the actual status of the user on the MSN client.

6647122

Setting the privacy profile to "Invisible to All" in Instant Messenger shows the user as online in the AIM client.

6646712

Cannot detect the AIM or MSN user who logs in to the transport in the Instant Messaging client.
In the Instant Messenger client, the MSN or AIM transport credentials that a user provides to log in are not displayed. It is not possible to detect the MSN or AIM user credentials provided to log in to the transport.

6646707

MSN user status "Appear offline" results in messages not being delivered.
If a user on the MSN client changes the status to "Appear offline" and then if a Instant Messaging client user sends a message to the MSN user, the message is not delivered. No error or information indicating that the message was not delivered is displayed to the client user.

6646702

The subject of the alert sent from the Instant Messaging client to the MSN client is not displayed in the MSN client.
When an alert is sent from the Instant Messaging client to the MSN client user, the subject of the Alert message does not appear in the MSN client. Only the content of the alert message is displayed.

6646700

An alert is sent as a chat conversation and the delivery status of the alert is not updated correctly.
Sending an alert from the Instant Messaging client to a user to a MSN client results in an alert being delivered in a chat window as a chat conversation. Also, the delivery status of the alert is not updated correctly. For example, although the user of MSN client has read the message, the status is not updated as read.

6646379

The poll functionality does not exists between the Instant Messaging client and AIM, MSN or Yahoo.

6646375

Text formatting changes made in the Instant Messaging client do not appear in AIM or MSN.

6646372

Alerts sent to the AIM client has extra spaces. The extra spaces affect the message display.
Extra spaces appear in alerts sent from Instant Messaging client to the AIM client. When alerts are forwarded to the AIM client, additional spaces tend to be appended to the message affecting the message display.

6641280

The font size of messages sent to the AIM user from the Instant Messaging client is inappropriate.

Workaround: In the config.xml file of the gateway, disable XHTML by uncommenting the line <disableXHTML/>.

6621474

Cannot kick the participants from conference room.
When a user tries to kick another user through the Kick option, a message "Not Allowed Text" is displayed in the conference window.

6634205

The IMPS gateway does not handle multiple resource login correctly.

6634210

Notification about users joining and leaving the chat room should be displayed with IMPS.

6645826

Conference communication does not work between users with the same username on different domains with schema 1 setup.

Workaround: Users must log in with a different username.

6486498

Alerts that contain a message and a URL image cannot be sent.

6511487

Configuring Instant Messenger by using the state file should not pop any questions.

6513448

The Configurator tool hangs in case of an incorrect ID while configuring using the state file.

6514018

Unable to choose different ports while configuring Instant Messenger by using the state file.

Workaround: Stop the Instant Messaging server and Multiplexor during configuration.

6532048

The configure utility should have all help options beginning with -- sign.

6642652

(Windows Vista only) Some options are missing in the Instant Messaging client Settings window in the Windows Vista operating system.

6669561

imadmin assign_services does not register the Instant Messaging services to the domain in the identity realm.

6568622

(On Linux only) httpd does not display with 3.7 Java Message Queue on the Linux operating system.

Redistributable Files for Instant Messaging

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

Labels

instantmessaging instantmessaging Delete
guide guide Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Feb 20, 2008

    prakpa says:

    There are two entries of the following bug. Please remove one entry 6643628 Co...

    There are two entries of the following bug. Please remove one entry

    6643628
    Configurator does not connect to DS SSL port(636)

  2. Feb 21, 2008

    prakpa says:

    Some of the bugs in RN has explanation and some of them don't. Please have a lit...

    Some of the bugs in RN has explanation and some of them don't. Please have a little explanation for all bugs

    1. Feb 22, 2008

      nileshp says:

      Hi Prakash, Most of the release notes entries that have no descriptions are ...

      Hi Prakash,
      Most of the release notes entries that have no descriptions are the ones which are fixed delivered and needs verification. If these bugs are fixed, they will have to be removed from the release notes. So I thought I'd visit the release notes when your team has finished with verifying those bugs.

      I'll add the descriptions for the remaining ones later. Also, some of the bug's synopsis is self explanatory so I just left them that way. If you think i need to add descriptions for any specific bugs, I can do that.

      Thanks,
      Nilesh

  3. Feb 21, 2008

    prakpa says:

    Please remove Chapter 5 from the title

    Please remove Chapter 5 from the title

    1. Feb 21, 2008

      nileshp says:

      Hi Prakash, The Chapter 5 in the release notes is required because we publis...

      Hi Prakash,
      The Chapter 5 in the release notes is required because we publish the release notes for the entire comms suite. The IM release notes is the fifth chapter.

      See http://wikis.sun.com/display/CommSuite/Communications+Suite+6+Release+Notes

  4. Feb 22, 2008

    Supreet says:

    Hi Nilesh, Please remove these issues which are listed below,there are in close...

    Hi Nilesh,

    Please remove these issues which are listed below,there are in closed state.

    6652197 - copyright show 2007 for client's about diaolog & in homepage.
    6481214 - renaming of contact is not getting displayed in the roster.
    6649478 - In Alert window file transfer not working.
    6651753 - Issues with IM version.

  5. Feb 25, 2008

    krishnakumarganesan says:

    6664299 Config location changes after upgrade from Beta to Beta Refresh on Linux...

    6664299 Config location changes after upgrade from Beta to Beta Refresh on Linux

    6664382 Created P2 iplanet_inst/documentation Upgrade is supported only from Beta to Beta Refresh

    The above bugs is missing in the release notes

  6. Feb 27, 2008

    krishnakumarganesan says:

    In whats new in this release section Under Propstore migration there is no con...

    In whats new in this release section

    Under Propstore migration there is no content yet. This has to be updated

  7. Feb 27, 2008

    prakpa says:

    bug ID Description. is repeated under Problems Fixed in This Release of Inst...

    bug ID
    Description.

    is repeated under

    Problems Fixed in This Release of Instant Messaging

    Please remove one

  8. Feb 27, 2008

    Supreet says:

    Hi Nilesh Under "Instant Messaging Online Help and Quick Reference" If no bug ...

    Hi Nilesh

    Under "Instant Messaging Online Help and Quick Reference"

    If no bug id is present for 'The Start Screen launches Instant Messenger' Instead of putting "No ID" put it as "Note".

    1. Feb 29, 2008

      ravikumar says:

      Hi Supreet, I spoke to Nilesh. He doesn't feel it should be changed. -Ravi

      Hi Supreet,

      I spoke to Nilesh. He doesn't feel it should be changed.

      -Ravi

  9. Mar 24, 2008

    Pravin_Sinha says:

    Hi Nilesh, Please doc this in the release notes. 6676055 : SSO cannot be enable...

    Hi Nilesh,

    Please doc this in the release notes.
    6676055 : SSO cannot be enabled unless policy is identity.

    Description:
    Although configurator allows to select SSO even if policy is non identity, this is a conflicting configuration with which even if configurator shows successful but server will not start and user will get the log message "SSO Configurations are conflicting ...".

    Workaround: If SSO is selected, select identity as policy.

  10. May 09, 2008

    Thiru says:

    Remove below bug from Knowm issues:- From Instant Messenger Calendar Pop-Up Iss...

    Remove below bug from Knowm issues:-
    From 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 the alarm type to caldb.serveralarms.contenttype = "text/calendar"."

  11. May 09, 2008

    prakpa says:

    Rahim , Please put the Messaging server version in the compatability chart

    Rahim ,

    Please put the Messaging server version in the compatability chart

  12. May 14, 2008

    SwethaRaj says:

    Rahim, Kindly add this bug 6669561 to release notes Thanks, Swetha

    Rahim,
    Kindly add this bug 6669561 to release notes

    Thanks,
    Swetha

Sign up or Log in to add a comment or watch this page.


The individuals who post here are part of the extended Sun Microsystems community and they might not be employed or in any way formally affiliated with Sun Microsystems. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Sun nor any other party necessarily agrees with them.

Copyright 1994-2009 Sun Microsystems, Inc.
Powered by Atlassian Confluence
Sun Guidelines on Public Discourse Privacy Policy Terms of Use Trademarks Site Map Employment Investor Relations Contact