From 781512114b4c304f3c72af251e4f416767afe20a Mon Sep 17 00:00:00 2001
From: jestin
Date: Tue, 7 Jan 2003 17:12:59 +0000
Subject: 1.2.3 bientôt dans les bois

---
 BUGS             | 37 ++++++++++++++++++++++++++++++++++++-
 Changelog        | 13 ++++++++++++-
 Makefile         |  5 ++++-
 debian/changelog | 20 ++++++++++++++++++++
 4 files changed, 72 insertions(+), 3 deletions(-)

diff --git a/BUGS b/BUGS
index db1d6fc..5caadf1 100644
--- a/BUGS
+++ b/BUGS
@@ -12,7 +12,42 @@ TODO List:
 -------------------------------------------------------------------------------------
 Known bugs:
 
-  -> i'm writing a testbench for the Api ( TestAPI ) . In progress.
+réf: [BUGXX]
+
+   Using the Blackdown Linux jdk 1.1.8_v3, the console is flooded with the
+   following messages :
+   -->ivy<-- Error IvyServer exception:  Socket closed
+   Ivy server socket reader caught an exception Socket closed
+   java.net.SocketException: Socket closed
+   at java.net.PlainSocketImpl.close(PlainSocketImpl.java:408)
+   at java.net.SocketImpl.reset(SocketImpl.java:227)
+   at java.net.ServerSocket.implAccept(ServerSocket.java:207)
+   at java.net.ServerSocket.accept(ServerSocket.java:181)
+   at fr.dgac.ivy.Ivy.run(Ivy.java:441)
+   at java.lang.Thread.run(Thread.java)
+   It seems to be a bug in the JVM implementation. This is reproduced with the
+   -native and -green flags .
+   It doesn't happen with the 1.1.7A sun JDK on a solaris box.
+
+réf: [BUGXY]
+
+   Using the blackdown jdk 1.2.2
+   Classic VM (build Linux_JDK_1.2.2_FCS, native threads, sunwjit)
+   The program sometimes hang or head to a SIGSEGV ( extract below )
+   SIGSEGV   11*  segmentation violation
+    si_signo [11]: SIGSEGV   11*  segmentation violation
+    si_errno [0]: Succès
+    si_code [1]: SEGV_MAPERR [addr: 0x890096C]
+        stackpointer=0xbe9ff234
+    Full thread dump Classic VM (Linux_JDK_1.2.2_FCS, native threads):
+    "Thread-6" (TID:0x40efc090, sys_thread_t:0x8219e78, state:CW, native
+    ID:0x4000) prio=5
+    "Thread-3" (TID:0x40efc030, sys_thread_t:0x821ab88, state:R, native
+    ID:0x20009) prio=5
+        at fr.dgac.ivy.IvyClient.<init>(IvyClient.java, Compiled Code)
+        at fr.dgac.ivy.Ivy.addClient(Ivy.java, Compiled Code)
+    I don't know if it is the jvm thread implementation or my code. I will
+    eventually investigate.
 
 -------------------------------------------------------------------------------------
 Fixed:
diff --git a/Changelog b/Changelog
index f9d9e50..7f8776b 100644
--- a/Changelog
+++ b/Changelog
@@ -12,10 +12,21 @@
     - I added a regression test to check the API ( java TestApi in the tests
     directory )
     - I added the early disconnexion test ( probe < /dev/null )
-  bugfix
+    - handles the different JVMs more cleanly in the makefiles
+    - testbenches OK for linux jdk from 1.1 to 1.4
+  bugfixes
+    - the datagram sender is encapsulated within its own thread. Closes
+      another bug.
     - IvyClient doesn't loop any more in certain conditions of remote
     disconnexion this closes the new bugreport jan/2002
     - early disconnexion is now possible ( java fr.dgac.ivy.Probe < /dev/null), 
+    - handles the InterruptedIOException happening on certain thread
+      conditions in jdk1.1 and jdk1.2. Threads and multiple VMs is a very
+      complex mix.
+  known bugs
+    - there is an Interrupt on Blackdown linux leading to an innocuous error
+      message. I will investigate later ... It is OK on Solaris jvm 1.1.7A.
+    - in Linux jdk1.2.2, a SIGSEGV from time to time.
 
 ------------------------------------------------------------------------------
 1.2.2
diff --git a/Makefile b/Makefile
index 1fc4b42..8392d43 100644
--- a/Makefile
+++ b/Makefile
@@ -3,7 +3,10 @@
      DIST = lib/ivy-java-$(VER).jar 
      DOCS = doc/html/api
 
-all: class
+all: class examples
+
+examples:
+	( cd examples; make; )
 
 class:
 	( cd src; make; )
diff --git a/debian/changelog b/debian/changelog
index 780d0a9..c98be0f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,23 @@
+ivy-java (1.2.3) unstable; urgency=low
+
+ - Many bugfixes thanks to a new testbench
+   * the datagram sender is in its own thread. Now works with jdk1.2
+   * IvyClient doesn't loop any more on a remote disconnexion
+   * early disconnect is now possible without hanging
+   * fixed a bug on older JVM with an exotic thread handling. Threads are
+     really hard to debug.
+ - new Features:
+   * directMessage now available in the API and in Probe
+   * IVYBUS System property is set according to the policy, and propagated to
+     the children. It is useful if you want to fork.
+ - new Doc
+   * README rewritten
+   * IvyDaemon as a TCP to Ivy relay is now documented
+ - new Bug found on thread handling ( blackdown linux 1.1.8-v2 )
+ - new Bug found on thread handling ( blackdown linux 1.2.2 ) SIGSEGV
+
+ -- Yannick Jestin <jestin@cena.fr>  Tue, 07 Jan 2003 18:09:00 +0200
+
 ivy-java (1.2.2) unstable; urgency=low
 
   - bugfix in IvyClient leading to a growth in CPU usage
-- 
cgit v1.1