This week's book giveaway is in the Design forum.
We're giving away four copies of Mastering Non-Functional Requirements and have Sameer Paradkar on-line!
See this thread for details.
Win a copy of Mastering Non-Functional Requirements this week in the Design forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

HttpConnection on kyocera phone  RSS feed

Wayne Hefner
Posts: 13
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
We have developed a MIDP compliant Java application that works just fine on
a Palm IIIx using Palm OS 3.5.0 with the Java Manager and "INetLib"
extension. This extension enables httpd requests via the OS which the Java
Manager relies on for httpd based apps.
I loaded the Java Manager and app on my smartphone. The app makes a httpd
request to a server via the Java Manager. The connection is never
established. The app immediately displays the following error:
Can't open Net.lib,
error: 4615
I have noticed that I if I put the call that establishes the connection in StartApp that it works fine. However if I have the HttpConnection triggered off of a button event after the StartApp if fails with the net.lib error. If anyone has any information that may help I would appreciate it.
Andrew Morrow
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The Kyocera only provides 128K Dynamic Heap in its modified
version of Palm OS 3.5 while almost all other recent Palm
devices running Palm OS 3.5 provide 256 KB Dynamic Heap.
Also, NetLib requires 32KB of Palm OS dynamic heap
in order to be activated. The PalmOS cannot suggest
to the JVM that is it time to garbage collect,
it just returns the error.
Perhaps you should garbage collect just before you create the
HttpConnection (which will call NetLib). That will give back
to PalmOS as much memory as possible, thus giving NetLib
the best chance of the Palm OS having enough.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!