On-Device Debug : Execution failed with error code 3

[openskymap]

My platforms :
windows 7 x32 (firewall is off)
Netbeans 7.1, jdk 1.6_27,
asha 302 V 14.26 23-01-12 RM-813 Variant 00.00

The device management is connected to device (GetAPI ok in Options), jar is uploaded to device and launched but it stops immediatly with the following trace :
Starting emulator in debug server mode on port 49579
series 40 on-device debugger version 0.2 beta
emulator starting ....
Contacted Connection Manager ...
Sending Files for Debug Session ...
nbdebug:
Adding 264 second for debugger timeout
KdpDebugTask connecting to debugger 1 ..
Attached JPDA debugger to localhost:49579
Closing Emulator ....

D:\cut_v0\nbproject\build-impl.xml:895: Execution failed with error code 3.
BUILD FAILED (total time: 16 seconds)

Debugger Console :
Attaching to localhost:49579
Connection refused.

When launched in Run Mode it's OK :
Starting emulator in execution mode
series 40 on-device debugger version 0.2 beta
emulator starting ....
Launching Connection Manager ...
Sending Files for Run Session ...
(play and exit app on mobile)
Closing Emulator ....

What else Georges ?

[openskymap]

Nokia guys, are you here ? I need your help, i'm stuck !

[skalogir]

Hi openskymap and apologies for the delay,

Based on the information you have provided it seems that you haven't modified the timeout values correctly.

You would need to set the debugger timeout to 180000 from Window>Preferences>Java>Debug>Debugger Timeout = 180000
and also the Launch timeout to the same value.

Also keep in mind that if you are attempting to debug a MIDlet Suite, this is currently not supported.

[patmolly]

great.. that is nice to hear..

[openskymap]

hello,

i'm using Netbeans not Eclipse -> timeout is set only at Project properties -> running -> Debugger timeout (180000) ?
This is set and it doesn't work.

[skalogir]

Apart from disabling the firewall installed on your PC, you would need to ensure that the router/administrator of your home/work network doesn't block the specific port, by testing the specific port with this online tool.

You have also changed the port from the default 1976 to a custom 49579. Have you changed the Connection Manager configuration file as well?
You need to modify the port inside this file: C:\myplatform\bin\config.txt

# Connection Manager's phone's port number
CM.phoneport: 1976

If you have a BT enabled PC, try the Bluetooth option, it works fine on NetBeans 7.0.1 (JDK 1.7.0_03) with Nokia 302 (tested on software 14.52).

[openskymap]

it's on localhost -> no problem with connection : the connection is established between the PC and mobile (thru BT), jar is sent and launched.
I tryed withLocalizationDemo example -> the list of 2 midlet is displayed when launching one or the other the session is ended :

Jad URL for OTA execution: http://localhost:8082/servlet/org.ne...ationDemo1.jad
Starting emulator in debug server mode on port 51846
series 40 on-device debugger version 0.2 beta
emulator starting ....
Contacted Connection Manager ...
Sending Files for Debug Session ...
nbdebug:
Adding 169 second for debugger timeout
KdpDebugTask connecting to debugger 1 ..
KdpDebugTask connecting to debugger 2 ..
KdpDebugTask connecting to debugger 3 ..
Attached JPDA debugger to localhost:51846
Closing Emulator ....

D:\openskymap\offres\nokia\S40\LocalizationDemo1\nbproject\build-impl.xml:895: Execution failed with error code 3.
BUILD FAILED (total time: 1 minute 16 seconds)

i changed nothing related to the port -> the config.txt file has a value of 1976.

The 302 is not 14.52 but 14.26, it cannot be updated because a SIM card must be inserted (!)

Still stuck...

[openskymap]

Also keep in mind that if you are attempting to debug a MIDlet Suite, this is currently not supported.

How can i set a project that is not a MIDlet Suite : all new MIDlet projects are MIDlet Suite !

[skalogir]

the list of 2 midlet is displayed

MIDlet Suite is not supported unfortunately by the On-Device Debugger.

[skalogir]

How can i set a project that is not a MIDlet Suite : all new MIDlet projects are MIDlet Suite !

A MIDlet Suite contains typically 2 or more MIDlets per NetBeans project. You can see a list of available MIDlets in the Suite, upon launch on Device. You would need to break it down to one MIDlet per project.

In order to see how many MIDlets are included in your MIDlet Suite you can check your Project's properties in NetBeans:

Properties > Application Descriptor >MIDlets

[openskymap]

If there is only one (1) Midlet , even if it's tagged as a Midlet Suite in Netbeans, it can be debugged with ODD ?

[skalogir]

Yes it should. But then you shouldn't be seeing a list of MIDlets to choose from, but instead the application should be directly launched on the device. Did you manage to launch a single MIDlet on the ODD? You can try also with a simple HelloWorld example.

[openskymap]

yes i tried with a single MIDlet (HelloMidlet) but it's the same : Execution failed with error code 3.

i added System.getProperty("com.nokia.targetdebug"); -> the app is seen in session:Running application, but connection is refused when attaching the debugger at specified port (5000) :

Attaching to laurent-PC:5000
Connection refused.

[openskymap]

It's now weeks to get an answer instead of days ?

It tryed with running netbeans as admin (i'm already admin but ...), with no better result.
How can i activate some logs, what can i do to find why the connection is refused ?

FYI, due to Maps API 1.0 crashing the device and the emulator, i had to go back to SDK_1.0 (same behaviour).
(Maps API 1.0 works on SDK 1.0 but this is not the problem to solve here).

Br

[bandarap]

Hi openskymap,
Did you check and followed the steps explained here.http://nds2.fds.nokia.com/fdp/gdinte...ed_v1_0_en.swf