Forum Stats

  • 3,814,956 Users
  • 2,258,936 Discussions
  • 7,892,896 Comments

Discussions

Not able to start imlet from netbeans to a connected rasberrypi

geoaxis
geoaxis Member Posts: 3
edited May 14, 2014 8:14AM in Java ME Embedded

Hello,

I am following instructions from http://docs.oracle.com/javame/8.0/get-started-rpi/debugging.htm

(watched https://www.youtube.com/watch?v=tY2NtP-fmWU)

I cannot seem to deploy imlet from netbeans 8

This is what I get in device log

0:39.464]   INFO - lkit.bootstrap.DeployerManager - Registering custom property editors
[01:40:39.524]   INFO - me.toolkit.bootstrap.Namespace - Starting batch, base module object-server
[01:40:39.542]   INFO - bootstrap.ObjectGraphProcessor - Consolidating dependencies...
[01:40:39.542]   INFO - bootstrap.ObjectGraphProcessor - Consolidated dependencies...
[01:40:39.542]   INFO - bootstrap.ObjectGraphProcessor - Calculating order...
[01:40:39.542]   INFO - bootstrap.ObjectGraphProcessor - Calculated order
[01:40:39.586]   INFO - un.jme.toolkit.bootstrap.Batch - Initializing objects...
[01:40:39.586]   INFO - un.jme.toolkit.bootstrap.Batch - Applying I18N
[01:40:39.586]   INFO - un.jme.toolkit.bootstrap.Batch - Initialized objects
[01:40:39.586]   INFO - un.jme.toolkit.bootstrap.Batch - Calling create() methods...
[01:40:39.602]   INFO - un.jme.toolkit.bootstrap.Batch - Calling start() methods...
[01:40:39.602]   INFO - un.jme.toolkit.bootstrap.Batch - Objects started
[01:40:39.602]   INFO - me.toolkit.bootstrap.Namespace - Starting batch, base module devices/EmbeddedExternalDevice
[01:40:39.680]   WARN - otstrap.deployer.bean.BeanFile - Unsupported container property: .file
[01:40:39.698]   WARN - otstrap.deployer.bean.BeanFile - Unsupported container property: .bound-classes
[01:40:39.712]   WARN - otstrap.deployer.bean.BeanFile - Unsupported container property: .file
[01:40:39.712]   WARN - otstrap.deployer.bean.BeanFile - Unsupported container property: .bound-classes
[01:40:39.821]   INFO - bootstrap.ObjectGraphProcessor - Consolidating dependencies...
[01:40:39.821]   INFO - bootstrap.ObjectGraphProcessor - Consolidated dependencies...
[01:40:39.821]   INFO - bootstrap.ObjectGraphProcessor - Calculating order...
[01:40:39.837]   INFO - bootstrap.ObjectGraphProcessor - Calculated order
[01:40:41.822]   INFO - un.jme.toolkit.bootstrap.Batch - Initializing objects...
[01:40:42.196]   INFO - un.jme.toolkit.bootstrap.Batch - Applying I18N
[01:40:42.196]   INFO - un.jme.toolkit.bootstrap.Batch - Initialized objects
[01:40:42.196]   INFO - un.jme.toolkit.bootstrap.Batch - Calling create() methods...
[01:40:42.322]   INFO - un.jme.toolkit.bootstrap.Batch - Calling start() methods...
[01:40:42.727]   INFO - .rmiimpl.RemotingConnectorImpl - Starting JMX connector on service:jmx:rmi:///jndi/rmi://127.0.0.1:60806/device-3
[01:40:43.417]   INFO - toolkit.ui.actions.AmsExecImpl - Proxy connected. isNetworkMonitorSupported = false
[01:40:44.228]   INFO - un.jme.toolkit.bootstrap.Batch - Objects started
[01:40:45.119]  FATAL - lkit.ui.actions.AmsExecInstall - There is insufficient storage to install this suite

Also I noticed that when starting proxy from console on windows, I get some sort of warning

C:\oracle-jmee-8-0-rr-raspberrypi-linux-bin\util>java -jar proxy.jar -socket 192.168.0.105
Trying to open socket connection with device: 192.168.0.105:2201
Connected to the socket: Socket[addr=/192.168.0.105,port=2201,localport=51871]
ManagerFactory: Unable to instantiate InstallerManagerFactory: com.oracle.swm.I
nstallerManagerFactory. This disables host based installation. Only device based
installation is possible.
Open channel 8 with hash 0x3953d0af
Channel 8 CLOSED -> OPENED
notifyResponse AVAILABLE_RESPONSE on channel 8
Channel 8 OPENED -> AVAILABLE
Open channel 9 with hash 0x0
[ERROR] [PROXY] iso=-1:Transport not connected for receive
[ERROR] [PROXY] iso=-1:Transport not connected to get input status
Channel 8 AVAILABLE -> REQUEST_SENT
notifyResponse ACK_RESPONSE on channel 8
Channel 8 REQUEST_SENT -> ACKNOWLEDGED
Channel 8 ACKNOWLEDGED -> DATA_SENT
notifyResponse AVAILABLE_RESPONSE on channel 8
Channel 8 DATA_SENT -> AVAILABLE
Channel 8 AVAILABLE -> REQUEST_SENT
notifyResponse ACK_RESPONSE on channel 8
Channel 8 REQUEST_SENT -> ACKNOWLEDGED
Channel 8 ACKNOWLEDGED -> DATA_SENT
notifyResponse AVAILABLE_RESPONSE on channel 8
Channel 8 DATA_SENT -> AVAILABLE

The video and docs makes the deployment look quite easy, but I am stuck.

Oh and I did tinker with settings in jwc_properties.ini (increase the system.jam_space and changing the com.oracle.midp.ams.headless.listening.port to 65002, it came by default at 65012 but the docs were suggesting to use 65002 instead). Nothing has worked for me so far, would appreciate some help-

Answers

  • Hi!

    According to this "There is insufficient storage to install this suite" message your card either full or size of all installed IMlets exceeds 4Mb or IMlet size exceeds 4Mb.  You can adjust storage size at jwc_properties.ini->system.jam_space

    /Sergey

  • geoaxis
    geoaxis Member Posts: 3

    My imlet is default netbeans java ME project and the raspberry pi has 2.6 GB available in in rootfs

  • geoaxis
    geoaxis Member Posts: 3

    Ok, so I am able to start the IMLET now. All I did was unzip the javaME folder again and do a chmod 777 on all things in it. Seems to be working fine for me now.

    Although I did discover that the ams.headless.listening.port is different in the current shipping Java ME than what is described in the docs/tutorials.

  • Hi!

    Need to mention that local AMS CLI (that's what configured by ams.headless.listening.port) is deprecated and no longer to be used. AFAIK it shall not be listed in the product documentation. Could I ask you kindly suggest where you have found the reference to it? I'll work with course authors to remove the references in the course materials

    Thanks,

    Andrey

  • Hi again,

    To clarify. The port 65002 is indeed the right port for AMS CLI as it's described in the docs. There is no discrepancy between the docs and the code. That is because the connection has to be made to the host, running Developer Agent as per description in documentation. Such connection to the board which runs Java ME is not supported

    Andrey

This discussion has been closed.