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 ++++++++++++++++++++++++++++++++++++- 1 file changed, 36 insertions(+), 1 deletion(-) (limited to 'BUGS') 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.(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: -- cgit v1.1