New Posts New Posts RSS Feed: Using DevForce with MSDTC
  FAQ FAQ  Forum Search   Calendar   Register Register  Login Login

Using DevForce with MSDTC
 Post Reply Post Reply
Author
  Share Topic Share Topic  Topic Search Topic Search  Topic Options Topic Options
Real View Drop Down
Newbie
Newbie


Joined: 16-Nov-2007
Location: Canada
Posts: 6 		Post Options Post Options   Quote Real Quote  Post ReplyReply Direct Link To This Post Topic: Using DevForce with MSDTC
    Posted: 16-Nov-2007 at 6:20am
Hi,
 
We are developing WCF web services and we access the database through DevForce on a Sql Server 2005 database.  The connection string specified the SQLNCLI provider.  Our web methods must work in a transacted environment.  The WCF correct atributes have been set on the method and transaction flow has been enabled.  We also checked that MSDTC works fine on all the involved computers.
 
DevForce has been set to support transaction with the 'useDTC. Xml tag right under the 'ideaBlade' tag.  The problem is simple: whenever we perform a SaveChanges() on the PersistenceManager, the operation times out.  The timeout is that of the ADO command after 30 seconds.  This transaction should last milliseconds.  It performs a simple update in a single table.
 
Does anyone have any idea ?
Back to Top
davidklitzke View Drop Down
IdeaBlade
IdeaBlade
Avatar

Joined: 14-Jun-2007
Posts: 715 		Post Options Post Options   Quote davidklitzke Quote  Post ReplyReply Direct Link To This Post Posted: 16-Nov-2007 at 8:12am
What is your timeout value for transactions?  (see  TransactionSettings Class Properties)
 
What are your CommandTimeout settings? (See Consolidated DevForce Help)
If this doesn't help, please send Client and Server Debug log files to support@ideablade.com along with any additional information you think might be helpful.
 
Back to Top
Real View Drop Down
Newbie
Newbie


Joined: 16-Nov-2007
Location: Canada
Posts: 6 		Post Options Post Options   Quote Real Quote  Post ReplyReply Direct Link To This Post Posted: 16-Nov-2007 at 10:44am

After further testing, I found that when  the "IsTransactional" setting is set to false at save time, the process does not timeout anymore and it executes at normal speed... except that the transaction is aborted and the client does not receive any error.  But i think this is another problem.  The /IsTransactional" setting seems to really have been the key here.
Back to Top
 Post Reply Post Reply

Forum Jump Forum Permissions View Drop Down