You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Rob Scheepens <sc...@oce.nl> on 2006/07/17 10:19:38 UTC
[jira] Created: (DERBY-1435) Conglomerate does not exist occurs in a specific case after dropping a table referenced by a trigger
Goodmorning all,
I am also experiencing the conglomerate not found issue.
I use Quartz to trigger a task that will perform some actions (See below
for the stack trace).
The thread that I have read is especially interested in reproducing these
issues.
But I also want to know if you all have a solution for this problem that I
can try?
Will derby.language.statementCacheSize=0 be sufficient?
Thanks in advance.
Kind regards,
Rob Scheepens
***
zo, 16 jul 01:48:34.319 ERROR - MisfireHandler: Error handling misfires:
The conglomerate (45,872) requested does not exist.
org.quartz.JobPersistenceException: The conglomerate (45,872) requested
does not exist. [See nested exception: SQL Exception: The conglomerate
(45,872) requested does not exist.]
at
org.quartz.impl.jdbcjobstore.JobStoreTX.doRecoverMisfires(JobStoreTX.java:1310)
at
org.quartz.impl.jdbcjobstore.JobStoreSupport$MisfireHandler.manage(JobStoreSupport.java:2322)
at
org.quartz.impl.jdbcjobstore.JobStoreSupport$MisfireHandler.run(JobStoreSupport.java:2340)
* Nested Exception (Underlying Cause) ---------------
ERROR XSAI2: The conglomerate (45,872) requested does not exist.
at org.apache.derby.iapi.error.StandardException.newException(Unknown
Source)
at
org.apache.derby.impl.store.access.heap.HeapConglomerateFactory.readConglomerate(Unknown
Source)
at
org.apache.derby.impl.store.access.RAMAccessManager.conglomCacheFind(Unknown
Source)
at
org.apache.derby.impl.store.access.RAMTransaction.findExistingConglomerate(Unknown
Source)
at
org.apache.derby.impl.store.access.RAMTransaction.getDynamicCompiledConglomInfo(Unknown
Source)
at org.apache.derby.impl.sql.execute.TableScanResultSet.openCore(Unknown
Source)
at
org.apache.derby.impl.sql.execute.BulkTableScanResultSet.openCore(Unknown
Source)
at
org.apache.derby.impl.sql.execute.ProjectRestrictResultSet.openCore(Unknown
Source)
at org.apache.derby.impl.sql.execute.BasicNoPutResultSetImpl.open(Unknown
Source)
at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown
Source)
at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown
Source)
at
org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown
Source)
at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeQuery(Unknown
Source)
at
org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:92)
at
org.quartz.impl.jdbcjobstore.StdJDBCDelegate.selectTriggersInState(StdJDBCDelegate.java:253)
at
org.quartz.impl.jdbcjobstore.JobStoreSupport.recoverMisfiredJobs(JobStoreSupport.java:722)
at
org.quartz.impl.jdbcjobstore.JobStoreTX.doRecoverMisfires(JobStoreTX.java:1308)
at
org.quartz.impl.jdbcjobstore.JobStoreSupport$MisfireHandler.manage(JobStoreSupport.java:2322)
at
org.quartz.impl.jdbcjobstore.JobStoreSupport$MisfireHandler.run(JobStoreSupport.java:2340)
--
****************************
Rob Scheepens
Océ-Technologies
Dept.: CC-SI, R&D
Location: 3B-70
St. Urbanusweg 43
5914 CA Venlo
The Netherlands
P.O. Box 101
5900 MA Venlo
The Netherlands
E-mail: schr@oce.nl
Phone: 0031-(0)77-3594428
****************************
Re: [jira] Created: (DERBY-1435) Conglomerate does not exist occurs in a specific case after dropping a table referenced by a trigger
Posted by Deepa Remesh <dr...@gmail.com>.
On 7/17/06, Rob Scheepens <sc...@oce.nl> wrote:
> Goodmorning all,
>
> I am also experiencing the conglomerate not found issue.
> I use Quartz to trigger a task that will perform some actions (See below
> for the stack trace).
>
> The thread that I have read is especially interested in reproducing these
> issues.
> But I also want to know if you all have a solution for this problem that I
> can try?
>
> Will derby.language.statementCacheSize=0 be sufficient?
>
On looking at the stack trace, this does not look like the scenario
described in DERBY-1435 which is a specific case where this error
(conglomerate does not exist) can occur. To see if it is a similar
case, can you please provide the details of the task you are trying to
execute using Quartz? It would be helpful to see the database schema,
sql/jdbc program being executed.
Thanks,
Deepa