Instant Messaging 8 Update 1 Release Notes

Sun Java System Instant Messaging Software 8 Update 1 Release Notes

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

About Instant Messaging

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 Instant Messaging 8 Update 1 document.

Deprecated and Removed Features for Instant Messaging 8 Update 1

The following features have been deprecated from Instant Messaging 8 Update 1:

  • IM Client - The Java client that is used to access the Instant Messaging server is deprecated. As a result, the following client features are deprecated:
    • VOIP Support - This feature enables you to convert a user's chat session into a live voice call over the internet by using Instant Messaging client
    • Poll - This feature helps you in surveying a group rapidly by conducting online polls
    • News - This feature enables you to access published information such as company announcements, project updates, or event notices on a subscription basis
    • Moderated Conferences - This feature enables the moderator to moderate private messages that are sent to conferences
    • Alerts - This feature enables you to notify users of time-sensitive information, either in individual messages or as broadcasts to multiple users. You can also specify routing of alerts received when offline
  • Redirect Server - This feature enables you to balance the load between different servers in a server pool
  • Communications Channel in Portal Server - This is the channel that is used to launch Instant Messaging in Portal Server
  • Portal Server Archiving - This feature enables you to archive chat content in the portal server

Requirements for Instant Messaging 8 Update 1

See Requirements for Communications Suite 6 Update 2 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 Compatibility Issues

The following table lists the compatibilities issues in Instant Messaging 8 Update 1.

Table 5-1 Instant Messaging 8 Update 1 Compatibility Issues

Incompatibility Impact Comments
Versions of Instant Messenger prior to Sun Java System Instant Messaging 7 2006Q1 do not support XMPP redirection.   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.  
Sun Java System Instant Messaging 8 is incompatible with Sun Java System Access Manager version 7 2005Q4. The supported version of Sun Java System Access Manager is version 7.1.  
Sun Java System Instant Messaging 8 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 Update 1.  
Due to a protocol change the Instant Messaging server 8 Update 1 cannot communicate with a server of a version older than 7.3 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 7 2005Q4 and 2006Q1 are incompatible with the shared components that ship with Sun Java System Instant Messaging 8. 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 8 Update 1.
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.  
Sun Java System Instant Messaging 6 2004Q2 server is incompatible with the default behavior of the latest version of the SDK. To use the Instant Messaging 6 2004Q2 server with the current Instant Messaging SDK, set the property of the collaboration session factory object to use the legacy protocol implementation.  
Instant Messaging 8 Multiplexor might not work correctly with the older versions of the server.   Use Instant Messaging 8 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 8 server might not work correctly with the previous versions of the Instant Messaging SDK.   Use the 8 version of the server and the SDK.
URL to the default codebase URL for Sun Java System Instant Messaging 8. The default URL for the codebase is http://server:port/im.  
Default port numbers for Sun Java System Instant Messaging 8 The default server port number is 45222 and the default Multiplexor port number is 5222.  
Instant Messaging 8 server might not work correctly with Multiplexor version 7.3.   Upgrade the Multiplexor to 8 Update 1.
Although the 7.3 client is supported on 8 server, all functionalities might not work.   Upgrade the client to version 8.

Problems Fixed in Instant Messaging 8 Update 1

This section contains a list of problems fixed in the Instant Messaging 8 Update 1 release.

6807458

When TLS is enabled on the server, there could be a deadlock with the server getting hanged.

6807465

Messages added to a group chat are blocked in the server.

6807482

Conferences have multiplying effect on data thus enabling dishbackup more often.

6807494

When several people try to join conferences and post messages to it, the server gets blocked.

6808075

When TLS is enabled, steady inflow of data on a session can exhaust the threads in the server.

6770917

Ability to obtain presence info for the buddies (in the roster list) in various locations from Convergence client.

6777467

Offline messages are not sent as SMS, if the user has not logged in to IM client even once.

6808094

When the server is restarted, old conference history shows up but not the new history.

6808103

Ability to change the logging configuration of a server on the fly.

6809830

Cannot delete a contact from the roster if the contact has been deleted from LDAP.

6812306

Time stamp corruption occurs in Directory Server for a conference history.

6818164

Missing Java classes result in broken functionality.

6818707

Calendar reminders are sent in iCal format even when content type is set to text/plain.

6818819

When you upgrade from IM 7.3 or 8.0 to 8.0 Update 1, conference history is not displayed in SunIM client.

