Hi Fabio, I tryed various combinations and I found that using thin client and excluding usage of jdbc/syncopeDataSource connection pool the error disappear.
Are you able to reproduce the error using OCI and jndi Connection Pool? Thanks, Denis. > -----Messaggio originale----- > Da: Denis Signoretto [mailto:[email protected]] > Inviato: mercoledì 18 aprile 2012 11.01 > A: [email protected] > Oggetto: R: [jira] [Created] (SYNCOPE-59) ERROR > org.syncope.core.init.JobInstanceLoader - While loading > NotificationJob > instance - ORA-01002: fetch out of sequence > > > > Hi Fabio, > > for completeness, we are using: > > as Database: Oracle Database 10g Release 10.2.0.3.0 - 64bit > Production, > and we are accessing to DB with this settings (by OCI Driver). > > <Resource name="jdbc/syncopeDataSource" auth="Container" > type="javax.sql.DataSource" > > factory="org.apache.tomcat.jdbc.pool.DataSourceFactory" > testWhileIdle="true" > testOnBorrow="true" testOnReturn="true" > validationQuery="SELECT 1 FROM DUAL" validationInterval="30000" > maxActive="150" minIdle="2" maxWait="10000" > initialSize="2" removeAbandonedTimeout="10" > removeAbandoned="true" logAbandoned="true" > suspectTimeout="10" > timeBetweenEvictionRunsMillis="5000" > minEvictableIdleTimeMillis="5000" > > jdbcInterceptors="org.apache.tomcat.jdbc.pool.interceptor.Conn > ectionState;org.apache.tomcat.jdbc.pool.interceptor.StatementF > inalizer" > username="xxxxx" password="xxxxx" > driverClassName="oracle.jdbc.OracleDriver" > url="jdbc:oracle:oci:@ORACLE" /> > > Do you think, we should try excluding connection pool and > switching to thin client (without Oracle OCI driver)? > What Oracle configuration are you using? > > Thanks, > Denis. > > P.S. Further more at startup we have a warning on connection > pool abandoned (probably it doesn't matter) > > Apr 18, 2012 10:55:26 AM > org.apache.tomcat.jdbc.pool.ConnectionPool abandon > WARNING: Connection has been abandoned > PooledConnection[oracle.jdbc.driver.T2CConnection@305bf465]:ja va.lang.Exception > at > org.apache.tomcat.jdbc.pool.ConnectionPool.getThreadDump(Conne > ctionPool.java:1006) > at > org.apache.tomcat.jdbc.pool.ConnectionPool.borrowConnection(Co > nnectionPool.java:735) > at > org.apache.tomcat.jdbc.pool.ConnectionPool.borrowConnection(Co > nnectionPool.java:591) > at > org.apache.tomcat.jdbc.pool.ConnectionPool.getConnection(Conne > ctionPool.java:179) > at > org.apache.tomcat.jdbc.pool.DataSourceProxy.getConnection(Data > SourceProxy.java:124) > at > ch.qos.logback.core.db.JNDIConnectionSource.getConnection(JNDI > ConnectionSource.java:69) > > > -----Messaggio originale----- > > Da: Fabio Martelli [mailto:[email protected]] > > Inviato: mercoledì 18 aprile 2012 10.47 > > A: [email protected] > > Oggetto: Re: [jira] [Created] (SYNCOPE-59) ERROR > > org.syncope.core.init.JobInstanceLoader - While loading > > NotificationJob > > instance - ORA-01002: fetch out of sequence > > > > > > Hi Denis, > > I've just tried to reproduce the problem. > > > > Following the steps performed: > > 1. create a new project [1] > > 2. change to use oracle ad backend [2] > > 3. deploy syncope and syncope-console > > 4. start container > > 5. shutdown and startup again > > > > The problem has not been reproduced. > > Please, let me know if I missed some steps. > > > > Regards, > > F. > > > > [1] > > https://cwiki.apache.org/confluence/display/SYNCOPE/Create+a+n > > ew+Syncope+project > > [2] > > https://cwiki.apache.org/confluence/display/SYNCOPE/Run+Syncop > > e+in+real+environments#RunSyncopeinrealenvironments-Oracle > > > > Il giorno 17/apr/2012, alle ore 18.08, Denis Signoretto > > (Created) (JIRA) ha scritto: > > > > > ERROR org.syncope.core.init.JobInstanceLoader - While > > loading NotificationJob instance - ORA-01002: fetch out of sequence > > > > > -------------------------------------------------------------- > > ----------------------------------------------------------- > > > > > > Key: SYNCOPE-59 > > > URL: > > https://issues.apache.org/jira/browse/SYNCOPE-59 > > > Project: Syncope > > > Issue Type: Bug > > > Components: core > > > Affects Versions: 1.0.0-incubating > > > Environment: Oracle 10g, Linux x86_64, > > > Reporter: Denis Signoretto > > > Priority: Critical > > > > > > > > > Stracktrace Error on startup: > > > > > > 15:51:05.908 ERROR org.syncope.core.init.JobInstanceLoader > > - While loading NotificationJob instance > > > org.quartz.impl.jdbcjobstore.LockException: Failure > > obtaining db row lock: ORA-01002: fetch out of sequence > > > {prepstmnt 155276228 SELECT * FROM QRTZ_LOCKS WHERE > > LOCK_NAME = ? FOR UPDATE [params=?]} [code=1002, state=72000] > > > at > > org.quartz.impl.jdbcjobstore.StdRowLockSemaphore.executeSQL(St > > dRowLockSemaphore.java:109) ~[quartz-1.8.6.jar:na] > > > at > > org.quartz.impl.jdbcjobstore.DBSemaphore.obtainLock(DBSemaphor > > e.java:112) ~[quartz-1.8.6.jar:na] > > > at > > org.quartz.impl.jdbcjobstore.JobStoreCMT.executeInLock(JobStor > > eCMT.java:235) ~[quartz-1.8.6.jar:na] > > > at > > org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInLock(Job > > StoreSupport.java:3712) ~[quartz-1.8.6.jar:na] > > > at > > org.quartz.impl.jdbcjobstore.JobStoreSupport.storeJobAndTrigge > > r(JobStoreSupport.java:1059) ~[quartz-1.8.6.jar:na] > > > at > > org.quartz.core.QuartzScheduler.scheduleJob(QuartzScheduler.ja > > va:822) ~[quartz-1.8.6.jar:na] > > > at > > org.quartz.impl.StdScheduler.scheduleJob(StdScheduler.java:243 > > ) ~[quartz-1.8.6.jar:na] > > > at > > org.syncope.core.init.JobInstanceLoader.registerJob(JobInstanc > > eLoader.java:134) ~[JobInstanceLoader.class:na] > > > at > > org.syncope.core.init.JobInstanceLoader.registerJob(JobInstanc > > eLoader.java:162) ~[JobInstanceLoader.class:na] > > > at > > org.syncope.core.init.JobInstanceLoader.load(JobInstanceLoader > > .java:210) ~[JobInstanceLoader.class:na] > > > at > > org.syncope.core.init.JobInstanceLoader$$FastClassByCGLIB$$edd > > 08387.invoke(<generated>) [cglib-2.2.2.jar:na] > > > at > > net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) > > [cglib-2.2.2.jar:na] > > > > > > -- > > > This message is automatically generated by JIRA. > > > If you think it was sent incorrectly, please contact your > > JIRA administrators: > > https://issues.apache.org/jira/secure/ContactAdministrators!de > fault.jspa > > For more information on JIRA, see: > http://www.atlassian.com/software/jira > > > > > >
