Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Lost Application Link

After a system restart on OS upgrade (RHEL 7), the Application Link between Jira and Confluence stopped working.  Jira seems to be running without issue, and Confluence started.  But when trying to log into the Confluence admin page I get a 500 error as well.  I suspect our reverse proxy configuration is off somewhere.

image.png

2 answers

1 accepted

0 votes
Answer accepted

Red Hat has confirmed the jdk.tlk.maxHandshakeMessageSize parameter has been added to Java 8.  The fix is to add the following in the setenv.sh file for Jira, Confluence, and any other applications running:

-Djdk.tls.maxHandshakeMessageSize=35000

Stop the application, edit the setenv.sh, then restart.

[root@jira jira]# java SSLPoke jira.bizops.nrl.navy.mil 443
javax.net.ssl.SSLProtocolException: The size of the handshake message (34669) exceeds the maximum allowed size (32768)
at sun.security.ssl.SSLSocketInputRecord.decodeInputRecord(SSLSocketInputRecord.java:309)
at sun.security.ssl.SSLSocketInputRecord.decode(SSLSocketInputRecord.java:190)
at sun.security.ssl.SSLTransport.decode(SSLTransport.java:108)
at sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1143)
at sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1054)
at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:394)
at sun.security.ssl.SSLSocketImpl.ensureNegotiated(SSLSocketImpl.java:708)
at sun.security.ssl.SSLSocketImpl.access$100(SSLSocketImpl.java:72)
at sun.security.ssl.SSLSocketImpl$AppOutputStream.write(SSLSocketImpl.java:961)
at sun.security.ssl.SSLSocketImpl$AppOutputStream.write(SSLSocketImpl.java:933)
at SSLPoke.main(SSLPoke.java:31)

 

Is this indicating that our CA chain may be too long?  Is there a way to increase the allowed handshake message size?

Nope!  It's an update to Java 8 that adds a new configuration component:

jdk.tls.maxHandshakeMessageSize

So this is going to have to be modified in Jira to set a higher handshake message size.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
8.7.1
TAGS
Community showcase
Published in Jira

Announcing the waitlist for Jira Work Management

Hey there Cloud Community members! We’re excited to give you the first glimpse of the new home for business teams on Jira — Jira Work Management. Jira Work Management is the next generation of J...

153 views 3 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you