6821743

Server hangs in a server pool setup when conferences are used.

6782713

A race condition causes an endless loop in server.

6792217

Roster responses for newly added users are not always updated with the extra attributes.

6795228

When user enters service runtime options, the configurator fails with permission denied error.

6795305

When configuring IM server components on Linux, the configurator goes into a loop.

6802803

Upgrade from IM 7.3 to IM 8 Update 1 fails if password contains the "!" character.

6805125

Corrupted conference history causes exceptions.

6805235

Cannot specify multiple options for iim_server.jvm.options parameter.

6807445

If joining a conference results in session termination, the client endlessly reconnects and joins the conference.

6423351

Duplicate entries of properties exist in the property file.

6628502

Usage of imadmin migratepropstore is documented incorrectly in the CLI Help.

6689323

When you run the redeploy command after an upgrade, incorrect status message is displayed.

6701028

The Instant Messaging watchdog probe causes a Java stack trace when TLS is enabled.

6726237

Default value of iim_wd.period configuration parameter is very high to failover.

6728796

All ports accept connections by default even after the user has mandated it to use a particular protocol.

6739701

MSN and AOL gateways cannot connect to the server when TLS is enabled on the server.

6749724

When using Yahoo gateway, the existing contacts are not displayed in the Sun IM buddy list.

6749726

When using Yahoo gateway, the chat functionality is not working properly with Sun-IM Client.

6762310

The localized Index file in the Online Help is invalid.

Known Issues and Limitations in Instant Messaging 8 Update 1

This section contains a list of known issues at the time of release of Instant Messaging 8 Update 1.

Instant Messaging Agent Issues

6821946

Yahoo gateway can not connect to the server when TLS is mandated on the server.

6724472

Offline SMS messages are sent to user even after you block messages from a particular user.

6745138

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

6646700

Sending an alert from the Instant Messaging client to a user in AIM, MSN, or Yahoo client results in an alert being delivered as a chat conversation. The delivery status of the alert is also not updated correctly.

6646702

The subject of the alert sent from the Instant Messaging client to an AIM, MSN, or Yahoo client is not displayed.

6646704

The Offline Alert functionality does not work when alerts are sent from the Sun Java System Instant Messaging client to users in the MSN, Yahoo, and AIM clients.

6646712

In the Instant Messenger client, the MSN, AIM, or Yahoo transport credentials that a user provides to log in are not displayed.

Instant Messaging Installation, Upgrade, and Uninstallation Issues

6824676

When you upgrade from Instant Messaging 7.2 or 7.3 to Instant Messaging 8 Update 1, Calendar agent parameters (jmq) are incorrect.

6818830

When you upgrade from Instant Messaging version 8 to Instant Messaging 8 Update 1, redeployment of client resources fails.
Workaround:
Before you redeploy the client resources, edit the imwebapp.properties file, and set the im_WAR_GENERATE_COMMAND parameter to a valid Java path.

6758197

If the server is reconfigured, the iim.conf file does not retain the previous configuration details.

6768193

The propstore_migraton.conf file does not exist when Instant Messaging is upgraded from version 7.2 to 8 Update 1.

6643628

The Configurator tool does not connect to the Sun Java System Directory Server SSL port number 636.
Workaround:
Manually add the SSL port number as 636 in the iim.conf file.

6672605

The Instant Messaging server takes the property store migration source from the iim.conf file even though the migration options are specified by using the command line.

6677138

The Configurator tool should be able to handle a scenario where Instant Messaging server and web server run as different users.
The Instant Messaging server defaults to running as inetuser and inetgroup. Web server defaults to running as webserverd. In this case, all the Instant Messaging configuration files that are generated by Configurator are readable only by inetuser. The Configurator tool must change the ownership of these files to the web server runtime user, so that they can be read by web applications.

6689151

The init-config utility should provide an option to perform Calendar Agent integration with JMQ, ENS, and None.
The Instant Messaging init-config utility provides the option to configure the Calendar Agent configuration settings. The Instant Messaging configure utility currently assumes that the integration with the Calendar Server uses the ENS (Event Notification Service) mechanism. As JMQ is also an option for notifications, it would be advantageous to provide the ability to configure JMQ during initial configuration.

Hence, the three options JMQ (preferred), ENS (legacy), and None with the defaults values for each mechanism should be provided during configuration.
Workaround:
Do not integrate the calendar agent during initial configuration. After the initial configuration process, manually configure the preferred mechanism, that is, ENS, JMQ, or None in the iim.conf file.

