Project

General

Profile

Actions
Copy link

Defect #365

closed

IdM not working after restart DB

Added by Ondřej Kopr about 7 years ago. Updated about 5 years ago.

Status:
Closed
Priority:
Low
Assignee:
Radek Tomiška
Category:
Scheduler
Target version:
Garnet (7.7.0)
Start date:
04/10/2017
Due date:
% Done:

100%

Estimated time:
Affected versions:
Owner:

Description

After restart DB with running IdM, IdM not working.

Potential issue: quartz, settings DataSource?

org.postgresql.util.PSQLException: This connection has been closed.
    at org.postgresql.jdbc.PgConnection.checkClosed(PgConnection.java:806)
    at org.postgresql.jdbc.PgConnection.rollback(PgConnection.java:813)
    at sun.reflect.GeneratedMethodAccessor155.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at org.apache.tomcat.jdbc.pool.ProxyConnection.invoke(ProxyConnection.java:126)
    at org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:108)
    at org.apache.tomcat.jdbc.pool.DisposableConnectionFacade.invoke(DisposableConnectionFacade.java:81)
    at com.sun.proxy.$Proxy87.rollback(Unknown Source)
    at sun.reflect.GeneratedMethodAccessor155.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at org.quartz.impl.jdbcjobstore.AttributeRestoringConnectionInvocationHandler.invoke(AttributeRestoringConnectionInvocationHandler.java:73)
    at com.sun.proxy.$Proxy295.rollback(Unknown Source)
    at org.quartz.impl.jdbcjobstore.JobStoreSupport.rollbackConnection(JobStoreSupport.java:3666)
    at org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInNonManagedTXLock(JobStoreSupport.java:3825)
    at org.quartz.impl.jdbcjobstore.JobStoreSupport.acquireNextTriggers(JobStoreSupport.java:2756)
    at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:272)

Files

03.png (10.2 KB) 03.png Ondřej Kopr, 04/10/2017 10:49 AM
Actions
Copy link
 #1

Updated by Ondřej Kopr about 7 years ago

  • Description updated (diff)
Actions
Copy link
 #2

Updated by Vít Švanda about 7 years ago

  • Assignee changed from Vít Švanda to Ondřej Kopr
Actions
Copy link
 #3

Updated by Ondřej Kopr almost 7 years ago

  • Priority changed from Normal to Low
Actions
Copy link
 #4

Updated by Radek Tomiška almost 7 years ago

  • Target version changed from Citrine (7.3.0) to Diamond (7.4.0)
Actions
Copy link
 #5

Updated by Ondřej Kopr over 6 years ago

  • Target version changed from Diamond (7.4.0) to Emerald (7.5.0)
Actions
Copy link
 #6

Updated by Radek Tomiška over 6 years ago

  • Target version deleted (Emerald (7.5.0))
Actions
Copy link
 #7

Updated by Radek Tomiška over 6 years ago

  • Status changed from New to Needs feedback
  • Target version set to Garnet (7.7.0)
  • % Done changed from 0 to 90

I configured validation, when db connection is reused from pool, doc:
https://wiki.czechidm.com/devel/dev/configuration/backend#jpa

Invalid connections are removed from pool, when db server is restarted.

Could you do a feedback pls?

Actions
Copy link
 #8

Updated by Ondřej Kopr over 6 years ago

  • Status changed from Needs feedback to Resolved
  • Assignee changed from Ondřej Kopr to Radek Tomiška
  • % Done changed from 90 to 100

I made test for this new feature, start CzechIdM and then reset DB (postgresql) and check if application response => Awesome now our application survive database restart! Thank you for that :)

Actions
Copy link
 #9

Updated by Radek Tomiška over 6 years ago

  • Status changed from Resolved to Closed
Actions
Copy link
 #10

Updated by Radek Tomiška about 5 years ago

  • Category changed from 20 to Scheduler
Actions
Copy link

Also available in: Atom PDF