Eclipse Version: 3.3.1.1 Build M20071023-1652
Logback-Plugin Version: 1.0.1
Slf4j: 1.5.0
Logback-core/Logback-classic: 0.9.9

Well, the main issue is stated in the summary, i have a simple java class with some logging output which should appear in the Eclipse Logback View.

Here is the logging statement that gets executed:
logger.info("This is an test")

I have set up an logback-test.xml which uses the
<console-Plugin> and an Console-Appender.

The Plugin is installed and configured with the standard values (Port 4321).
netstat show me the port set up by eclipse.

Now i run my program (while running tcpdump on the port).

Logevents appear on the console but not in the plugin.

After examining the network trace i saw many TCP CHECKSUM INCORRECT Pakets such as the following:

6 0.144089 127.0.0.1 127.0.0.1 TCP 46684 > 4321 [PSH, ACK] Seq=5 Ack=1 Win=32832 [TCP CHECKSUM INCORRECT] Len=400 TSV=1642891 TSER=1642857

0000 00 00 00 00 00 00 00 00 00 00 00 00 08 00 45 00 ..............E.
0010 01 c4 29 b8 40 00 40 06 11 7a 7f 00 00 01 7f 00 ..).@.@..z......
0020 00 01 b6 5c 10 e1 d9 5c 38 d7 d9 b6 b8 79 80 18 ...\...\8....y..
0030 02 01 ff b8 00 00 01 01 08 0a 00 19 11 8b 00 19 ................
0040 11 69 73 72 00 27 63 68 2e 71 6f 73 2e 6c 6f 67 .isr.'ch.qos.log
0050 62 61 63 6b 2e 63 6c 61 73 73 69 63 2e 73 70 69 back.classic.spi
0060 2e 4c 6f 67 67 69 6e 67 45 76 65 6e 74 2a b0 05 .LoggingEvent*..
0070 69 f2 3a cf 95 03 00 09 4a 00 09 74 69 6d 65 53 i.:.....J..timeS
0080 74 61 6d 70 5b 00 0f 63 61 6c 6c 65 72 44 61 74 tamp[..callerDat
0090 61 41 72 72 61 79 74 00 28 5b 4c 63 68 2f 71 6f aArrayt.([Lch/qo
00a0 73 2f 6c 6f 67 62 61 63 6b 2f 63 6c 61 73 73 69 s/logback/classi
00b0 63 2f 73 70 69 2f 43 61 6c 6c 65 72 44 61 74 61 c/spi/CallerData
00c0 3b 4c 00 10 66 6f 72 6d 61 74 74 65 64 4d 65 73 ;L..formattedMes
00d0 73 61 67 65 74 00 12 4c 6a 61 76 61 2f 6c 61 6e saget..Ljava/lan
00e0 67 2f 53 74 72 69 6e 67 3b 4c 00 10 6c 6f 67 67 g/String;L..logg
00f0 65 72 52 65 6d 6f 74 65 56 69 65 77 74 00 2d 4c erRemoteViewt.-L
0100 63 68 2f 71 6f 73 2f 6c 6f 67 62 61 63 6b 2f 63 ch/qos/logback/c
0110 6c 61 73 73 69 63 2f 73 70 69 2f 4c 6f 67 67 65 lassic/spi/Logge
0120 72 52 65 6d 6f 74 65 56 69 65 77 3b 4c 00 06 6d rRemoteView;L..m
0130 61 72 6b 65 72 74 00 12 4c 6f 72 67 2f 73 6c 66 arkert..Lorg/slf
0140 34 6a 2f 4d 61 72 6b 65 72 3b 4c 00 0e 6d 64 63 4j/Marker;L..mdc
0150 50 72 6f 70 65 72 74 79 4d 61 70 74 00 0f 4c 6a PropertyMapt..Lj
0160 61 76 61 2f 75 74 69 6c 2f 4d 61 70 3b 4c 00 07 ava/util/Map;L..
0170 6d 65 73 73 61 67 65 71 00 7e 00 02 4c 00 0a 74 messageq.~..L..t
0180 68 72 65 61 64 4e 61 6d 65 71 00 7e 00 02 4c 00 hreadNameq.~..L.
0190 0d 74 68 72 6f 77 61 62 6c 65 49 6e 66 6f 74 00 .throwableInfot.
01a0 31 4c 63 68 2f 71 6f 73 2f 6c 6f 67 62 61 63 6b 1Lch/qos/logback
01b0 2f 63 6c 61 73 73 69 63 2f 73 70 69 2f 54 68 72 /classic/spi/Thr
01c0 6f 77 61 62 6c 65 49 6e 66 6f 72 6d 61 74 69 6f owableInformatio
01d0 6e 3b n;

As you can see, the logging statement could not be found in the network paket.