WFTools Work Item Rss Feed

Commented Issue: DbParamter can't be converted to MySqlParamter

ksteenkamp — Fri, 28 Aug 2009 11:38:50 GMT

Changeset 15876

In function PopulateType(DbParameter dbParameter, AdoDbType type) why is the dbParamter trying to be cast as a MySqlParameter to get the DbType? In function PopulateValue(DbParameter dbParameter, object value) it doesn't do this conversion. I am getting the error that dbParameter can't be converted to MySqlParameter and so the function throws an exception.
Comments: ** Comment from web user: ksteenkamp **

Sorry...

if (type == AdoDbType.Guid)
{
base.PopulateType(dbParameter, AdoDbType.String);
}
else
{
base.PopulateType(dbParameter, type);
}

Commented Issue: DbParamter can't be converted to MySqlParamter

ksteenkamp — Fri, 28 Aug 2009 11:27:59 GMT

Hi,

I too got this error. I am using MySql.
WFTools seems to be very work in progress... this might fix your problem...
Guid is not spported in mySQL and the offending method is meant to convert an incoming guid type to a string.

In the WFTools.Services.MySql poject, MySqlResourceProvider overrides DefaultAdoResourceProvider

I modified the code and recompiled the WFTools.Services.MySql assembly.

OLD:
protected override void PopulateType(DbParameter dbParameter, AdoDbType type)
{
MySqlParameter mySqlParameter = dbParameter as MySqlParameter;
if (mySqlParameter == null)
throw new ArgumentException(RM.Get_Error_MySqlParameterExpected());

if (type == AdoDbType.Guid)
mySqlParameter.DbType = DbType.String;
}

NEW: (note I call base method as well, previous method seems to do nothing???)

protected override void PopulateType(DbParameter dbParameter, AdoDbType type)
{
if (type == AdoDbType.Guid)
dbParameter.DbType = DbType.String;
else
base.PopulateType(dbParameter, type);
}

The problem went away, but the workflow doesnt seem to be persisting.

Created Issue: Windows Workflow Foundation persistence service for Oracle

wrvasquez — Fri, 24 Jul 2009 01:36:55 GMT

Hi,

I want to use WFT for percistence ORACLE, but I have a problem with de example. The track that show is the following:

