stack trace indicates that the code is still getting called. You'd want to
remove the setTransactionIsolation call in jobstoreJTA
-mbs
On 2/2/07, Raja Balasubramanian/MAXIMUS <[EMAIL PROTECTED]>
wrote:
Hi Maciej,
Thank you for the fast response.
I made a build with the code changes. Now ode fails to start and forces
Geronimo to close immediately.
It throws exception as
====================
15:30:34,619 DEBUG [BpelServerImpl] BPEL SERVER initializing
15:30:34,651 DEBUG [BpelServerImpl] BPEL SERVER starting.
15:30:34,651 DEBUG [NotSoSimpleSemaphore] Lock 'TRIGGER_ACCESS' is desired
by: ODE_QuartzSchedulerThread
15:30:34,651 DEBUG [NotSoSimpleSemaphore] Lock 'TRIGGER_ACCESS' is being
obtained: ODE_QuartzSchedulerThread
15:30:34,651 DEBUG [NotSoSimpleSemaphore] Lock 'TRIGGER_ACCESS' given to:
ODE_QuartzSchedulerThread
15:30:34,651 DEBUG [NotSoSimpleSemaphore] Lock 'JOB_ACCESS' is desired by:
ODE_QuartzSchedulerThread
15:30:34,651 DEBUG [NotSoSimpleSemaphore] Lock 'JOB_ACCESS' is being
obtained: ODE_QuartzSchedulerThread
15:30:34,651 DEBUG [NotSoSimpleSemaphore] Lock 'JOB_ACCESS' given to:
ODE_QuartzSchedulerThread
15:30:34,651 DEBUG [JobStoreJTA] prepareStmt: UPDATE QRTZ_TRIGGERS SET
TRIGGER_STATE = ? WHERE (TRIGGER_STATE = ? OR TRIGGER_STATE = ?) AND
NEXT_FIRE_TIME < ?
15:30:34,651 DEBUG [JobStoreJTA] prepareStmt: UPDATE QRTZ_TRIGGERS SET
TRIGGER_STATE = ? WHERE (TRIGGER_STATE = ? OR TRIGGER_STATE = ?) AND
NEXT_FIRE_TIME < ?
15:30:34,651 DEBUG [JobStoreJTA] prepareStmt: SELECT MIN(NEXT_FIRE_TIME)
AS ALIAS_NXT_FR_TM FROM QRTZ_TRIGGERS WHERE TRIGGER_STATE = ? AND
NEXT_FIRE_TIME >= 0
15:30:34,651 DEBUG [JobStoreJTA] prepareStmt: SELECT MIN(NEXT_FIRE_TIME)
AS ALIAS_NXT_FR_TM FROM QRTZ_TRIGGERS WHERE TRIGGER_STATE = ? AND
NEXT_FIRE_TIME >= 0
15:30:34,651 DEBUG [NotSoSimpleSemaphore] Lock 'TRIGGER_ACCESS' retuned
by: ODE_QuartzSchedulerThread
15:30:34,651 DEBUG [NotSoSimpleSemaphore] Lock 'JOB_ACCESS' retuned by:
ODE_QuartzSchedulerThread
15:30:34,651 DEBUG [JobStoreJTA] close
15:30:34,651 DEBUG [JobStoreJTA] close
15:30:34,651 WARN [GeronimoConnectionEventListener]
connectionErrorOccurred called with null
java.sql.SQLException: ORA-01453: SET TRANSACTION must be first statement
of transaction
at
oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:743)
at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:207)
at
oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:946)
at
oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.ja
va:1168)
at
oracle.jdbc.driver.OracleStatement.executeInternal(OracleStatement.java:16
87)
at
oracle.jdbc.driver.OracleStatement.execute(OracleStatement.java:1653)
at
oracle.jdbc.driver.PhysicalConnection.setTransactionIsolation(PhysicalConn
ection.java:1591)
at
org.tranql.connector.jdbc.ConnectionHandle.setTransactionIsolation(Connect
ionHandle.java:381)
at
org.apache.ode.utils.LoggingConnectionWrapper.setTransactionIsolation(Logg
ingConnectionWrapper.java:194)
at
org.apache.ode.bpel.scheduler.quartz.JobStoreJTA.getNonManagedTXConnection
(JobStoreJTA.java:1298)
at
org.apache.ode.bpel.scheduler.quartz.JobStoreJTA.recoverJobs(JobStoreJTA.j
ava:100)
at
org.quartz.impl.jdbcjobstore.JobStoreSupport.schedulerStarted(JobStoreSupp
ort.java:510)
at org.quartz.core.QuartzScheduler.start(QuartzScheduler.java:396)
at org.quartz.impl.StdScheduler.start(StdScheduler.java:147)
at
org.apache.ode.bpel.scheduler.quartz.QuartzSchedulerImpl.start(QuartzSched
ulerImpl.java:152)
at
org.apache.ode.bpel.engine.BpelServerImpl.start(BpelServerImpl.java:117)
at org.apache.ode.axis2.ODEServer.init(ODEServer.java:149)
====================
Thank you
Raja
-----Original Message-----
From: Maciej Szefler [mailto:[EMAIL PROTECTED]
Sent: Friday, February 02, 2007 2:55 PM
To: [email protected]
Subject: Re: Using ODE with ORACLE and Geronimo
Raja,
You may have not hit that part of the code path before. It appears to be
be
a bug inherted from quartz job store implementation. I believe it should
have been trying to set the isolation level to READ_COMMITTED, but it was
setting to READ_UNCOMMITTED (whichis not supported by ORacle). Fixed in
svn.
-mbs
On 2/2/07, Raja Balasubramanian/MAXIMUS <[EMAIL PROTECTED]>
wrote:
>
> Hello,
>
> I got the latest code base. Compiled.
> Created a new Oracle Connection Pool.
> When I tried to deploy ODE, getting exception.
> " java.sql.SQLException: READ_COMMITTED and SERIALIZABLE are the only
> valid transaction levels"
>
> This is happening at JobStoreJTA.java Line#1293
>
> I didn't get the exception in my old code base (Dated 1/16/2007)
>
> How to solve this?
>
> Thank you
>
> Raja
>
> -----Original Message-----
> From: Maciej Szefler [mailto:[EMAIL PROTECTED]
> Sent: Friday, February 02, 2007 11:48 AM
> To: [email protected]
> Subject: Re: Using ODE with ORACLE and Geronimo
>
> Raja,
>
> This looks like a deadlock issue. Also if you could, (a) set oracle's
> deadlock timeout to some short period (5 sec) and run to see what
happens,
> or (b) query oracle's lock table once the system hangs and include the
> output. Also if you run with logging at the debug level (esp wrt to
> hibernate SQL calls), the output could be very helpful. Also, it'd be
best
> if you file an issue for this.
>
> Thanks,
> -mbs
>
> On 2/2/07, Raja Balasubramanian/MAXIMUS
<[EMAIL PROTECTED]>
> wrote:
> >
> > Hi All,
> >
> > I'm trying to use ODE in Geronimo with ORACLE 10g as back end.
> > ODE in Geronimo with MySQL works like a charm.
> >
> > I have created ORACLE schema and created a connection pool for that
and
> > mapped in web.xml and geronimo-web.xml.
> >
> > ODE deployment went fine and BPEL deployments went fine.
> > But when I invoke a process (which calls another web service), it just
> > hangs. No exceptions, but waiting for something indefinitely.
> >
> > Anybody faced this problem?
> > Could somebody show me how to overcome this?
> >
> > Thank you
> >
> > Raja
> >
>
