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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,993
Community Members
 
Community Events
176
Community Groups

Plan could not be started JDBC exception in Hibernate data access: SQLException for SQL

Hi Team,
one of our plans stopped working recently, when we try to run manually we get this error and the plan doesn't start at all:

Plan 'PTAUT' could not be started. org.springframework.orm.hibernate5.HibernateJdbcException: JDBC exception on Hibernate data access: SQLException for SQL [n/a]; SQL state [53300]; error code [0]; could not extract ResultSet; nested exception is org.hibernate.exception.GenericJDBCException: could not extract ResultSet

in the logs we can see this:

JDBC exception on Hibernate data access: SQLException for SQL [n/a]; SQL state [53300]; error code [0]; could not extract ResultSet; nested exception is org.hibernate.exception.GenericJDBCException: could not extract ResultSet
Caused by: org.postgresql.util.PSQLException: ERROR: remaining connection slots are reserved for non-replication superuser and rds_superuser connections

We have Bamboo datacentre 8.1.2 build 80109 connected to RDS

anyone knows what could be the problem here?

Thank you!

3 answers

1 accepted

0 votes
Answer accepted

we found the reason why our plans wouldn't run.

we hit a limit on the number of iterations.
basically one of our customers configured a plan to run every 15 min, after a year this became over 26k iterations and suddenly stop working


deleting  old entries from the history of the plan got it working again, however it was easier to clone it and start fresh

Hi @Eduardo A 
thank you very much for the information, checking the database we are pretty sure max_connections is not the problem. we are well below
 

SHOW max_connections; 
3466

we also experience this problem with only one plan in particular, all the other plans are working fine.

we suspect there is something in the cache related to this plan that is throwing this error.
is there a way to refresh that for a particular plan?

Cheers

0 votes
Eduardo A Atlassian Team Jul 12, 2022

Hey @Julian Jaramillo

The following message:

Caused by: org.postgresql.util.PSQLException: ERROR: remaining connection slots are reserved for non-replication superuser and rds_superuser connections

Indicates that the database has exceeded the max_connections parameter.

You can try extending upgrade your RDS instance or adjusting the max_connections on parameter groups directly on the database:

Regards,

Eduardo Alvarenga
Atlassian Support APAC

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events