Custom Query (172 matches)

I'm running my modeltrains with the in Java written program iTrain (​http://www.berros.eu/itrain/download/preview/iTrain_install.jar). So I was very curious to see if it would run on eCS. Just tested the 1.6 JRE beta with the latest Beta version 2.0.0-b44 of iTrain (build 2011/01/02). Here are some results:

1. Installation of iTrain runs fine, except the progress bars, they were empty and therefore nothing visible happened.
2. iTrain is coming with two special Java DLL's for serial port support (JSPOS2J.DLL and SCCOMIO.DLL) for OS/2. Still there is no serial port connection possible. Both DLL's were put in the /JRE/bin directory and Java 1.6 crashed as soon as in the iTrain application the menu to check the serial interface was opened. Below you will find the output of the commandline during the crash:

OpenJDK Client VM (build 16.0-b13, mixed mode)

[D:\Programs\ITRAIN2TEST]java -jar D:\Programs\iTrain2test\itrain.jar Serialio Library: version 9.9.9: build 9193 Copyright (c) 1996-2008 Serialio.com, All Rights Reserved. os.name="OS/2", os.arch="x86" SerialPort? class loaded: jspos2j # # A fatal error has been detected by the Java Runtime Environment: # # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x10cce647, pid=1140, tid=74711 056 # # JRE version: 6.0 # Java VM: OpenJDK Client VM (16.0-b13 mixed mode os2-x86 ) # Problematic frame: # V [JVM+0x25e647] # # An error report file with more information is saved as: # C:\var\temp\hs_err_pid1140.log SYS1808: The process has stopped. The software diagnostic code (exception code) is 001E.

3. iTrain is a heavy swing application. On the eCS 2.0 platform with Java 1.6 beta no "drag and drop" was possible within the iTrain application (e.g. it should be possible to drag a locomotive from the loc list to the throttle window, see also attached screenshot). Furthermore some context menu's disappear as soon as they were tried to open.

These are my first impressions with Java 1.6 beta for OS/2 & eCS tested on a T42 IBM Thinkpad

Java 6 still feels a quite a bit slow (in some areas). To demonstrate it, I used Jeti/2, measuring time from starting it and until GUI is up and roster and 4 MUCs (2 on local server 2 on remote) are populated.

All tests done from same client PC, only the loaded Java versions are different.

Jabber server Java 6 on eCS

Time to start Jeti/2 until roster and 4 MUC are filled

Java 1.41 | Java 1.42 | Java 1.50 | Java 1.60 |

| | | |

9 secs | 20 secs | 45 secs | 35 secs | 9 secs | 15 secs | 35 secs | 25 secs | 9 secs | 25 secs | 38 secs | 33 secs | 9 secs | 16 secs | 30 secs | 24 secs |

| | | |

1) 2) 3) 4)

(A lot more tests was actually done - these are the best results)

1) Java 1.41 loads in 9 secs in almost every test done.

2) Between 15-25 secs in mosts test. Not easy to see any specific

slow part.

3) Has seems to have some timing issues with sockets / DNS - hang

for a long time in same place.

4) Lots of tests were over 1 minut to load. Splash screen is

visible slowly drawn in parts. Communication with server seems to take a long time.

There seems to be room for improvement - although it may be hard to compete with our native 1.41

Java includes a dependence on ​ftp://ftp.netlabs.org/pub/gcc/gcc4core.wpi. This can result in multiple installs of these DLLs, wasted bandwidth downloading them yet again for very little benefit. Simple solution is to set GCCOPT='-static-libgcc' This will statically link the couple of small functions that may be needed.