[jira] [Comment Edited] (AMQ-7317) HTTP/HTTPS Connector session commit times are long
[
https://issues.apache.org/jira/browse/AMQ-7317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16950753#comment-16950753
]
Paul Rousset edited comment on AMQ-7317 at 10/14/19 7:06 AM:
-
our connector is pretty basic:
https://0.0.0.0:8188?maximumConnections=1000=104857600"/>
We don't specify a keepalive so I suppose it's the default value
As to the number of connections, we have 9 connections on the https connector
and 6 on the tcp one; fyi, there are approximately 30 consumers on the broker
at any given time.
We already use the jetty.xml for a specific security constraint and SSL
settings (see attached) where we use the IdleTimeout tag
was (Author: prousset.monoprix):
our connector is pretty basic:
https://0.0.0.0:8188?maximumConnections=1000=104857600"/>
We don't specify a keepalive so I suppose it's the default value
As to the number of connections, we have 9 connections on the http connector
and 6 on the tcp one; fyi, there are approximately 30 consumers on the broker
at any given time.
We already use the jetty.xml for a specific security constraint and SSL
settings (see attached) where we use the IdleTimeout tag
> HTTP/HTTPS Connector session commit times are long
> --
>
> Key: AMQ-7317
> URL: https://issues.apache.org/jira/browse/AMQ-7317
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Connector
>Affects Versions: 5.15.6, 5.15.9
>Reporter: Paul Rousset
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Attachments: jetty.xml.sample, sampleCode.txt
>
>
> 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:
> {quote}*connection created in 642ms*
> *session created in 27ms*
> *Taft : got message in 64ms*
> *message acknowledged in 0ms*
> *consumer closed in 0ms*
> *session committed in {color:#FF}2691ms{color}*
> *session closed in 2ms*
> *session created in 5ms*
> *Cleveland : got message in 40ms*
> *message acknowledged in 0ms*
> *consumer closed in 0ms*
> *session committed in {color:#FF}2377ms{color}*
> *session closed in 3ms*
> *session created in 5ms*
> *Truman : got message in 174ms*
> *message acknowledged in 0ms*
> *consumer closed in 0ms*
> *session committed in {color:#FF}2308ms{color}*
> *session closed in 3ms*
> *session created in 5ms*
> *Quincy : got message in 40ms*
> *message acknowledged in 0ms*
> *consumer closed in 0ms*
> *session committed in {color:#FF}2304ms{color}*
> *session closed in 3ms*
> *...*
> {quote}
> As opposed to (same code, with just a change of protocol/PROVIDER_URL to TCP)
> :
> {quote}*connection created in 195ms*
> *session created in 20ms*
> *Kennedy : got message in 50ms*
> *message acknowledged in 0ms*
> *consumer closed in 0ms*
> *session committed in {color:#FF}7ms{color}*
> *session closed in 0ms*
> *session created in 1ms*
> *Roosevelt : got message in 27ms*
> *message acknowledged in 0ms*
> *consumer closed in 0ms*
> *session committed in {color:#FF}6ms{color}*
> *session closed in 0ms*
> *session created in 0ms*
> *McKinley : got message in 56ms*
> *message acknowledged in 0ms*
> *consumer closed in 0ms*
> *session committed in {color:#FF}59ms{color}*
> *session closed in 1ms*
> *session created in 1ms*
> *Pierce : got message in 15ms*
> *message acknowledged in 0ms*
> *consumer closed in 0ms*
> *session committed in {color:#FF}60ms{color}*
> *session closed in 0ms*
> *...*
> {quote}
>
> Attached is a sample of the Java code.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (AMQ-7317) HTTP/HTTPS Connector session commit times are long
[
https://issues.apache.org/jira/browse/AMQ-7317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16950753#comment-16950753
]
Paul Rousset edited comment on AMQ-7317 at 10/14/19 7:04 AM:
-
our connector is pretty basic:
https://0.0.0.0:8188?maximumConnections=1000=104857600"/>
We don't specify a keepalive so I suppose it's the default value
As to the number of connections, we have 9 connections on the http connector
and 6 on the tcp one; fyi, there are approximately 30 consumers on the broker
at any given time.
We already use the jetty.xml for a specific security constraint and SSL
settings (see attached) where we use the IdleTimeout tag
was (Author: prousset.monoprix):
our connector is pretty basic:
https://0.0.0.0:8188?maximumConnections=1000wireFormat.maxFrameSize=104857600"/>
We don't specify a keepalive so I suppose it's the default value
As to the number of connections, we have 9 connections on the http connector
and 6 on the tcp one; fyi, there are approximately 30 consumers on the broker a
any given time.
We already use the jetty.xml for a specific security constraint and SSL
settings (see attached) where we use the IdleTimeout tag
> HTTP/HTTPS Connector session commit times are long
> --
>
> Key: AMQ-7317
> URL: https://issues.apache.org/jira/browse/AMQ-7317
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Connector
>Affects Versions: 5.15.6, 5.15.9
>Reporter: Paul Rousset
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Attachments: jetty.xml.sample, sampleCode.txt
>
>
> 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:
> {quote}*connection created in 642ms*
> *session created in 27ms*
> *Taft : got message in 64ms*
> *message acknowledged in 0ms*
> *consumer closed in 0ms*
> *session committed in {color:#FF}2691ms{color}*
> *session closed in 2ms*
> *session created in 5ms*
> *Cleveland : got message in 40ms*
> *message acknowledged in 0ms*
> *consumer closed in 0ms*
> *session committed in {color:#FF}2377ms{color}*
> *session closed in 3ms*
> *session created in 5ms*
> *Truman : got message in 174ms*
> *message acknowledged in 0ms*
> *consumer closed in 0ms*
> *session committed in {color:#FF}2308ms{color}*
> *session closed in 3ms*
> *session created in 5ms*
> *Quincy : got message in 40ms*
> *message acknowledged in 0ms*
> *consumer closed in 0ms*
> *session committed in {color:#FF}2304ms{color}*
> *session closed in 3ms*
> *...*
> {quote}
> As opposed to (same code, with just a change of protocol/PROVIDER_URL to TCP)
> :
> {quote}*connection created in 195ms*
> *session created in 20ms*
> *Kennedy : got message in 50ms*
> *message acknowledged in 0ms*
> *consumer closed in 0ms*
> *session committed in {color:#FF}7ms{color}*
> *session closed in 0ms*
> *session created in 1ms*
> *Roosevelt : got message in 27ms*
> *message acknowledged in 0ms*
> *consumer closed in 0ms*
> *session committed in {color:#FF}6ms{color}*
> *session closed in 0ms*
> *session created in 0ms*
> *McKinley : got message in 56ms*
> *message acknowledged in 0ms*
> *consumer closed in 0ms*
> *session committed in {color:#FF}59ms{color}*
> *session closed in 1ms*
> *session created in 1ms*
> *Pierce : got message in 15ms*
> *message acknowledged in 0ms*
> *consumer closed in 0ms*
> *session committed in {color:#FF}60ms{color}*
> *session closed in 0ms*
> *...*
> {quote}
>
> Attached is a sample of the Java code.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
