Build: NetBeans IDE 6.9.1 (Build 201007282301)
VM: Java HotSpot(TM) Client VM, 17.0-b17, Java(TM) SE Runtime Environment, 1.6.0_21-b07
OS: Windows XP
netbeans just sits there 'waiting for connection (netbeans-xdebug)'.
java.lang.IllegalArgumentException: URI has an authority component
Created attachment 107538[details]
When using Netbeans and XDebug this exeption is thrown.
I am using a localhosted Virtual Server, with a Documentroot on a networked drive.
It is no problem for Netbeans to edit these files, but it seems that XDebug has no acces to this networked drive.
Using localhost with files on the c: drive debug with no problem.
See exceptions report #170565.
Preconditions for this exception to occur on my setup:
- windows xp sp3 environment
- my apache webserver with php+xdebug is running locally, but loading its files from a network share (this is working)
- my project's source and project folders are located on the local machine as well, but netbeans is set up to copy the source folder to the network share
- no path mappings were defined (however, when I defined them they were not used anyway, maybe because the webserver is running on the local machine)
I initiated a debug session, browser requested the correct URL with XDEBUG_SESSION_START param, and xdebug seemed to take note of that request:
<init xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" fileuri="file://SERVER/SHARE/bos-dev/index.php" language="PHP" protocol_version="1.0" appid="4800" idekey="netbeans-xdebug"><engine version="2.1.1"><![CDATA[Xdebug]]></engine><author><![CDATA[Derick Rethans]]></author><url><![CDATA[http://xdebug.org]]></url><copyright><![CDATA[Copyright (c) 2002-2011 b ...
XDebug then sent a TCP packet to Netbeans listening on :9000. (I was not able to capture the packet sent.) At this point the exception occured. The behaviour is repeatable.
I read in some forum that Netbeans (or Java) has problems with network shares, and that using a network-mapped drive should be working. I did not test this option, but debugging a script residing in the local file system however works.
According to Wireshark, Xdebug connects back successfully. My computer receives this XML data at port 9000:
<?xml version="1.0" encoding="iso-8859-1"?>
<copyright><![CDATA[Copyright (c) 2002-2011 by Derick Rethans]]></copyright>
(XML was reformatted for better visualization, original comes in two lines.)