Comms Express problem after installing patch
I had the mail and address book components of comms express working but was hitting the bug with the calendar not being able to show dates after 2006. So I installed patch 122793-12 which is supposed to fix this issue.
After installing the patch I got the following error on restarting the application server (which is the web container):
[#|2007-06-13T18:44:00.848+0100|SEVERE|sun-appserver-ee8.1_02|org.apache.catali n
a.session.ManagerBase|_ThreadID=10;|IOException while loading persisted sessions
: java.io.WriteAbortedException: writing aborted; java.io.NotSerializableExcepti
on: com.sun.uwc.common.util.UWCPreferences
java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException
: com.sun.uwc.common.util.UWCPreferences
This occurs when the app svr tries to load the comms express web app.
I went through the uwcconfig.properties and uwcauth.properties carefully, comparing the old version and the version modified by the patch. The only change of note is that the patch added the following to uwcconfig.properties:
webmail.securedproxyauth=false
webmail.proxyadmin=ZZZ
webmail.proxyadminpass=ZZZ
I found that if I commented out these lines the application server started up correctly. However, on logging into comms express I found the Mail tab had dissapeared and clicking the Calendar tab produced "The selected calendar(s) was either deleted or does not exist or you do not have permissions to view it. Select another calendar(s).".
So any ideas as to (a) what these new webmail.proxy settings are all about and/or (b) any other ideas as to why this patch has messed up Comms Express?
The version of our Messenging Server is v6.2 Rev. 3.04 Build 2005.196.0138 and we are using Identity SSO.
Thanks.
[1833 byte] By [
bontempi.a] at [2007-11-27 7:35:19]
# 2
Hi,
>> So any ideas as to (a) what these new webmail.proxy settings are all about and/or (b) any other ideas as to why this patch has messed up Comms Express?
Please note that by installing patch 122793-12, you have actually upgraded to a new release of the product which introduced a number of underlying structural changes (one of these being that comms-express now communicates differently for webmail access).
Prior to doing this upgrade there are a large number of pre-requisite and also post-install steps that need to be carried out as per the upgrade guide:
http://docs.sun.com/app/docs/doc/819-7561
Other 6.3 (comm-suite-5) upgrade patches are available at:
http://www.sun.com/bigadmin/hubs/comms/downloads/updates.jsp
Regards,
Shane.
# 3
Shane, thanks for alerting me to the fact that I had inadvertantly upgraded from 6.2 to 6.3. I decided to backout this patch and to install one of the obsoleted patches that fixes the calendar server date problem without upgrading to 6.3.
So I backed out the patch using backout-newconfig and restarted the application server.
The problem is that now when I try and login to communications express I get the following errors in the log:
SEVERE: Could not load the file: <uwcbasedir>/WEB-INF/domain/<Our.Domain.Name>/uwcdomainconfig.prope rties (No such file or directory)
Jun 27, 2007 3:22:02 PM com.sun.uwc.common.util.UWCDomainCache loadUWCDomainProp
erties
WARNING: Unable to load domain configuration file for domain<Our.Domain.Name>
uwcdomainconfig.properties has also just existed in the root of <uwcbasedir>/WEB-INF/domain and this directory has never had our domain name as a subdirectory. So why would installing/uninstalling this patch suddently cause Comm Express to start looking for things in different directories?
I have tried manually creating this directory and putting a copy of uwcdomainconfig.properties there but that caused "Invalid Session ID" errors.
I have checked uwcauth.properties and uwcconfig.properties and they are back to being exactly as they were before the patch was installed.
Thanks.
# 7
After uninstalling the patch it seems that Comms Express was expecting a domain specific configuration. I'm not sure why, but anyway, I created a directory for the domain under <uwcdeploydir>/WEB-INF/domain and copied the
uwcdomainconfig.properties and locale directories into it.
Then when I restart the application server there are no errors in either the app server log or uwc log. But when I browse to the Comms Express login page I get the following errors in the log:
FINE: IdentitySSOAuthFilter: Resolved domain? <My.Domain.Name>
Jun 28, 2007 11:35:27 AM com.sun.uwc.common.auth.IdentitySSOAuthFilter doFilter
FINE: 1. session is not present.. get token manager..
Jun 28, 2007 11:35:27 AM com.sun.uwc.common.auth.IdentitySSOAuthFilter doFilter
WARNING: SSOException..Invalid session ID.
Jun 28, 2007 11:35:27 AM com.sun.uwc.common.auth.LDAPAuthFilter doFilter
FINE: Check If Identity is enabled
Jun 28, 2007 11:35:27 AM com.sun.uwc.common.auth.LDAPAuthFilter doFilter
FINE: Identity is enabled....return
Jun 28, 2007 11:35:27 AM com.sun.uwc.common.util.UWCDomainCache loadUWCTheme
WARNING: Theme for localeenand<My.Domain.Name> is not configured
Jun 28, 2007 11:35:27 AM com.sun.uwc.common.util.UWCDomainCache loadUWCTheme
Nothing has changed other than the fact that I installed and uninstalled the patch. I have checked the uwcauth.properties and uwcconfig.properties and they are identical to the original versions (prior to installing the patch).
I have tried creating a locale and domain specific theme but that didn't help and I think the errors about the theme just result from the original "Invalid Session ID" error.
Thanks.
