This section lists the feature enhancements released in Calendar Server 8.0 patch sets.

• MySQL Server 8.4 Support
• Calendar Server is Now Certified on Oracle WebLogic Server (Patch Set 4)
• WCAP Support for Storing External Attachments (Patch Set 2)
• TLS1.3 Supported in Calendar Server

Calendar Server 8.0.0.8.20250424 supports MySQL Server 8.4.

From patch set 8.0.0.4.0 onwards, Oracle Communications Calendar Server is supported and certified only on Oracle WebLogic Server.

A new WCAP parameter is introduced for storing external attachments. See WCAP Developer's Guide for for more information.

Calendar Server supports TLSv1.3 in addition to TLSv1.2 from 8.0.0.8.0.

Calendar Server 8.0 uses a managed bean (MBean) created in Oracle GlassFish Server to collect monitoring data. By using the GlassFish Server’s Java Management Extension (JMX) interface, you can then access this data by using a JMX-compliant client. The JMX client connects to the platform’s MBeanServer by using a JMX Service URL. Once a client connects to the MBeanServer, it uses the Calendar Server monitoring MBean object name to access the MBean’s attributes. In addition to using monitoring data gathered by the Calendar Server monitoring MBean, you can also check the health of your hosts by using the Calendar Server supplied responsetime script. This script sends a set of basic requests to Calendar Server and measures the amount of time needed to process those requests. When the responsetime script shows a spike or a large increase in response time, this indicates a potential issue with Calendar Server that needs to be addressed. For more information, see the chapter on monitoring in Calendar Server System Administrator’s Guide.

The davadmin repair command now includes domain migration support.

This section lists issues fixed in Oracle Communications Calendar Server 8.0.0.8.0.

This section lists the known problems in Calendar Server 8.0 patch sets.

Patch Set 8.0.0.4.0 onwards

Bug number: 32187735

Configuration of Calendar Server fails only on WebLogic Server 12.2.1.4 but works with WebLogic Server 12.2.1.3.

Workaround: Before configuring Calendar Server on WebLogic Server 12.2.1.4, perform the following steps:

1. Copy the required mysql-connector-java-5.1.x connector jar version to the lib directory of your WebLogic domain. For example, if you want to deploy Calendar Server on domain 1, copy the jar to: WebLogic_home/user_projects/domains/domain1/lib/

   Note:

   The mysql-connector-java-5.1.35-bin.jar file is already available in the installation location of Calendar Server: /opt/sun/comms/davserver/lib/jars. Copy this jar to the lib directory of WebLogic domain.
2. Restart WebLogic Server.

Patch set 8.0.0.3.0 onwards

Bug number: 30031880

This impacts only the GlassFish Server 3.x deployments. These deployments are supported only with Java 7.

Workaround: Before running the davadmin command, set your terminal's JAVA_ HOME and PATH environment variables to JDK 1.8.0_update

Patch set 8.0.0.4.0 onwards

Bug number: 29649135

WebLogic Server deployments do not support the Browse-servlet option of Calendar Server.

Workaround: Use the davadmin CLI Admin tool for all administrative activities.

Patch set: All 8.0 patch sets

Bug number: 30547042

This is applicable only for GlassFish Server 3.x deployments for all releases since 8.0 and patch sets.

Workaround: Use GlassFish Server version 3.1.2.18.

Patch Set 8.0.0.4.0 onwards

Bug number: 30744543

Till 8.0.0.4.0, Calendar Server product version included a short version. For example, Oracle Communications Calendar Server version: 8.0.0.2.0 (8-2.00; built 2018-01-09T23:53:06-0800).

From Calendar server 8.0.0.4.0 release onwards, the product version string is optimized and the short pattern string is removed to support Weblogic as the deployment container. For example, Oracle Communications Calendar Server version: 8.0.0.4.0 (built 2019-11-15T05:47:08-0800).

Patch Set 8.0.0.6.0 onwards

Bug Number: 33445205

Initial configuration for Calendar Server 8.0.0.6.0 is failing when MySQL 5.7.26 is used with JDK versions higher than JDK 8.

Workaround: Add TLS version 1.2 to the MySQL configuration file /etc/my.cnf.

[mysqld]
tls_version=TLSv1.2

Patch Set 8.0.0.6.0 onwards

Bug Number: 33322960

Initial configuration for Calendar Server 8.0.0.6.0 is failing when MySQL is used in setups with PDT timezone.

Workaround: Add default-time-zone entry in the MySQL configuration file /etc/my.cnf.

Patch Set 8.0.0.8.0 onwards

Bug Number: 37854240

Migration from Calendar Server 6 to Calendar Server 8 is not supported from Calendar Server 8.0.0.8.0 onwards.

This section lists the known problems in Calendar Server 8.0.

SR number: N/A

Bug number: 24818711

After running the davadmin account repair -D command, due to a user being moved from one domain to another, VALARM still shows the user’s old email address.

SR number: N/A

Bug number: 21487603

If the host that the responsetime script queries is experiencing high load, the script might fail and display the message '207: Response Time request failed.

SR number: N/A

Bug number: 20427454

Calendar Server cannot create events for, nor can users invite, users whose email address contains double quotation marks, such as "caluser1"@example.com.'

SR number: N/A

Bug number: 20606487

The davadmin command accepts incorrect values for the following configuration parameters:

• log.dav.commands.loglevel
• log.dav.errors.loglevel
• log.dav.scan.loglevel
• log.dav.scheduling.loglevel
• log.dav.telemetry.loglevel
• notification.dav.smtpport

If you had inadvertently set an incorrect value on any of these parameters, and then upgrade to the current version of Calendar Server, the server might not start.

Workaround:

To work around this issue:

1. Stop Calendar Server:

   GlassFish_home/bin/asadmin stop-domain domain

2. Manually edit the davserver.properties file to change any incorrect value of the affected configuration parameters.

   Valid log level values are OFF, SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST, or ALL.

3. Start Calendar Server:

SR number: N/A

Bug number: N/A

If you create a calendar by using Convergence, and then try to delete the calendar on a device that is on iOS 8, an iOS 8 device, the calendar is not removed from the Calendar Server database. If you create and delete the calendar on iOS 8, it is removed from the Calendar Server database.

This problem occurs because Convergence creates calendars with both VEVENT and VTODO as supported components. The VTODO component instructs the iOS Calendar app that other VTODO applications can use the calendar, and so the iOS Calendar app does not delete it.

SR number: N/A

Bug number: 20050746

Calendar Server can process a calendar event received in an iCalendar Message-Based Interoperability Protocol (iMIP) message by using the iSchedule protocol. This capability enables "internal" users to automatically process calendar invitations from "external" users. Currently, however, Calendar Server cannot process a calendar invitation email from Yahoo, and the event does not get added to the user's calendar. The problem is that the Yahoo calendar invitation is improperly formatted. As a result, Calendar Server rejects the event.

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.