[ https://jira.jboss.org/jira/browse/JBAS-6304?page=com.atlassian.jira.plug... ] Martin Malina updated JBAS-6304: -------------------------------- Attachment: oracle10g.log Attached the server output. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-6304?page=com.atlassian.jira.plug... ] Martin Malina commented on JBAS-6304: ------------------------------------- In the case of Sybase the error looks a bit different: 08:56:53,530 ERROR [AbstractKernelController] Error installing to Start: name=jboss.ejb:service=EJB3TimerService state=Create mode=Manual requiredState=Installed org.quartz.SchedulerConfigException: Failure occured during job recovery. [See nested exception: org.quartz.JobPersistenceException: Couldn't clean volatile data: Implicit conversion from datatype 'VARCHAR' to 'BIT' is not allowed. Use the CONVERT function to run this query. [See nested exception: com.sybase.jdbc3.jdbc.SybSQLException: Implicit conversion from datatype 'VARCHAR' to 'BIT' is not allowed. Use the CONVERT function to run this query. ]] at org.quartz.impl.jdbcjobstore.JobStoreSupport.initialize(JobStoreSupport.java:493) at org.quartz.impl.jdbcjobstore.JobStoreCMT.initialize(JobStoreCMT.java:144) .. *** CONTEXTS IN ERROR: Name -> Error jboss.ejb:service=EJB3TimerService -> org.quartz.SchedulerConfigException: Failure occured during job recovery. [See nested exception: org.quartz.JobPersistenceException: Couldn't clean volatile data: Implicit conversion from datatype 'VARCHAR' to 'BIT' is not allowed. Use the CONVERT function to run this query. [See nested exception: com.sybase.jdbc3.jdbc.SybSQLException: Implicit conversion from datatype 'VARCHAR' to 'BIT' is not allowed. Use the CONVERT function to run this query. ]] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-6304?page=com.atlassian.jira.plug... ] Martin Malina updated JBAS-6304: -------------------------------- Environment: Oracle10g, PostgreSQL, DB2 v9, Sybase15 (was: Oracle10g, PostgreSQL, Sybase15) Description: After setting up Oracle10g as the DefaultDS using this docs: http://www.jboss.org/file-access/default/members/jbossas/freezone/docs/In... and starting the AS instance with "all" config, this error occured: 07:21:09,609 ERROR [AbstractKernelController] Error installing to Start: name=jboss.ejb:service=EJB3TimerService state=Create mode=Manual requiredState=Installed org.quartz.SchedulerConfigException: Failure occured during job recovery. [See nested exception: org.quartz.impl.jdbcjobstore.LockException: Failure obtaining db row lock: ORA-00942: table or view does not exist [See nested exception: java.sql.SQLException: ORA-00942: table or view does not exist ]] at org.quartz.impl.jdbcjobstore.JobStoreSupport.initialize(JobStoreSupport.java:493) at org.quartz.impl.jdbcjobstore.JobStoreCMT.initialize(JobStoreCMT.java:144) ... *** CONTEXTS IN ERROR: Name -> Error jboss.ejb:service=EJB3TimerService -> org.quartz.SchedulerConfigException: Failure occured during job recovery. [See nested exception: org.quartz.impl.jdbcjobstore.LockException: Failure obtaining db row lock: ORA-00942: table or view does not exist [See nested exception: java.sql.SQLException: ORA-00942: table or view does not exist ]] It seems it fails due to trying to recover non-existing data from the database. Similar failure occurs with PostgreSQL and DB2 v9. was: After setting up Oracle10g as the DefaultDS using this docs: http://www.jboss.org/file-access/default/members/jbossas/freezone/docs/In... and starting the AS instance with "all" config, this error occured: 07:21:09,609 ERROR [AbstractKernelController] Error installing to Start: name=jboss.ejb:service=EJB3TimerService state=Create mode=Manual requiredState=Installed org.quartz.SchedulerConfigException: Failure occured during job recovery. [See nested exception: org.quartz.impl.jdbcjobstore.LockException: Failure obtaining db row lock: ORA-00942: table or view does not exist [See nested exception: java.sql.SQLException: ORA-00942: table or view does not exist ]] at org.quartz.impl.jdbcjobstore.JobStoreSupport.initialize(JobStoreSupport.java:493) at org.quartz.impl.jdbcjobstore.JobStoreCMT.initialize(JobStoreCMT.java:144) ... *** CONTEXTS IN ERROR: Name -> Error jboss.ejb:service=EJB3TimerService -> org.quartz.SchedulerConfigException: Failure occured during job recovery. [See nested exception: org.quartz.impl.jdbcjobstore.LockException: Failure obtaining db row lock: ORA-00942: table or view does not exist [See nested exception: java.sql.SQLException: ORA-00942: table or view does not exist ]] It seems it fails due to trying to recover non-existing data from the database. Similar failure occurs with PostgreSQL. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-6304?page=com.atlassian.jira.plug... ] Martin Malina commented on JBAS-6304: ------------------------------------- Thanks Andre, I will check that. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-6304?page=com.atlassian.jira.plug... ] Martin Malina resolved JBAS-6304. --------------------------------- Resolution: Rejected Not a bug. I will probably create a task for this to be documented. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-6304?page=com.atlassian.jira.plug... ] Dimitris Andreadis commented on JBAS-6304: ------------------------------------------ Does it make sense to remove from 5.0.1 / 5.1.0 if it's not currently used? That will save us the overhead of 10 idle quartz threads, plus the user's asking for DB setup. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira