CAN DEAD LOCKS OCCUR BETWEEN CORBA SERVERS?
[Recently created (12/1998). Click here to go to the next FAQ in the chain of recent changes] Dead-locks can occur between two or more CORBA servers. Dead-locks can only occur under certain conditions. First of all, a cyclic or looping relationship must exist between the servers. For example: one server must make invocations on the second server which is in turn implemented to make an invocation upon the first server. This situation is referred to by some as nested call-backs. While cyclic relationship between servers might seem easy to avoid, it often arises, if CORBA is being used to support the combination of client/server request/response and server/client notification. If a cyclic relationship exists and a remote invocation blocks a process, a dead-lock will occur. Blocking can occur upon remote invocation if multiple threads are not used and the CORBA product does not dispatch events while remote invocations are being performed.
Related Questions
- When I am using a wizard to create or update CORBA servers, the command line in the servers activation property list does not appear to be correct. Do I need to edit it?
- CAN CORBA ALLOW SERVERS TO CAUSE CLIENT SIDE EVENTS OR NOTIFICATIONS?
- What is the difference between dead bolt locks and latch bolt locks?
