JobStoreCMT does not open non managed connections. about quartznet

[lahma]

Are you using this job store as is instead of JobStoreTX? Normally you want to use JobStoreTX - the CMT version is extension point for containers like Spring.NET. It's important that this job store does not open the connection as it's container's job to do so.

[herrmic]

Yes, I'm using it directly. Changes to jobs and triggers that my code makes must be part of ambient transaction (TransactionScope) that the code runs in. For me, the connections are not that important - the transaction is. As long as everything is in one transaction, it's fine. I had to choose between letting JobStoreCMT open its own connection (in its code I saw that it creates a connection after all, it just doesn't open it) and let the transaction to be escalated to MSDTC (no big deal here, these parts are not critical performance-wise) or overload JobStoreCMT so that it would use connection created by NHibernate (and wrap the connection so that Quartz wouldn't close that connection when it no longer needs it). I chose the former, mostly because it was quicker to implement.

In situations like mine (no problem with letting Quartz escalate the transaction) JobStoreCMT is useful on its own (provided it opens the connection). My infrastructure manages the ambient transactions and JobStoreCMT plays well with them.