-
Bug
-
Resolution: Fixed
-
High
-
None
-
32
-
Severity 3 - Minor
-
1
-
Issue Summary
During the custom PDF export of a space, because the Request includes the content ID of every page regardless of if it is selected or not, it overruns the available space for the field it is later stored in and the export fails to ever run.
Steps to Reproduce
- Create a space with around 4000 pages in it (about 3600 is probably near the lower bound)
- Attempt a PDF "custom" export. (the selection is irrelevant. Selecting one or all the pages will still cause the issue)
- Start the export.
Expected Results
The Export does not start instead giving a 500 error with this content on the page:
Oops - an error has occurred System Error A system error has occurred — our apologies! For immediate troubleshooting, consult our knowledge base for a solution. If you would like to receive support from Atlassian's support team, ask your Confluence administrator to create a support issue on Atlassian's support system with the following information: a description of your problem and what you were doing at the time it occurred a copy of the error and system information found below a copy of the application logs (if possible). Your Confluence administrator can use the support request form to create a support ticket which will include this information. We will respond as promptly as possible. Thank you! Return to site homepage…
You can also see the following error when trying to make a custom export:
Already running this task.
The below exception is thrown in the logs:
rg.springframework.dao.DataIntegrityViolationException: Hibernate operation: could not execute statement; ERROR: value too long for type character varying(32768); nested exception is org.postgresql.util.PSQLException: ERROR: value too long for type character varying(32768) org.springframework.jdbc.support.SQLStateSQLExceptionTranslator.doTranslate(SQLStateSQLExceptionTranslator.java:104) org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:72) org.springframework.orm.hibernate.HibernateTransactionManager.convertJdbcAccessException(HibernateTransactionManager.java:619) org.springframework.orm.hibernate.HibernateTransactionManager.convertHibernateAccessException(HibernateTransactionManager.java:605) org.springframework.orm.hibernate.HibernateTransactionManager.doCommit(HibernateTransactionManager.java:518) com.atlassian.confluence.impl.hibernate.ConfluenceHibernateTransactionManager.doCommit(ConfluenceHibernateTransactionManager.java:58) org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:746) org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:714) sun.reflect.GeneratedMethodAccessor86.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) java.lang.reflect.Method.invoke(Method.java:498) org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:343) org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:205) com.sun.proxy.$Proxy70.commit(Unknown Source)
Workaround
Currently, the best workaround is to move the pages that you want to export into a new space, being sure to keep the number of pages in the space around 2000 or below.