Banujee,

without any more information (e.g. a complete stack trace that shows where
in the Castor code things go wrong), it is going to be pretty impossible to
help you any further.

FYI, the deadlock situation can be a 'correct' one, especially when trying
to update the same physical record from within multiple transactions. And by
the looks of your descriptions it seesm that you are indeed 'artificially'
creating some random load on your system for test purpose.

Regards
Werner

> 
> Hi,
> 
>       Plz. help with a soultion for the below said problem.
>       
>       A deadlock found in a multi-transaction scenario (minimum 10
> processes(JVM) executed concurrently)
>       when same operation each using different transaction is executed
> on the different processes (JVM) at same time,
>       resulted in a deadlock. The  operation uses the same
> relation(table) to record history for each process.
>       
>       fatal error occurred during an insert, Find below traces:
>       
>       Sep 2, 2004 6:43:50 PM org.exolab.castor.jdo.engine.SQLEngine
> create
>       SEVERE: A fatal error occurred while creating
> com.stortek.indigo.scheduler.domainObjects.ActivityHis
>       tory using SQL: INSERT INTO ACTIVITY_HISTORY
> (ACTIVITY_ID,ACTIVITY_HISTORY_OLD_STATE_ID,ACTIVITY_HISTORY_NEW_STATE_ID
> ,ACTIVITY_HISTORY_DATETIME,ACTIVITY_HISTORY_COMMENT,ACTIVITY_HISTORY_ACT
> OR) VALUES (?,?,?,?,?,?)
>       
>       Sep 2, 2004 6:43:50 PM
> com.stortek.indigo.scheduler.domainObjects.Activity retrieve
>       INFO: number of activities histories retrieved --->[106, 106]
>       Sep 2, 2004 6:43:50 PM
> com.stortek.indigo.scheduler.domainObjects.Activity retrieve
>       INFO: filtered activities::[106]
>       Sep 2, 2004 6:43:50 PM
> com.stortek.indigo.scheduler.domainObjects.Activity retrieve
>       INFO: Activity ID : 106 :: State : Suspended
>       Sep 2, 2004 6:43:50 PM
> com.stortek.indigo.scheduler.SchedulerController completeActivity
>       WARNING: EXCEPTION:
> com.stortek.indigo.exceptions.infrastructure.persistence.DbPersistenceEx
> ception:
> 
> com.stortek.indigo.exceptions.infrastructure.persistence..DbPersistenceE
> xception(org.exolab.castor.jdo.PersistenceException: Nested error:
> java.sql.SQLException: Deadlock found when trying to get lock; Try
> restarting transaction,  message from server: "Deadlock found when
> trying to get lock; Try restarting transaction")
>               at
> com.stortek.indigo.infrastructure.persistence.CastorDAO.daoErrorHandler(
> CastorDAO.java:230)
>               at
> com.stortek.indigo.infrastructure.persistence.CastorDAO.create(CastorDAO
> .java:101)
>               at
> com.stortek.indigo.scheduler.domainObjects.ActivityHistory.create(Activi
> tyHistory.java:205)
>               at
> com.stortek.indigo.scheduler.domainObjects.Activity.setState(Activity.ja
> va:725)
>               at
> com.stortek.indigo.scheduler.SchedulerController.completeActivity(Schedu
> lerController.java:946)
>               at
> com.stortek.indigo.objectStoreMetadata.domainObjects.OSActivity.complete
> (OSActivity.java:1476)
>               at
> com.stortek.indigo.objectStoreMetadata.OSDBIFController.completePrimaryI
> O(OSDBIFController.java:2085)
>               at
> com.stortek.indigo.objectStoreMetadata.kernalDBIF.OSDBIFCompletePrimaryI
> O..execute(OSDBIFCompletePrimaryIO.java:82)
>               at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
>               at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
> a:39)
>               at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
> Impl.java:25)
>               at java.lang.reflect.Method.invoke(Method.java:324)
>               at
> com.stortek.indigo.infrastructure.rmi.IndigoHandler.run(IndigoHandler.ja
> va:130)
>       Sep 2, 2004 6:43:50 PM
> com.stortek.indigo.scheduler.domainObjects.Activity
> sortActivityListINFO: value of all the history records::
>       
>       
>       Rgds,
>       Banujee KrishnaMurthy
>       
>       
> 
> 
> 
> Confidentiality Notice
> 
> The information contained in this electronic message and any attachments
> to this message are intended
> for the exclusive use of the addressee(s) and may contain confidential
> or privileged information. If
> you are not the intended recipient, please notify the sender at Wipro or
> [EMAIL PROTECTED] immediately
> and destroy all copies of this message and any attachments.
> 
> 
> 
> 
> 
> 
> Confidentiality Notice
> 
> The information contained in this electronic message and any attachments
> to this message are intended
> for the exclusive use of the addressee(s) and may contain confidential or
> privileged information. If
> you are not the intended recipient, please notify the sender at Wipro or
> [EMAIL PROTECTED] immediately
> and destroy all copies of this message and any attachments.

-- 
+++ GMX DSL Premiumtarife 3 Monate gratis* + WLAN-Router 0,- EUR* +++
Clevere DSL-Nutzer wechseln jetzt zu GMX: http://www.gmx.net/de/go/dsl



----------------------------------------------------------- 
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
        unsubscribe castor-user

Reply via email to