This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Created attachment 115940 [details] IDE log Product Version: NetBeans IDE 7.1.1 RC1 (Build 201202141941) Java: 1.6.0_31; Java HotSpot(TM) Client VM 20.6-b01 System: Windows XP version 5.1 running on x86; Cp1252; en_US (nb) Steps: Fresh NB 7.1.1 installation. Create new Mobile App. Run the app. During the first run, Device Manager shows up in the system tray, but the emulator doesn't start, with following output: OUTPUT: ... cldc-run: Copying 1 file to C:\Documents and Settings\tester\My Documents\NetBeansProjects\MobileApplication1\dist\nbrun1766154693140935031 Copying 1 file to C:\Documents and Settings\tester\My Documents\NetBeansProjects\MobileApplication1\dist\nbrun1766154693140935031 Jad URL for OTA execution: http://localhost:8082/servlet/org.netbeans.modules.mobility.project.jam.JAMServlet/C%3A/Documents+and+Settings/tester/My+Documents/NetBeansProjects/MobileApplication1/dist//MobileApplication1.jad Starting emulator in execution mode C:\Documents and Settings\tester\My Documents\NetBeansProjects\MobileApplication1\nbproject\build-impl.xml:782: Execution failed with error code 1. BUILD FAILED (total time: 18 seconds) On a second attempt, the emulator starts.
Same with JDK 6 and with JDK 7. Doesn't happen always though. During a few NB and JDK reinstalls, the emulator started even on the first run sometimes.
*** This bug has been marked as a duplicate of bug 208636 ***
The issue 208636 has no effect on this. Device Manager starts fine even on the first Run attempt, but the Application isn't deployed and opened into an emulator. On the second and any another Run, when the Device Manager is already started, I never noticed any failure and the application always runs fine. The failure is only on the first run and also seems to be random, so there might be just some problem with timing.
Alexander, please evaluate whether this problem is in NetBeans code or in ME SDK code. If it is ME SDK please close here as WONTFIX and track in JIRA. If in NetBeans either try to resolve or re-assign to different category.
When emulator starts first time, Device Manager registers all devices and this process takes some time. As the result, in some cases emulator does not have enough time to connect to Device Manager since device manager is busy with registering of devices. To avoid this situation, the emulator connection timeout should be extended. Tracked here: http://javafx-jira.kenai.com/browse/MESDK-284