×

Discussion Board

Page 3 of 4 FirstFirst 1234 LastLast
Results 31 to 45 of 46
  1. #31
    Nokia Developer Champion
    Join Date
    Nov 2011
    Posts
    79

    Re: Help a internal RMI registry port number.

    Hi all,

    This question has been answered before in this thread:

    Currently, the only way to fix those issues you are experiencing is following: uninstall whatever version of JDK you have and install 32bit JDK7u17. It's still available for download from Oracle:

    http://www.oracle.com/technetwork/ja...k-7u17-oth-JPR

    Make sure that you use 32bit version of JDK, even if your PC is 64bit.

    SDK team is aware of this issue and hopefully something will change in the future.

    Best

  2. #32
    Registered User
    Join Date
    Mar 2003
    Posts
    4,105

    Re: Help a internal RMI registry port number.

    Thanks Michael! However, I try to run as much emulators as possible on one machine. Therefore, I seek the best JRE. The JDK seems not to be any issue.
    Quote Originally Posted by aaraodeo View Post
    Its working fine with Java 7 Update 21 32 bit (Win 7 prof 64 bit OS)
    Interesting. Here on Windows 7 Ultimate 32 bit, I cannot use Java 7 Update 21.
    Last edited by traud; 2013-07-03 at 12:20.

  3. #33
    Registered User
    Join Date
    Mar 2013
    Posts
    1

    Re: Help a internal RMI registry port number.

    Windows 7 32bits Ultimate here. I did as above - uninstalled all Javas stuff then got JDK 7u17 and Nokia SDK 2.0 for Java. Solution works perfect. No problems with registry etc. Thank you for help !

  4. #34
    Registered User
    Join Date
    Mar 2003
    Posts
    4,105

    Re: Help a internal RMI registry port number.

    marcin_marga, just a note: The new Asha software platform comes with the latest version of the Nokia IDE. I would start with that and from there load the old SDK 2.0 (to get the emulator).

  5. #35
    Registered User
    Join Date
    Mar 2003
    Posts
    4,105

    Re: Help a internal RMI registry port number.

    Did I miss the post here in the discussion board, on Twitter, on Facebook or in the Blogs?
    The Asha software platform emulator got updated on 7th of June. Now we can use Java Runtime Environment 7 Update 21 again.
    Last edited by traud; 2013-06-12 at 09:21.

  6. #36
    Registered User
    Join Date
    Jun 2013
    Posts
    1

    Re: Help a internal RMI registry port number.

    Hey Jm4
    How did U solve the RMI port problem please explain..
    I am having a same issue too..!!

    thannk in advance..!!

  7. #37
    Registered User
    Join Date
    Jun 2013
    Posts
    2

    Re: Help a internal RMI registry port number.

    i help this problem asha sdk 2.0 in emulator error "The internal RMI port 1099 may be in use by another application. if the SDK does not start selected The Networking tab and enter another internal RMI registry por number." what the solution for this?

  8. #38
    Registered User
    Join Date
    Nov 2004
    Posts
    12

    Re: Help a internal RMI registry port number.

    I installed current latest Asha SDK build Nokia_Asha_SDK_1_0_installer_offline_em_update1.zip (460 MB) on the latest j2se 1.7.0_25 32 bit on windows 7 64 bit edition. It is working fine and the old internal RMI port error is not coming now. Note: I haven't installed any 64 bit java on machine. After installation it updated the emulator which is working fine too. Waiting for the final ver of sdk and hope it will continue to work fine with latest version of j2se 32 bit as well 64 bit.

  9. #39
    Registered User
    Join Date
    Mar 2003
    Posts
    4,105
    Alejandro, I start the Asha software platform emulator (Nokia 501) from Windows Start menu. Then, all previous emulators do start. Because of that, I put the Asha software emulator into my auto-start items. Alternatives are to go back to Java 7 Update 17 or Java 6 Update 43. Did that fix your issue?
    Quote Originally Posted by ad_ditya98 View Post
    Jm4, how did you solve the RMI port problem?
    Jm4 removed the latest Java Runtime and downgraded to Java 7 Update 17. Did that fix your issue?
    Quote Originally Posted by jm4 View Post
    Downgrading the Java version is out of the question with known security issues in the wild.
    I recommend to use this in a virtual machine or a stand-alone development machine. If you cannot afford this, you are able to disable the Java plug-in within your Internet browsers. Anyway, the trick to use the latest Asha software platform emulator and then using the older emulators works for me even with the latest Java Runtime updates.

  10. #40
    Registered User
    Join Date
    Oct 2013
    Posts
    1

    Re: Help a internal RMI registry port number.

    See http://docs.oracle.com/javase/7/docs...cements-7.html.
    "From JDK 7 Update 21, the RMI property java.rmi.server.useCodebaseOnly is set to true by default. In earlier releases, the default value was false"
    I assume this will be broken forever now as it is a change of policy by Oracle. I am using 1.7.0_40 32 bit on Win7 64 bit and got round the problem by explicitly starting the rmiregistry daemon in a cmd tool before running the emulator using
    rmiregistry -J-Djava.rmi.server.useCodebaseOnly=false.
    This sets the rmi behaviour back to how it was pre-update 21 and the emulator worked as expected thereafter.

  11. #41
    Nokia Developer Moderator
    Join Date
    Feb 2006
    Location
    Oslo, Norway
    Posts
    28,698

    Re: Help a internal RMI registry port number.

    This is a very useful finding, thank you for posting.

  12. #42
    Registered User
    Join Date
    Feb 2013
    Posts
    31

    Re: Help a internal RMI registry port number.

    Quote Originally Posted by Dris101 View Post
    See http://docs.oracle.com/javase/7/docs...cements-7.html.
    "From JDK 7 Update 21, the RMI property java.rmi.server.useCodebaseOnly is set to true by default. In earlier releases, the default value was false"
    I assume this will be broken forever now as it is a change of policy by Oracle. I am using 1.7.0_40 32 bit on Win7 64 bit and got round the problem by explicitly starting the rmiregistry daemon in a cmd tool before running the emulator using
    rmiregistry -J-Djava.rmi.server.useCodebaseOnly=false.
    This sets the rmi behaviour back to how it was pre-update 21 and the emulator worked as expected thereafter.
    If I try that command I get this error:
    Code:
    C:\Users\Revolt>rmiregistry -J-Djava.rmi.server.useCodebaseOnly=false
    java.rmi.server.ExportException: Port already in use: 1099; nested exception is:
            java.net.BindException: Address already in use: JVM_Bind
            at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:329)
            at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:237)
            at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:411)
            at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:147)
            at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:207)
            at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:122)
            at sun.rmi.registry.RegistryImpl.<init>(RegistryImpl.java:108)
            at sun.rmi.registry.RegistryImpl$3.run(RegistryImpl.java:353)
            at sun.rmi.registry.RegistryImpl$3.run(RegistryImpl.java:351)
            at java.security.AccessController.doPrivileged(Native Method)
            at sun.rmi.registry.RegistryImpl.main(RegistryImpl.java:350)
    Caused by: java.net.BindException: Address already in use: JVM_Bind
            at java.net.DualStackPlainSocketImpl.bind0(Native Method)
            at java.net.DualStackPlainSocketImpl.socketBind(DualStackPlainSocketImpl.java:106)
            at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:376)
            at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:190)
            at java.net.ServerSocket.bind(ServerSocket.java:376)
            at java.net.ServerSocket.<init>(ServerSocket.java:237)
            at java.net.ServerSocket.<init>(ServerSocket.java:128)
            at sun.rmi.transport.proxy.RMIDirectSocketFactory.createServerSocket(RMIDirectSocketFactory.java:45)
            at sun.rmi.transport.proxy.RMIMasterSocketFactory.createServerSocket(RMIMasterSocketFactory.java:344)
            at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:666)
            at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:318)
            ... 10 more

  13. #43
    Registered User
    Join Date
    Mar 2003
    Posts
    4,105

    Re: Help a internal RMI registry port number.

    Dris101, that works great here with Java 7 Update 45 on Windows 7 32bit. Because I do not use a JDK but a JRE, let us refine that command a bit:
    Code:
    Start » All Programs » Accessories » Notepad:
    "C:\Program Files\Java\jre7\bin\rmiregistry" -J-Djava.rmi.server.useCodebaseOnly=false
    and we put that into Start » All Programs » Startup » right-click » Open all users
    By the way, in the first week of August, the final version of the SDK with the Nokia Asha Software Platform (Nokia Asha 501) emulator and Nokia IDE was released.
    Last edited by traud; 2013-11-20 at 12:46.

  14. #44
    Registered User
    Join Date
    Mar 2003
    Posts
    4,105

    Re: Help a internal RMI registry port number.

    Quote Originally Posted by traud View Post
    In the first week of August, the final version 1.0 of the SDK with the Nokia Asha Software Platform (Nokia Asha 501) emulator and Nokia IDE was released.
    And today we saw an update to version 1.1 …
    Quote Originally Posted by traud View Post
    Did I miss the post here in the discussion board, on Twitter, on Facebook or in the Blogs?
    Just follow the Nokia Developer tweet …

  15. #45
    Registered User
    Join Date
    Feb 2013
    Posts
    31

    Re: Help a internal RMI registry port number.

    Quote Originally Posted by traud View Post
    And today we saw an update to version 1.1 …Just follow the Nokia Developer tweet …
    Are you replying to yourself? Why?

Similar Threads

  1. a internal RMI registry port number.
    By sunnybest1990 in forum Mobile Java General
    Replies: 8
    Last Post: 2012-05-29, 15:02
  2. Push Registry when MiFare Internal Tag is accessed
    By mmartinleon in forum Near Field Communication
    Replies: 1
    Last Post: 2008-03-19, 09:20
  3. push registry port problem
    By Larry101 in forum Mobile Java General
    Replies: 7
    Last Post: 2007-12-14, 22:46
  4. Replies: 1
    Last Post: 2004-10-05, 05:05
  5. Replies: 3
    Last Post: 2004-08-26, 10:15

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
×