Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of gaurav.cs.sharma@gmail.com
 designates 209.85.214.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAAtCmqN6CSOxQQLLfzsiWkjyWeRsGWxcFJGPPOp-7DR1kcBkQg@mail.gmail.com>
References: <1348209293639-4656787.post@n4.nabble.com>
 <E72D0C8D-EF17-44A6-97B5-D9C904339BD2@gmail.com>
 <CAAtCmqN=M1UEkw1_P3tbjtpN0YAHsZDxQ+t+jMpYKEnDQbAtvQ@mail.gmail.com>
 <3AF6A3D6-5EE3-47C3-A7B7-A662352DACC3@gmail.com>
 <CAAtCmqN6CSOxQQLLfzsiWkjyWeRsGWxcFJGPPOp-7DR1kcBkQg@mail.gmail.com>
From: Gaurav Sharma <gaurav.cs.sharma@gmail.com>
Date: Thu, 27 Sep 2012 03:21:45 -0700
Message-ID: 
 <CAA=go7nftMiQ57oiFsZoYRwK6dvBS+x0NkwF0hmVuaTqKjYJQQ@mail.gmail.com>
Subject: Re: ActiveMQ Broker Scheduler unable to create new native thread
To: users@activemq.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Your memoryUsage limit is only 256megs; bump it up. Some more pointers
here: http://activemq.apache.org/javalangoutofmemory.html