GenericPersistenceService::LoadExpiredWorkflowIds
GenericPersistenceService::LoadExpiredWorkflowIds
Workflow 22074fdb-0dd3-44c8-85c6-05a73408752d: Aborted
GenericPersistenceService::Complete
AdoWorkBatchService::WorkBatchRolledback
Workflow Runtime: Service Exception - WFTools.Services.Persistence.PersistenceException: An unexpected exception occurred while performing a workflow persistence operation. System.InvalidOperationException: No se ha podido inscribir en una transacción distribuida
en Oracle.DataAccess.Client.OracleConnection.EnlistTransaction(Transaction transaction)
en WFTools.Services.Common.Ado.DefaultAdoResourceProvider.CreateEnlistedConnection(Transaction transaction, Boolean& shouldClose) en C:\Users\Usuario\Downloads\WFTools-v0.3.0.0\Services\Common\Ado\DefaultAdoResourceProvider.cs:línea 107
en WFTools.Services.Batching.Ado.AdoWorkBatchService.AdoResourceProviderWrapper.CreateEnlistedConnection(Transaction transaction, Boolean& shouldClose) en C:\Users\Usuario\Downloads\WFTools-v0.3.0.0\Services\Batching\Ado\AdoWorkBatchService.cs:línea 445
en WFTools.Services.Persistence.Ado.AdoPersistenceResourceAccessor..ctor(IAdoResourceProvider resourceProvider, IPersistenceNameResolver nameResolver, IAdoValueReader valueReader, Transaction transaction) en C:\Users\Usuario\Downloads\WFTools-v0.3.0.0\Services\Persistence\Ado\AdoPersistenceResourceAccessor.cs:línea 85
en WFTools.Services.Persistence.Ado.AdoPersistenceService.CreateAccessor(IResourceProvider resourceProvider, Transaction transaction) en C:\Users\Usuario\Downloads\WFTools-v0.3.0.0\Services\Persistence\Ado\AdoPersistenceService.cs:línea 162
en WFTools.Services.Persistence.GenericPersistenceService.Commit(Transaction transaction, ICollection items) en C:\Users\Usuario\Downloads\WFTools-v0.3.0.0\Services\Persistence\GenericPersistenceService.cs:línea 680 ---> System.InvalidOperationException: No se ha podido inscribir en una transacción distribuida
en Oracle.DataAccess.Client.OracleConnection.EnlistTransaction(Transaction transaction)
en WFTools.Services.Common.Ado.DefaultAdoResourceProvider.CreateEnlistedConnection(Transaction transaction, Boolean& shouldClose) en C:\Users\Usuario\Downloads\WFTools-v0.3.0.0\Services\Common\Ado\DefaultAdoResourceProvider.cs:línea 107
en WFTools.Services.Batching.Ado.AdoWorkBatchService.AdoResourceProviderWrapper.CreateEnlistedConnection(Transaction transaction, Boolean& shouldClose) en C:\Users\Usuario\Downloads\WFTools-v0.3.0.0\Services\Batching\Ado\AdoWorkBatchService.cs:línea 445
en WFTools.Services.Persistence.Ado.AdoPersistenceResourceAccessor..ctor(IAdoResourceProvider resourceProvider, IPersistenceNameResolver nameResolver, IAdoValueReader valueReader, Transaction transaction) en C:\Users\Usuario\Downloads\WFTools-v0.3.0.0\Services\Persistence\Ado\AdoPersistenceResourceAccessor.cs:línea 85
en WFTools.Services.Persistence.Ado.AdoPersistenceService.CreateAccessor(IResourceProvider resourceProvider, Transaction transaction) en C:\Users\Usuario\Downloads\WFTools-v0.3.0.0\Services\Persistence\Ado\AdoPersistenceService.cs:línea 162
en WFTools.Services.Persistence.GenericPersistenceService.Commit(Transaction transaction, ICollection items) en C:\Users\Usuario\Downloads\WFTools-v0.3.0.0\Services\Persistence\GenericPersistenceService.cs:línea 680
--- Fin del seguimiento de la pila de la excepción interna ---
GenericPersistenceService::Commit - An unexpected exception occurred while performing a workflow persistence operation. System.InvalidOperationException: No se ha podido inscribir en una transacción distribuida
en Oracle.DataAccess.Client.OracleConnection.EnlistTransaction(Transaction transaction)
en WFTools.Services.Common.Ado.DefaultAdoResourceProvider.CreateEnlistedConnection(Transaction transaction, Boolean& shouldClose) en C:\Users\Usuario\Downloads\WFTools-v0.3.0.0\Services\Common\Ado\DefaultAdoResourceProvider.cs:línea 107
en WFTools.Services.Batching.Ado.AdoWorkBatchService.AdoResourceProviderWrapper.CreateEnlistedConnection(Transaction transaction, Boolean& shouldClose) en C:\Users\Usuario\Downloads\WFTools-v0.3.0.0\Services\Batching\Ado\AdoWorkBatchService.cs:línea 445
en WFTools.Services.Persistence.Ado.AdoPersistenceResourceAccessor..ctor(IAdoResourceProvider resourceProvider, IPersistenceNameResolver nameResolver, IAdoValueReader valueReader, Transaction transaction) en C:\Users\Usuario\Downloads\WFTools-v0.3.0.0\Services\Persistence\Ado\AdoPersistenceResourceAccessor.cs:línea 85
en WFTools.Services.Persistence.Ado.AdoPersistenceService.CreateAccessor(IResourceProvider resourceProvider, Transaction transaction) en C:\Users\Usuario\Downloads\WFTools-v0.3.0.0\Services\Persistence\Ado\AdoPersistenceService.cs:línea 162
en WFTools.Services.Persistence.GenericPersistenceService.Commit(Transaction transaction, ICollection items) en C:\Users\Usuario\Downloads\WFTools-v0.3.0.0\Services\Persistence\GenericPersistenceService.cs:línea 680
GenericPersistenceService::Commit
AdoWorkBatchService::TransactionCreated
GenericWorkBatchService::CommitWorkBatch
GenericPersistenceService::UnlockWorkflowInstanceState
GenericPersistenceService::Complete
AdoWorkBatchService::WorkBatchRolledback
Workflow Runtime: Service Exception - WFTools.Services.Persistence.PersistenceException: An unexpected exception occurred while performing a workflow persistence operation. System.InvalidOperationException: No se ha podido inscribir en una transacción distribuida
en Oracle.DataAccess.Client.OracleConnection.EnlistTransaction(Transaction transaction)
en WFTools.Services.Common.Ado.DefaultAdoResourceProvider.CreateEnlistedConnection(Transaction transaction, Boolean& shouldClose) en C:\Users\Usuario\Downloads\WFTools-v0.3.0.0\Services\Common\Ado\DefaultAdoResourceProvider.cs:línea 107
en WFTools.Services.Batching.Ado.AdoWorkBatchService.AdoResourceProviderWrapper.CreateEnlistedConnection(Transaction transaction, Boolean& shouldClose) en C:\Users\Usuario\Downloads\WFTools-v0.3.0.0\Services\Batching\Ado\AdoWorkBatchService.cs:línea 445
en WFTools.Services.Persistence.Ado.AdoPersistenceResourceAccessor..ctor(IAdoResourceProvider resourceProvider, IPersistenceNameResolver nameResolver, IAdoValueReader valueReader, Transaction transaction) en C:\Users\Usuario\Downloads\WFTools-v0.3.0.0\Services\Persistence\Ado\AdoPersistenceResourceAccessor.cs:línea 85
en WFTools.Services.Persistence.Ado.AdoPersistenceService.CreateAccessor(IResourceProvider resourceProvider, Transaction transaction) en C:\Users\Usuario\Downloads\WFTools-v0.3.0.0\Services\Persistence\Ado\AdoPersistenceService.cs:línea 162
en WFTools.Services.Persistence.GenericPersistenceService.Commit(Transaction transaction, ICollection items) en C:\Users\Usuario\Downloads\WFTools-v0.3.0.0\Services\Persistence\GenericPersistenceService.cs:línea 680 ---> System.InvalidOperationException: No se ha podido inscribir en una transacción distribuida
en Oracle.DataAccess.Client.OracleConnection.EnlistTransaction(Transaction transaction)
en WFTools.Services.Common.Ado.DefaultAdoResourceProvider.CreateEnlistedConnection(Transaction transaction, Boolean& shouldClose) en C:\Users\Usuario\Downloads\WFTools-v0.3.0.0\Services\Common\Ado\DefaultAdoResourceProvider.cs:línea 107
en WFTools.Services.Batching.Ado.AdoWorkBatchService.AdoResourceProviderWrapper.CreateEnlistedConnection(Transaction transaction, Boolean& shouldClose) en C:\Users\Usuario\Downloads\WFTools-v0.3.0.0\Services\Batching\Ado\AdoWorkBatchService.cs:línea 445
en WFTools.Services.Persistence.Ado.AdoPersistenceResourceAccessor..ctor(IAdoResourceProvider resourceProvider, IPersistenceNameResolver nameResolver, IAdoValueReader valueReader, Transaction transaction) en C:\Users\Usuario\Downloads\WFTools-v0.3.0.0\Services\Persistence\Ado\AdoPersistenceResourceAccessor.cs:línea 85
en WFTools.Services.Persistence.Ado.AdoPersistenceService.CreateAccessor(IResourceProvider resourceProvider, Transaction transaction) en C:\Users\Usuario\Downloads\WFTools-v0.3.0.0\Services\Persistence\Ado\AdoPersistenceService.cs:línea 162
en WFTools.Services.Persistence.GenericPersistenceService.Commit(Transaction transaction, ICollection items) en C:\Users\Usuario\Downloads\WFTools-v0.3.0.0\Services\Persistence\GenericPersistenceService.cs:línea 680
--- Fin del seguimiento de la pila de la excepción interna ---
GenericPersistenceService::Commit - An unexpected exception occurred while performing a workflow persistence operation. System.InvalidOperationException: No se ha podido inscribir en una transacción distribuida
en Oracle.DataAccess.Client.OracleConnection.EnlistTransaction(Transaction transaction)
en WFTools.Services.Common.Ado.DefaultAdoResourceProvider.CreateEnlistedConnection(Transaction transaction, Boolean& shouldClose) en C:\Users\Usuario\Downloads\WFTools-v0.3.0.0\Services\Common\Ado\DefaultAdoResourceProvider.cs:línea 107
en WFTools.Services.Batching.Ado.AdoWorkBatchService.AdoResourceProviderWrapper.CreateEnlistedConnection(Transaction transaction, Boolean& shouldClose) en C:\Users\Usuario\Downloads\WFTools-v0.3.0.0\Services\Batching\Ado\AdoWorkBatchService.cs:línea 445
en WFTools.Services.Persistence.Ado.AdoPersistenceResourceAccessor..ctor(IAdoResourceProvider resourceProvider, IPersistenceNameResolver nameResolver, IAdoValueReader valueReader, Transaction transaction) en C:\Users\Usuario\Downloads\WFTools-v0.3.0.0\Services\Persistence\Ado\AdoPersistenceResourceAccessor.cs:línea 85
en WFTools.Services.Persistence.Ado.AdoPersistenceService.CreateAccessor(IResourceProvider resourceProvider, Transaction transaction) en C:\Users\Usuario\Downloads\WFTools-v0.3.0.0\Services\Persistence\Ado\AdoPersistenceService.cs:línea 162
en WFTools.Services.Persistence.GenericPersistenceService.Commit(Transaction transaction, ICollection items) en C:\Users\Usuario\Downloads\WFTools-v0.3.0.0\Services\Pe

