activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arnaud Marchand (JIRA)" <>
Subject [jira] [Commented] (AMQ-6266) REST API and CURL leaking connections
Date Fri, 17 Jun 2016 07:08:05 GMT


Arnaud Marchand commented on AMQ-6266:

That's easy to reproduce with something like that:

for i in `seq 1 1000`;  do curl -u admin:admin -d "body=message";

===> Result:

<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<title>Error 500 Server Error</title>
<body><h2>HTTP ERROR 500</h2>
<p>Problem accessing /api/message/TEST.FOO. Reason:
<pre>    Server Error</pre></p><h3>Caused by:</h3><pre>java.lang.OutOfMemoryError:
unable to create new native thread
	at java.lang.Thread.start0(Native Method)
	at java.lang.Thread.start(
	at java.util.concurrent.ThreadPoolExecutor.addWorker(
	at java.util.concurrent.ThreadPoolExecutor.execute(
	at org.apache.activemq.thread.PooledTaskRunner.wakeup(
	at org.apache.activemq.transport.vm.VMTransport.wakeup(

On my side, it crashes after 3000 CURLs.

> REST API and CURL leaking connections
> -------------------------------------
>                 Key: AMQ-6266
>                 URL:
>             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

View raw message