Known Issues
This page collects known issues and general information about JXTA/JXSE. For specific bugs or detailed information, see the issue tracker.
Connectivity (JXTA)
The tables below indicates what is known about peer connectivity across release versions.
If you experience something different, make sure that a) your NATs are properly configured, b) your peers have proper IP addresses (i.e. public for Relays) and c) seeds have been set properly in EDGE peers. If you still encounter issues or have new information to provide, please report this on the development mailing list.
Remark: The 2.5 release contains a lurking bug regarding connectivity behind NATs that was initially reported here, but not replicated. Another issue was opened later and led to a patch.
Hence, 2.5 JXTA/JXSE peers do not connect properly across different LANs.
Connectivity (JXME)
During the JXTA/JXSE 2.6 release process, some connectivity tests have been performed between JXME peers and JXTA peers:
Remark: The JXME code is based on JXTA 2.4.1 code. Work is required to make it compatible with JXTA/JXSE 2.6.
NAT-ed Peers (2.5)
The 2.5 code base contains a lurking connectivity bug. Peers located behind NATs are not able to connect rapidely (and often not at all). This has been solved in release 2.6.
NetworkManager Restart (2.6)
The NetworkManager stop and restart functionality is broken. This issue has been solved in trunk code and will be part of the next release.
OSGi Manifest (2.6)
OSGi interfaces have not been exported properly in the delivered 2.6 jar manifest. This has been solved in trunk code. Those willing to use OSGi with 2.6 code should:
- Take a look at updates in current trunk pom.xml
- Check-out 2.6 code base
- Update the checked-out pom.xml
- Recompile the checked-out code
Threads Running After Shutdown (2.6)
Some developers have reported that some threads remain alive after stopping the NetworkManager. Usually, these threads stop by themselves after they have performed remaining duties.
There is a known exception: if peers are configured to use HTTP, the current Jetty library does not shutdown properly. Some threads can remain open. We have implemented a new HTTP protocol over the Netty library which will be part of the next release. This will solve this issue.
