Issue Details (XML | Word | Printable)

Key: NBAPPENGINE-41
Type: Bug Bug
Status: Open Open
Priority: Major Major
Assignee: marigan
Reporter: harishashim
Votes: 1
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
nbappengine

Unable to debug GWT, suspected appengine (debug mode) server is not started

Created: 09/Nov/09 06:46 PM   Updated: 23/Jun/10 07:58 PM
Component/s: None
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Original Estimate: 1 day
Original Estimate - 1 day
Remaining Estimate: 1 day
Remaining Estimate - 1 day
Time Spent: Not Specified
Time Spent - Not Specified

Environment:

Windows 7 Build 7100
Netbeans 6,8 beta
Appengine (appengine-java-sdk-1.2.6)
GWT (gwt-windows-1.7.1).


Tags: GWT debug


 Description  « Hide

Netbeans 6,8 beta here with the latest Appengine (appengine-java-sdk-1.2.6) GWT (gwt-windows-1.7.1).

Running the project is not a problem.

Debugging is different story. It got stuck at

[OUTPUT: Google App Engine]
runserver-debug:
[java] Listening for transport dt_socket at address: 8765

The port is correct. Silly work around is to debug sample guestbook project (which is not GWT). Stop it after it open the page (and the app engine server is already running in debug mode). And then debug the GWT project. This works.



shaottan added a comment - 23/Jun/10 07:58 PM

This problem can be resolved by changing the ant-deploy runserver-debug target to not suspend the server on start.

<arg value="--jvm_flag=-Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=${appengine.debug.port}"/>

<arg value="--jvm_flag=-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=${appengine.debug.port}"/>