Server log entries

Each time you start a server configuration, it creates a new server log file to record all activity. If a server log file already exists, the existing file is renamed before the new file is created.

The server log file has been renamed to reflect your language environment. For example, a Server.en-US.log file indicates the US English language. Note that even if your language is not US English, a Server.en-US.log file will always be created for use by support.

This section shows sample ActiveMQ MPX-related messages that may appear in a server log file. These messages are typically prefixed with ActiveMQ MPX..

Note: Each message written to the server log file includes a line number, and a date-time stamp. This information has been omitted from the following sample for the purposes of clarity.

Start-Up Messages

When you start a server configuration, the system records all start-up messages in the server log file. When you start an ActiveMQ MPX configuration, the server log file also records start-up information for the Event Transmitter. The following sample shows the typical entries that are made in the server log file when you start an ActiveMQ MPX-enabled server configuration. (

Found Event Transmitter configuration of type "ActiveMQ MPX Transmitter" with ServerDefault settings: 
	server_write_timeout=30
	server_names=tcp:localhost:61616
	socket_connect_timeout=10
	server_start_delay=10
	transport.commandTracingEnabled=true
	enable_control_msgs=echo
	server_max_reconnect_delay=10
	project=Starbase
	server_start_max_tries=1
	server_read_timeout=30
	server_keep_alive_timeout=30
	
Connecting to broker(s): tcp://localhost:61616,
EventTransmitter: Initialized PubSub Library
EventTransmitter: Created connection to StarTeam Message Broker
EventTransmitter: Created encryption cipher
MPX File Transmitter: Using hive index file: c:\repository\testActiveMQ\HiveIndex\hive-index.xml
MPX File Transmitter: Using journal file: c:\repository\testActiveMQ\CacheJournal.dat
MPX File Transmitter: Hive #10 mapped to folder: c:\repository\testActiveMQ\DefaultHive\Archives\
MPX File Transmitter: Using data transfer rate of 256 kbps 
MPX File Transmitter: Using packet transmission delay of 32 ms

Back to top

Reconnect Messages

If an MPX-enabled server configuration loses the connection to its Message Broker, it records that event in the server log file. A server configuration will always attempt to re-establish communication with the Message Broker and it will wait for the Message Broker to come back online.. The number of retries made and the time between retries depends on the parameters set in the Event Transmitter XML file’s server default profile.

The following sample shows the typical entries that are made in the server log file when an MPX configuration loses and then reconnects to its Message Broker. 

49  00000001  2015-06-30 16:07:05  ActiveMQ MPX: Lost connection to broker
50  00000001  2015-06-30 16:07:32  ActiveMQ MPX: Resumed connection to broker

Back to top