Please, I need your help.

Regrats

Wagner

Commented Issue: DbParamter can't be converted to MySqlParamter

AlexanderYao — Wed, 15 Jul 2009 03:13:37 GMT

I've encountered similar problem that DbParameter can't be converted to OracleParameter, and the WFTools samples solution can't be compiled.

Looking for answers too...

Created Issue: GenericPersistenceService - Oracle 9i Scripts

mrehm — Fri, 13 Mar 2009 14:24:53 GMT

Hi,

I was facing some problems try to run WFTools 0.3.0.0 (15876) with Oracle 9i.
Some persisted workflows weren't loading after expired timers, i found that some statements in WHERE clauses of procedures RetrieveNonblockingInstanceIds, RetrieveExpiredTimerIds and RetrieveInstanceState were causing that problem.
The statement (OWNED_UNTIL < SYS_EXTRACT_UTC(SYSTIMESTAMP)) must be changed to (to_timestamp(OWNED_UNTIL) < SYS_EXTRACT_UTC(SYSTIMESTAMP)). After this the problem was solved.

Commented Issue: Workflow is getting completed even after workbatch rolled back (AdoWorkBatchService::WorkBatchRolledback)

vasu — Wed, 04 Feb 2009 18:07:37 GMT

Workflow is getting completed even after workbatch rolled back (AdoWorkBatchService::WorkBatchRolledback)
Any idea when this could happen.
I am using adoworkbatch service to have the application database & workflow database in a single transaction. it is distributed transaction.
It is not writing anything in the tracking tables but completing the workflow and unable to load the workflow next time.
Deleted the workflow item from the instance_state table.
Comments: ** Comment from web user: vasu **

