Flex debugging on vista - a workaround
From Flexcoders
雖然在很久很久的將來我都不會有需要面對這種麻煩事，但還是先預備一下…
—
I just now finally figured out a workaround for the occasional problem
when using Flex Builder on Vista, where Flex Builder tells you that
another debugger is already running.
The workaround is to add this line to flexbuilder.ini or eclipse.ini
(the name of the ini file depends on whether you installed standalone
Flex Builder or the Eclipse plugin version of Flex Builder):
-Djava.net.preferIPv4Stack=true
That’s it. I suspect a bug in Vista — the first time you debug, I
can clearly see that Flex Builder is closing the socket, but when I
run TCPView, it shows that the IPv6 version of the socket is still
open, and that causes the problem. Adding the above property
definition causes Java to only use IPv4.
- Mike Morearty, Adobe Flex Builder team
1 Comment Add your own
1. SuperJogos - Todos os jog&hellip | November 21st, 2007 at 9:37 am
[...] Present Tensed wrote an interesting post today!.Here’s a quick excerptFlex debugging on vista - a workaround In flex November 21, 2007 - 8:09 am From Flexcoders 雖然在很久很久的將來我都不會有需要面對這種麻煩事，但還是先預備一下… — I just now finally figured out a workaround for the occasional problem when using Flex Builder on Vista, where Flex Builder tells you that another debugger is already running. The workaround is to add this line to flexbuilder.ini or eclipse.ini (the name of the ini file depends on whether you installed standalone Flex Builder or the Eclipse plugin version o [...]
Trackback this post | Subscribe to the comments via RSS Feed