What's really peculiar is that the behavior of the consumer changes if a producer connects and produces to the route. As you can see in the attached log file it starts out with the consumer running and the log entries are about 2 seconds apart (the fake processing time for each message). Then the producer connects and starts producing. At the same time the consumer starts consuming concurrently until the producer finishes (the timer is configured to produce 30 new messages). Then the consumer falls back to the serialized consumption.
Any help is highly appreciated. Thanks! -- This message and any attachment (the "message") is intended solely for the addressees and is confidential. If you receive this message by mistake, please delete it and notify the sender immediately. Any use not in accordance with its purpose, any out-spread or disclosure, either as a whole or partially, is prohibited except with formal approval. Internet cannot guarantee the integrity of this message, therefore Tradescape will not be liable for the message if modified. -