Here is the trace:

GenericPersistenceService::LoadWorkflowInstanceState
GenericTrackingService::GetProfile
GenericTrackingChannel::Send
System.Workflow.Activities Information: 0 : Firing event RejectRequest for instance 50e325a3-934c-4004-b354-02da2334be49
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::MustCommit
GenericTrackingChannel::MustCommit
GenericTrackingChannel::Send
GenericPersistenceService::SaveWorkflowInstanceState
GenericWorkBatchService::CommitWorkBatch
AdoWorkBatchService::TransactionCreated
GenericTrackingChannel::Commit
AdoWorkBatchService::WorkBatchRolledback
GenericTrackingChannel::Complete
GenericPersistenceService::Complete
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::Complete
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::Complete
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::InstanceCompletedOrTerminated
GenericTrackingChannel::MustCommit
GenericTrackingChannel::Send
GenericPersistenceService::SaveWorkflowInstanceState
GenericTrackingChannel::MustCommit
GenericTrackingChannel::MustCommit
GenericPersistenceService::MustCommit
GenericWorkBatchService::CommitWorkBatch
AdoWorkBatchService::TransactionCreated
GenericTrackingChannel::Commit
GenericPersistenceService::Commit
AdoWorkBatchService::WorkBatchCommitted
GenericTrackingChannel::Complete
GenericPersistenceService::Complete
GenericPersistenceService::LoadWorkflowInstanceState
GenericPersistenceService::LoadWorkflowInstanceState - An unexpected exception occurred while performing a workflow persistence operation. WFTools.Services.Persistence.PersistenceException: Instance with identifier 50e325a3-934c-4004-b354-02da2334be49 could not be loaded.
at WFTools.Services.Persistence.Ado.AdoPersistenceResourceAccessor.CheckResult(DbCommand dbCommand, String resultParameter, String instanceParameter)
at WFTools.Services.Persistence.Ado.AdoPersistenceResourceAccessor.RetrieveInstanceState(Guid instanceId, Guid ownerId, DateTime ownedUntil)
at WFTools.Services.Persistence.GenericPersistenceService.LoadWorkflowInstanceState(Guid instanceId)

