EuroRunner Interfaces - Third Party Software

Introduction

Each interface is controlled by its own COM+ Application; each can run as a queued component using MSMQ.

Outgoing interfaces are initiated by the user using the EuroRunner Client, these can be synchronous, or asynchronous using MSMQ.

The GMSL Service, which runs as a Windows Service, controls incoming interfaces, all of which run asynchronously using MSMQ.

Microsoft Message Queue (MSMQ)

By default MSMQ has three attempts to perform an action per queue, and then waits an amount of time before starting again on the next queue as detailed in the table below.

Queue Default wait period
0 1 second
1 1 minute
2 2 minutes
3 4 minutes
4 8 minutes

For EuroRunner we suggest these values are changed to get a quicker user response, see the MSMQ section of the Registry documentation for details.

If the queued process (name ends with QC) fails all attempts in the queues, then an exception handler is called (name ends with EX), this retries one final time, and if it fails again an error is logged to the Event Viewer.

Registry Keys

See the MSMQ section of the Registry documentation.

COM+

By default COM+ allows many concurrent threads to run for each queue, for EuroRunner this setting should be altered to reduce the possibility of session timeouts due to too many processes running simultaneously. Set the Maximum concurrent players on the Queuing tab of the Properties for each of the EuroRunner COM+ Applications to 1.

Note: This setting is not available in Windows 2000.

GMSL Logo About Us | Contact Us | Fluxys SA | © 2006 Gas Management Services Limited