ArrayIndexOutOfBoundsException when trying to create Calendar
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
You can't create a Calendar, and following appears in atlassian-confluence.log:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
2014-10-13 15:17:59,497 ERROR [http-bio-6060-exec-5] [extra.calendar3.rest.CalendarResource] getResponseError Unable to save/update sub-calendar test
-- referer: <URL>/calendar/mycalendar.action | url: /rest/calendar-services/1.0/calendar/subcalendars.json | userName: user
com.atlassian.activeobjects.internal.ActiveObjectsSqlException: There was a SQL exception thrown by the Active Objects library:
Database:
- name:Oracle
- version:Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
- minor version:1
- major version:11
Driver:
- name:Oracle JDBC driver
- version:11.1.0.7.0-Production
java.sql.SQLException: An SQLException was provoked by the following failure: java.lang.ArrayIndexOutOfBoundsException
at com.atlassian.activeobjects.internal.EntityManagedActiveObjects.create(EntityManagedActiveObjects.java:111)
at com.atlassian.activeobjects.osgi.DelegatingActiveObjects.create(DelegatingActiveObjects.java:129)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
Cause
This is happening when you are using Oracle 11g database. In particular this is because of the 11.1 JDBC driver, and you can read more about it here:
Resolution
According to
:
For Oracle 11.2g you should use the 11.2.0.1.0 driver (Java 6 ojdbc6.jar).
For Oracle 11.1g use the 10.2.0.4 driver (Java 6 ojdbc6.jar) to avoid this issue with 11.1 driver.
Was this helpful?