Sun Java System Communications Services 2005Q4 Release Notes

Problems Fixed in This Release

Table 3–5 describes problems fixed in this Instant Messaging 7 2005Q4 release.

Table 3–5 Fixed Issues in Instant Messaging 7 2005Q4

Issue Number 



When an end user deletes an active privacy profile, the server still continues to apply the deleted active privacy profile even though Instant Messenger shows the privacy profile to be deleted. 

Workaround: When an end user deletes an active privacy profile Instant Messenger now automatically activates the “Visible to All” privacy profile. End users need to make a different privacy list active and then reactivate the “Visible to all” profile. 


Previously, for locales other than English, for example Japanese, you couldn't change access rights for a conference room to READ. Instead, when you saved, the access right was changed to NONE. This no longer occurs. 


When you add a user to your contact list, the Conference tab no longer gains the focus in the Instant Messenger client’s main window. 

6198525, 6207036 

In Conference and News Channels, you need to set default access for users before granting special access. 


Previously, if you were using the French localized version of the resource files, you needed to add an escape character to the apostrophes in the resource files. You no longer need to do this. 


While running the configure utility in Japanese, some of the screen element titles were truncated.


Email alerts that contain multibyte characters are now readable. 


Changes made to a user entry in the LDAP directory are not reflected in Instant Messaging until the cache is revalidated. By default this happens every 10 minutes or every time the Instant Messaging server is started. 

Workaround: Restart the Instant Messaging server or set the cache validity interval to a more appropriate number. To change this interval, add the iim.policy.cache.validity parameter and its desired value to iim.conf.