The following bug has been logged online:
Bug reference: 3245
Logged by: Michel Dorochevsky
Email address: Michel(dot)Dorochevsky(at)softcon(dot)de
PostgreSQL version: 8.2.3
Operating system: Windows 2000 / XP / 2003
Description: PANIC: failed to re-find shared lock object
We are using "PostgreSQL 8.2.3 on i686-pc-mingw32, compiled by GCC gcc.exe
(GCC) 3.4.2 (mingw-special)"
We are encountering the following problem:
>> start extract from the log files in pg_log <<
2007-04-19 15:52:29 LOG: database system is ready
2007-04-19 16:22:19 PANIC: failed to re-find shared lock object
2007-04-19 16:22:19 STATEMENT: COMMIT PREPARED
This application has requested the Runtime to terminate it in an unusual
Please contact the application's support team for more information.
2007-04-19 16:22:19 LOG: server process (PID 20184) exited with exit code
2007-04-19 16:22:19 LOG: terminating any other active server processes
>> end extract from the log files in pg_log <<
Our log_error_verbosity is set to verbose.
We are experiencing this problem on different Windows platforms: Windows
2000 Professional, XP and XP Server 2003 (with the latest service packs) on
We have reinstalled the database from scratch several times.
Our application accesses the database through the JDBC driver included in
the PostgreSQL distribution. It is a complex application
(JBoss/Hibernate/2-Phase-Commit) where it is difficult to provide a consise
test routine to reproduce the problem. We can reproduce this problem almost
deterministically with a test suite 2 times of 3 runs, but still with all
the JBoss/Hibernate/... environment.
My question is: how could we proceed to get help?
Does any one know of a clever way to record the JDBC statements (including
the bind parameters) in order have a strpped down test routine?
SOFTCON-IT Service GmbH
pgsql-bugs by date
|Next:||From: Tom Lane||Date: 2007-04-19 20:36:13|
|Subject: Re: BUG #3245: PANIC: failed to re-find shared lock object |
|Previous:||From: William Lawrance||Date: 2007-04-19 14:23:22|
|Subject: BUG #3244: problem with PREPARE|