org.transitime.avl

Class AvlExecutor

java.lang.Object

org.transitime.avl.AvlExecutor

public class AvlExecutor
extends java.lang.Object

A singleton thread executor for executing AVL reports. For when not using JMS to handle queue of AVL reports. One can dump AVL reports into this executor and then have them be executed, possibly using multiple threads. The number of threads is specified using the Java property transitime.avl.numThreads . The queue size is set using the Java property transitime.avl.queueSize .

Causes AvlClient.run() to be called on each AvlReport, unless using test executor, in which case the AvlClientTester() is called.

Author:

SkiBu Smith

Method Summary

Modifier and Type	Method and Description
static AvlExecutor	getInstance() Returns singleton instance.
static void	main(java.lang.String[] args) For testing.
void	processAvlReport(AvlReport newAvlReport, boolean... useTestExecutor) Instead of writing AVL report to JMS topic this method directly processes it.

Methods inherited from class java.lang.Object

equals, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Method Detail

getInstance

public static AvlExecutor getInstance()

Returns singleton instance. Not synchronized since it is OK if an executor is replaced by a new one.

Returns:

the singleton AvlExecutor

processAvlReport

public void processAvlReport(AvlReport newAvlReport,
                             boolean... useTestExecutor)

Instead of writing AVL report to JMS topic this method directly processes it. By doing this one can bypass the need for a JMS server. Uses a thread executor so that can both use multiple threads and queue up requests. This is especially important if getting a dump of AVL data from either polling a feed or from an AVL feed hitting the Transitime web server and the AVL data getting then pushed to the core system in batches.

Uses a queue so that if system gets behind in processing AVL data then AVL data is written to a queue that keeps track of the latest AVL report per vehicle. If another AVL report is to be added to the queue then the previous one is removed since there is no point processing an old AVL report for a vehicle when new data is available.

Causes AvlClient.run() to be called on each AvlReport, unless using test executor, in which case the AvlClientTester() is called.

Parameters:

newAvlReport - The AVL report to be processed

useTestExecutor - So can optional specify that should use a different test executor for testing out the queuing

main

public static void main(java.lang.String[] args)

For testing.