T.R | Title | User | Personal Name | Date | Lines |
---|
2783.1 | | MICROW::SEVIGNY | She's a walking ulcer... | Thu Apr 16 1992 18:39 | 14 |
|
Some additional info on the previous problem...
The AM uses DCE RPC to communicate to the agent. There is
exception-handling code in the AM however to deal with exceptions
raised by RPC from the RPC call to the agent code.
Do exceptions which are raised in the AM get propagated to the
Director?
Which process (AM or MCC Director) is priting out the exception?
|
2783.2 | | TOOK::MINTZ | Erik Mintz, DECmcc Development, dtn 226-5033 | Thu Apr 16 1992 18:52 | 6 |
| >Exception in Mgt Module (id=16), CMA code = 40802c
The exception is being reported by the PM, but has occured in whichever
module is using enroll id=16. Use "ps -ax | grep mcc" to find out
which module is using which id.
|
2783.3 | | MACROW::SEVIGNY | She's a walking ulcer... | Thu Apr 16 1992 21:30 | 8 |
|
Does that mean that every time an exception occurs in an AM that the PM
is going to display it? That isn't the behavior I would expect if I
have provided a handler in the AM... is it?
Marc
|
2783.4 | How do we track this down? | MICROW::LANG | | Fri Apr 17 1992 13:22 | 7 |
|
Does anyone have any idea of how to track down what CMA error
that is ? I can't find it in the cma h files.
thanks,
Bonnie
|