Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
5.15.6, 5.15.9
-
None
-
None
-
Important
Description
Session commit times for a consumer are very long when using an HTTP or HTTPS connector... Is there any way to improve this?
For example, output with the HTTP connector:
connection created in 642ms
session created in 27ms
Taft : got message in 64ms
message acknowledged in 0ms
consumer closed in 0ms
session committed in 2691ms
session closed in 2ms
session created in 5ms
Cleveland : got message in 40ms
message acknowledged in 0ms
consumer closed in 0ms
session committed in 2377ms
session closed in 3ms
session created in 5ms
Truman : got message in 174ms
message acknowledged in 0ms
consumer closed in 0ms
session committed in 2308ms
session closed in 3ms
session created in 5ms
Quincy : got message in 40ms
message acknowledged in 0ms
consumer closed in 0ms
session committed in 2304ms
session closed in 3ms...
As opposed to (same code, with just a change of protocol/PROVIDER_URL to TCP) :
connection created in 195ms
session created in 20ms
Kennedy : got message in 50ms
message acknowledged in 0ms
consumer closed in 0ms
session committed in 7ms
session closed in 0ms
session created in 1ms
Roosevelt : got message in 27ms
message acknowledged in 0ms
consumer closed in 0ms
session committed in 6ms
session closed in 0ms
session created in 0ms
McKinley : got message in 56ms
message acknowledged in 0ms
consumer closed in 0ms
session committed in 59ms
session closed in 1ms
session created in 1ms
Pierce : got message in 15ms
message acknowledged in 0ms
consumer closed in 0ms
session committed in 60ms
session closed in 0ms...
Attached is a sample of the Java code.