Created Issue: Instance is being completed even though workbatchrolledback.

vasu — Wed, 04 Feb 2009 18:06:21 GMT

Instance is being completed even though workbatchrolledback.
Using ADOWorkbatchservice to have a transaction between application database & workflow database.
Using distributed transaction.

Any help is greatly appreciated.
Here is the trace:

GenericPersistenceService::LoadWorkflowInstanceState
GenericTrackingService::GetProfile
GenericTrackingChannel::Send
System.Workflow.Activities Information: 0 : Firing event RejectRequest for instance 50e325a3-934c-4004-b354-02da2334be49
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::MustCommit
GenericTrackingChannel::MustCommit
GenericTrackingChannel::Send
GenericPersistenceService::SaveWorkflowInstanceState
GenericWorkBatchService::CommitWorkBatch
AdoWorkBatchService::TransactionCreated
GenericTrackingChannel::Commit
AdoWorkBatchService::WorkBatchRolledback
GenericTrackingChannel::Complete
GenericPersistenceService::Complete
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::Complete
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::Complete
GenericTrackingChannel::Send
GenericTrackingChannel::Send
GenericTrackingChannel::InstanceCompletedOrTerminated
GenericTrackingChannel::MustCommit
GenericTrackingChannel::Send
GenericPersistenceService::SaveWorkflowInstanceState
GenericTrackingChannel::MustCommit
GenericTrackingChannel::MustCommit
GenericPersistenceService::MustCommit
GenericWorkBatchService::CommitWorkBatch
AdoWorkBatchService::TransactionCreated
GenericTrackingChannel::Commit
GenericPersistenceService::Commit
AdoWorkBatchService::WorkBatchCommitted
GenericTrackingChannel::Complete
GenericPersistenceService::Complete
GenericPersistenceService::LoadWorkflowInstanceState
GenericPersistenceService::LoadWorkflowInstanceState - An unexpected exception occurred while performing a workflow persistence operation. WFTools.Services.Persistence.PersistenceException: Instance with identifier 50e325a3-934c-4004-b354-02da2334be49 could not be loaded.
at WFTools.Services.Persistence.Ado.AdoPersistenceResourceAccessor.CheckResult(DbCommand dbCommand, String resultParameter, String instanceParameter)
at WFTools.Services.Persistence.Ado.AdoPersistenceResourceAccessor.RetrieveInstanceState(Guid instanceId, Guid ownerId, DateTime ownedUntil)
at WFTools.Services.Persistence.GenericPersistenceService.LoadWorkflowInstanceState(Guid instanceId)

Created Issue: Workflow is getting completed even after workbatch rolled back (AdoWorkBatchService::WorkBatchRolledback)

vasu — Wed, 04 Feb 2009 17:18:51 GMT

Created Issue: DbParamter can't be converted to MySqlParamter

rupurt — Wed, 26 Nov 2008 04:45:17 GMT

Created Issue: Removing workflow from instance_state without being completed.

vasu — Thu, 20 Nov 2008 14:53:33 GMT

Removing workflow from instance_state without being completed.
This happens when transaction fails.
Any body else had the same problem?Any ideas?

Created Issue: Workflow changes not being stored in tracking tables correctly

jimblust — Fri, 31 Oct 2008 17:27:53 GMT

To align with the functionality of the SQL Server provider and make sure that change stored to the tracking store can be re-applied during tracking query, the way changes are stored in ADDED_ACTIVITY and REMOVED_ACTIVITY must be changed. Currently, only the XML of the activity being added or deleted is stored in the table, but instead, the XML of the AddedActivityAction or RemovedActivityAction should be stored there. Also, for child entries, the ORDER field should be NULL rather than -1 for consistency.

