Issue in log4Net when using with COM+

--0-2058411699-1080827967=:35327
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

 Hi ...I am using log4net for logging messages thru my application. The main components involved doing so are, 

1. MyLogServer: This component is implemented by us which uses .Net EnterpriseServices and deployed as COM+ Server Application. This component calls log4net assembly to log the messages. This exposes every method which is there in log4net e.g. LogInfo, PushNDC, PopNDC etc. You can say this is the only interface for all my clients to use log4net in turn. 

2. MyLogClient: This is the client component for testing. This calls MyLogServer to log a message. 

So, if we go thru the call stack then, its like, 
MyLogClient ------> MyLogServer -----> log4net 

I am facing a problem in this scenario. Consider the following sequence of calls given by MyLogClient, 
MyLogServer.NDCPush(userID) 
MyLogServer.LogInfo(msg1) 
MyLogServer.LogInfo(msg2) 
MyLogServer.LogInfo(msg3) 
MyLogServer.NDCPop() 

The log file output is not the expected one. For some of the messages it sets the userID set by NDCPush method and for some it does not do. I really donn understand why is this happening. 

I found one thing that as and when I deploy MyLogServer component as COM+ Library application rather than server application, everything starts working fine. Please consider that I have to deploy it as server application because I want to use some COM+ services. 

Please help me if anyone have any clue as to why is this showing such kind of behaviour. 


Win an evening with the Indian cricket captain: Yahoo! India Promos.
--0-2058411699-1080827967=:35327
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<DIV><!--StartFragment -->&nbsp;Hi ...
<DIV class=moz-text-flowed lang=x-western style="FONT-SIZE: 13px; FONT-FAMILY: -moz-fixed">I am using log4net for logging messages thru my application. The main components involved doing so are, <BR><BR>1. MyLogServer: This component is implemented by us which uses .Net EnterpriseServices and deployed as COM+ Server Application. This component calls log4net assembly to log the messages. This&nbsp;exposes every method which is there in log4net e.g. LogInfo, PushNDC, PopNDC etc. You can say this is the only interface for all my clients to use log4net in turn. <BR><BR>2. MyLogClient: This is the client component for testing. This calls MyLogServer to log a message. <BR><BR>So, if we go thru the call stack then, its like, <BR>MyLogClient ------&gt; MyLogServer -----&gt; log4net <BR><BR>I am facing a problem in this scenario. Consider the following sequence of calls given by MyLogClient, <BR>
 MyLogServer.NDCPush(userID) <BR>MyLogServer.LogInfo(msg1) <BR>MyLogServer.LogInfo(msg2)
 <BR>MyLogServer.LogInfo(msg3) <BR>MyLogServer.NDCPop() <BR><BR>The log file output is not the expected one. For some of the messages it sets the userID set by NDCPush method and for some it does not do. I really donn understand why is this happening. <BR><BR>I found one thing that as and when I deploy MyLogServer component as COM+ Library application rather than server application, everything starts working fine. Please consider that I have to deploy it as server application because I want to use some COM+ services. <BR><BR>Please help me if anyone have any clue as to why is this showing such kind of behaviour. </DIV></DIV><p><font face=arial size=-1>
<a href="http://in.rd.yahoo.com/specials/mailtg/*http://pepsizone.yahoo.co.in/pepsi3/cktkipyaas/" target="_blank">
Win an evening</a> with the <b>Indian cricket captain</b>: 
<a href="http://in.rd.yahoo.com/specials/mailtg2/*http://pepsizone.yahoo.co.in/pepsi3/cktkipyaas/" target="_blank">
Yahoo! India Promos</a>.</font>
--0-2058411699-1080827967=:35327--


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click