Skip to main content

Can multiple instances of JXTA run on the same PC (it does not seems so)

6 replies [Last post]
adamman71
Offline
Joined: 2007-01-31
Points: 0

Hi,

Can someone confirm that multiple instances of JXSE (i.e., applications running JXSE) cannot run on the same device? It does not seem so when I perform tests.

Thanks,

J.

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
moxi_m
Offline
Joined: 2007-02-01
Points: 0

You can shortcut the wait if you set the InfrastructureID before starting the network, like so:

NetworkConfigurator config = // get it from a NetworkManager instance
config.setInfrastructureID(PG_ID);

For peers to find each other in a LAN it is sufficient if you set their multicast ability like so:

config.setUseMulticast(true);

acid
Offline
Joined: 2008-03-03
Points: 0

Hei, I have a question about connect to rendezvous peer.

If i use default seed JXTA and connected to internet it takes 10 -30 seconds, but if i deploy rendezvous peer in my LAN and client peer connected to it , it takes more time, 1-2 minutes sometimes more. Do you thinks why this happen?

buzzheavyyear
Offline
Joined: 2005-06-18
Points: 0

It works fine - separate config dirs and different ports - I run five instances with just tcp running

- incidently, when are you likely to submit the proposal on cybersuites?

Cheers
Nick

adamman71
Offline
Joined: 2007-01-31
Points: 0

Hi buzzheavyyear,

I tried to run two peers on the same PC on separate config dir and different IP port, but they can't see each see other, I have set one as a rendezvous and I set it as a seed rendezvous for the other, but it does not help. Did you use a peer on a remote PC to help them connect together? Did you do something special?

About the cybersuite, if think this issue can be tackled by modifying the code of class TlsConn in package net.jxta.impl.endpoint.tls in the TlsConn(TlsTransport tp, EndpointAddress destAddr, boolean client) constructor. The setEnabledCipherSuite(String[] suites) method can be called on the ssls object after the call to ssls.setEnabledProtocols(new String[]{"TLS"}) to restrain the usage to specific cipher suites.

My belief is that only TLS_DH_RSA_WITH_3DES_EDE_CBC_SHA should be selected as a suite (full diffie-hellman, RSA for certification, triple des for ciphering and SHA for hashing). There is also possibility to use another version of TLSv1, but there might be compatibility issues with previous versions of JXTA.

I don't known when I'll be able to submit a full patch and I am having second thoughts about it. I think we should simply warn people and let them make that modification if they want to.

Thanks,

J.

buzzheavyyear
Offline
Joined: 2005-06-18
Points: 0

Both the rendezvous and clients are on the same machine - I used the actual ipaddress of the machine (not localhost etc) for the seeds - normally takes 1-2 minutes to connect to the rendezvous.

As for the cybersuite, I'm quite in favour of having good security built in as default - until you raised this issue, I was quite unaware of this vunerability.

Nick

adamman71
Offline
Joined: 2007-01-31
Points: 0

I was not patient enough to wait for rendezvous connections and I needed to enable multicasting.

Thanks,

J.