-
Type:
Bug
-
Resolution: Won't Fix
-
Priority:
Low
-
None
-
Affects Version/s: JCMA - 1.9.3, JCMA - 1.9.5, JCMA - 1.9.7, JCMA - 1.9.8
-
Component/s: Jira - Migration Assistant - All data at once
-
2
-
Severity 3 - Minor
-
3
Issue Summary
This is reproducible on Data Center: (yes)
When using "Migrate all at once" option, the migration failed "Export Jira data" step, checking the error log, the exception is "This ResultSet is closed."
Steps to Reproduce
Unclear, this error seems to be related to the socket/connection timeout setting in the database, increasing the timeout can solve the issue.
Expected Results
The export should be successful without error.
Actual Results
The below exception is thrown in the atlassian-jira.log file:
Caused by: org.postgresql.util.PSQLException: This ResultSet is closed. at org.postgresql.jdbc.PgResultSet.checkClosed(PgResultSet.java:2932) at org.postgresql.jdbc.PgResultSet.next(PgResultSet.java:1951) at org.apache.commons.dbcp2.DelegatingResultSet.next(DelegatingResultSet.java:191) at org.apache.commons.dbcp2.DelegatingResultSet.next(DelegatingResultSet.java:191) at org.ofbiz.core.entity.EntityListIterator.next(EntityListIterator.java:266) ... 35 more
Workaround
Increase the socket/connection timeout in database config
This is an existing issue in Jira server export, for the reference, here are some existing support tickets and solutions: