Avoid hang of the component manager with com+ console messages [modified]
-
Hello Friends, I've a problem with some com+ components developed in vc++, and running on w2003 sp2, the problems is simple, when an error happend in the component (yes it can happend on best families with big loads :^) ), the component manager must close this component and recycle it, but some times, the system thows a message to the OS console, this message it's the well known: dllhost - Application Error The instruction at "0x1002650d" referenced memory at "0x0000000". The memory could not be "written". Asking the user to continue or debug.... opsss user interaction on a service is not a good idea :( Sometimes this is easy to solve, will you think, just correct your code, but other times, this only ocurr with high load, or networks errors that make your program fail, and the component manager must do his job :laugh: When a small number of this messages (20/30) are in the console, the component manager fail and doesn't do his job, at this moment the component manager it's down and you will manualy kill dllhosts or interact with the console :sigh:!! ¿Does any body knows how to solve this kind of problem, preventing component manager to ask for user interaction on an error? Regards, Vider -- modified at 8:00 Tuesday 18th September, 2007