6709951

Deploying client resources fails if there are multiple http listeners.

6498428

The Configurator tool fails if you specify a user ID and a group ID other than root.
If you use any user ID or group 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, manually set permissions for imuser and imgroup. To do this, type the following command:

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 that you use to install Instant Messaging.

6444431

The Configurator tool accepts values for Use Assess Manager for Policy and Use Assess Manager for SSO options and succeeds in configuration even when Sun Java System Access Manager is not installed.

Instant Messenger Issues

This section contains a list of known issues at the time of release of Instant Messenger 8 Update 1.

Instant Messenger General and Usability Issues

6739173

If the Alert if user status changes option is set for a MSN user, three alert messages are sent to other users when the status of the MSN user changes.

6815865

Status is not getting updated for Yahoo gateway users in the IM client.

6824201

If nick is not set, conference history displays messages from different domains as messages from local domain in a server-to-server setup in the IM client.

6831470

In MSN and Yahoo clients, chat functionality does not work properly with httpbind.

6770412

Status of the AIM users is not updated in the Sun Java System Instant Messaging client.

6766505

Conference history is not displayed in the Instant Messaging client if a user joins the conference before the owner of the conference.

6824299

Conference history does not display all the messages but only those messages from users who have currently joined the conference. This issue is with Sun IM Client only.

6751392

Transport name is not consistent.

6750943

MSN, AIM, and Yahoo Transport users are not shown in roster on a Red Hat Linux platform.

6750250

Entering a conference room with a multibyte nickname sometimes fails.

6649550

A Status Unknown message is displayed when offline users re-login in a server-to-server setup.

6626931

Users with self-JID (Jabber ID) encounter authorization issues in the Instant Messaging client.

6626943

Subscribe news channel displays an org.jabberstudio.jso.JIDFormatException error in a Schema2 hosted domain setup.

6486498

If you send an alert containing an image of a URL and a text message, the recipient receives only the text message.

6576575

The Authorize Contact message is not sent when a user is added from the Alert and Chat windows.

6727849

In a server-to-server installation, the File->Import Contacts option does not work.

Instant Messaging Server Issues

6777818

The following message is displayed when you register a duplicate user to blocked domains:

User already registered

6821779

File transfer does not work in a public conference if the user rejoins the conference.

6805154

IM client settings window is not displayed in a profile with non-default privacy setting and jid.encoding.compat value set to 'false'.

6794173

Can not create conferences with restricted characters.

6744631

Subscription does not work in a server pool when identity is enabled.

6817064

Re-subscription does not happen as Yahoo users are not getting deleted from the gateway.
Workaround: Delete the users from the Yahoo gateway and then re-subscribe.

6742973

Only users who are recently added to the IM client are synchronized with the Sun Java System Instant Messaging client. Users who are removed from the AIM client are not synchronized.
Workaround:
If a user is deleted in the AIM client, manually delete the user in the Sun Java System Instant Messaging client.

6742857

SMS messages are not delivered if the SMS gateway is enabled on a single peer in a server pool.
Workaround:
Enable the SMS gateway on all peers. For more details about the SMS gateway, see SMS Gateway for Instant Messaging.

6740782

Private conference communication does not work between users who have the same user names but are on different domains.
Workaround:
Users should log in with a different resource and start a chat session.

6739134

Restarting the Instant Messaging services removes the MSN Transport from the Instant Messaging client compelling the user to register again.

6646034

The imadmin assign_services command fails if Instant Messaging interacts with the LDAP server in the SSL mode.
Workaround:
Ensure that the Instant Messaging interacts with the LDAP server in the non-SSL mode. Invoke the assign-services command and change the interaction back to the SSL mode.

6628423

In a server-to-server setup, users that log in through third-party messaging clients are unable to search conferences.

6632080

In a server-to-server setup, users are unable to join the conference rooms on a server that has the TLS (Transport Layer Security) enabled.

6620273

Data migration fails for user IDs that contain uppercase characters.

6724468

Propstore migration does not migrate the vcard-temp.xml file.

6752716

Null pointer exception is seen in the xmppd.log file when a MSN user is deleted from the Sun Java System Instant Messaging roster.

6599164

The Configurator tool should create the im.war and httpbind.war files if the web container used for Instant Messaging is not a supported web container.

Instant Messaging Voice Issues

