title: Delays in java.rmi.Naming.bind()
body: <p>A driver from one of our vendors suddenly started failing last week, on a machine where it has worked for almost a year.  The last two descriptive messages output by the driver are now three minutes apart (whereas before they were seconds).  Reverse-engineering the code, I've found that the three minute delays happen during calls to java.rmi.Naming.bind().</p>
  
  <p>What's my starting point for troubleshooting this and getting more information out of the call to bind()?  It does not return a success or failure indication, and it does not appear to be throwing any Exceptions.  I would assume that the consistent 3-minute delay means that some timeout is being hit at some point during the process, but then why is there no indication of failure?</p>