Xporter Bulk Export SSL issue

Gabor Petranyi
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 3, 2013

HI,

I installed Xporter for JIRA and it is working fine exporting a single issue. However when I try to do bulk export I alwys receive the following error message even with the sample template included.

An error occurred while exporting your issues. Please contact your JIRA administration to check the server log for additional information.

This is what I can see in the log file.

/secure/views/bulkedit/BulkExportDetails!perform.jspa [xpandit.jiraxporter.action.BulkExport] Error while performing BulkExportOperation

javax.net.ssl.SSLProtocolException: handshake alert: unrecognized_name

at sun.security.ssl.ClientHandshaker.handshakeAlert(Unknown Source)

at sun.security.ssl.SSLSocketImpl.recvAlert(Unknown Source)

at sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source)

at sun.security.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)

at sun.security.ssl.SSLSocketImpl.writeRecord(Unknown Source)

at sun.security.ssl.AppOutputStream.write(Unknown Source)

at java.io.BufferedOutputStream.flushBuffer(Unknown Source)

at java.io.BufferedOutputStream.flush(Unknown Source)

I wonder if someone can give me some clues how to resolve this.

1 answer

1 accepted

1 vote
Answer accepted
Gabor Petranyi
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 4, 2013

This issue is resolved with a great help from the Xporter support .

Java 7 introduced SNI support which is enabled by default. I have found out that certain misconfigured servers send an "Unrecognized Name" warning in the SSL handshake which is ignored by most clients... except for Java.

Adding

-Djsse.enableSNIExtension=false

to the startup options of JIRA resolved the issue.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events