6678951

Voice chat fails if users do a side chat in a conference.

6768190

If VoIP is enabled, the participant list option in the View menu of the Chat window does not work.

6730494

Voice call will not work if third user joins a voice conference of two users.

6727794

Inconsistent issues with voice chat.

6714770

If you use the Instant Messaging VoIP client to communicate with a remote peer that blocks the UDP (User Datagram Protocol) traffic due to a firewall, the VoIP connection is not established.

6689918

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

6665839

Voice chat status displays as Connected even after the server has shut down.

6723424

User with admin privileges should be able to specify a default port range in the jnlp file.

6705989

In one-to-one conversation, the Voice Chat icon should be enabled by default.

Instant Messaging Administration Issues

6763462

The imadmin assign_services and migratepropstore commands do not work if the primary LDAP server is down.
Workaround:
Restart the primary LDAP server and rerun the imadmin assign_services and migratepropstore commands.

6719455

The ./iwadmin redeploy all command does not redeploy IMPS.
Workaround:
To redeploy IMPS, type the following command:
/opt/SUNWiim/sbin/iwadmin -v redeploy imps

6740272

ACL file behavior is different for identity and file-based policy management.
If the policy is identity, the Manage Conferences and Manage News Channel options are not enabled by default. However, these options are enables by default in file-based ACLs (Access Control List).

Instant Messaging Archive Issues

6738078

The Disabling Archive option does not work during a chat session.

Instant Messaging Interoperability Issues

6621474

Cannot kick the participants from a conference room.

Instant Messaging Performance Issues

6815949

Embryonic session closures occur in a server pool setup and single server.
Workaround: Use either of the following options:

  • If the deployment supports, run the multiplexer on the same host as the IM server
  • Use large number of multiplexers that would help in reducing the number embryonic session closures

6812926

When there is high load in a server pool setup, Null Pointer Exceptions are displayed.

6837866

Embryonic session closures are seen at a high load in the following circumstances:

  • When the following load is generated every ten seconds, and when the number of concurrent users is 60,000 or more:
    • 50 users log into server
    • 50 users logout
    • 1450 presence updates
    • 350 messages sent to offline destinations
    • 2400 messages sent to online destinations
    • 850 messages sent to random destinations
    • 50 roster additions
    • 50 roster rename
    • 50 roster removal
  • When there are more than ten chat messages per second across conference rooms
  • When there are too many messages sent to fewer conference rooms

6812313

Messages that are added to group chats or conferences are not deleted upon refreshing the setup.

6812928

Error messages received under load in the following format are only warn messages.

[RWLock] Releasing lock which is not held!


6837307

Need to configure a separate thread pool for multiplexor to reduce the disk backup of files.
To reduce the number of files written to disk under high load, the following parameters must be added in the iim.conf file:

iim_server.port.45222.worker-out="muxout"
iim_server.port.45222.worker-in="muxin"
iim_server.threadpool="muxout,muxin"
iim_server.threadpool.muxout.maxthreads=5
iim_server.threadpool.muxin.maxthreads=5

where
Maxthreads value is the number of multiplexers expected to connect to the server in a particular deployment.

Other Known Issues

6742967

The status of AIM (AOL Instant Messaging) user is always shown as Offline in the Sun Java System Instant Messaging client.

6740263

In IMPS, response to a sent message is displayed as 'successfully completed' even when there is an error in the xmpp side.

6746794

In IMPS, a user in the virtual domain is not able to send messages to the user in the primary domain.

6738075

The Instant Messaging client does not display nicknames that have special characters.

6726738

In IMPS, an incorrect message is displayed when a user joins a conference with the duplicate nickname.

6673225

The imadmin start and imadmin stop commands do not invoke the SMF (Service Management Facility) command to start and stop the server or Multiplexor.
If you require the SMF, disable the SMF by typing the following command:

svccfg delete application/sunim

6671297

SMF does not support multiple Instant Messaging instances.

6641777

Selecting the Stop Moderating option in a conference room does not remove the moderate conference pane.

6635262

Configure parameters are not updated properly when httpbind option is enabled in the Configurator tool.

6726335

In IMPS, a null pointer exception is displayed when a user with a nickname that has a special character leaves a group.

6726347

In IMPS, a mobile phone user is listed twice in the member list when the user leaves and joins the group with different nicknames.

Redistributable Files for Instant Messaging

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

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

Labels

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

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