HP NonStop G-Series - Manual (Page 32)

Incorrect CLOPT options can prevent JSL from starting
The Jolt Server Listener (JSL) parses the CLOPT options that occur in the string CLOPT="-- optionletters" to
get command-line options. The following problems can occur if you enter an incorrect option in the CLOPT
line or if it already contains an incorrect option:
When the JSL first encounters an incorrect option, it stops parsing the CLOPT clause and uses the options it
encountered up to the incorrect one.
If the incorrect option occurs before the -n option, the JSL will not parse the -n option and may not start.
The JSL may be started successfully with some of the built-in default options. For example, if the JSL
encounters an incorrect option before the -Z option (the encryption option), the JSL will be forced to use the
default value (NO ENCRYPTION). This may not be ideal.
Workaround. Make sure that you use only valid CLOPT options, as described in Table 3-1 .
Check the TUXEDO user log for any warning messages on the JSL startup.
JRLY might trim the last character in its configuration file
If the last line in the JRLY configuration file does not end with a newline character, the jrly program will
ignore the last character of the last line. Depending on what is in the last line of the configuration file, this
might result in incorrect configuration.
Workaround. Make sure that the last line in the JRLY configuration file ends with a newline character (ASCII
10 decimal).
TUXVERSION and JOLTVERSION are not supported
The attributes TUXVERSION and JOLTVERSION in the class JoltSessionAttributes are not supported in Jolt
1.1. They still exist for compatibility reasons.
Workaround. Do not reference the values of these attributes. The attributes will be removed in a future version
of Jolt. Remove references to these attributes in your existing applications.
The client program may hang when calling JoltSession.endSession()
Note
This situation should only arise during application development.
The client program may hang when calling JoltSession.endSession().
Workaround. Don't call a JoltSession.endSession(). Allow the Java garbage collection to call the Jolt
endSession().
Note that in JDK 1.1, JavaSoft has fixed a socket bug that causes this error.
Limit of 64 network sockets per process
On Windows NT systems there is a limit of 64 network sockets per process. When the JRLY process is running
on a Windows NT system, it can have no more than 63 clients connected to it (one of the 64 sockets is used to
communicate with the JRLY process itself).