Intermittent JIRA Server could not be contacted error

Please add any details that might help us help you.

some of our users are getting "Jira Server Could not be contacted" error. These are happening intermittently and doesn't belong to specific tasks.They are mostly caused when moving/cloning and assigning tickets to other users. Here's the recent log to better understand the issue.

I have attached some pictures of the issue - The first one is when the user is trying to clone a ticket and assign it to a different user and the second one is when the user was trying to add a label to exisiting ticket.

Any help to understand the root of the issue is appreciated.


Jira Error.jpg




Log : 
DEBUG: JavaMail version 1.4.5
DEBUG: successfully loaded resource: /META-INF/javamail.default.providers
DEBUG: Tables of loaded providers
DEBUG: Providers Listed By Class Name: {com.sun.mail.smtp.SMTPSSLTransport=javax.mail.Provider[TRANSPORT,smtps,com.sun.mail.smtp.SMTPSSLTransport,Sun Microsystems, Inc], com.sun.mail.smtp.SMTPTransport=javax.mail.Provider[TRANSPORT,smtp,com.sun.mail.smtp.SMTPTransport,Sun Microsystems, Inc], com.sun.mail.imap.IMAPSSLStore=javax.mail.Provider[STORE,imaps,com.sun.mail.imap.IMAPSSLStore,Sun Microsystems, Inc], com.sun.mail.pop3.POP3SSLStore=javax.mail.Provider[STORE,pop3s,com.sun.mail.pop3.POP3SSLStore,Sun Microsystems, Inc], com.sun.mail.imap.IMAPStore=javax.mail.Provider[STORE,imap,com.sun.mail.imap.IMAPStore,Sun Microsystems, Inc], com.sun.mail.pop3.POP3Store=javax.mail.Provider[STORE,pop3,com.sun.mail.pop3.POP3Store,Sun Microsystems, Inc]}
DEBUG: Providers Listed By Protocol: {imaps=javax.mail.Provider[STORE,imaps,com.sun.mail.imap.IMAPSSLStore,Sun Microsystems, Inc], imap=javax.mail.Provider[STORE,imap,com.sun.mail.imap.IMAPStore,Sun Microsystems, Inc], smtps=javax.mail.Provider[TRANSPORT,smtps,com.sun.mail.smtp.SMTPSSLTransport,Sun Microsystems, Inc], pop3=javax.mail.Provider[STORE,pop3,com.sun.mail.pop3.POP3Store,Sun Microsystems, Inc], pop3s=javax.mail.Provider[STORE,pop3s,com.sun.mail.pop3.POP3SSLStore,Sun Microsystems, Inc], smtp=javax.mail.Provider[TRANSPORT,smtp,com.sun.mail.smtp.SMTPTransport,Sun Microsystems, Inc]}
DEBUG: successfully loaded resource: /META-INF/
2015-06-09 04:24:38,749 QuartzWorker-0 ERROR ServiceRunner    Partners 4 Solutions Feedback Service [atlassian.mail.incoming.mailfetcherservice] Partners 4 Solutions Feedback Service[10111]: Error connecting to host '' as user 'p4solutionsfeedback' via protocol 'imaps': javax.mail.MessagingException: Connection refused;
  nested exception is: Connection refused
javax.mail.MessagingException: Connection refused;
  nested exception is: Connection refused
        at com.sun.mail.imap.IMAPStore.protocolConnect(
        at javax.mail.Service.connect(
        at com.atlassian.jira.service.ServiceRunner.execute(
        at com.atlassian.multitenant.quartz.MultiTenantThreadPool$
        at org.quartz.simpl.SimpleThreadPool$
Caused by: Connection refused
        at Method)
        at com.sun.mail.util.SocketFetcher.createSocket(
        at com.sun.mail.util.SocketFetcher.getSocket(
        at com.sun.mail.iap.Protocol.<init>(
        at com.sun.mail.imap.protocol.IMAPProtocol.<init>(
        at com.sun.mail.imap.IMAPStore.protocolConnect(
        ... 9 more

1 answer

0 votes

Hi, Sudhir.

I don't think the stack trace you attached has much to do with the problem as that is regarding emails. Perhaps using the Development Tool in Chrome or Firefox may help diagnose this better.

A good test would be to try putting JIRA in safe-mode to ensure this is not being caused by any add-ons. smile


Thanks Mattheus, 

I tried the safe mode thing but that doesn't seem to help. Since, this happens intermittently, I had to wait until today to replicate the error on users' machines. The weird part is, this has only been reported by couple of users. As you said, I have asked them to use Development Tool in the browsers and get back to me with the trace logs. 

Do you know if there is any other log file I can provide that helps figure out the problem? 


There may be something in the atlassian-jira.log or catalina.out (or stdout-******.log in Windows) if this is being caused by another error. This is most likely though a client side problem, so the development tools would be the best place I think. :)

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

1,105 views 4 9
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you