Java ME SDK 3.0-"Cannot connect to device manager" on port 1299 error HELP!

Question

Hello,
I am running Vista 32 bit. I just downloaded the Java ME sdk 3.0. It installed "successfully". I just tried to launch it several times and it gets stuck in the error below. In summary, something about "Connection refused to host: localhost; DeviceManagerConnection error". Why am I getting that error? This is the first time I installed this.
I run netstat -an, and nothing shows that something is taking up my 1299 port. Also "ping localhost" returns ::1:. And my hosts file looks good. Windows Defender and Firewall are both off. Does anyone have had this issue in the past? If so, please kindly let me know how you resolved it. Thank you.
[ 1052] INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://localhost:1299/device-manager
[ 2189] WARN - mpl.ObjectServerConnectionImpl - Remote object server is not running at service:jmx:rmi:///jndi/rmi://localhost:1299/device-manager
[ 2297] INFO - l.process.GenericProcessRunner - Starting process: C:\Java_ME_platform_SDK_3.0/bin/device-manager.exe
[ 23372] ERROR - un.jme.toolkit.bootstrap.Batch - Problem calling start() on DeviceManagerConnection
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.jme.toolkit.bootstrap.Batch.invoke(Unknown Source)
at com.sun.jme.toolkit.bootstrap.Batch.tryInvoke(Unknown Source)
at com.sun.jme.toolkit.bootstrap.Batch.startObjects(Unknown Source)
at org.netbeans.modules.javame.common.container.Module.start(Module.java:21)
at org.netbeans.modules.javame.common.container.ContainerSupport.startModule(ContainerSupport.java:67)
at org.netbeans.modules.javame.common.container.devicemanager.DevicemanagerHelper.getDeviceManagerConnection(DevicemanagerHelper.java:41)
at org.netbeans.modules.javame.common.container.devicemanager.DevicemanagerHelper.ensureConnected(DevicemanagerHelper.java:48)
at org.netbeans.modules.javame.common.container.devicemanager.DevicemanagerHelper.getDeviceManager(DevicemanagerHelper.java:84)
at org.netbeans.modules.javame.platform.jme_sdk.autoinstaller.AutoInstaller.ensureDMStarted(AutoInstaller.java:292)
at org.netbeans.modules.javame.platform.jme_sdk.autoinstaller.AutoInstaller.restored(AutoInstaller.java:63)
at org.netbeans.core.startup.NbInstaller.loadCode(NbInstaller.java:421)
at org.netbeans.core.startup.NbInstaller.load(NbInstaller.java:342)
at org.netbeans.ModuleManager.enable(ModuleManager.java:906)
at org.netbeans.core.startup.ModuleList.installNew(ModuleList.java:428)
at org.netbeans.core.startup.ModuleList.trigger(ModuleList.java:364)
at org.netbeans.core.startup.ModuleSystem.restore(ModuleSystem.java:276)
at org.netbeans.core.startup.Main.getModuleSystem(Main.java:165)
at org.netbeans.core.startup.Main.start(Main.java:312)
at org.netbeans.core.startup.TopThreadGroup.run(TopThreadGroup.java:110)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is:
java.net.ConnectException: Connection refused: connect]
at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:338)
at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
at com.sun.jme.toolkit.remoting.client.rmiimpl.ObjectServerConnectionImpl.connect(Unknown Source)
at com.sun.jme.toolkit.remoting.client.rmiimpl.ObjectServerConnectionImpl.start(Unknown Source)
... 24 more
Caused by: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is:
java.net.ConnectException: Connection refused: connect]

Answer 1

Hi there,
I believe I am having the problem reported by the first person in this thread.
In fact, I installed NetBeans and ran a Java ME sample and it gave me the following error
Jad URL for OTA execution: http://localhost:8082/servlet/org.netbeans.modules.mobility.project.jam.JAMServlet/C%3A/Users/Afamefuna/Documents/NetBeansProjects/CurrencyConverter3/dist//CurrencyConverter3.jad
Starting emulator in execution mode
+{color:#ff0000}*C:\Users\Afamefuna\Documents\NetBeansProjects\CurrencyConverter3\nbproject\build-impl.xml:889:*{color} Execution failed with error code 1.+
BUILD FAILED (total time: 26 seconds)
Of course, I went to the file but the stipulated line didn't make much sense. Eventually, I seperately installed Java(TM) ME Platform SDK 3.0, but when I doubled clicked on its icon to open it, the initial splashscreen showed up, but when the progress bar got to "+{color:#ff0000}starting modules....{color}+", it gave me a java.net.ConnectionException error.
When I went to the generated log file, amongst other things, it also contained the following snippet
+Connecting to service:jmx:rmi:///jndi/*{color:#ff0000}rmi://localhost:1299/device-manager{color}< </strong>[  23398] ERROR - un.jme.toolkit.bootstrap.Batch - Problem calling start() on DeviceManagerConnection java.lang.reflect.InvocationTargetException+
+ at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)+
+ at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)+
+ at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)+
From the above I can only imagine there is a problem with the device manager set-up for SDK, but how can it be solved?
The device manager icon shows up in the windows toolbar, however, the "device manager" menu choice is greyed out.
This same problem was replicated in my friend's PC, so I am certain this has to do with low-grade packaging/programming from the vendor end.
Please how do I solve this problem? I am hoping that solving one problem, resolves the other.
thanks
ABCDEFGH1JKLMNOPQRSTUVWXYZ