camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reji Mathews <contactr...@gmail.com>
Subject Re: ACTIVE MQ Error :org.apache.activemq.transport.tcp.ExceededMaximumConnectionsException
Date Tue, 10 Jun 2014 01:52:22 GMT
Hi

How would connection pool work ? What's the difference between convention
way of configuring activemq and that with connection pool .

Can someone help me understand this .

Cheers
Reji
On 09/06/2014 7:58 pm, "Larry Meadors" <larry.meadors@gmail.com> wrote:

> I was getting the same error in my application - for me, the solution
> appears to be using a connection pool - since adding that to my
> configuration, this error has gone away for a couple of weeks (I was
> getting it almost daily before that).
>
> Larry
>
>
>
> On Mon, Jun 9, 2014 at 2:13 AM, vs_mahesh <vsmahesh111@yahoo.co.in> wrote:
> > Hi all,
> >
> > Kindly explain the possible cause and solution for the following ActiveMq
> > error
> >
> >
> > /Connections=1000 | TransportConnector               | 126 -
> > org.apache.activemq.activemq-core - 5.7.0.fuse-71-047 | Could not accept
> > connection :
> > *org.apache.activemq.transport.tcp.ExceededMaximumConnectionsException:
> > Exceeded the maximum number of allowed client connections. See the
> > 'maximumConnections' property on the TCP transport configuration URI in
> the
> > ActiveMQ configuration file (e.g., activemq.xml)*09 Jun 2014
> 01:01:26,698 |
> > ERROR | Connections=1000 | TransportConnector               | 126 -
> > org.apache.activemq.activemq-core - 5
> >
> >  org.springframework.jms - 3.0.7.RELEASE | Could not refresh JMS
> Connection
> > for destination 'Q_ID56_COPPERRECOVERYPERCENTAGE_INB' - retrying in 5000
> ms.
> > Cause: Wire format negotiation timeout: peer did not send his wire
> format.
> > 09 Jun 2014 01:01:36,713 | WARN  | CONSUMPTION_INB] |
> > faultJmsMessageListenerContainer | 154 - org.springframework.jms -
> > 3.0.7.RELEASE | Could not refresh JMS Connection for destination
> > 'Q_ID63_WATERCONSUMPTION_INB' - retrying in 5000 ms. Cause: Wire format
> > negotiation timeout: peer did not send his wire format.
> >
> >
> >
> > The Active MQ Bean configured to connect to the JMS system  in the route
> > file is as follows.
> >
> > <bean id="activemq"
> > class="org.apache.activemq.camel.component.ActiveMQComponent">
> >                 <property name="brokerURL"
> value="tcp://localhost:61630"/>
> >                 <property name="userName" value="admin"/>
> >                 <property name="password" value="admin" />
> >         </bean>
> >
> >
> > The following is the activemq.xml config file contains
> >
> > <bean
> >
> class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
> >         <property name="properties">
> >             <bean
> class="org.fusesource.mq.fabric.ConfigurationProperties"/>
> >         </property>
> >     </bean>
> >
> >     <broker xmlns="http://activemq.apache.org/schema/core"
> >             brokerName="${broker-name}"
> >             dataDirectory="${data}"
> >             start="false">
> >
> >         <destinationPolicy>
> >             <policyMap>
> >               <policyEntries>
> >                 <policyEntry topic=">" producerFlowControl="true">
> >                   <pendingMessageLimitStrategy>
> >                     <constantPendingMessageLimitStrategy limit="1000"/>
> >                   </pendingMessageLimitStrategy>
> >                 </policyEntry>
> >                 <policyEntry queue=">" producerFlowControl="true"
> > memoryLimit="1mb">
> >                 </policyEntry>
> >               </policyEntries>
> >             </policyMap>
> >         </destinationPolicy>
> >
> >         <managementContext>
> >             <managementContext createConnector="false"/>
> >         </managementContext>
> >
> >         <persistenceAdapter>
> >             <kahaDB directory="${data}/kahadb"/>
> >         </persistenceAdapter>
> >
> >         <plugins>
> >             <jaasAuthenticationPlugin configuration="karaf" />
> >         </plugins>
> >
> >         <systemUsage>
> >             <systemUsage>
> >                 <memoryUsage>
> >                     <memoryUsage limit="64 mb"/>
> >                 </memoryUsage>
> >                 <storeUsage>
> >                     <storeUsage limit="100 gb"/>
> >                 </storeUsage>
> >                 <tempUsage>
> >                     <tempUsage limit="50 gb"/>
> >                 </tempUsage>
> >             </systemUsage>
> >         </systemUsage>
> >
> >         <transportConnectors>
> >             <transportConnector name="openwire"
> > uri="tcp://0.0.0.0:0?maximumConnections=1000"/>
> >         </transportConnectors>
> >     </broker>
> >
> > Am I missing anything in the bean creation ?
> > kindly guide me with a solution for this.
> >
> > Thanks,
> > Mahesh
> >
> >
> >
> > -----
> > Thanks And regards,
> > Mahesh
> > --
> > View this message in context:
> http://camel.465427.n5.nabble.com/ACTIVE-MQ-Error-org-apache-activemq-transport-tcp-ExceededMaximumConnectionsException-tp5752046.html
> > Sent from the Camel - Users mailing list archive at Nabble.com.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message