Released: Java ME Platform SDK 3.0 now available
Java ME SDK team is happy to announce availability of Java ME Platform SDK 3.0.
Java ME SDK 3.0 is the successor to the popular Java Wireless Toolkit
2.5.2 and Java Toolkit 1.0 for CDC. It provides device emulation, a
standalone development environment and a set of utilities for rapid
development of Java ME applications.Users will get all-in-one for cldc/midp, cdc and BD-J development.
Among new features are:
- on-device deployment and on-device debugging
- CLDC runtime based on PhoneME Feature
- optimized MSA 1.1
- new development environment based on Netbeans platform
- integrated profiler and network monitor
- lightweight UI Toolkit (LWUIT) support
- device database WURFL search tool
- BD-J support
- Windows Mobile Java VM included
Read more details on Java ME Platform SDK 3.0 page.
Submitt questions to other users in Java ME SDK forum.
Where are the versions for Linux or OpenSolaris. Is there anything in the pipeline?
Posted by Stephan Bardubitzki on April 22, 2009 at 04:04 PM CEST #
run sdk 3.0 , get an error :
[ 282] INFO - un.jme.toolkit.bootstrap.Batch - Initializing objects...
[ 328] INFO - un.jme.toolkit.bootstrap.Batch - Applying I18N
[ 328] INFO - un.jme.toolkit.bootstrap.Batch - Initialized objects
[ 328] INFO - un.jme.toolkit.bootstrap.Batch - Calling create() methods...
[ 344] INFO - un.jme.toolkit.bootstrap.Batch - Calling start() methods...
[ 547] ERROR - un.jme.toolkit.bootstrap.Batch - Problem calling start() on RmiRegistryService
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 com.sun.jme.toolkit.bootstrap.Namespace.startBatch(Unknown Source)
at com.sun.jme.toolkit.bootstrap.MainNamespace.runModules(Unknown Source)
at com.sun.jme.toolkit.bootstrap.MainNamespace.run(Unknown Source)
at com.sun.jme.toolkit.bootstrap.Container.run(Unknown Source)
at com.sun.jme.toolkit.bootstrap.Container.main(Unknown Source)
Caused by: java.rmi.server.ExportException: Port already in use: 1299; nested exception is:
java.net.BindException: Address already in use: JVM_Bind
at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:310)
at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:218)
at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:393)
at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:129)
at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:190)
at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:92)
at sun.rmi.registry.RegistryImpl.<init>(RegistryImpl.java:68)
at java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:222)
at com.sun.jme.toolkit.remoting.registry.rmiimpl.RmiRegistryService.start(Unknown Source)
... 12 more
Caused by: java.net.BindException: Address already in use: JVM_Bind
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359)
at java.net.ServerSocket.bind(ServerSocket.java:319)
at java.net.ServerSocket.<init>(ServerSocket.java:185)
at com.sun.jme.toolkit.remoting.shared.rmiimpl.LoopbackSocketFactory.createServerSocket(Unknown Source)
at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:649)
at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:299)
... 20 more
it seems there is a port already used.
then I got a Unexpected Exception Error dialog with the message:
A java.io.IOException exception has occurred.
Click Show Details or see the messages.log file located in your C:\Documents and Settings\myc\javame-sdk\toolbar\3.0\var\log folder
when i click the cacel button. after a little while , the error dialog shows again , again and again.
i can not going into the sdk .
Posted by ryan on April 23, 2009 at 08:48 AM CEST #
Hi ryan
it looks that internal port that sdk uses is taken. You can switch to another one.
First of all switch off sdk or kill it. Exit also device-manager. Its icon is in system tray.
* Go to %SDK_INSTALL_DIR%/toolkit-lib/modules/bootstrap/conf/system.properties
* Change port number in property device-manager.object-registry.port=1299 to something else for example 1399.
* Start device manager %SDK_INSTALL_DIR%/bin/device-manager.exe
* Try to run emulator from comandline: %SDK_INSTALL_DIR%/bin/emulator.exe -Xjam
hope this helps
Go to
Posted by Tom on April 23, 2009 at 10:41 AM CEST #
asfasd
Posted by rojin on April 23, 2009 at 11:12 AM CEST #
any update in this..
me too getting the same error
Posted by himanshu on June 13, 2009 at 12:37 PM CEST #
I had a similar startup problem but this time problem was due to a misconfiguration of localhost at hosts file.
http://www.ceviktavsan.com/java-me-sdk-startup-problem/
Posted by Ali Utku Selen on June 16, 2009 at 11:24 PM CEST #
OK
Posted by Juris Slezins on June 29, 2009 at 09:14 PM CEST #
same problem.. changing the port number worked for me.. just do what Tom said
Posted by larsking on July 12, 2009 at 05:31 AM CEST #
Thanks God!!!!
http://www.ceviktavsan.com/java-me-sdk-startup-problem/
it really worked!!!
Posted by Izabela on August 20, 2009 at 06:03 PM CEST #
How can i make my saved program will turn into a .exe file extention
Posted by starstruck on September 11, 2009 at 05:02 AM CEST #