When there are a lot of rows (10s of thousands which is possible in certain cases) in the EN_MESSAGE_QUE_T table, attempting to open the route queue view is very slow and can cause an OutOfMemoryError.
I think this is because we select the entire set of queue rows into memory when we load the view. We need to constrain the set that gets loaded. We can do this by putting a throttle on the number of rows we select (similar to doc search) and/or we could implement custom paging/sorting using the display tag. Either way, we need to make sure we only select a reasonable number of rows from the queue table.