Description
Xporter is facing an error in Mysql Databases with composite indexes.
When the user migrates from 6.9.2 to 6.9.3, Xporter stops working and the user is not able to load data from the database.
StackTrace:
13.197,192.168.66.153 /servicedesk/customer/portal/4/user/login [c.x.jiraxporter.condition.JsdQueuesAccessCondition] An error occured while Xporter validate the option Xporter Jsd queue integration com.atlassian.activeobjects.internal.ActiveObjectsInitException: bundle [com.xpandit.plugins.jiraxporter] at com.atlassian.activeobjects.osgi.TenantAwareActiveObjects$1$1$1.call(TenantAwareActiveObjects.java:95) at com.atlassian.activeobjects.osgi.TenantAwareActiveObjects$1$1$1.call(TenantAwareActiveObjects.java:86) at com.atlassian.sal.core.executor.ThreadLocalDelegateCallable.call(ThreadLocalDelegateCallable.java:38) at java.base/java.util.concurrent.FutureTask.run(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.base/java.lang.Thread.run(Unknown Source) Caused by: com.atlassian.activeobjects.internal.ActiveObjectsSqlException: There was a SQL exception thrown by the Active Objects library: Database: - name:MySQL - version:5.7.33-log - minor version:7 - major version:5 - name:MySQL Connector Java - version:mysql-connector-java-5.1.48 ( Revision: 29734982609c32d3ab7e5cac2e6acee69ff6b4aa ) com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was too long; max key length is 3072 bytes
Xporter should use only single indexes