Java User’s Guide
8.11 How To
63
s
wm_java_usersguide_v12
Page 63 of 123
2008-02-25
Confidential / Released
device reboots. You can now check the content of the file system and if the correct jar and
jad files were loaded into the correct location.
8. Analyze errors. If the above test failed, looking at your device’s behavior and your http serv-
ers access log can give you a hint as to what went wrong:
-
Ι
f the device did not terminate the running Java application and did not reboot, not even
after the safety timeout, either your SM was not understood (probably in the wrong for-
mat) or it did not properly authenticate (probably used the wrong password) or your
parameter set is incomplete for the requested operation.
- If the device terminated the running Java application, but did not access your http server,
and rebooted after the safety timeout, there were most likely some problems when open-
ing the network connection. Check your network parameters.
- If the device downloaded the jad and possibly even the jar file but then rebooted without
saving them in the file system, most likely one of the errors outlined in
Section 8.5
occurred. These are also the only errors which will return a response. They are posted to
the http server if the jad file contains the required URL.
9. Start update of remote devices. If you were able to successfully update your local device,
which is hopefully a mirror of all your remote devices, you can start the update of all other
devices.
