A link checker found the following broken link:

specs/jpda/jpda.html:66: id not found: specs/jpda/conninv.html#SPI

In addition, it found the following 5 broken references, because the links are missing the module name in the path (between "api/" and "com/sun/")

grep -r api/com/sun build/linux-x86_64-server-release/images/docs/specs/
build/linux-x86_64-server-release/images/docs/specs/jpda/conninv.html:<p>JPDA includes service provider interfaces to allow the development and deployment of connector and transport implementations. These service provider interfaces allow debugger and other tool vendors develop new connector implementations and provide addition transport mechanisms over and beyond the socket and shared memory transport provided by Oracle. The service provider interfaces in JDI are specified in the <a href="../../api/com/sun/jdi/connect/spi/package-summary.html">com.sun.jdi.connect.spi</a> package.</p>
build/linux-x86_64-server-release/images/docs/specs/jpda/architecture.html:<p>JPDA includes service provider interfaces to allow the development and deployment of connector and transport implementations. These service provider interfaces allow debugger and other tool vendors to develop new connector implementations and provide addition transport mechanisms over and beyond the socket and shared memory transport provided by Oracle. The service provider interfaces in JDI are specified in the <a href="../../api/com/sun/jdi/connect/spi/package-summary.html">com.sun.jdi.connect.spi</a> package.</p>
build/linux-x86_64-server-release/images/docs/specs/jpda/jpda.html:<p>Where <code>theStackFrame</code> is a <a href="../../api/com/sun/jdi/StackFrame.html"><code>com.sun.jdi.StackFrame</code></a> and <code>theLocalVariable</code> is a <a href="../../api/com/sun/jdi/LocalVariable.html"><code>com.sun.jdi.LocalVariable</code></a>.</p>
build/linux-x86_64-server-release/images/docs/specs/jpda/jpda.html:<p>This back-end function starts a chain of activity which filters the event to see if it is interesting, queues it, and sends it across the socket in the JDWP format defined for breakpoint events. The front-end decodes and processes the event, eventually generating a JDI event. In particular, the JDI event is exposing it as a <a href="../../api/com/sun/jdi/event/BreakpointEvent.html"><code>com.sun.tools.jdi.event.BreakpointEvent</code></a>. The IDE then gets the event by removing it from the event queue:</p>
build/linux-x86_64-server-release/images/docs/specs/jpda/jpda.html:<p>where <code>theEventQueue</code> is a <a href="../../api/com/sun/jdi/event/EventQueue.html"><code>com.sun.jdi.event.EventQueue</code></a>. The IDE will probably update its displays by making many query calls across the JDI.</p>

That's a bit unreadable: here is the summary:

api/com/sun/jdi/LocalVariable.html
    in specs/jpda/jpda.html
api/com/sun/jdi/StackFrame.html
    in specs/jpda/jpda.html
api/com/sun/jdi/connect/spi/package-summary.html
    in specs/jpda/architecture.html
    in specs/jpda/conninv.html
api/com/sun/jdi/event/BreakpointEvent.html
    in specs/jpda/jpda.html
api/com/sun/jdi/event/EventQueue.html
    in specs/jpda/jpda.html

Also, this one is closely related to be fixed at the same time:

api/java/lang/ThreadGroup.html
    in specs/jdwp/jdwp-protocol.html

These broken links are part of the noise that is affecting our ability to achieve a goal of no broken links.