Discussions
Categories
- 385.5K All Categories
- 5.1K Data
- 2.5K Big Data Appliance
- 2.5K Data Science
- 453.4K Databases
- 223.2K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 47 Multilingual Engine
- 606 MySQL Community Space
- 486 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.2K ORDS, SODA & JSON in the Database
- 585 SQLcl
- 4K SQL Developer Data Modeler
- 188K SQL & PL/SQL
- 21.5K SQL Developer
- 46 Data Integration
- 46 GoldenGate
- 298.4K Development
- 4 Application Development
- 20 Developer Projects
- 166 Programming Languages
- 295K Development Tools
- 150 DevOps
- 3.1K QA/Testing
- 646.7K Java
- 37 Java Learning Subscription
- 37.1K Database Connectivity
- 201 Java Community Process
- 108 Java 25
- 22.2K Java APIs
- 138.3K Java Development Tools
- 165.4K Java EE (Java Enterprise Edition)
- 22 Java Essentials
- 176 Java 8 Questions
- 86K Java Programming
- 82 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 208 Java User Groups
- 25 JavaScript - Nashorn
- Programs
- 667 LiveLabs
- 41 Workshops
- 10.3K Software
- 6.7K Berkeley DB Family
- 3.6K JHeadstart
- 6K Other Languages
- 2.3K Chinese
- 207 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 474 Portuguese
Not able to start imlet from netbeans to a connected rasberrypi
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
-
My imlet is default netbeans java ME project and the raspberry pi has 2.6 GB available in in rootfs
-
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