activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Viktorya Harutyunyan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-6266) REST API and CURL leaking connections
Date Thu, 16 Jun 2016 22:51:05 GMT

    [ https://issues.apache.org/jira/browse/AMQ-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15334874#comment-15334874
] 

Viktorya Harutyunyan commented on AMQ-6266:
-------------------------------------------

[UNABLE TO REPRODUCE]
Hi

I have tried with latest source code (June-14-2016) and could not reproduce.
I tried with:
- offline consumer and sent 30 messages using CURL using REST
- online consumer and sent 20 messages using CURL using REST

my curl I tested with:
curl -u admin:admin -d "body=message" http://andromeda:8161/api/message/TEST.FOO?type=queue

on console under connections I was able to see only the consumer connection.
and after closing the consumer connection the connection was gone on console as well. 

@Arnaud Marchand could you please:
1.  provide more details, was the consumer running at the moment the messages were sent
2. could you please provide your code for consumer

Thanks

> REST API and CURL leaking connections
> -------------------------------------
>
>                 Key: AMQ-6266
>                 URL: https://issues.apache.org/jira/browse/AMQ-6266
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.13.2
>         Environment: Broker 5.13.2 running on MAC or PC
> curl client on MAC and LINUX
>            Reporter: Arnaud Marchand
>            Priority: Minor
>
> Sending messages via the REST API via a curl leaks ActiveMQ connections.
> Any curl such as the one in the ActiveMQ web site creates the problem:
> curl -u system:manager -d "body=message" http://localhost:8161/demo/message/TEST?type=queue
> The number of connections can be checked via the Jolokia or the JConsole interface.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message