NonStop JMS User's Manual (H06.03+, J06.03+, NonStop JMS 3.0+)

Reliable Messaging Bridge
NonStop Server for Java Message Service User’s Manual—522356-006
5-27
Optional Files Created by the User

Bridge.reconnect.delay
An example of the sampl.properties file generated during the Add a Bridge
Pathway Configuration with Server Class on page 5-10 is
Optional Files Created by the User
You can override or add to the properties for a server class by creating files which
contain properties that the bridge process will apply only to the specified server class.
The server_class.jndi.properties file and the
pathmon_process_name.server_class_name.properties file are described
below.
server_class.jndi.properties File
The server_class.jndi.properties file is an optional file you create if you have
additional JNDI properties to specify for a specific server class in addition to the
general JNDI properties specified in the add dest command.
You create this file using an editor of your choice and populate the file with the
additional JNDI properties that you want to apply to the specified server class. The file
must be named
server_class.jndi.properties
where server_class is the name entered at the Pathway Server Class Name:
prompt in the add bridge command (for example, qtoq.jndi.properties).
At startup, the JNDI values specified in the add dest command are passed to the
bridge process on the command line in the start script. The bridge process then
Default: 60000
Values: milliseconds
Value
Descriptions:
milliseconds—The time (in milliseconds) between
when a connection is lost and an attempt is made to
reconnect.
Example: Bridge.reconnect.delay=60000
#NSJMS Messaging Bridge Properties for sampl
#Fri Aug 08 10:24:21 PDT 2003
Bridge.receive.timeout=60000
Logger.filename=sampl.log
Bridge.reconnect.delay=60000
Database.delay=1000
Logger.loglevel=info
Database.timeout=100
Database.volsubvol=$myvol.mysubvol
Note. The properties in the server_class.jndi.properties file are applied only to the
specified server class.