Re: FW: Problem with blocking in sendReceiveTimeout
Dion Picco <[email protected]>
| Newsgroups | gmane.comp.corba.orbacus |
|---|---|
| Organization | IONA | Making Software Work Together TM |
| Message-ID | <[email protected]> |
Hi Henrik, On Wed, Jan 05, 2005 at 11:36:24AM +0100, Henrik Nørgaard wrote: > Hi Dion. > > I don't think that the server is blocked - though I am not sure. The dumps I > have, I get from our production environment when the system is very busy and > I only have dumps from the client side. > > Do you know if the mutex used by the client is a static or an instance mutex? > If it is an instance mutex, it might help to have more than one server > object in a 'server pool'. In order for me to examine what is going on here, it would be necessary to know what version of Orbacus you are working with here. Additionally it could also prove useful to know some general Orbacus-specific properties regarding your system such as your dispatch strategy (thread pool, threaded, etc). It IS possible that a latent deadlock condition is existing here. However if that is the case then java should alert you of the potential deadlock situation. It could be possible that one thread of the client made a request and is awaiting a reply from the server and therefore holding the lock until it receives it. But if the server is in a deadlocked state, then the client obviously will never receive it. I'm just making a guess here as an example. A full backtrace of all your client threads would also prove to be useful in determining this. We should be able to see what thread has the mutex locked at the time of the hang. -- Dion Picco, Software Engineer IONA Technologies Inc. Team Orbacus - Your CORBA Source mailto:[email protected] http://www.orbacus.com _______________________________________________ OB-Users Mailing List - [email protected] http://mail.ooc.nf.ca/mailman/listinfo/ob-users Visit our support FAQ before you send a message. http://www.orbacus.com/faq/support.html