Databases
StackOverflow2013
Postsdbo
POUnity not honoring TransientLifetimeManager?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUnity not honoring TransientLifetimeManager?
    primarykey
    data
    text
    <p>I have the following scenario:</p> <p>A <code>WCF</code> service solution that contains a service implementation layer, business layer and data layer. The <code>WCF</code> implementation layer depends on the business layer and the business layer on the data layer. Each layer receives it's dependencies via constructor injection. We've wired this all together using Unity. We have a custom <code>WCF</code> service host/factor/behavior/instance provider that calls into our Unity container to resolve the <code>WCF</code> service to use and it's various dependencies. </p> <p>It's working great...almost.</p> <p>We're using <code>EntityFramework</code> code first in our data layer. What we're seeing is that a new DbContext class is created on the initial call into <code>WCF</code>, but that class is reused on subsequent calls into the service. This becomes a problem of course when our service is serving multiple calls that are accessing the database concurrently. I was able to prove out that the <code>DbContext</code> class is in fact being reused by placing some trace statements in the DbContext class' constructor. I went further up the chain and places similar trace statements in the business layer implementation constructor and found that this is also only being called once. In fact, it appears that only the <code>WCF</code> service implementation is being constructed on each service call and that the data and business layers are behaving as singletons.</p> <p>From what I've read, it sounds like the default behavior when using <code>RegisterType</code> with Unity is to use the <code>TransientLifetimeManager</code> and that this implies a new instance will be created on every call to <code>Resolve</code>. Since it didn't appear that this default behavior was working correctly, we tried explicitly setting the lifetime manager as <code>TransientLifetimeManager</code>, however we're still seeing our business and data layers behaving as singletons. </p> <p>Any ideas on what I need to do to get our <code>WCF</code> dependencies to behave as singletons?</p> <p><strong>Update:</strong> Still no success. I tried using the PerResolveLifetimeManager, however that did not solve the problem. As a temporary work around, I refactored my code so that it's injecting a factory into my data layer. The factory provides DbContext instances, so I'm able to ensure that each call into my data layer is using a new DbContext. This is working ok for now, but I'd like to resolve whatever issue is causing Unity to hold onto and re-use instances after they're created.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USdiosney
    1. USchris.house.00
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. POUnity not honoring TransientLifetimeManager?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POUnity not honoring TransientLifetimeManager?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POUnity not honoring TransientLifetimeManager?
      1. USvanja.
      1. VTFavorite
    1. CODefault life time manager is ContainerControlledLifetimeManager http://msdn.microsoft.com/en-us/library/ff648098.aspx
      singulars
      1. POUnity not honoring TransientLifetimeManager?
      1. USonof
    2. COActually, according to the Unity 2.0 docs, containerControlledLifetimeManager is the default when you use RegisterInstance. We're using RegisterType, which used TransientLifetimeManager by default.
      singulars
      1. POUnity not honoring TransientLifetimeManager?
      1. USchris.house.00
    3. COHi chris, do you have any new information about this issue? Thanks!
      singulars
      1. POUnity not honoring TransientLifetimeManager?
      1. USRodrigo Juarez
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload