https://bugs.winehq.org/show_bug.cgi?id=51903
Bug ID: 51903 Summary: Nokia SDK 2.0: Can't detect Java RMI ports Product: Wine Version: 6.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: joseskvolpe@gmail.com Distribution: ---
Created attachment 70854 --> https://bugs.winehq.org/attachment.cgi?id=70854 Screenshot
Wine fails to connect Nokia SDK to a open Java RMI port. After opening the software ($NOKIADIR/bin/emulator.exe), it shows a pop-up with a message saying:
"The internal RMI registry port 1099 may be in use by another application. If the SDK does not start select the Networking tab and enter another internal RMI registry port number."
Forcing to initialize the RMI from Wine (wine start $JDK_DIR/bin/rmiregistry.exe $PORT) or from Java for Linux (rmiregistry $PORT), or changing the port number, doesn't changes the result.
After pressing Ok, the applciation crashes with this message on Wine CMD:
Error: invalid query "Nokia SDK 2.0 for Java" Connection Terminated
I'm reporting it on Wine 6.16 because that's currently the latest version for my distribution, but i've tried it on Wine 6.19 too.
I've reported it in the forum with some screenshots: https://forum.winehq.org/viewtopic.php?f=8&t=35774 I've also reported it on AppDB: https://appdb.winehq.org/objectManager.php?sClass=version&iId=40335
Procedures: 1 - First, that's needed to install 32-Bits Java 1.6 for Windows to run this application. Java 1.7 works too according to the software changelogs. You can download it from Oracle but you'll need to login: https://www.oracle.com/java/technologies/downloads/archive/ 2 - Install Nokia SDK 2.0 3 - Run it from the shortcut or from the EXE located in bin/emulator.exe
Download for Nokia SDK 2.0: https://www.softpedia.com/get/Programming/SDK-DDK/Nokia-SDK.shtml SHA1 (Offline installer): 969dc440a420a7a3a210518f7fc4730f52826ad2
https://bugs.winehq.org/show_bug.cgi?id=51903
Josesk Volpe joseskvolpe@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Other
https://bugs.winehq.org/show_bug.cgi?id=51903
Josesk Volpe joseskvolpe@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Distribution|Other |ArchLinux
https://bugs.winehq.org/show_bug.cgi?id=51903
--- Comment #1 from Bruni earns.61@gmail.com --- Hi Josesk!
Please take a look at https://stackoverflow.com/questions/8630779/the-internal-rmi-registry-port-1...
It looks like Windows users observed the same issue since Java 7 u21 (and Java 6 u45).
I tried to change the port, killed all other java apps, but no luck. In the end, the problem turned out to be a jdk/jre bug. Apparently, the bug surfaced since 1.6 u 29. So switching to older JDK should fix the problem. I uninstalled jdk and installed JDK1.6 update 23 and it's working fine now!
Try removing Nokia SDK 2.0 and install SDK 1.1, JDK1.6 update 23 since it worked for that windows user.
https://bugs.winehq.org/show_bug.cgi?id=51903
--- Comment #2 from Josesk Volpe joseskvolpe@gmail.com --- Created attachment 70858 --> https://bugs.winehq.org/attachment.cgi?id=70858 Working in JDK 6u23
¡Great, it works! Thanks ^w^ Instead of installing v1.1, i kep the 2.0 version and installed JDK 6u23
https://bugs.winehq.org/show_bug.cgi?id=51903
--- Comment #3 from Josesk Volpe joseskvolpe@gmail.com --- I'm making some tests, then i'll give a new rating for this software
https://bugs.winehq.org/show_bug.cgi?id=51903
--- Comment #4 from Josesk Volpe joseskvolpe@gmail.com --- ¿May i close this bug report as NOTOURBUG?
https://bugs.winehq.org/show_bug.cgi?id=51903
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID
--- Comment #5 from Ken Sharp imwellcushtymelike@gmail.com --- Invalid
https://bugs.winehq.org/show_bug.cgi?id=51903
Anastasius Focht focht@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@gmx.net
--- Comment #6 from Anastasius Focht focht@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/De...
https://web.archive.org/web/20121022153258/http://www.developer.nokia.com/in...
Snapshot:
https://web.archive.org/web/20211110080017/https://download.informer.com/win...
$ 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//sf...
$ 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/techn...
--- 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
https://bugs.winehq.org/show_bug.cgi?id=51903
Gijs Vermeulen gijsvrm@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #7 from Gijs Vermeulen gijsvrm@gmail.com --- Closing.
-
WineHQ Bugzilla