JXTA Shell Troubleshooting Answers

  1. The jxta.exe. failed to run

  2. The JXTA.exe failed on Window NT with the exception "Cannot find OS JRE."

  3. You cannot run two instances of the platform on the same peer.

  4. Cannot find other peers via the 'peers' command.

  5. HTTP was configured, but you want to modify the configuration


  1. The jxta.exe failed to run
    Try first to remove any configuration files jxtaConfig, PlatformConfig,
    PlatformPeerGroup, and the cm directory.
    If you still have problem, you may want check if you have IE 5.5 installed.
    We recommend that you use the IE 5.5 version.

    Make sure that you don't have an already running instance of the shell on your system (Task Manager)


    If you have Java installed on your system you can also run directly:
    java -cp ../lib/jxta.jar;../lib/jxtashell.jar net.jxta.impl.peergroup.Boot
     

  2. The JXTA.exe failed on Window NT with the exception "Cannot find OS JRE."

    Known problem in the exec program that will be fixed in the next release.

    For now run the Shell via the:

    java -cp ../lib/jxta.jar;../lib/jxtashell.jar net.jxta.impl.peergroup.Boot

  3. You cannot  run two instances of the platform on the same peer.
    You need to change the TCP/IP transport port binding to enable two instances of the
    platform running on the same node. This can be done via the configuration tool
     

  4. Cannot find peers via the 'peers' command
    Wait at least 5 minutes. The rendezvous may be busy. You cannot find peers unless the are running on your subnet or you have connected to a rendezvous.  You can check your rendezvous connection via the Shell command rdvstatus.

    JXTA>rdvstatus

    ======= Rendezvous status ======

    This peer is not connected to any rendezvous

    This peer is not a rendezvous

    The command should tell you that you are connected to a least one rendezvous. If it is not the case. Try to reconfigure Jxta with a different JXTA router (see Quick Shell Configuration) or by enabling HTTP you may be behind NAT.
    Try to ping the IP address of the JXTA router to see if you can be located under
    your network configuration.

    If you are behind a firewall or NAT you MUST configure the HTTP transport.
    If you are behind a firewall, you need to have enter a valid web proxy.
    At any time you can reconfigure JXTA by entering the Shell command 'peerconfig'

    the mext time you restart the Shell the config tool will be restarted.

    Currently the JXTA configuration tool does not support well systems which have

    multiple network interfaces. We expect to make the configuration more sophisticated in the future. For now you may have to disable the network interface you do not want JXTA to use, you may also modify by hand the PlatformConfig endpoint address to hardcode the IP address you want to use.

     

  5. HTTP was configured, but you want to modify the configuration
    Run peerconfig and restart JXTA the configuration tool will run