You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomee.apache.org by tschuler <th...@opentext.com> on 2013/10/16 11:37:51 UTC
Default scheduler initialize error in case of oracle persisted
scheduler beans
Hi!
We are using latest TomEE 1.6.0 snapshot and try to persist scheduled beans
in an oracle database.
The TomEE startup fails because the default scheduler cannot be initialized.
Attached zip ( DefaultSchedulerInitializeError.zip
<http://openejb.979440.n4.nabble.com/file/n4665596/DefaultSchedulerInitializeError.zip>
) includes the error message and simple tests for scheduler initializations:
- PersistedSchedulerBeanOracleTest.java: demonstrates failed startup for
oracle database
- PersistedSchedulerBeanMSSQLTest.java: demonstrates successful startup for
mssql database
- SchedulerBeanUnderTest.java: (needed as @Module and for further tests)
- DefaultSchedulerInitializeError.txt: Server startup exception while
default scheduler initialization
To make the tests running an oracle/mssql database and an oracle/mssql jdbc
driver (ojdbc6.jar/sqljdbc4.jar) are needed, also URL, USERNAME and PASSWORD
in Testclasses must be adapted.
The test creates the needed quartz tables while startup and deletes them
while shutdown. A simple test case (that does nothing right now) enforces
the server startup.
Can you give a hint why default scheduler cannot be initialized while server
startup?
Best regards,
Thomas
--
View this message in context: http://openejb.979440.n4.nabble.com/Default-scheduler-initialize-error-in-case-of-oracle-persisted-scheduler-beans-tp4665596.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: Default scheduler initialize error in case of oracle persisted
scheduler beans
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hi
first can be related to column format/size.
second is related to driver I think. This parameter can be not supported
(that's why we removed it by default in our db pool - before it was set for
each db pool)
*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2013/10/22 tschuler <th...@opentext.com>
> Hi Romain!
>
> I was able to get the scheduled beans running with oracle database
> persisting.
>
> First approach was to deactivate oracle optimization handling disk space
> for
> empty tables (DEFERRED_SEGMENT_CREATION).
> This fixes the problem only partially - tomee startup was successful but
> adding cron timers failed unpredictable (showing the same oracle error
> ORA-08177).
>
> Second approach was successful:
> In application.properties (describing the quartz persistence) the
> org.quartz.jobStore.txIsolationLevelSerializable must be set to false.
> Tomee
> startup is successful, scheduled beans are handled as expected.
>
> Do you have an idea, why:
> - in the first approach - adding the cron timers sometimes failed?
> - in the second approach - txIsolationLevelSerializable cannot be set to
> true in case of an oracle database?
>
> Best regards,
> Thomas
>
>
>
>
> --
> View this message in context:
> http://openejb.979440.n4.nabble.com/Default-scheduler-initialize-error-in-case-of-oracle-persisted-scheduler-beans-tp4665596p4665698.html
> Sent from the OpenEJB User mailing list archive at Nabble.com.
>
Re: Default scheduler initialize error in case of oracle persisted
scheduler beans
Posted by tschuler <th...@opentext.com>.
Hi Romain!
I was able to get the scheduled beans running with oracle database
persisting.
First approach was to deactivate oracle optimization handling disk space for
empty tables (DEFERRED_SEGMENT_CREATION).
This fixes the problem only partially - tomee startup was successful but
adding cron timers failed unpredictable (showing the same oracle error
ORA-08177).
Second approach was successful:
In application.properties (describing the quartz persistence) the
org.quartz.jobStore.txIsolationLevelSerializable must be set to false. Tomee
startup is successful, scheduled beans are handled as expected.
Do you have an idea, why:
- in the first approach - adding the cron timers sometimes failed?
- in the second approach - txIsolationLevelSerializable cannot be set to
true in case of an oracle database?
Best regards,
Thomas
--
View this message in context: http://openejb.979440.n4.nabble.com/Default-scheduler-initialize-error-in-case-of-oracle-persisted-scheduler-beans-tp4665596p4665698.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
RE: Properties Command line Tool
Posted by "Patel, Sanjay" <Sa...@nemours.org>.
Thanks. This is helpful.
-----Original Message-----
From: Romain Manni-Bucau [mailto:rmannibucau@gmail.com]
Sent: Thursday, October 17, 2013 3:10 PM
To: users@tomee.apache.org
Subject: Re: Properties Command line Tool
Hi
All is exported to jmx so just use a jmx client would work.
Le 17 oct. 2013 20:32, "Patel, Sanjay" <Sa...@nemours.org> a écrit :
> How to look at current properties' values in tomee? I want to look at
> values of PoolSize and TimeOut etc.
>
>
Re: Properties Command line Tool
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hi
All is exported to jmx so just use a jmx client would work.
Le 17 oct. 2013 20:32, "Patel, Sanjay" <Sa...@nemours.org> a écrit :
> How to look at current properties' values in tomee? I want to look at
> values of PoolSize and TimeOut etc.
>
>
Properties Command line Tool
Posted by "Patel, Sanjay" <Sa...@nemours.org>.
How to look at current properties' values in tomee? I want to look at values of PoolSize and TimeOut etc.
Re: Default scheduler initialize error in case of oracle persisted
scheduler beans
Posted by Romain Manni-Bucau <rm...@gmail.com>.
I spriche nicht german but I think it can be an issue from column type in
the database. The one with lobs. We store more than default data handled by
quartz so maybe the type is not more relevant.
Did you try tunning it?
*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2013/10/17 tschuler <th...@opentext.com>
> Hi Romain!
>
> Do you mean the error I added in the attachment?
>
> Here it is:
>
> org.apache.openejb.OpenEJBException: Creating application failed:
> C:\Perforce\ps\ps\main\pkg\PS_TOMEE\PersistedSchedulerBeanOracleTest: Error
> deploying 'SchedulerBeanUnderTest'. Exception: class
> org.apache.openejb.OpenEJBRuntimeException: Fail to initialize the default
> scheduler: Fail to initialize the default scheduler
> at
> org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:897)
> at
> org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:613)
> at
> org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:609)
> at
> org.apache.openejb.testing.ApplicationComposers.before(ApplicationComposers.java:639)
> at
> org.apache.openejb.testing.ApplicationComposers.evaluate(ApplicationComposers.java:722)
> at
> org.apache.openejb.junit.ApplicationComposer$DeployApplication.evaluate(ApplicationComposer.java:64)
> at
> org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> at
> org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at
> org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at
> org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at
> org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at
> org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at
> org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at
> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
> at
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
> Caused by: org.apache.openejb.OpenEJBException: Error deploying
> 'SchedulerBeanUnderTest'. Exception: class
> org.apache.openejb.OpenEJBRuntimeException: Fail to initialize the default
> scheduler: Fail to initialize the default scheduler
> at
> org.apache.openejb.assembler.classic.Assembler.startEjbs(Assembler.java:1121)
> at
> org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:805)
> ... 22 more
> Caused by: org.apache.openejb.OpenEJBRuntimeException: Fail to initialize
> the default scheduler
> at
> org.apache.openejb.core.timer.EjbTimerServiceImpl.getDefaultScheduler(EjbTimerServiceImpl.java:194)
> at
> org.apache.openejb.core.timer.EjbTimerServiceImpl.start(EjbTimerServiceImpl.java:450)
> at
> org.apache.openejb.core.singleton.SingletonContainer.deploy(SingletonContainer.java:118)
> at
> org.apache.openejb.assembler.classic.Assembler.startEjbs(Assembler.java:1108)
> ... 23 more
> Caused by: org.quartz.JobPersistenceException: Couldn't store job:
> ORA-08177: Zugriff für diese Transaktion kann nicht serialisiert werden
> [See nested exception: java.sql.SQLException: ORA-08177: Zugriff für diese
> Transaktion kann nicht serialisiert werden
> ]
> at
> org.quartz.impl.jdbcjobstore.JobStoreSupport.storeJob(JobStoreSupport.java:1117)
> at
> org.quartz.impl.jdbcjobstore.JobStoreSupport$3.execute(JobStoreSupport.java:1089)
> at
> org.quartz.impl.jdbcjobstore.JobStoreSupport$45.execute(JobStoreSupport.java:3705)
> at
> org.quartz.impl.jdbcjobstore.JobStoreCMT.executeInLock(JobStoreCMT.java:245)
> at
> org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInLock(JobStoreSupport.java:3701)
> at
> org.quartz.impl.jdbcjobstore.JobStoreSupport.storeJob(JobStoreSupport.java:1085)
> at
> org.quartz.core.QuartzScheduler.addJob(QuartzScheduler.java:999)
> at
> org.quartz.core.QuartzScheduler.addJob(QuartzScheduler.java:988)
> at
> org.quartz.impl.StdScheduler.addJob(StdScheduler.java:268)
> at
> org.apache.openejb.core.timer.EjbTimerServiceImpl.getDefaultScheduler(EjbTimerServiceImpl.java:192)
> ... 26 more
> Caused by: java.sql.SQLException: ORA-08177: Zugriff für diese Transaktion
> kann nicht serialisiert werden
>
> at
> oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:450)
> at
> oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:399)
> at
> oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1017)
> at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:655)
> at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:249)
> at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:566)
> at
> oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:215)
> at
> oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:58)
> at
> oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:943)
> at
> oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1075)
> at
> oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3820)
> at
> oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3897)
> at
> oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(OraclePreparedStatementWrapper.java:1361)
> at
> org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
> at
> org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
> at
> org.quartz.impl.jdbcjobstore.oracle.OracleDelegate.insertJobDetail(OracleDelegate.java:170)
> at
> org.quartz.impl.jdbcjobstore.JobStoreSupport.storeJob(JobStoreSupport.java:1111)
> ... 35 more
>
> Best regards,
> Thomas
>
> Von: Romain Manni-Bucau [via OpenEJB] [mailto:
> ml-node+s979440n4665606h96@n4.nabble.com]
> Gesendet: Donnerstag, 17. Oktober 2013 14:08
> An: Thomas Schuler
> Betreff: Re: Default scheduler initialize error in case of oracle
> persisted scheduler beans
>
> Hmm, I can't test against oracle :s. I didn't see the error in the thread
> can you past it, maybe it will make some bell ringing to anyone.
>
> *Romain Manni-Bucau*
> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> *Blog: **http://rmannibucau.wordpress.com/*<
> http://rmannibucau.wordpress.com/>
> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> *Github: https://github.com/rmannibucau*
>
>
>
> 2013/10/17 tschuler <[hidden
> email]</user/SendEmail.jtp?type=node&node=4665606&i=0>>
>
> > Hi!
> >
> > I checked MSSQL database (works) and the TomEE internal hsql database
> > (works too).
> > I have no experiences with Mysql, sorry!
> > So it seems to be a problem for oracle databases only - as far as I know
> > independent from oracle database version and oracle jdbc driver version.
> >
> > Best regards,
> > Thomas
> >
> >
> > Von: Romain Manni-Bucau [via OpenEJB] [mailto:
> > [hidden email]</user/SendEmail.jtp?type=node&node=4665606&i=1>]
> > Gesendet: Donnerstag, 17. Oktober 2013 12:52
> > An: Thomas Schuler
> > Betreff: Re: Default scheduler initialize error in case of oracle
> > persisted scheduler beans
> >
> > Hi
> >
> > is it linked to the db or does it behave the same way with mysql/hsqldb?
> >
> > *Romain Manni-Bucau*
> > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> > *Blog: **http://rmannibucau.wordpress.com/*<
> > http://rmannibucau.wordpress.com/>
> > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> > *Github: https://github.com/rmannibucau*
> >
> >
> >
> > 2013/10/16 tschuler <[hidden
> > email]</user/SendEmail.jtp?type=node&node=4665604&i=0>>
> >
> > > Hi!
> > >
> > > We are using latest TomEE 1.6.0 snapshot and try to persist scheduled
> > beans
> > > in an oracle database.
> > > The TomEE startup fails because the default scheduler cannot be
> > > initialized.
> > >
> > > Attached zip ( DefaultSchedulerInitializeError.zip
> > > <
> > >
> >
> http://openejb.979440.n4.nabble.com/file/n4665596/DefaultSchedulerInitializeError.zip
> > > >
> > > ) includes the error message and simple tests for scheduler
> > > initializations:
> > >
> > > - PersistedSchedulerBeanOracleTest.java: demonstrates failed startup
> for
> > > oracle database
> > > - PersistedSchedulerBeanMSSQLTest.java: demonstrates successful startup
> > for
> > > mssql database
> > > - SchedulerBeanUnderTest.java: (needed as @Module and for further
> tests)
> > > - DefaultSchedulerInitializeError.txt: Server startup exception while
> > > default scheduler initialization
> > >
> > > To make the tests running an oracle/mssql database and an oracle/mssql
> > jdbc
> > > driver (ojdbc6.jar/sqljdbc4.jar) are needed, also URL, USERNAME and
> > > PASSWORD
> > > in Testclasses must be adapted.
> > > The test creates the needed quartz tables while startup and deletes
> them
> > > while shutdown. A simple test case (that does nothing right now)
> enforces
> > > the server startup.
> > >
> > > Can you give a hint why default scheduler cannot be initialized while
> > > server
> > > startup?
> > >
> > > Best regards,
> > > Thomas
> > >
> > >
> > >
> > >
> > > --
> > > View this message in context:
> > >
> >
> http://openejb.979440.n4.nabble.com/Default-scheduler-initialize-error-in-case-of-oracle-persisted-scheduler-beans-tp4665596.html
> > > Sent from the OpenEJB User mailing list archive at Nabble.com.
> > >
> >
> > ________________________________
> > If you reply to this email, your message will be added to the discussion
> > below:
> >
> >
> http://openejb.979440.n4.nabble.com/Default-scheduler-initialize-error-in-case-of-oracle-persisted-scheduler-beans-tp4665596p4665604.html
> > To unsubscribe from Default scheduler initialize error in case of oracle
> > persisted scheduler beans, click here<
> > >.
> > NAML<
> >
> http://openejb.979440.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
> > >
> >
> >
> >
> >
> > --
> > View this message in context:
> >
> http://openejb.979440.n4.nabble.com/Default-scheduler-initialize-error-in-case-of-oracle-persisted-scheduler-beans-tp4665596p4665605.html
> > Sent from the OpenEJB User mailing list archive at Nabble.com.
> >
>
> ________________________________
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://openejb.979440.n4.nabble.com/Default-scheduler-initialize-error-in-case-of-oracle-persisted-scheduler-beans-tp4665596p4665606.html
> To unsubscribe from Default scheduler initialize error in case of oracle
> persisted scheduler beans, click here<
> http://openejb.979440.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4665596&code=dGhvbWFzLnNjaHVsZXJAb3BlbnRleHQuY29tfDQ2NjU1OTZ8LTE4NTIyNTQ0OTI=
> >.
> NAML<
> http://openejb.979440.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
> >
>
>
>
>
> --
> View this message in context:
> http://openejb.979440.n4.nabble.com/Default-scheduler-initialize-error-in-case-of-oracle-persisted-scheduler-beans-tp4665596p4665607.html
> Sent from the OpenEJB User mailing list archive at Nabble.com.
>
AW: Default scheduler initialize error in case of oracle persisted
scheduler beans
Posted by tschuler <th...@opentext.com>.
Hi Romain!
Do you mean the error I added in the attachment?
Here it is:
org.apache.openejb.OpenEJBException: Creating application failed: C:\Perforce\ps\ps\main\pkg\PS_TOMEE\PersistedSchedulerBeanOracleTest: Error deploying 'SchedulerBeanUnderTest'. Exception: class org.apache.openejb.OpenEJBRuntimeException: Fail to initialize the default scheduler: Fail to initialize the default scheduler
at org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:897)
at org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:613)
at org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:609)
at org.apache.openejb.testing.ApplicationComposers.before(ApplicationComposers.java:639)
at org.apache.openejb.testing.ApplicationComposers.evaluate(ApplicationComposers.java:722)
at org.apache.openejb.junit.ApplicationComposer$DeployApplication.evaluate(ApplicationComposer.java:64)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
Caused by: org.apache.openejb.OpenEJBException: Error deploying 'SchedulerBeanUnderTest'. Exception: class org.apache.openejb.OpenEJBRuntimeException: Fail to initialize the default scheduler: Fail to initialize the default scheduler
at org.apache.openejb.assembler.classic.Assembler.startEjbs(Assembler.java:1121)
at org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:805)
... 22 more
Caused by: org.apache.openejb.OpenEJBRuntimeException: Fail to initialize the default scheduler
at org.apache.openejb.core.timer.EjbTimerServiceImpl.getDefaultScheduler(EjbTimerServiceImpl.java:194)
at org.apache.openejb.core.timer.EjbTimerServiceImpl.start(EjbTimerServiceImpl.java:450)
at org.apache.openejb.core.singleton.SingletonContainer.deploy(SingletonContainer.java:118)
at org.apache.openejb.assembler.classic.Assembler.startEjbs(Assembler.java:1108)
... 23 more
Caused by: org.quartz.JobPersistenceException: Couldn't store job: ORA-08177: Zugriff für diese Transaktion kann nicht serialisiert werden
[See nested exception: java.sql.SQLException: ORA-08177: Zugriff für diese Transaktion kann nicht serialisiert werden
]
at org.quartz.impl.jdbcjobstore.JobStoreSupport.storeJob(JobStoreSupport.java:1117)
at org.quartz.impl.jdbcjobstore.JobStoreSupport$3.execute(JobStoreSupport.java:1089)
at org.quartz.impl.jdbcjobstore.JobStoreSupport$45.execute(JobStoreSupport.java:3705)
at org.quartz.impl.jdbcjobstore.JobStoreCMT.executeInLock(JobStoreCMT.java:245)
at org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInLock(JobStoreSupport.java:3701)
at org.quartz.impl.jdbcjobstore.JobStoreSupport.storeJob(JobStoreSupport.java:1085)
at org.quartz.core.QuartzScheduler.addJob(QuartzScheduler.java:999)
at org.quartz.core.QuartzScheduler.addJob(QuartzScheduler.java:988)
at org.quartz.impl.StdScheduler.addJob(StdScheduler.java:268)
at org.apache.openejb.core.timer.EjbTimerServiceImpl.getDefaultScheduler(EjbTimerServiceImpl.java:192)
... 26 more
Caused by: java.sql.SQLException: ORA-08177: Zugriff für diese Transaktion kann nicht serialisiert werden
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:450)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:399)
at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1017)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:655)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:249)
at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:566)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:215)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:58)
at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:943)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1075)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3820)
at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3897)
at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(OraclePreparedStatementWrapper.java:1361)
at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
at org.quartz.impl.jdbcjobstore.oracle.OracleDelegate.insertJobDetail(OracleDelegate.java:170)
at org.quartz.impl.jdbcjobstore.JobStoreSupport.storeJob(JobStoreSupport.java:1111)
... 35 more
Best regards,
Thomas
Von: Romain Manni-Bucau [via OpenEJB] [mailto:ml-node+s979440n4665606h96@n4.nabble.com]
Gesendet: Donnerstag, 17. Oktober 2013 14:08
An: Thomas Schuler
Betreff: Re: Default scheduler initialize error in case of oracle persisted scheduler beans
Hmm, I can't test against oracle :s. I didn't see the error in the thread
can you past it, maybe it will make some bell ringing to anyone.
*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2013/10/17 tschuler <[hidden email]</user/SendEmail.jtp?type=node&node=4665606&i=0>>
> Hi!
>
> I checked MSSQL database (works) and the TomEE internal hsql database
> (works too).
> I have no experiences with Mysql, sorry!
> So it seems to be a problem for oracle databases only - as far as I know
> independent from oracle database version and oracle jdbc driver version.
>
> Best regards,
> Thomas
>
>
> Von: Romain Manni-Bucau [via OpenEJB] [mailto:
> [hidden email]</user/SendEmail.jtp?type=node&node=4665606&i=1>]
> Gesendet: Donnerstag, 17. Oktober 2013 12:52
> An: Thomas Schuler
> Betreff: Re: Default scheduler initialize error in case of oracle
> persisted scheduler beans
>
> Hi
>
> is it linked to the db or does it behave the same way with mysql/hsqldb?
>
> *Romain Manni-Bucau*
> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> *Blog: **http://rmannibucau.wordpress.com/*<
> http://rmannibucau.wordpress.com/>
> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> *Github: https://github.com/rmannibucau*
>
>
>
> 2013/10/16 tschuler <[hidden
> email]</user/SendEmail.jtp?type=node&node=4665604&i=0>>
>
> > Hi!
> >
> > We are using latest TomEE 1.6.0 snapshot and try to persist scheduled
> beans
> > in an oracle database.
> > The TomEE startup fails because the default scheduler cannot be
> > initialized.
> >
> > Attached zip ( DefaultSchedulerInitializeError.zip
> > <
> >
> http://openejb.979440.n4.nabble.com/file/n4665596/DefaultSchedulerInitializeError.zip
> > >
> > ) includes the error message and simple tests for scheduler
> > initializations:
> >
> > - PersistedSchedulerBeanOracleTest.java: demonstrates failed startup for
> > oracle database
> > - PersistedSchedulerBeanMSSQLTest.java: demonstrates successful startup
> for
> > mssql database
> > - SchedulerBeanUnderTest.java: (needed as @Module and for further tests)
> > - DefaultSchedulerInitializeError.txt: Server startup exception while
> > default scheduler initialization
> >
> > To make the tests running an oracle/mssql database and an oracle/mssql
> jdbc
> > driver (ojdbc6.jar/sqljdbc4.jar) are needed, also URL, USERNAME and
> > PASSWORD
> > in Testclasses must be adapted.
> > The test creates the needed quartz tables while startup and deletes them
> > while shutdown. A simple test case (that does nothing right now) enforces
> > the server startup.
> >
> > Can you give a hint why default scheduler cannot be initialized while
> > server
> > startup?
> >
> > Best regards,
> > Thomas
> >
> >
> >
> >
> > --
> > View this message in context:
> >
> http://openejb.979440.n4.nabble.com/Default-scheduler-initialize-error-in-case-of-oracle-persisted-scheduler-beans-tp4665596.html
> > Sent from the OpenEJB User mailing list archive at Nabble.com.
> >
>
> ________________________________
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://openejb.979440.n4.nabble.com/Default-scheduler-initialize-error-in-case-of-oracle-persisted-scheduler-beans-tp4665596p4665604.html
> To unsubscribe from Default scheduler initialize error in case of oracle
> persisted scheduler beans, click here<
> >.
> NAML<
> http://openejb.979440.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
> >
>
>
>
>
> --
> View this message in context:
> http://openejb.979440.n4.nabble.com/Default-scheduler-initialize-error-in-case-of-oracle-persisted-scheduler-beans-tp4665596p4665605.html
> Sent from the OpenEJB User mailing list archive at Nabble.com.
>
________________________________
If you reply to this email, your message will be added to the discussion below:
http://openejb.979440.n4.nabble.com/Default-scheduler-initialize-error-in-case-of-oracle-persisted-scheduler-beans-tp4665596p4665606.html
To unsubscribe from Default scheduler initialize error in case of oracle persisted scheduler beans, click here<http://openejb.979440.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4665596&code=dGhvbWFzLnNjaHVsZXJAb3BlbnRleHQuY29tfDQ2NjU1OTZ8LTE4NTIyNTQ0OTI=>.
NAML<http://openejb.979440.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
--
View this message in context: http://openejb.979440.n4.nabble.com/Default-scheduler-initialize-error-in-case-of-oracle-persisted-scheduler-beans-tp4665596p4665607.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: Default scheduler initialize error in case of oracle persisted
scheduler beans
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hmm, I can't test against oracle :s. I didn't see the error in the thread
can you past it, maybe it will make some bell ringing to anyone.
*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2013/10/17 tschuler <th...@opentext.com>
> Hi!
>
> I checked MSSQL database (works) and the TomEE internal hsql database
> (works too).
> I have no experiences with Mysql, sorry!
> So it seems to be a problem for oracle databases only - as far as I know
> independent from oracle database version and oracle jdbc driver version.
>
> Best regards,
> Thomas
>
>
> Von: Romain Manni-Bucau [via OpenEJB] [mailto:
> ml-node+s979440n4665604h34@n4.nabble.com]
> Gesendet: Donnerstag, 17. Oktober 2013 12:52
> An: Thomas Schuler
> Betreff: Re: Default scheduler initialize error in case of oracle
> persisted scheduler beans
>
> Hi
>
> is it linked to the db or does it behave the same way with mysql/hsqldb?
>
> *Romain Manni-Bucau*
> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> *Blog: **http://rmannibucau.wordpress.com/*<
> http://rmannibucau.wordpress.com/>
> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> *Github: https://github.com/rmannibucau*
>
>
>
> 2013/10/16 tschuler <[hidden
> email]</user/SendEmail.jtp?type=node&node=4665604&i=0>>
>
> > Hi!
> >
> > We are using latest TomEE 1.6.0 snapshot and try to persist scheduled
> beans
> > in an oracle database.
> > The TomEE startup fails because the default scheduler cannot be
> > initialized.
> >
> > Attached zip ( DefaultSchedulerInitializeError.zip
> > <
> >
> http://openejb.979440.n4.nabble.com/file/n4665596/DefaultSchedulerInitializeError.zip
> > >
> > ) includes the error message and simple tests for scheduler
> > initializations:
> >
> > - PersistedSchedulerBeanOracleTest.java: demonstrates failed startup for
> > oracle database
> > - PersistedSchedulerBeanMSSQLTest.java: demonstrates successful startup
> for
> > mssql database
> > - SchedulerBeanUnderTest.java: (needed as @Module and for further tests)
> > - DefaultSchedulerInitializeError.txt: Server startup exception while
> > default scheduler initialization
> >
> > To make the tests running an oracle/mssql database and an oracle/mssql
> jdbc
> > driver (ojdbc6.jar/sqljdbc4.jar) are needed, also URL, USERNAME and
> > PASSWORD
> > in Testclasses must be adapted.
> > The test creates the needed quartz tables while startup and deletes them
> > while shutdown. A simple test case (that does nothing right now) enforces
> > the server startup.
> >
> > Can you give a hint why default scheduler cannot be initialized while
> > server
> > startup?
> >
> > Best regards,
> > Thomas
> >
> >
> >
> >
> > --
> > View this message in context:
> >
> http://openejb.979440.n4.nabble.com/Default-scheduler-initialize-error-in-case-of-oracle-persisted-scheduler-beans-tp4665596.html
> > Sent from the OpenEJB User mailing list archive at Nabble.com.
> >
>
> ________________________________
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://openejb.979440.n4.nabble.com/Default-scheduler-initialize-error-in-case-of-oracle-persisted-scheduler-beans-tp4665596p4665604.html
> To unsubscribe from Default scheduler initialize error in case of oracle
> persisted scheduler beans, click here<
> http://openejb.979440.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4665596&code=dGhvbWFzLnNjaHVsZXJAb3BlbnRleHQuY29tfDQ2NjU1OTZ8LTE4NTIyNTQ0OTI=
> >.
> NAML<
> http://openejb.979440.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
> >
>
>
>
>
> --
> View this message in context:
> http://openejb.979440.n4.nabble.com/Default-scheduler-initialize-error-in-case-of-oracle-persisted-scheduler-beans-tp4665596p4665605.html
> Sent from the OpenEJB User mailing list archive at Nabble.com.
>
AW: Default scheduler initialize error in case of oracle persisted
scheduler beans
Posted by tschuler <th...@opentext.com>.
Hi!
I checked MSSQL database (works) and the TomEE internal hsql database (works too).
I have no experiences with Mysql, sorry!
So it seems to be a problem for oracle databases only - as far as I know independent from oracle database version and oracle jdbc driver version.
Best regards,
Thomas
Von: Romain Manni-Bucau [via OpenEJB] [mailto:ml-node+s979440n4665604h34@n4.nabble.com]
Gesendet: Donnerstag, 17. Oktober 2013 12:52
An: Thomas Schuler
Betreff: Re: Default scheduler initialize error in case of oracle persisted scheduler beans
Hi
is it linked to the db or does it behave the same way with mysql/hsqldb?
*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2013/10/16 tschuler <[hidden email]</user/SendEmail.jtp?type=node&node=4665604&i=0>>
> Hi!
>
> We are using latest TomEE 1.6.0 snapshot and try to persist scheduled beans
> in an oracle database.
> The TomEE startup fails because the default scheduler cannot be
> initialized.
>
> Attached zip ( DefaultSchedulerInitializeError.zip
> <
> http://openejb.979440.n4.nabble.com/file/n4665596/DefaultSchedulerInitializeError.zip
> >
> ) includes the error message and simple tests for scheduler
> initializations:
>
> - PersistedSchedulerBeanOracleTest.java: demonstrates failed startup for
> oracle database
> - PersistedSchedulerBeanMSSQLTest.java: demonstrates successful startup for
> mssql database
> - SchedulerBeanUnderTest.java: (needed as @Module and for further tests)
> - DefaultSchedulerInitializeError.txt: Server startup exception while
> default scheduler initialization
>
> To make the tests running an oracle/mssql database and an oracle/mssql jdbc
> driver (ojdbc6.jar/sqljdbc4.jar) are needed, also URL, USERNAME and
> PASSWORD
> in Testclasses must be adapted.
> The test creates the needed quartz tables while startup and deletes them
> while shutdown. A simple test case (that does nothing right now) enforces
> the server startup.
>
> Can you give a hint why default scheduler cannot be initialized while
> server
> startup?
>
> Best regards,
> Thomas
>
>
>
>
> --
> View this message in context:
> http://openejb.979440.n4.nabble.com/Default-scheduler-initialize-error-in-case-of-oracle-persisted-scheduler-beans-tp4665596.html
> Sent from the OpenEJB User mailing list archive at Nabble.com.
>
________________________________
If you reply to this email, your message will be added to the discussion below:
http://openejb.979440.n4.nabble.com/Default-scheduler-initialize-error-in-case-of-oracle-persisted-scheduler-beans-tp4665596p4665604.html
To unsubscribe from Default scheduler initialize error in case of oracle persisted scheduler beans, click here<http://openejb.979440.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4665596&code=dGhvbWFzLnNjaHVsZXJAb3BlbnRleHQuY29tfDQ2NjU1OTZ8LTE4NTIyNTQ0OTI=>.
NAML<http://openejb.979440.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
--
View this message in context: http://openejb.979440.n4.nabble.com/Default-scheduler-initialize-error-in-case-of-oracle-persisted-scheduler-beans-tp4665596p4665605.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: Default scheduler initialize error in case of oracle persisted
scheduler beans
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hi
is it linked to the db or does it behave the same way with mysql/hsqldb?
*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2013/10/16 tschuler <th...@opentext.com>
> Hi!
>
> We are using latest TomEE 1.6.0 snapshot and try to persist scheduled beans
> in an oracle database.
> The TomEE startup fails because the default scheduler cannot be
> initialized.
>
> Attached zip ( DefaultSchedulerInitializeError.zip
> <
> http://openejb.979440.n4.nabble.com/file/n4665596/DefaultSchedulerInitializeError.zip
> >
> ) includes the error message and simple tests for scheduler
> initializations:
>
> - PersistedSchedulerBeanOracleTest.java: demonstrates failed startup for
> oracle database
> - PersistedSchedulerBeanMSSQLTest.java: demonstrates successful startup for
> mssql database
> - SchedulerBeanUnderTest.java: (needed as @Module and for further tests)
> - DefaultSchedulerInitializeError.txt: Server startup exception while
> default scheduler initialization
>
> To make the tests running an oracle/mssql database and an oracle/mssql jdbc
> driver (ojdbc6.jar/sqljdbc4.jar) are needed, also URL, USERNAME and
> PASSWORD
> in Testclasses must be adapted.
> The test creates the needed quartz tables while startup and deletes them
> while shutdown. A simple test case (that does nothing right now) enforces
> the server startup.
>
> Can you give a hint why default scheduler cannot be initialized while
> server
> startup?
>
> Best regards,
> Thomas
>
>
>
>
> --
> View this message in context:
> http://openejb.979440.n4.nabble.com/Default-scheduler-initialize-error-in-case-of-oracle-persisted-scheduler-beans-tp4665596.html
> Sent from the OpenEJB User mailing list archive at Nabble.com.
>