JDK-8140263 : (ch) java/nio/channels/FileChannel/Transfer.java timed out
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.nio
  • Affected Version: 8,9
  • Priority: P3
  • Status: Resolved
  • Resolution: Cannot Reproduce
  • OS: os_x
  • CPU: x86_64
  • Submitted: 2015-10-21
  • Updated: 2017-04-28
  • Resolved: 2017-04-28
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
tbd_minorResolved
Related Reports
Relates :  
Relates :  
Relates :  
Relates :  
Relates :  
Relates :  
Relates :  
Relates :  
Description
java/nio/channels/FileChannel/Transfer.java timed out in an
Aurora Adhoc RT/SVC run testing the fix for the following bug:

JDK-8047212 runtime/ParallelClassLoading/bootstrap/random/inner-complex assert(ObjectSynchronizer::verify_objmon_isinpool(inf)) failed: monitor is invalid 
Comments
Removed Confidential marking.
28-02-2017

This is really outside my expertise but it looks like the stack is suggesting a lock up in finalization / Cleaner code.
16-02-2017

I agree with Alan. I looked at the logs for all four of the tests Amy listed and it appears that they actually complete successfully but the Agent times out nonetheless and the result appears to be a failure.
14-02-2017

Something fishy here as the .jtr files suggest that the test completed successfully, it makes me wonder if the jtreg cleanup is the issue. We aren't seeing this issue in JPRT and I can't duplicate it locally either. I suspect we'll need to get a thread dump of jtreg when this timeout occurs.
14-02-2017

Now that JDK-8174127 has been resolved, the test will have more debugging output which might prove useful.
10-02-2017

Thanks for the logs and debug info. I would be curious to see whether running these tests in agentvm or, in the worst case, othervm modes would make any difference.
07-02-2017

There is precious little information to go on here aside from the .jtr file snippet in the first comment. If another failure is observed, attaching the full .jtr file could be helpful. Meanwhile the main option appears to be to instrument the test to dump more information.
07-02-2017

All the links above from the dates 2017-01-15 and 2017-01-21 are dead (404 error) so those comments might as well be deleted. So far no idea what is going on, but have not really investigated much as yet either.
06-02-2017