Thread safety for synchronization process

Question

We are invoking multiple instance of our
application and attempt to issue synchronization calls simultaneously in order
to perform some load testing.
Is the Oracle lite synchronization process thread safe? Does anyone have
recommendation on how to perform concurrent synchronization from the same
computer?
We recieve following exception:
System.AccessViolationException {"Attempted to read or write protected memory.
This is often an indication that other memory is corrupt."}
StackTrace
at Oracle.DataAccess.Lite.OracleSync.netSynchronize(IntPtr hWnd, Int32 nMsg)
at Oracle.DataAccess.Lite.OracleSync.Synchronize()
at Point2.CCIPDA.Core.Data.Database.SynchronizeThread() in
X:\CCIPDA_2_0\src\Core\Data\Database.cs:line 325
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext,
ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

Answer 1

Did you have a windows form or a web based application? Did you use LoadRunner to invoke multiple concurrent synchronization calls to move data from the lite database to the back-end database? Also, was LoadRunner executing against one instance of your application or multiple instances? Were application instances running on one machine or multiple machines? We are just trying to get a better understanding of your application/load test setup and see if it was structurally similar to ours.
We basically have a windows form based application designed for a single user. This application allows user to synchronize data from Olite to back-end Oracle database after user has completed their data entry.
We wanted to test the performance of our synchronization process. That is how many user can concurrently synchronize their data at the same time.
Given that our application is a single user application, we decided to invoke multiple instances of application on a single machine and then simultaneously try to synchronize (via a tool) each instance of the application. Hence the error.
Thanks for your feedback.