This list identifies any known limitations, restrictions, or unique
behaviors in the IBM® Developer Kit for Java™.
- When a class is loaded and its superclasses are not found, the error indicates
that the original class was not found. For example, if class B extends class
A, and class A is not found when loading class B, the error indicates that
class B was not found, even though it is actually class A that was not found.
When you see an error that indicates that a class was not found, check to
make sure that the class and all of its superclasses are in the CLASSPATH.
This also applies to interfaces that are implemented by the class being loaded.
- The garbage collection heap is limited to 240 GB.
- There is no explicit limit to the number of constructed objects.
- The java.net backlog parameter on an iSeries™ server may behave differently
than on other platforms. For example:
- Listen backlogs 0, 1
- Listen(0) means to allow one pending connection; it does not disable a
socket.
- Listen(1) means to allow one pending comment, and means the same as Listen(0).
- Listen backlogs > 1
- This allows many pending requests to remain on the listen queue. If a
new connection request arrives and the queue is at the limit, then it deletes
one of the pending requests.
- You can only use the Java virtual machine, regardless of the
JDK version you are using, in multi-thread capable (that is, thread-safe)
environments. The iSeries server is thread-safe, but some file systems
are not. For a list of nonthread-safe file systems, see Integrated File System.
- Internet Protocol version 6 (IPv6) support is not fully implemented and
some side effects may occur. For more information, see Sockets.