Created Issue: MySQL Table "Type" unique index length to large for UTF8 encoding.

rupurt — Mon, 27 Oct 2008 02:54:55 GMT

Due to a bug/"feature" in MySQL currently all versions the max size for a unique index is 1000 bytes. (UTF8 encoding uses 3 bytes per char, therefore max size is 333 chars).
So unfortunately on the table "TYPE" the index "TYPE_UQ01" has a length of 384 chars which is invalid.

,TYPE_FULL_NAME VARCHAR(128) NOT NULL
,ASSEMBLY_FULL_NAME VARCHAR(256) NOT NULL

The only current solution would be to create a regular index out of it and enforce the uniqueness in the app logic.

Created Issue: Workflow Tracking (InsertWorkflowInstance) fails under ODP.NET

jimblust — Tue, 21 Oct 2008 17:39:17 GMT

Running 0.3.0.0 Changeset 15876, with ODP.NET 2.111.6.20 against Oracle 9i 9.2.0.5.0.

Under ODP.NET, AdoTrackingResourceAccessor.InsertworkflowInstance fails with an error "ORA-01460: unimplemented or unreasonable conversion requested" when trying to retrieve the Instance ID from the RefCursor returned by the InsertWorkflowInstance stored proc on the following line:

workflowInstanceSummary.InternalId = _valueReader.GetInt64(dataReader, 0);

Recommended change: Pass the workflow_instance_id back as a number (WORKFLOW_INSTANCE.WORKFLOW_INSTANCE_ID%TYPE) rather than a RefCursor. Other stored procs in this package (e.g. InsertWorkflowTrackingRecord) already work this way.

Created Issue: Exception persisting large workflow to Oracle

jimblust — Tue, 21 Oct 2008 16:43:39 GMT

Running 0.3.0.0 Changeset 15876, with ODP.NET 2.111.6.20 against Oracle 9i 9.2.0.5.0. AdoPersistenceResourceAccessor.InsertInstanceState fails when the workflow size (workItem.SerialisedActivity) is larger than 32k, with Oracle error "ORA-01460: unimplemented or unreasonable conversion requested".

I receive this error both under System.Data.OracleClient and Oracle.DataAccess.Client.

This is similar to Issue 5056, but in that case it was Tracking and CLOBs, and in this case, it's Persistence and BLOBs.

Recommended change: In both OracleResourceProvider.cs and OdpResourceProvider.cs, change the PopulateType method's IF condition to translate AdoDbType.Binary into (OracleType or OracleDbType).Blob, the same way as you're doing for AdoDbType.Text -> Clob.

Created Issue: AdoWorkBatchService: Accesses to _connectionsByTransaction dictionary not threadsafe

jimblust — Tue, 21 Oct 2008 16:15:30 GMT

Running 0.3.0.0 Changeset 15876. Under load, workflows will occasionally terminate with the exception below. Additions to the _connectionsByTransaction dictionary are not protected by a lock. I'm running Persistence and Tracking with AdoWorkBatchService, UseLocalTransactions=true, with ODP.NET 2.111.6.20 against Oracle 9i 9.2.0.5.0.

Suggested change: Protect all accesses of _connectionsByTransaction by a lock, like this class already does with _resourceProvidersByConnectionString.

