Maybe the timeout of five seconds is too small? Our AIX boxes are not the fastest and we also have a lot of stuff on NFS shares.
I recently saw this one: [CLIENT] Exception caught: java.io.IOException: No port file values materialized. Giving up after 6676 ms Normally the timeout should be just about a little more than 5 seconds but here the exception reports more than 6 seconds which might be a hint that the machine was severely overloaded. Regards, Volker On Thu, Jan 14, 2016 at 1:23 PM, Andreas Lundblad <andreas.lundb...@oracle.com> wrote: > On Thu, Jan 14, 2016 at 09:06:56AM +0100, Erik Joelsson wrote: >> There is a bug for that as we see the same thing on Solaris from >> time to time, as I see you know. Andreas, who is the main engineer >> working on sjavac, is currently on vacation. We don't currently know >> the cause of this issue. Any help would be appreciated. >> >> /Erik > > As Erik said, I'm on vacation until Monday. > > This issue is however currently my top priority. I'm thankful that you let me > know that the fix for JDK-8145944 did not solve JDK-8145392. > > best regards, > Andreas
