Calendar No Longer Works in Convergence and Other CalDAV Clients After Applying Patch and Choosing a Different Directory (Doc ID 1371380.1)

Last updated on APRIL 01, 2016

Applies to:

Oracle Communications Calendar Server - Version 7.0 and later
Information in this document applies to any platform.

Symptoms

Observed on Calendar 7 with patch 142785-03.

After applying the patch 142785-04 (Update 2), within Convergence, the Calendar does not work anymore.  Users get an error such as:  Login to Calendar Service failed.

Access to the calendar also fails when using other CalDAV clients such as Lightning.

Errors such as the following may be observed in the logs:

Convergence iwc.log displays:

PROXY_CAL: INFO from com.sun.comms.client.web.services.sun.SunCalDAVServiceProxyImpl Thread httpSSLWorkerThread-443-5 ipaddress=##.##.##.## sessionid=0f48c0411401c2c6edf86377dae5 at 12:51:03, 938- Performing Sun CalDAV Authentication
PROXY_CAL: ERROR from com.sun.comms.client.web.services.sun.SunCalDAVServiceProxyImpl Thread httpSSLWorkerThread-443-5 ipaddress=##.##.##.## sessionid=0f48c0411401c2c6edf86377dae5 at 12:51:03, 957- Failed to authenticate the user jdoer to CalDAV service. HTTP Response code: 404
PROXY_CAL: ERROR from com.sun.comms.client.web.services.BaseProxyServlet Thread httpSSLWorkerThread-443-5 ipaddress=##.##.##.## sessionid=0f48c0411401c2c6edf86377dae5 at 12:51:03, 961- Error processing the request by the proxy servlet: Error while executing the service request : Login to Calendar Service failed.


And the Glassfish server.log displays:

[#|2011-10-20T11:20:15.696+0200|SEVERE|sun-appserver2.1.1|javax.enterprise.system.container.web|_ThreadID=10;_ThreadName=main;_RequestID=5a539afd-81a1-4341-9651-12908ef360fa;|WebModule[/davserver]PWC1396: Servlet /davserver threw load() exception
com.sun.comms.davserver.services.DavException: can not load config
      at com.sun.comms.davserver.core.DavServer.readConfig(DavServer.java:518)
      at com.sun.comms.davserver.core.DavServer.<init>(DavServer.java:298)
      at com.sun.comms.davserver.core.DavServer.getInstance(DavServer.java:665)
      at com.sun.comms.davserver.core.DavServiceFactoryImpl.initialize(DavServiceFactoryImpl.java:70)
      at com.sun.comms.davserver.services.DavServiceFactory.getInstance(DavServiceFactory.java:78)
      at com.sun.comms.davserver.services.DavServiceFactory.getInstance(DavServiceFactory.java:53)
      at com.sun.comms.davserver.protocols.DavServerServlet.init(DavServerServlet.java:102)
      at com.sun.comms.davserver.protocols.RESTServlet.init(RESTServlet.java:66)
....etc

[#|2011-10-20T11:20:15.992+0200|SEVERE|sun-appserver2.1.1|javax.enterprise.system.container.web|_ThreadID=10;_ThreadName=main;_RequestID=5a539afd-81a1-4341-9651-12908ef360fa;|WEB0207: Error starting web context StandardEngine[com.sun.appserv].StandardHost[server].StandardContext[/davserver] on virtual server server
LifecycleException: com.sun.comms.davserver.services.DavException: can not load config
      at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4979)
      at org.apache.catalina.core.StandardContext.start(StandardContext.java:5376)
      at com.sun.enterprise.web.WebModule.start(WebModule.java:345)
      at com.sun.enterprise.web.LifecycleStarter.doRun(LifecycleStarter.java:58)
      at com.sun.appserv.management.util.misc.RunnableBase.runSync(RunnableBase.java:304)
      at com.sun.appserv.management.util.misc.RunnableBase._submit(RunnableBase.java:176)
      at com.sun.appserv.management.util.misc.RunnableBase.submit(RunnableBase.java:192)
      at com.sun.enterprise.web.VirtualServer.startChildren(VirtualServer.java:1768)
      at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1244)
      at org.apache.catalina.core.StandardHost.start(StandardHost.java:971)
      at com.sun.enterprise.web.LifecycleStarter.doRun(LifecycleStarter.java:58)
      at com.sun.appserv.management.util.misc.RunnableBase.runSync(RunnableBase.java:304)
      at com.sun.appserv.management.util.misc.RunnableBase._submit(RunnableBase.java:176)
      at com.sun.appserv.management.util.misc.RunnableBase.submit(RunnableBase.java:192)
      at com.sun.enterprise.web.EmbeddedWebContainer$WebEngine.startChildren(EmbeddedWebContainer.java:497)
      at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1244)
      at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:549)
      at org.apache.catalina.startup.Embedded.start(Embedded.java:945)
      at com.sun.enterprise.web.WebContainer.start(WebContainer.java:873)
      at com.sun.enterprise.web.PEWebContainer.startInstance(PEWebContainer.java:799)
      at com.sun.enterprise.web.PEWebContainerLifecycle.onStartup(PEWebContainerLifecycle.java:89)
      at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:449)
      at com.sun.enterprise.server.ondemand.OnDemandServer.onStartup(OnDemandServer.java:134)
      at com.sun.enterprise.server.PEMain.run(PEMain.java:398)
      at com.sun.enterprise.server.PEMain.main(PEMain.java:325)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:597)
      at com.sun.enterprise.server.PELaunch.main(PELaunch.java:415)
|#]

Changes

After installing the patch and then running init-config, the directory for the data and configuration files had to be specified and a new directory was chosen instead of the existing directory.  This is the log:

# ./init-config
/usr/java/bin/java -Djava.library.path=/opt/sun/comms/davserver/lib -classpath /
opt/sun/comms/davserver/lib/jars/mysql-connector-java-5.1.6-bin.jar:/opt/sun/com
ms/davserver/lib/jars/ojdbc6.jar:/opt/sun/comms/davserver/lib:/usr/java/lib/clas
ses.zip config-davserver -saveState /opt/sun/comms/davserver/install/saveState20
111014151615
Finished Loading Default Properties...
...
Welcome to the Oracle Communications Calendar Server Configuration Program.

<Press ENTER to Continue>

Please specify the directory in which the configuration and data files should
be installed. It is recommended that you configuration director path Oracle
Communications Calendar Server is same as suggested by this configurator
program.

Specify the directory in which the configuration and data files should be
installed [/var/opt/sun/comms/davserver] {"<" goes back, "!" exits}:



The directory /var/opt/sun/comms/davserver is not empty, any previous
configuration data will be overwritten.

1. Choose New
2. Accept Anyway

Enter the number corresponding to your choice [1] {"<" goes back, "!"
exits}

Please specify the directory in which the configuration and data files should
be installed. It is recommended that you configuration director path Oracle
Communications Calendar Server is same as suggested by this configurator
program.

Specify the directory in which the configuration and data files should be
installed [/var/opt/sun/comms/davserver] {"<" goes back, "!" exits}: /var/opt
/sun/comms/davserver_cs7u2

The directory "/var/opt/sun/comms/davserver_cs7u2" does not exist.



Do you want to create it now or choose another directory?

1. Create Directory
2. Choose New

Enter the number corresponding to your choice [1] {"<" goes back, "!"
exits}

Please wait for the components to be loaded...


Loading components...


Select the components to be configured.


[X] 1 Calendar Server 0 bytes
....

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms