0 Replies Latest reply on Nov 23, 2010 4:03 PM by 817943

    Java ME SDK 3.0, Mac OS X: java.net.SocketException: Cannot allocate memory


      in general, my problem is the old one: Failed to connect to device 3!

      Full log from the IDE while trying to run UIDemo: http://pastebin.com/cbcCakF3

      Log located in +~/Library/Application Support/javame-sdk/3.0/log/device-manager.log+: http://pastebin.com/vTjvk4gs. Several tries of running the emulator are logged.

      Log located in +~/Library/Application Support/javame-sdk/3.0/work/3/device.log+: http://pastebin.com/UwG7xNkN. The interesting part: java.lang.reflect.InvocationTargetException, because of: Caused by: java.net.SocketException: Cannot allocate memory

      device-manager.app starts OK and shows up in the menu bar. While trying to run the UIDemo, an emulator sort of shows up in Dock and then closes.

      1. removing +~/Library/Application Support/javame-sdk/+
      2. changing device-manager.object-registry.host to +

      Firewall is disabled.

      I'm using a fresh install of Mac OS X Snow Leopard 10.6.5 with the latest updates (as of today).

      $ java -version
      java version "1.6.0_22"
      Java(TM) SE Runtime Environment (build 1.6.0_22-b04-307-10M3261)
      Java HotSpot(TM) 64-Bit Server VM (build 17.1-b03-307, mixed mode)

      Could this be caused by the latest Java update? I remember that I was able to start the emulator, like, a month ago on another machine; it didn't start the first time it was ran, but eventually, after a couple of tries it managed to run itself :)

      And, if this is in fact caused by Java update, what could be the alternatives for running the Java ME SDK on Mac OS X? I've tried Soylatte, but the IDE didn't even start properly.