[Bug 51903] Nokia SDK 2.0: Can't detect Java RMI ports (bug in Java 7u21+ / 6u29+)
WineHQ Bugzilla
wine-bugs at winehq.org
Wed Nov 10 02:49:39 CST 2021
https://bugs.winehq.org/show_bug.cgi?id=51903
Anastasius Focht <focht at gmx.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
URL| |https://web.archive.org/web
| |/20211110080017/https://dow
| |nload.informer.com/win-1191
| |566151-4fe722a8-6e031ef5/no
| |kia_sdk_2_0_java_installer_
| |offline_emd.exe
Summary|Nokia SDK 2.0: Can't detect |Nokia SDK 2.0: Can't detect
|Java RMI ports |Java RMI ports (bug in Java
| |7u21+ / 6u29+)
Keywords| |download
CC| |focht at gmx.net
--- Comment #6 from Anastasius Focht <focht at gmx.net> ---
Hello folks,
adding stable download links via Internet Archive for documentation.
Original site:
https://web.archive.org/web/20121031153854/http://www.developer.nokia.com/Develop/Java/Tools/Series_40_platform_SDKs/
https://web.archive.org/web/20121022153258/http://www.developer.nokia.com/info/sw.nokia.com/id/d312c223-c68a-447e-b295-c3a9ebc4b630/Nokia_SDK_2.0_for_Java_offline_installer_win.html
Snapshot:
https://web.archive.org/web/20211110080017/https://download.informer.com/win-1191566151-4fe722a8-6e031ef5/nokia_sdk_2_0_java_installer_offline_emd.exe
$ sha1sum nokia_sdk_2_0_java_installer_offline_emd.exe
969dc440a420a7a3a210518f7fc4730f52826ad2
nokia_sdk_2_0_java_installer_offline_emd.exe
$ du -sh nokia_sdk_2_0_java_installer_offline_emd.exe
421M nokia_sdk_2_0_java_installer_offline_emd.exe
Affected JRE:
https://web.archive.org/web/20211110080516/https://free.nchc.org.tw/osdn//sfnet/a/ac/acts/jre-6u45-windows-i586.exe
$ sha1sum jre-6u45-windows-i586.exe
5100b8eafaa7ed73ed6dab5469ba3faff38a9ae9 jre-6u45-windows-i586.exe
$ du -sh jre-6u45-windows-i586.exe
17M jre-6u45-windows-i586.exe
Bug mention:
https://web.archive.org/web/20200701120633/https://www.oracle.com/java/technologies/javase/6u29-relnotes.html
--- quote ---
RMI Registry Issue
A bug in the rmiregistry command included in this release may cause unintended
exceptions to be thrown when an RMI server attempts to bind an exported object
which includes codebase annotations using the "file:" URL scheme. The RMI
servers most likely to be effected are those which are invoked only by RMI
clients executing on the same host as the server.
RMI annotates codebase information as part of the serialized state of a remote
object reference to assist RMI clients in loading the required classes and
interfaces associated with the object at runtime. Exported objects which are
looked up in the RMI registry and invoked by RMI clients running on hosts other
than the server are usually annotated with codebase URL schemes, such as
"http:" or "ftp:" and these should continue to work correctly.
As a workaround, RMI servers can set the java.rmi.server.codebase property to
use codebase URLs other than the "file:" scheme for the objects they export.
--- quote ---
Regards
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
More information about the wine-bugs
mailing list