On Thu, Sep 27, 2012 at 3:11 AM, jockeyyan <jockeyyan@gmail.com> wrote:
> Hi Gaurav:
>
> It seems the ActiveMQ is not stable, from 5.4.3 to 5.6.0, and I tried
> many times, and it always throw "unable to create new create native
> thread", Does anyone know how to solve it?
>
> my AMQ configuratoin of activemq.xml as following:
> -------------------------------------------------------------------------=
--------
> <!--
>     Licensed to the Apache Software Foundation (ASF) under one or more
>     contributor license agreements.  See the NOTICE file distributed with
>     this work for additional information regarding copyright ownership.
>     The ASF licenses this file to You under the Apache License, Version 2=
.0
>     (the "License"); you may not use this file except in compliance with
>     the License.  You may obtain a copy of the License at
>
>     http://www.apache.org/licenses/LICENSE-2.0
>
>     Unless required by applicable law or agreed to in writing, software
>     distributed under the License is distributed on an "AS IS" BASIS,
>     WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or impli=
ed.
>     See the License for the specific language governing permissions and
>     limitations under the License.
> -->
> <!-- START SNIPPET: example -->
> <beans
>   xmlns=3D"http://www.springframework.org/schema/beans"
>   xmlns:amq=3D"http://activemq.apache.org/schema/core"
>   xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance"
>   xsi:schemaLocation=3D"http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
>   http://activemq.apache.org/schema/core
> http://activemq.apache.org/schema/core/activemq-core.xsd">
>
>     <!-- Allows us to use system properties as variables in this
> configuration file -->
>     <bean class=3D"org.springframework.beans.factory.config.PropertyPlace=
holderConfigurer">
>         <property name=3D"locations">
>             <value>file:${activemq.base}/conf/credentials.properties</val=
ue>
>         </property>
>     </bean>
>
>     <!--
>         The <broker> element is used to configure the ActiveMQ broker.
>     -->
>     <broker xmlns=3D"http://activemq.apache.org/schema/core"
> brokerName=3D"localhost" dataDirectory=3D"${activemq.base}/data"
>         persistent=3D"true" destroyApplicationContextOnStop=3D"true">
>
>         <!--
>                         For better performances use VM cursor and small m=
emory limit.
>                         For more information, see:
>
>             http://activemq.apache.org/message-cursors.html
>
>             Also, if your producer is "hanging", it's probably due to
> producer flow control.
>             For more information, see:
>             http://activemq.apache.org/producer-flow-control.html
>         -->
>
>         <destinationPolicy>
>             <policyMap>
>               <policyEntries>
>                 <policyEntry topic=3D">" producerFlowControl=3D"false"
> memoryLimit=3D"16mb">
>                   <pendingSubscriberPolicy>
>                     <vmCursor />
>                     <!--fileCursor /-->
>                   </pendingSubscriberPolicy>
>                 </policyEntry>
>                 <policyEntry queue=3D">" producerFlowControl=3D"false"
> memoryLimit=3D"16mb">
>                   <!-- Use VM cursor for better latency
>                        For more information, see:
>
>                        http://activemq.apache.org/message-cursors.html
>
>                   -->
>                   <pendingQueuePolicy>
>                     <vmQueueCursor/>
>                     <!--fileQueueCursor/-->
>                   </pendingQueuePolicy>
>                 </policyEntry>
>               </policyEntries>
>             </policyMap>
>         </destinationPolicy>
>
>         <!--
>             The managementContext is used to configure how ActiveMQ is
> exposed in
>             JMX. By default, ActiveMQ uses the MBean server that is start=
ed by
>             the JVM. For more information, see:
>
>             http://activemq.apache.org/jmx.html
>         -->
>         <managementContext>
>             <managementContext createConnector=3D"false"/>
>         </managementContext>
>
>                                 <networkConnectors>
>                                         <networkConnector name=3D"bridge"
>                                                 uri=3D"static:(nio://192.=
168.128.184:61616)"
>                                                 duplex=3D"true" />
>                                 </networkConnectors>
>
>         <!--
>             Configure message persistence for the broker. The default
> persistence
>             mechanism is the KahaDB store (identified by the kahaDB tag).
>             For more information, see:
>
>             http://activemq.apache.org/persistence.html
>         -->
>         <persistenceAdapter>
>             <kahaDB directory=3D"${activemq.base}/data/kahadb"/>
>         </persistenceAdapter>
>
>
>           <!--
>             The systemUsage controls the maximum amount of space the
> broker will
>             use before slowing down producers. For more information, see:
>
>             http://activemq.apache.org/producer-flow-control.html
>                 -->
>
>         <systemUsage>
>             <systemUsage>
>                 <memoryUsage>
>                     <memoryUsage limit=3D"256 mb"/>
>                 </memoryUsage>
>                 <storeUsage>
>                     <storeUsage limit=3D"1 gb"/>
>                 </storeUsage>
>                 <tempUsage>
>                     <tempUsage limit=3D"512 mb"/>
>                 </tempUsage>
>             </systemUsage>
>         </systemUsage>
>
>         <!--
>             The transport connectors expose ActiveMQ over a given protoco=
l to
>             clients and other brokers. For more information, see:
>
>             http://activemq.apache.org/configuring-transports.html
>         -->
>                                 <transportConnectors>
>                                         <transportConnector name=3D"local=
-listening"
>                                                 uri=3D"nio://0.0.0.0:6262=
6" />
>                                 </transportConnectors>
>
>     </broker>
>
>     <!--
>         Enable web consoles, REST and Ajax APIs and demos
>
>         Take a look at ${ACTIVEMQ_HOME}/conf/jetty.xml for more details
>     -->
>     <import resource=3D"jetty.xml"/>
>
> </beans>
> <!-- END SNIPPET: example -->
> -------------------------------------------------------------------------=
-----------------------------------
>
>
> Very urgent, thanks!
>
>
> 2012/9/22 Gaurav Sharma [via ActiveMQ]
> <ml-node+s2283324n4656828h31@n4.nabble.com>:
>> For starters, simply give it more heap. So, increase heap as a step func=
tion
>> (1G, 1.5G, 2G...) and measure throughput. Throughput sustenance will als=
o
>> depend on message size and how well both the broker and clients keep up.
>>
>> On Sep 21, 2012, at 18:49, jockeyyan <[hidden email]> wrote:
>>
>>> Dear Gaurav:
>>>
>>> The configuration parameters of my broker as following:
>>>
>>> -----------------------------------------------------------------------=
----------------------------
>>> ACTIVEMQ_OPTS=3D-Xmx512M
>>> -Dorg.apache.activemq.UseDedicatedTaskRunner=3Dfalse
>>> -Djava.util.logging.config.file=3Dlogging.properties -Xss256k
>>>
>>> -----------------------------------------------------------------------=
----------------------------
>>> There are 1 CPU of 4 kernels and 6G memory on this machine, and no
>>> other app is running.
>>>
>>>
>>> 2012/9/21 Gaurav Sharma [via ActiveMQ]
>>> <[hidden email]>:
>>>> How much heap have we given to the broker and what else is running on =
the
>>>> same machine? Also, just fire up jconsole, attach to the process and
>>>> watch
>>>> allocations, threads and cpu - should give a clue. v5.6 is the current
>>>> release, so, upgrade if possible.
>>>>
>>>> On Sep 20, 2012, at 23:34, jockeyyan <[hidden email]> wrote:
>>>>
>>>>> Hi:
>>>>>
>>>>> I am using ActiveMQ 5.4.3 to make some loading test. I created one
>>>>> producer,
>>>>> one broker and one consumer with Spring JAX-WS config. The producer
>>>>> invoke
>>>>> the functions to send messages to broker continuously and the consume=
r
>>>>> just
>>>>> receive and echo.
>>>>> Everything is OK at beginning. After invoke many times(about 2000 to
>>>>> 3000),
>>>>> the broker is crashed and display the following error message, Does
>>>>> anyone
>>>>> could help me fingure out what the matter of the broker is?
>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------=
-----------------------------
>>>>> Exception in thread "ActiveMQ Broker[localhost] Scheduler"
>>>>> java.lang.OutOfMemory
>>>>> Error: unable to create new native thread
>>>>>       at java.lang.Thread.start0(Native Method)
>>>>>       at java.lang.Thread.start(Thread.java:640)
>>>>>       at
>>>>> java.util.concurrent.ThreadPoolExecutor.addIfUnderMaximumPoolSize(Thr
>>>>> eadPoolExecutor.java:727)
>>>>>       at
>>>>> java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.ja
>>>>> va:657)
>>>>>       at
>>>>> org.apache.activemq.thread.PooledTaskRunner.wakeup(PooledTaskRunner.j
>>>>> ava:76)
>>>>>       at
>>>>> org.apache.activemq.broker.region.Queue.asyncWakeup(Queue.java:1637)
>>>>>       at
>>>>> org.apache.activemq.broker.region.Queue.expireMessages(Queue.java:773
>>>>> )
>>>>>       at
>>>>> org.apache.activemq.broker.region.Queue.access$100(Queue.java:83)
>>>>>       at org.apache.activemq.broker.region.Queue$2.run(Queue.java:123=
)
>>>>>       at
>>>>> org.apache.activemq.thread.SchedulerTimerTask.run(SchedulerTimerTask.
>>>>> java:33)
>>>>>       at java.util.TimerThread.mainLoop(Timer.java:512)
>>>>>       at java.util.TimerThread.run(Timer.java:462)
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------=
-----------------------------
>>>>>
>>>>> The config of my consumer as following:
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------=
-----------------------------
>>>>> <bean id=3D"jmsConnectionFactory"
>>>>> class=3D"org.springframework.jms.connection.CachingConnectionFactory"=
>
>>>>>   <property name=3D"targetConnectionFactory">
>>>>>       <bean class=3D"org.apache.activemq.ActiveMQConnectionFactory">
>>>>>           <property name=3D"brokerURL" value=3D"tcp://localhost:61616=
" />
>>>>>       </bean>
>>>>>   </property>
>>>>>   <property name=3D"sessionCacheSize" value=3D"50" />
>>>>> </bean>
>>>>>
>>>>> <bean id=3D"jmsConfig"
>>>>> class=3D"org.apache.cxf.transport.jms.JMSConfiguration"
>>>>>   p:connectionFactory-ref=3D"jmsConnectionFactory"
>>>>>   p:targetDestination=3D"test.queue"
>>>>> />
>>>>>
>>>>>
>>>>>   <jaxws:endpoint xmlns:customer=3D"http://customerservice.example.co=
m/"
>>>>>       id=3D"CustomerServiceHTTP" address=3D"jms://"
>>>>>
>>>>> implementor=3D"com.example.customerservice.server.CustomerServiceImpl=
">
>>>>>       <jaxws:features>
>>>>>           <bean class=3D"org.apache.cxf.feature.LoggingFeature" />
>>>>>           <bean class=3D"org.apache.cxf.transport.jms.JMSConfigFeatur=
e"
>>>>> p:jmsConfig-ref=3D"jmsConfig" />
>>>>>       </jaxws:features>
>>>>>   </jaxws:endpoint>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------=
-----------------------------
>>>>>
>>>>> The config of my producer as following:
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------=
-----------------------------
>>>>> <bean id=3D"jmsConnectionFactory"
>>>>> class=3D"org.springframework.jms.connection.SingleConnectionFactory">
>>>>>   <property name=3D"targetConnectionFactory">
>>>>>       <bean class=3D"org.apache.activemq.ActiveMQConnectionFactory">
>>>>>           <property name=3D"brokerURL" value=3D"tcp://localhost:61616=
" />
>>>>>       </bean>
>>>>>   </property>
>>>>> </bean>
>>>>>
>>>>> <bean id=3D"jmsConfig"
>>>>> class=3D"org.apache.cxf.transport.jms.JMSConfiguration"
>>>>>   p:connectionFactory-ref=3D"jmsConnectionFactory"
>>>>>   p:targetDestination=3D"test.queue"
>>>>> />
>>>>>
>>>>>   <jaxws:client id=3D"customerService"
>>>>>       address=3D"jms://"
>>>>>       serviceClass=3D"com.example.customerservice.CustomerService">
>>>>>       <jaxws:features>
>>>>>           <bean class=3D"org.apache.cxf.feature.LoggingFeature" />
>>>>>           <bean class=3D"org.apache.cxf.transport.jms.JMSConfigFeatur=
e"
>>>>> p:jmsConfig-ref=3D"jmsConfig" />
>>>>>       </jaxws:features>
>>>>>   </jaxws:client>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------=
-----------------------------
>>>>>
>>>>> Jockey Yan
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> View this message in context:
>>>>>
>>>>> http://activemq.2283324.n4.nabble.com/ActiveMQ-Broker-Scheduler-unabl=
e-to-create-new-native-thread-tp4656787.html
>>>>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>>>
>>>>
>>>> ________________________________
>>>> If you reply to this email, your message will be added to the discussi=
on
>>>> below:
>>>>
>>>> http://activemq.2283324.n4.nabble.com/ActiveMQ-Broker-Scheduler-unable=
-to-create-new-native-thread-tp4656787p4656820.html
>>>> To unsubscribe from ActiveMQ Broker Scheduler unable to create new nat=
ive
>>>> thread, click here.
>>>> NAML
>>>
>>>
>>>
>>> --
>>> =E9=97=AB=E7=BB=A7=E5=9F=B9
>>> Jockey Yan
>>>
>>> Email: [hidden email]
>>> Mobile: 13601186611
>>>
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://activemq.2283324.n4.nabble.com/ActiveMQ-Broker-Scheduler-unable-=
to-create-new-native-thread-tp4656787p4656827.html
>>
>>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>>
>> ________________________________
>> If you reply to this email, your message will be added to the discussion
>> below:
>> http://activemq.2283324.n4.nabble.com/ActiveMQ-Broker-Scheduler-unable-t=
o-create-new-native-thread-tp4656787p4656828.html
>> To unsubscribe from ActiveMQ Broker Scheduler unable to create new nativ=
e
>> thread, click here.
>> NAML
>
>
>
> --
> =E9=97=AB=E7=BB=A7=E5=9F=B9
> Jockey Yan
>
> Email: jockeyyan@gmail.com
> Mobile: 13601186611
>
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/Activ=
eMQ-Broker-Scheduler-unable-to-create-new-native-thread-tp4656787p4657080.h=
tml
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.