Hi,


I am working on a project involving financial transactions. 


There can be any number of transactions coming in at the same time.


*The problem is that, it seems as though, in a few cases, the transactions 
are being "mixed up", in an unpredictable way.* I don't know if it's a 
result of our *"bad"* Lifestyle choices 
<https://github.com/castleproject/Windsor/blob/master/docs/lifestyles.md> 
for Castle Windsor <http://www.castleproject.org/projects/windsor/> or 
there is other code causing it.


Would like to clear the air on Castle Windsor 
<http://www.castleproject.org/projects/windsor/>.


The logging shows that sometimes a particular request will be mixed up with 
a different response.


*I know...Scares us too!*


Main technology used is C# 4, Net 4.5, WCF, Castle Windsor


*It is structured as follows*:

   1. There are incoming transactions, so services should always be up
   2. There are 3 main services
   3. *Service A* - Singleton Lifestyle 
   
<https://github.com/castleproject/Windsor/blob/master/docs/lifestyles.md#singleton>
 
   - instantiates a client to Service B using the ChannelFactory. Can spawn up 
   to 3 threads.
   4. *Service B* - Singleton Lifestyle 
   
<https://github.com/castleproject/Windsor/blob/master/docs/lifestyles.md#singleton>
 
   - uses a service reference, proxy client to Service C
   5. *Service C* - Singleton Lifestyle 
   
<https://github.com/castleproject/Windsor/blob/master/docs/lifestyles.md#singleton>
 
   - connects externally to some API

+-----------------------+              +-----------------------+                
  +-----------------------+
|                       |              |                       |                
  |                       |
|                       |              |                       |                
  |                       |
| [WCF Service  A]      |              | [WCF Service  B]      |                
  | [WCF Service  C]      |
| Instantiates a        +------------->+ Instantiates a        
+----------------> | Connects to an external
| client to B using     |              | client to C using     |                
  | RESTful API           |
| ChannelFactory        |              | a serivice referece   |                
  | (Singleton Lifestyle) |
| (Singleton Lifestyle) |              | to C                  |                
  |                       |
|                       |              | (Singleton Lifestyle) |                
  |                       |
|                       |              |                       |                
  |                       |
+-----------------------+              +-----------------------+                
  +-----------------------+

Hope someone can confirm if our implementation is a possible cause of the bugs.

Thanks!

TK

-- 
You received this message because you are subscribed to the Google Groups 
"Castle Project Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/castle-project-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to