Not with this amount of information. What's the machinery (AR, NH,
other)? What kind of app? Have you configured a custom activity
manager?


On Tue, Jan 27, 2009 at 3:51 PM, Tim Scott <[email protected]> wrote:
>
> Any thoughts on how this exception might occur?
>
>
> On Jan 27, 5:26 pm, hammett <[email protected]> wrote:
>> This comment is stalled. The TM is now per thread, so there's nothing
>> being shared across threads.
>>
>>
>>
>> On Tue, Jan 27, 2009 at 1:07 PM, Tim Scott <[email protected]> 
>> wrote:
>>
>> > I am using AutomaticTransactionManagement in my app, and I am doing
>> > some stress testing.  All is well until I reach a fairly heavy load;
>> > then I get the following exception:
>>
>> > System.ArgumentException: transaction
>> > Parameter name: Tried to dispose a transaction that is not on the
>> > current active transaction
>> >   at Castle.Services.Transaction.DefaultTransactionManager.Dispose
>> > (ITransaction transaction)
>> >   at
>> > Castle.Facilities.AutomaticTransactionManagement.TransactionInterceptor.Int
>> >  ercept
>> > (IInvocation invocation)
>>
>> > I decided to have a look at the source code to see if I can figure out
>> > what might be happening.  The following comment the summary for
>> > DefaultTransactionManager jumped out at me:
>>
>> > TODO: Ensure this class is thread-safe
>>
>> > Has anyone else seen this behavior?  Might I be doing something wrong
>> > in my app?
>>
>> > Not sure it it's relevant but I am also using Rhino.Commons and
>> > UnitOfWorkApplication.
>>
>> --
>> Cheers,
>> hammetthttp://hammett.castleproject.org/
> >
>



-- 
Cheers,
hammett
http://hammett.castleproject.org/

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Castle Project Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/castle-project-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to