10/21/2008 4:03:37 PM Cat: System.Workflow.Runtime Msg: Uncaught exception escaped to the root of the workflow.
In instance 54447778-cce0-4475-a664-3950da66afd7 in activity
Inner exception: System.Workflow.Runtime.Hosting.PersistenceException: Index was outside the bounds of the array. ---> System.IndexOutOfRangeException: Index was outside the bounds of the array.
at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
at System.Collections.Generic.Dictionary`2.Add(TKey key, TValue value)
at WFTools.Services.Batching.Ado.AdoWorkBatchService.TransactionCreated(Transaction transaction) in C:\Code\WFTools\Main\Services\Batching\Ado\AdoWorkBatchService.cs:line 90
at WFTools.Services.Batching.GenericWorkBatchService.CommitWorkBatch(CommitWorkBatchCallback commitWorkBatchCallback) in C:\Code\WFTools\Main\Services\Batching\GenericWorkBatchService.cs:line 43
at System.Workflow.Runtime.WorkflowExecutor.CommitTransaction(Activity activityContext)
at System.Workflow.Runtime.WorkflowExecutor.Persist(Activity dynamicActivity, Boolean unlock, Boolean needsCompensation)

Created Issue: GenericPersistenceService - LoadWorkflowsWithExpiredTimers raises Ownership Exceptions

jimblust — Tue, 21 Oct 2008 15:38:01 GMT

Running 0.3.0.0 Changeset 15876. I'm running multiple runtimes in a load balanced environment, with LoadInterval set to 1 second. When two runtimes try to pick up the same instance with an expired timer, the PersistenceException is passed up to RaiseServicesExceptionNotHandledEvent twice, when it shouldn't be at all (this is a normal, ignorable scenario).

Suggested fixes:
1. LoadWorkflowInstanceState should not be calling RaiseServicesExceptionNotHandledEvent in its catch block, because it's throwing the exception to the caller (i.e. it's not "not handled").

2. loadWorkflowsWithExpiredTimers tries to catch and ignore the WorkflowOwnershipException, but your implementation of LoadWorkflowInstanceState wraps it inside a PersistenceException, so the catch block doesn't see it. Change the catch block in loadWorkflowsWithExpiredTimers to trap for a PersistenceException, and just "continue" if the inner exception is a WorkflowOwnershipException.

Commented Issue: ORA-02089: COMMIT is not allowed in a subordinate session--InsertInstanceState

spdude — Mon, 08 Sep 2008 13:36:55 GMT

I am getting the above mentioned exception when I am creating new workflow instance.

This only happens when it is being executed second time. If I try to create instance and if everything successful, there is no exception.
But if it fails and try it again, i am getting that exception... Any pointers are greatly appreciated......

Thanks!
Here is the TRACE.

GenericTrackingChannel::MustCommit
GenericWorkBatchService::CommitWorkBatch
AdoWorkBatchService::TransactionCreated
GenericTrackingChannel::Commit
A first chance exception of type 'System.InvalidOperationException' occurred in Oracle.DataAccess.dll
GenericPersistenceService::Commit
A first chance exception of type 'Oracle.DataAccess.Client.OracleException' occurred in Oracle.DataAccess.dll
GenericPersistenceService::Commit - An unexpected exception occurred while performing a workflow persistence operation. Oracle.DataAccess.Client.OracleException ORA-02089: COMMIT is not allowed in a subordinate session at Oracle.DataAccess.Client.OracleException.HandleErrorHelper(Int32 errCode, OracleConnection conn, IntPtr opsErrCtx, OpoSqlValCtx* pOpoSqlValCtx, Object src, String procedure)
at Oracle.DataAccess.Client.OracleException.HandleError(Int32 errCode, OracleConnection conn, String procedure, IntPtr opsErrCtx, OpoSqlValCtx* pOpoSqlValCtx, Object src)
at Oracle.DataAccess.Client.OracleCommand.ExecuteNonQuery()
at WFTools.Services.Persistence.Ado.AdoPersistenceResourceAccessor.InsertInstanceState(PendingWorkItem workItem, Guid ownerId, DateTime ownedUntil) in ..\WFTools\Services\Persistence\Ado\AdoPersistenceResourceAccessor.cs:line 254
at WFTools.Services.Persistence.GenericPersistenceService.Commit(Transaction transaction, ICollection items) in ..\WFTools\Services\Persistence\GenericPersistenceService.cs:line 687
Comments: ** Comment from web user: spdude **

hi dean ,
can we have a sample code (console host will do) showing how to use dependent transaction. I am aslo facing same issue

Created Issue: ORA-00918 column ambiguously defined

Frans — Mon, 25 Aug 2008 13:21:42 GMT

Oracle 11g gives this error when compiling GetTrackingProfile. The problem is in the line:
order by insert_date_time desc
in the open refcursor p_tracking_profile_xml code block.
After comparing this to the SQL Server code, this should be
order by tp.insert_date_time desc

Created Issue: STATUS Field not getting updated on Suspend

surjithlal — Thu, 03 Jul 2008 05:41:15 GMT

the Status field in the INSTANCE_STATE table not getting updated on Suspendig the Workflow

we are using the StateMachine Workflow, ManualSchedular and SuspendActivity

Any idea why it is not getting updated?

Closed Issue: ORA-02089: COMMIT is not allowed in a subordinate session--InsertInstanceState

deanward — Thu, 12 Jun 2008 15:34:43 GMT