Processing script [productname-0.js,86] failed: Server returned HTTP response code: 503

[Xiajh]

Hi,

I noticed that my breakpoint in Eclipse isn't triggered. (breakpoint is set on an eventhandler)

I'm using GWT 2.7 and the newest SDGB version.

I've turned on my trace and saw the following error which I can't solve. 

| Thread-101 | 2015-05-19 12:17:03.060 | com.github.sdbg.debug.core | /sourcemaps | com.github.sdbg.debug.core.util.Trace | trace | 45 | Checking script for sourcemaps: [productname-0.js,86] |

| Thread-101 | 2015-05-19 12:17:03.064 | com.github.sdbg.debug.core | /sourcemaps | com.github.sdbg.debug.core.util.Trace | trace | 45 | Found sourcemap with URL: http://127.0.0.1:9996/sourcemaps/productname/725674C7723CED743B1DE3B3ED88C2DE_sourcemap.json |

| Thread-101 | 2015-05-19 12:17:03.104 | com.github.sdbg.debug.core | /sourcemaps | com.github.sdbg.debug.core.util.Trace | trace | 45 | Processing script [productname-0.js,86] failed: Server returned HTTP response code: 503 for URL: http://127.0.0.1:9996/sourcemaps/productname/725674C7723CED743B1DE3B3ED88C2DE_sourcemap.json |

| Thread-101 | 2015-05-19 12:17:03.108 | com.github.sdbg.debug.core | /wireProtocol | com.github.sdbg.debug.core.util.Trace | trace | 45 | unhandled notification: Page.frameAttached |

Any ideas?

Cheers, Xia

[Ivan Markov]

As a start: are you able to debug successfully in ChromeDevTools?

[Xiajh]

Hi Ivan,

You mean directly via Chrome? If yes, than yes. My breakpoints does get triggered there.

[Xiajh]

Hi Ivan,

Do you need extra information?

Cheers, X

[Ivan Markov]

The problem seems to be this line:

| Thread-101 | 2015-05-19 12:17:03.104 | com.github.sdbg.debug.core | /sourcemaps | com.github.sdbg.debug.core.util.Trace | trace | 45 | Processing script [productname-0.js,86] failed: Server returned HTTP response code: 503 for URL: http://127.0.0.1:9996/sourcemaps/productname/725674C7723CED743B1DE3B3ED88C2DE_sourcemap.json |

Basically, SDBG cannot load the sourcemap. I thought that if the problem is somehow in your SuperDevMode server configuration, the problem will manifest itself also with ChromeDevTools, but apparently this is not the case.

 You can help me by trying to do the following:

1) Using Chrome Devtools, look at the end of script " [productname-0.js,86]". There should be a comment containing the sourcemap url. Please forward to me the contents of the comment

2) Using ChromeDevtools, enable Network tracing and try to find out in the network tracing log what URL ChromeDevtools is using to load the sourcemap.

[Xiajh]

HI Ivan,

I've send you a private message. Did you got it?

[Ivan Markov]

Yes.

[Xiajh]

Hi all,

Mystery around the HTTP response code has been solved. 

As it turns out, localhost and 127.0.0.1 weren't included in my Internetoptions Proxy Bypass. 

Once it is included, SDBG works like a charm :)

@Ivan: thanks for the support