RFR 8037274 (Round 0): sun.tools.attach.WindowsVirtualMachine#createPipe() needs more descriptive message when pipe creation fails

[Alan Bateman]

On 13/03/2014 13:29, Jaroslav Bachorik wrote:
>
> Currently the exception log looks like
>
> [2014-01-09T04:04:53.61] java.io.IOException: CreateNamedPipe failed
> [2014-01-09T04:04:53.61]     at 
> sun.tools.attach.WindowsVirtualMachine.createPipe(Native Method)
> [2014-01-09T04:04:53.61]     at 
> sun.tools.attach.WindowsVirtualMachine.execute(WindowsVirtualMachine.java:85)
> [2014-01-09T04:04:53.61]     at 
> sun.tools.attach.HotSpotVirtualMachine.loadAgentLibrary(HotSpotVirtualMachine.java:58)
> [2014-01-09T04:04:53.61]     at 
> sun.tools.attach.HotSpotVirtualMachine.loadAgentLibrary(HotSpotVirtualMachine.java:79)
> [2014-01-09T04:04:53.61]     at 
> nsk.share.aod.AgentsAttacher.tryToLoadAgent(AgentsAttacher.java:71)
> [2014-01-09T04:04:53.61]     at 
> nsk.share.aod.AgentsAttacher.attachAgents(AgentsAttacher.java:48)
> [2014-01-09T04:04:53.61]     at 
> nsk.share.aod.AODTestRunner.doTestActions(AODTestRunner.java:63)
> [2014-01-09T04:04:53.61]     at 
> nsk.share.aod.AODTestRunner.runTest(AODTestRunner.java:116)
> [2014-01-09T04:04:53.61]     at 
> nsk.share.aod.AODTestRunner.main(AODTestRunner.java:163)
>
> And the failure cause is lost somewhere.
I think it would be best to debug into the JNU_* function to see whether 
FormatMessage is called and see why it isn't translating the error.

-Alan