Thales' cellular IoT products business is now part of Telit Cinterion, find out more.

You are here

Community > Forum > Global Discussion > JAD server not found

JAD server not found | Telit Cinterion IoT Developer Community

Like
1
21
fortis's picture
fortis

April 10, 2014 - 10:52am, 18090 views

I am newbie in Gemalto technology and still on the IDE setup with eclipse. After following the user guide and using HellowWorld example I am keep getting the "JAD server not found" error. What I am doing wrong? //******** Using USB port COM15. Connecting to module... Initializing module for debugging... Establishing "IP connection for remote debugging of EHSx"... Registering ip address "192.168.244.1" of remote debugging device... Waiting for debug device registration of "IMP_NG_EHS5_REMOTE"... Passing control to external device emulator... Installing suite from: http://192.168.244.2:49778/HelloWorld.jad JAD server not found *** Error *** Failed to execute MIDlet suite End of debug session. Emulator is closed! //************* Thanks in advance,
21
Comment
Log in or register to post comments
1 - 10 of 21 Comments

Pages

Jędrzej Gemalto Moderator's picture
Jędrzej Gemalto...
Apr 10 2014 - 3:21pm
Hi, check state of "IP connection for remote debugging of EHSx" in Network Connection and disconnect it if connected, check if OJMEE Device Manager is in your system tray and shut it down if running. Restart the module and your IDE and try again. If this doesn't help restart your computer and check again. Please note also that when restarting the module all enumerated USB virtual com ports must be disconnected to be usable after restart. Regards Jedrzej
fortis's picture
fortis
Apr 10 2014 - 3:43pm
Hi Jadrzej, Did as instructed but still the same message. Also, where can I find the OJMEE Device Manager? Thanks.
Jędrzej Gemalto Moderator's picture
Jędrzej Gemalto...
Apr 10 2014 - 4:27pm
OJMEE Device Manager is in system tray, next to system clock. If you don't see the icon it means it's not running. Maybe something went wrong during installation process. Try reinstalling the drivers. Regards Jedrzej
fortis's picture
fortis
Apr 10 2014 - 7:50pm
Jadrzej, I have found the OJMEE Device Manager and did the suggested process again but still got the following: ***** Using USB port COM15. Connecting to module... Initializing module for debugging... Establishing "IP connection for remote debugging of EHSx"... Registering ip address "192.168.244.1" of remote debugging device... Waiting for debug device registration of "IMP_NG_EHS5_REMOTE"... Passing control to external device emulator... Installing suite from: http://192.168.244.2:56071/HelloWorld.jad JAD server not found *** Error *** Failed to execute MIDlet suite End of debug session. Emulator is closed! ***** It means that I should install again? Regards.
Jędrzej Gemalto Moderator's picture
Jędrzej Gemalto...
Apr 11 2014 - 11:29am
Dear Fortis, yes - uninstall Gemalto EGSx Software Development Kit and Gemalto IMP Debug Connection for EHSx and install it again. Hoping this will help. Regards Jedrzej
eppie's picture
eppie
May 6 2014 - 7:49pm
I also have multiple problems to get the SDK to work properly. (https://iot-developer.thalesgroup.com/threads/ehs6-development-environme...). For some reason I now also get the same message as you. :( Some additional logging from the file "device-manager.log" [2014-05-06 17:01:46.944] DEBUG - et.portforwarder.PortForwarder - Started forwarding 3403 <-> 192.168.244.1:51235. [2014-05-06 17:01:46.948] DEBUG - et.portforwarder.PortForwarder - Started forwarding 3404 <-> 192.168.244.1:51236. [2014-05-06 17:01:46.987] INFO - kdp.KDP - JavaME Debug Agent started with options: [2014-05-06 17:01:46.990] INFO - kdp.KDP - Local port listening for debugger: 3405 [2014-05-06 17:01:46.990] INFO - kdp.KDP - VM host: 192.168.244.1 [2014-05-06 17:01:46.990] INFO - kdp.KDP - VM debugging port: 2808 [2014-05-06 17:01:47.006] INFO - kdp.KDP - Waiting for debugger on port 3405 [2014-05-06 17:01:47.039] INFO - kdp.KDP - KVMListener: got connection Socket[addr=/192.168.244.1,port=2808,localport=3406] [2014-05-06 17:01:47.063] INFO - kdp.KDP - KVMListener: Sending handshake string to VM [2014-05-06 17:01:47.112] DEBUG - try.rmi.DeviceStateManagerImpl - Device 1 state set to: CONNECTED [2014-05-06 17:01:47.113] DEBUG - ver.rmiimpl.CallbackServerImpl - sendInvocationNotification 5 DeviceRegistrationManager stateChanged [2014-05-06 17:01:47.113] DEBUG - .client.rmiimpl.CallbackClient - isNotificationEnabled com.sun.jme.toolkit.remoting.shared.rmiimpl.CallbackNotification[source=DefaultDomain:object=CallbackServer][type=CALLBACK_NOTIFICATION][message=] returns true [2014-05-06 17:01:47.113] DEBUG - device.GenericOdtDeviceAdapter - Connection to device 1 established: stdout port = 3403, stderr port = 3404, jdwp port = 3405. [2014-05-06 17:01:47.167] DEBUG - ver.rmiimpl.CallbackServerImpl - Registering callback on Profiler with VMTraceListener [2014-05-06 17:01:47.174] DEBUG - ver.rmiimpl.CallbackServerImpl - Callback succesfully registered with id 0. [2014-05-06 17:01:47.184] DEBUG - ver.rmiimpl.CallbackServerImpl - Registering callback on Profiler with NetmonAttachListener [2014-05-06 17:01:47.187] DEBUG - ver.rmiimpl.CallbackServerImpl - Callback succesfully registered with id 1. [2014-05-06 17:01:47.228] DEBUG - ver.rmiimpl.CallbackServerImpl - Registering callback on AppManager with AppEventListener [2014-05-06 17:01:47.231] DEBUG - ver.rmiimpl.CallbackServerImpl - Callback succesfully registered with id 2. [2014-05-06 17:01:47.240] DEBUG - ver.rmiimpl.CallbackServerImpl - Registering callback on AppManager with AppEventListener [2014-05-06 17:01:47.240] DEBUG - ver.rmiimpl.CallbackServerImpl - Callback succesfully registered with id 3. [2014-05-06 17:01:47.240] DEBUG - ket.portforwarder.StreamCopier - Started copying Socket[addr=/192.168.244.1,port=51235,localport=3412] <-> Socket[addr=/127.0.0.1,port=3411,localport=3403]. [2014-05-06 17:01:47.242] DEBUG - ket.portforwarder.StreamCopier - Started copying Socket[addr=/192.168.244.1,port=51236,localport=3414] <-> Socket[addr=/127.0.0.1,port=3413,localport=3404].
eppie's picture
eppie
May 6 2014 - 8:08pm
I solved the problem on my computer, maybe it is also working for you. First I tried the HelloWorld Netbeans sample project which still is not working and gives only errors like it cannot connect to the module. (See my other thread) Second I tried the RS232Demo Netbeans sample project and I got the some problems as you. After a reboot, I tried again. Windows asked me permission for the opened port and after granted permission the project was succesfully uploaded!
Jędrzej Gemalto Moderator's picture
Jędrzej Gemalto...
May 7 2014 - 1:14pm
Good to see that you've managed to get it working. Such issues are sometimes caused by firewall or lack of administrative privileges. I've checked it again - with already working debugging under Eclipse, I've installed NetBeans 7.2, manually integrated WTK and ran HelloWorld project. In my case restart was necessary after integration. Regards Jedrzej
j.tang's picture
j.tang
May 12 2016 - 2:23pm

have get the same problem. shut down the firewall, it works. Thanks a lot!!!

antero.markkula@enkom.fi's picture
antero.markkula...
Apr 30 2014 - 2:03pm
One tip: When you are running again the Gemalto EGSx Software Development Kit and Gemalto IMP Debug Connection for EHSx, leave only the USB connected from the PC to the module. I have noticed that leaving the serial connection connected, the software does not find the EHSx module and will exit without installing the debug connection. Regards, Antero

Antero Markkula
Communication and Mechatronics

Enkom Active Oy – www.enkom-active.fi
Upseerinkatu 3 A, 02600 Espoo, Finland
Mobile: +358 400 411368
Office: +358 10 204 0000
Fax: +358 10 204 0010
E-mail: antero.markkula@enkom-active.fi

1 - 10 of 21 Comments

Pages