Description of problem: After upgrading our Spacewalk 1.0 server to 1.1 we receive a lot of deadlock tracebacks like this: ... org.quartz.JobExecutionException: com.redhat.rhn.common.db.WrappedSQLException: ORA-00060: deadlock detected while waiting for resource ORA-06512: at "SPACEWALK.RHN_SYNCH_PROBE_STATE", line 4 ORA-06512: at line 1 [See nested exception: com.redhat.rhn.common.db.WrappedSQLException: ORA-00060: deadlock detected while waiting for resource ORA-06512: at "SPACEWALK.RHN_SYNCH_PROBE_STATE", line 4 ORA-06512: at line 1 ] at com.redhat.rhn.taskomatic.task.SynchProbeState.run(SynchProbeState.java:59) at com.redhat.rhn.taskomatic.task.SingleThreadedTask.execute(SingleThreadedTask.java:55) at org.quartz.core.JobRunShell.run(JobRunShell.java:214) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:549) Caused by: com.redhat.rhn.common.db.WrappedSQLException: ORA-00060: deadlock detected while waiting for resource ORA-06512: at "SPACEWALK.RHN_SYNCH_PROBE_STATE", line 4 ORA-06512: at line 1 at com.redhat.rhn.common.translation.SqlExceptionTranslator.oracleSQLException(SqlExceptionTranslator.java:84) at com.redhat.rhn.common.translation.SqlExceptionTranslator.sqlException(SqlExceptionTranslator.java:42) at com.redhat.rhn.common.db.NamedPreparedStatement.execute(NamedPreparedStatement.java:119) at com.redhat.rhn.common.db.datasource.CachedStatement.executeCallable(CachedStatement.java:507) at com.redhat.rhn.common.db.datasource.CallableMode.execute(CallableMode.java:34) at com.redhat.rhn.taskomatic.task.SynchProbeState.run(SynchProbeState.java:52) ... 3 more Caused by: java.sql.SQLException: ORA-00060: deadlock detected while waiting for resource ORA-06512: at "SPACEWALK.RHN_SYNCH_PROBE_STATE", line 4 ORA-06512: at line 1 at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112) at oracle.jdbc.driver.T2CConnection.checkError(T2CConnection.java:676) at oracle.jdbc.driver.T2CConnection.checkError(T2CConnection.java:602) at oracle.jdbc.driver.T2CCallableStatement.executeForDescribe(T2CCallableStatement.java:572) at oracle.jdbc.driver.T2CCallableStatement.executeForRows(T2CCallableStatement.java:765) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1190) at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3370) at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3476) at oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:4400) at com.mchange.v2.c3p0.impl.NewProxyCallableStatement.execute(NewProxyCallableStatement.java:2706) at com.redhat.rhn.common.db.NamedPreparedStatement.execute(NamedPreparedStatement.java:116) ... 6 more ... We have already deleted all probe suites but the problem still occurs. Greets Marcus
Still valid for 1.2
We did not have time for this one during Spacewalk 1.4 time frame. Mass moving to Spacewalk 1.5.
Aligning under space16.
(In reply to comment #1) > Still valid for 1.2 The SynchProbeState code was refactored for Spacewalk 1.2 -- can you show the traceback for the current Spacewalk server?
We seem to have communication lost here. Closing, please reopen if you hit the problem with the latest Spacewalk release. Thank you, Jan