Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

Sudden Unexplained Jira Outage: PropertyImplementationException: Unable to load values for CacheKey Edited

After a routine "dnf update" on a CentOS8 machine, Jira Core v8.6.0 starts up without any errors, but refuses to serve any pages.

The end user is told "Sorry, we had some technical problems during your last operation".

The underlying Java stacktrace (summarised is as follows):

com.opensymphony.module.propertyset.PropertyImplementationException: Unable to load values for CacheKey[entityName=ApplicationUser,entityId=10083]
Caused by: com.atlassian.cache.CacheException: com.atlassian.jira.exception.DataAccessException: org.postgresql.util.PSQLException: Connection to localhost:5432 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
Caused by: com.atlassian.jira.exception.DataAccessException: org.postgresql.util.PSQLException: Connection to localhost:5432 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
Caused by: org.postgresql.util.PSQLException: Connection to localhost:5432 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
Caused by: java.net.ConnectException: Connection refused (Connection refused)

Obviously, this is telling me that the database is not accepting connections on localhost port 5432.

Except the database is accepting connections on localhost port 5432.

[jira@jira ~]$ telnet 127.0.0.1 5432
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
^]quit

telnet> quit
Connection closed.
[jira@jira ~]$ telnet ::1 5432
Trying ::1...
Connected to ::1.
Escape character is '^]'.
^]quit

telnet> quit
Connection closed.

[jira@jira ~]$ psql -d "postgresql://localhost:5432" jira
Password for user jira: 
psql (10.6)
Type "help" for help.

jira=> \d
                           List of relations
 Schema |                   Name                    |   Type   | Owner 
--------+-------------------------------------------+----------+-------
 public | AO_0201F0_KB_HELPFUL_AGGR                 | table    | jira
 public | AO_0201F0_KB_HELPFUL_AGGR_ID_seq          | sequence | jira
 public | AO_0201F0_KB_VIEW_AGGR                    | table    | jira
 public | AO_0201F0_KB_VIEW_AGGR_ID_seq             | sequence | jira
 public | AO_0201F0_STATS_EVENT                     | table    | jira
 public | AO_0201F0_STATS_EVENT_ID_seq              | sequence | jira

For obvious reasons I am very stuck.

Anyone seen weirdness like this happen before?

2 answers

1 accepted

0 votes
Answer accepted

Turned out the solution to this was more mundane - check that the reverse proxy you're connecting to points at the machine you think it's pointing at.

In this case, it was pointing at a different machine. Once I was able to connect to the correct machine, the problem was solved.

Hello @Graham Leggett ,

Few things to check:

  • See this similar question, in this case postgresql was running using IPV6 instead of IPV4. Check if listen_addresses is set to localhost instead of :: in postgresql.conf, this change requires restart database and application service.
  • Check this kb, it's for Confluence but it can help Confluence PostgreSQL JDBC direct connection refused
  • Are you running JIRA with docker ?

As shown above, the database responds successfully to both IPv6 and IPv4.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Asked in Jira Service Management

JSM June ask me anything (AMA)

Hello Community members! We’re wrapping up the end of JSM June with an Ask Me Anything (AMA) with the Jira Service Management product team. This is your chance to ask all your ITSM questions to o...

255 views 12 14
View question

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