Peer Information Protocol; used by peers to obtain
Starting from a clean state Some problems can be caused by stale configuration or cache information. Try removing the JXTA configuration files and cache directory: n ./.jxta/PlatformConfig n ./.jxta/cm (directory) Re-launch the application. When the Configuration window appears, enter the appropriate information for your network configuration. See http://platform.jxta.org/java/confighelp.html for more details on running the JXTA Configurator. Displaying additional log information If your JXTA application isn t behaving as you expect, you can turn on additional logging so that more information is displayed when your application runs. To select a new logging, or trace, level, re-run the JXTAConfigurator and from the Advanced Settings tab select the desired Trace Level from the pull-down menu. The default trace level is error; warn, info, and debug levels provide more information. For more information on running the JXTA Configurator, please see Appendix , Emphasisparatextefault . You can also choose to edit the PlatformConfig file in the current directory rather than rerunning the JXTA Configurator. For example, the following entry in PlatformConfig sets the trace level to “warning”:
Note: If you are looking for good and high quality web space to host and run your java application check Lunarwebhost java web hosting services