JXTA-C 2.1.1 "Disneyland" is released !!

--=-dBn/ba1w63d4W41BLHyX
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Community Members,

We are pleased to announce the availability of a new JXTA-C release,
2.1.1 "Disneyland". The JXTA-C "Disneyland" release provides
enhancements of the JXTA-C platform along with a number of important
bug fixes. You can access the release via the following CVS Tag
(JXTA_C_2_1_01) or via the download page:
http://download.jxta.org/build/release/c/2.1.1/

The JXTA-C Release Team


Acknowledgments
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Special thanks to all of the community members who have contributed
ideas, reported problems, provided patches, and have helped greatly to
improve the quality, and robustness of this release.

Particularly for this release:

- Saleem Muhammed <[email protected]>: Serious testing on Win32
  platform, bug reporting, memory/object leak fixes.
- Mathieu Jan <[email protected]>: Memory/object leak fixes
- Mike Duigou <[email protected]>, Mohamed Abdelaziz <[email protected]>:
  Object tracking

Also following people has been contributing a lot, although we failed
to include their contribution in this release, you bet we will see
those great enhancements in next 2.2 Palau release:

- Stefan Lankes <[email protected]>: Win32 DLL support, Win32 installer,
  and volunteer to maintain Win32 port.
- Rick Keiner <[email protected]>: XPath based query, SQL based CM,
  Rendezvous server support
- Mike Duigou <[email protected]>: Rendezvous server support


New Features & Significant Changes
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

- Rules for sharing/release Jxta_object

  The rules for jxta_object sharing/release is documented at
  http://wiki.java.net/bin/view/Jxta/JxtaCRefCount and we should be
following
  the rules for new code, and fix the existing code as we found them
  inconsistent.

- Major cleanup on memory/object leaks

  Cleanup on object/memory leak had been huge in this release. By
defining
  JXTA_OBJECT_TRACKING_ENABLE to 1(non-zero), all object reference count
  activity will appear in the log. By analyzing the log, you will be
able to
  spot object leak much easier then before. If you don't need a global
  tracking, you can also do JXTA_INIT_OBJECT_FLAGS with
JXTA_OBJECT_SHARE_TRACK
  flag, and that enables tracking on a particular class.

- PipeResolver now correctly handling PeerAdvertisement element
 =20
  In previous version, the pipe may not be resolved in time without
enabling
  multicast, the reason is that the PeerAdvertisement element in the
message
  was not correctly encoded. With this bug fix, the PipeResolver now is
much
  more reliable.

- New log level "paranoid" was introduced

  One additional log level "PARANOID" is now available for more verbose
  diagnostic. Refer to
http://wiki.java.net/bin/view/Jxta/JxtaCconventions for
  the appropriate usage.

- A new patched apr-0.9.6 for Win32 platform had been provided

  A bug had been found in libapr for Win32 platform which can cause
deadlock in
  case you create a Jxta_listeners allow multiple threads. Patch had
been
  tested and submitted to apr project(http://apr.apache.org). Before the
apr
  project adapts the patch, Win32 user will need to apply the patch
manually. A
  pre-built binary for your convenience is available at:
  http://jxta-c.jxta.org/files/documents/141/204/apr-0.9.6-win32.zip.


Downloading and Installing
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

You can download the dist tarball from:
http://download.jxta.org/build/release/c/2.1.1/
or alternatively directly access CVS with the tag "JXTA_C_2_1_01".

The instruction on how to build JXTA-C can be found at:
http://jxta-c.jxta.org/build.html
http://wiki.java.net/bin/view/Jxta/HowToBuildJXTA-C

You can download patched libapr for Solaris 8, Windows and RedHat
pre-built by JXTA team at:
http://jxta-c.jxta.org/servlets/ProjectDocumentList


Known incompatibilities between JXTA-C 2.1.1 and prior JXTA-C 2.x
releases
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

- The handler function for Jxta_listener should not release the
  Jxta_object passed to it based on the rule we established, the
  Jxta_listener will release the object instead.

- Create Jxta_listener with max queue size to 0 will now enforce a
  synchronize call to the listener function even though calling
  jxta_listener_schedule_object. This make sense in semantic meaning
  and should not really create a compatibility problem since 0 should
  have not been used as the behavior is undefined.


Issued Closed During JXTA-C 2.1.1
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
78   DEFECT       P1  jxta_object_priv.h cannot be found in the
distribution
107  DEFECT       P1  segfault in jxta_cm when call publish with invalid
adv type
19   DEFECT       P2  Http Poller error when multiple RDV are configured
72   DEFECT       P2  cat Env-0 after join a group cause segfault
73   DEFECT       P2  Memory leak on OutputPipe
75   DEFECT       P2  segfault after join a group
76   DEFECT       P2  peer connect to different peers as rdv/relay fails
receiving messages
79   DEFECT       P2  Segmantation fault in jxtaShell
82   PATCH        P2  shutdown rdv_client
16   DEFECT       P3  jxtaShell: env vars not flushed when ads flushed
77   DEFECT       P3  Bug in jxta_objecthash_test and object_hash_test
83   DEFECT       P3  Jxta object reference count issue
101  DEFECT       P3  Seg.fault when isClient (relay) is false
104  DEFECT       P3  Segmentation Fault in jxta_log_terminate
105  DEFECT       P3  Test program jstring_test calls the wrong function
114  DEFECT       P3  Not releasing thread handle on windows platform
85   PATCH        P3  Pipe service implementations never get released
86   PATCH        P3  Patch for issue 83
87   PATCH        P3  Painfully over complicated jpr_thread_delay?
89   PATCH        P3  Patch for jxta relay service release
90   PATCH        P3  Jxta listener with thread never get released
92   PATCH        P3  Removing rdv reference inside resolved service
93   PATCH        P3  Remove transport_tcp from endpoint service
94   PATCH        P3  Need to remove double self reference insde tcp
connection constructor
95   PATCH        P3  Patch for issue 89
96   PATCH        P3  Patch for failing to release listener
97   PATCH        P3  Patch to call jxta_initialize/jxta_terminate
multiple times
98   PATCH        P3  Patch to destroy vector mutex
113  PATCH        P3  Bug fixes using Valgrind
115  PATCH        P3  Fixed memory leaks
63   ENHANCEMENT  P3  improve usefullness of jxta_hashtable_stats
67   ENHANCEMENT  P3  Change JXTA_OBJECT_RELEASE for better bug
detection
112  ENHANCEMENT  P3  listener provider should be able to decide how
listener function should be called


Known issues in JXTA-C 2.1.1=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
None. There is no open defects causing substantial problem in JXTA-C
2.1.1. You can see a full list of currently open issues for JXTA-C at
following URL:

http://jxta-c.jxta.org/issues/buglist.cgi?issue_status=3DUNCONFIRMED&issue_=
status=3DNEW&issue_status=3DSTARTED&issue_status=3DREOPENED



--=-dBn/ba1w63d4W41BLHyX
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBCr3ZaLNaoAyBG0PURApQJAJ9nsf5xMWW7jsxL8WzGo/cbFca8SACfZ8o7
ysDrbPA5nJR7S6LIePQUIUM=
=edT/
-----END PGP SIGNATURE-----

--=-dBn/ba1w63d4W41BLHyX--