Known Bugs
On this page we will describe bugs in the current release of Renew.
You can also read about bugs in earlier versions.
- Cannot install under Windows
-
Description: During the installation process, the installation script terminates because of limited environment space.
Environments: Windows.
Cause: installation scripts.
Remedy: Increase the environment space in the properties of your DOS window.
- Some menu entries have no effect (for example: File->Exit)
-
Description: After pressing the mouse button on the menu bar, holding the button while navigating through the menu, and releasing it on the chosen menu item, nothing happens.
Environments: Java 6 (on Unix operating systems).
Cause: Java bug. It occurs when the chosen menu item is rendered outside the menu frame (i.e. the menu extends beyond the Renew status line).
Workaround: Either navigate through the menus by short clicks on navigation entries. Or download and install a Java 1.5 runtime environment and use that to execute Renew.
- Simulation startup sporadically hangs for 3 minutes
-
Description: After starting a simulation, it takes 3 minutes until the first net instance window is shown.
Environments: Java 5 and 6 (on Linux and Mac OS X operating systems).
Cause: Java bug. The remote simulation observation layer creates RMI-enabled objects that might be accessed both locally and remote, depending on the simulation configuration. However, depending on the networking configuration of the JVM host machine, there might be a 3-minute delay during RMI setup.
Workaround: Reconfigure the networking setup of the machine. According to comments on the Java bug, firewalls should be configured to allow local loopback connections for IPv4 and IPv6. A simpler measure on some notebooks might be to disable all WLAN or VPN connections.
Remedy: According to the Java bug report, the bug will be fixed in Java 7.
- Syntax error message about linkage problem
-
Description: After editing an inscription or when compiling a net, the syntax error window shows up with the follwing message:
Variable expected, but xxx is class with linkage problem:
java.lang.NoClassDefFoundError: some/package/xxx (wrong name: some/package/Xxx)Environments: Windows.
Cause: Due to a bug fix from release 2.0.1 to 2.1, the Java Net Compiler no longer ignores a
LinkageErrorreported by the class loader. One situation where the Java class loader reports such an error is when it is queried for a class name and finds a file on a case-insensitive file system (e.g. on Windows machines) that matches the name up to the case. This imposes a problem for Renew when untyped nets are combined with generic imports (e.g.import some.package.*;) or classes in the unnamed package.Workaround: There are alternative solutions that free Renew from the need to guess what the meaning of the name is. Either...
- ... declare all variables,
- ... use specific imports, or
- ... rename the variables so that they really differ from any class name.