Eclipse Community Forums: Eclipse Process Manager (Stardust) » IPP 5.3.4 resource busy and acquire with NOWAIT specified or timeout expired

Home » Eclipse Projects » Eclipse Process Manager (Stardust) » IPP 5.3.4 resource busy and acquire with NOWAIT specified or timeout expired

Show: Today's Messages :: Show Polls :: Message Navigator

IPP 5.3.4 resource busy and acquire with NOWAIT specified or timeout expired [message #930945]

Tue, 02 October 2012 15:41

Rahim Kanjiyani
Messages: 7
Registered: October 2012

Junior Member

Hi,

We are using IPP 5.3.4 in production environment. We have a timer activity which runs every 3 minutes. Occasionally, IPP throws following error which stops timer daemon. Any idea? Our integration stops running becasue of this error. The solution is to restart the daemon manually. Thanks.

26 Jul 2012 00:01:10 WARN - [Thread-275383 ] ApplicationException - BPMRT03601 - Concurrent attempt to lock object of type class ag.carnot.workflow.runtime.beans.daemons.DaemonLog with OID 2, row not selected.
java.sql.SQLException: ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired

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:745)
at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:210)
at oracle.jdbc.driver.T4CStatement.executeForDescribe(T4CStatement.java:804)
at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1049)
at oracle.jdbc.driver.T4CStatement.executeMaybeDescribe(T4CStatement.java:845)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1154)
at oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:1313)
at org.tranql.connector.jdbc.StatementHandle.executeQuery(StatementHandle.java:49)
at ag.carnot.db.jdbc.Session.executeLockQuery(Session.java:2326)
at ag.carnot.db.jdbc.Session.lock(Session.java:2900)
at ag.carnot.db.jdbc.IdentifiablePersistentBean.lock(IdentifiablePersistentBean.java:50)
at ag.carnot.workflow.runtime.beans.daemons.DaemonAction$ExecuteDaemonAction.lock(DaemonAction....

Report message to a moderator

Re: IPP 5.3.4 resource busy and acquire with NOWAIT specified or timeout expired [message #931370 is a reply to message #930945]

Wed, 03 October 2012 02:05

Shyam Prakash
Messages: 11
Registered: June 2012

Junior Member

What does this timer do? Can it so happen that it executes for more than 3 minutes and a new timer process is kicked off? Also, what is the value of useLockTables in carnot.properties? One of the workaround that I can suggest is to have a cron job which checks the status of this timer daemon. If the daemon is down, then start it automatically. This is quite simple to achieve using shell scripts and IPP console command.

~Shyam

Report message to a moderator

Re: IPP 5.3.4 resource busy and acquire with NOWAIT specified or timeout expired [message #949482 is a reply to message #931370]

Thu, 18 October 2012 22:39

Robert Emsbach
Messages: 56
Registered: October 2011
Location: Shanghai

Member

Florian, which version is this. We have stabilized the daemon further in several releases.
In a spring deployment this is an option:
http://wiki.eclipse.org/STP/Stardust/KnowledgeBase/SystemAdministration/Daemons/DaemonWatchdog

Report message to a moderator

Re: IPP 5.3.4 resource busy and acquire with NOWAIT specified or timeout expired [message #968888 is a reply to message #949482]

Fri, 02 November 2012 16:57

Rahim Kanjiyani
Messages: 7
Registered: October 2012

Junior Member

I am sorry that it took me so long to reply. I never received any notification on this.

To answer your questions,

1. Can it so happen that it executes for more than 3 minutes and a new timer process is kicked off?

This might be possible. Will it help if the interval is set to 5 minutes?

2. What is the value of useLockTables in carnot.properties

AuditTrail.UseLockTables is set to false

3. which version is this?

This is happening in IPP 5.3.4. Can you provide more details on how to implement Daemonwatchdog?

Report message to a moderator

Re: IPP 5.3.4 resource busy and acquire with NOWAIT specified or timeout expired [message #969286 is a reply to message #968888]

Sat, 03 November 2012 00:49

Robert Emsbach
Messages: 56
Registered: October 2011
Location: Shanghai

Member

1. might, but you should avoid to have such a long running transaction.
why is that required? Any way to implement this asynchronously?

2. Should stay false for Oracle

3. Have you seen the wiki article? What other information do you require?

Report message to a moderator

Previous Topic:	Eclipse Plugin Installation IPP 7.0.1
Next Topic:	Oracle "OAUTH marshalling failure" calling sysconsole command

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sat May 25 20:20:52 EDT 2013