Hello
I 'm trying to embed AMQ(5.3) into tomcat(6) with a simple WAR which is
containing the configuration files and all the JARs. I also want to use Http
Tunnel to avoid firewall issue ( so i' ll be using the tomcat port)

To do that i've tried to use the servlet (HttpSpringEmbeddedTunnelServlet) 
which isdelivered into the optional package and which seem to be done for
that.

May be it's due to the fact that i'm just start to use AMQ but i was unable
to make them work without modification for following reasons: 

1 
      - The servlet is using the BrokerFactoryBean -> XBeanBrokerService
which is starting automatically the broker.
      - Then adding the TransportConnector on a started broker is doing
nothing , and the HttpTunnelServlet cannot be initialised since the accept
listener is not set.

      => to avoid that i had to add start="false" into the broker tag of the
activemq.xml 
           This may be something usefull to have this into a documentation
to embed a broker :
             configure using a xml and the BrokerFactoryBean, then add what
you want to have programmatic-ally and then start the broker , but if you do
that .......


2 
     The second part is about the HttpTransportServer which is  starting a
jetty server 
     But the Bind address which is used is the one already used by tomcat
     It was unable to start.
      
       => to avoid the problem i 've made a another HttpTransportServer
class which is doing nothing except what is done into the base class
TransportServerSupport.
        I also add to modify the HttpEmbeddedTunnelServlet , since the
context which is used to transmit information with its base class
(HttpTunnelServlet) is set to the wrong attribute (
"transportChannelListener" when the base class expect the value to be set on
the attribute "acceptListener" )

After doing thing all seems to work for now.

I may be totally wrong in my analysis and what i ve done . But if somebody
can confirm that , i ll be happy to give the modified classes and open the
associated ticket in Jira.

Thanks.
 
 

   

-- 
View this message in context: http://old.nabble.com/Another-need-for-integrating-embedded-broker-into-Tomcat-tp26651812p26651812.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

that should work! :)
On 4 Dec 2009, at 22:16, lujan99 wrote:

>
> how can I Install Camel 2.1 over AMQ 5.3??
> only replace camel files??
>
> thanks
>
> Dan
>
> -- 
> View this message in context: http://old.nabble.com/camel-2.1-tp26642154p26642154.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>

Rob Davies
http://twitter.com/rajdavies
I work here: http://fusesource.com
My Blog: http://rajdavies.blogspot.com/
I'm writing this: http://www.manning.com/snyder/

how can I Install Camel 2.1 over AMQ 5.3??
only replace camel files??

thanks

Dan

-- 
View this message in context: http://old.nabble.com/camel-2.1-tp26642154p26642154.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

On Fri, Dec 4, 2009 at 9:38 AM, Fred Moore <fred.moore77@gmail.com> wrote:
> Hi folks,
>
> this is probably easy but we not able to figure it out: we have producers
> setting msg expiration and msgs ending up in DLQ upon expiration (with their
> expiration reset to "never").
>
> How can I set things up in a way such that expired msgs will simply
> disappear for good automatically (without going into a DLQ together with
> msgs discarded for more unexpected reasons)?

Just to clarify, I think you're asking for expired messages to simply
be discarded instead of being sent to the DLQ. To achieve this, you'll
need to set the processExpired property to false in the dead letter
strategy. Below is an example of how to configure this in the
activemq.xml:

<destinationPolicy>
  <policyMap>
    <policyEntries>
      <!-- Set the following policy on all queues using the '>' wildcard -->
      <policyEntry queue=">">
        <!-- Tell the dead letter strategy not to process expired messages
              so that they will just be discarded -->
        <deadLetterStrategy processExpired="false" />
      </policyEntry>
    </policyEntries>
  </policyMap>
</destinationPolicy>

Bruce
-- 
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'

ActiveMQ in Action: http://bit.ly/2je6cQ
Blog: http://bruceblog.org/
Twitter: http://twitter.com/brucesnyder

Hi all,

We have a forwarding bridge between an embedded broker in one VM and a remote broker in another
VM using the examples from the network-of-brokers documentation[1].  While testing failover,
we left the embedded broker VM running overnight but did not start the remote broker VM. 
NOTE: The embedded broker VM was idle (we were not testing application logic).

In the morning the embedded broker VM threw an OutOfMemoryError:

	Exception in thread "Simple Discovery Agent: java.util.concurrent.ThreadPoolExecutor$Worker@61472b3c"
java.lang.OutOfMemoryError: Java heap space
		at org.apache.activemq.openwire.OpenWireFormat.<init>(OpenWireFormat.java:60)
		at org.apache.activemq.openwire.OpenWireFormat.<init>(OpenWireFormat.java:69)
		at org.apache.activemq.openwire.OpenWireFormatFactory.createWireFormat(OpenWireFormatFactory.java:62)
		at org.apache.activemq.transport.TransportFactory.createWireFormat(TransportFactory.java:212)
		at org.apache.activemq.transport.TransportFactory.doConnect(TransportFactory.java:140)
		at org.apache.activemq.transport.TransportFactory.connect(TransportFactory.java:67)
		at org.apache.activemq.network.DiscoveryNetworkConnector.onServiceAdd(DiscoveryNetworkConnector.java:111)
		at org.apache.activemq.transport.discovery.simple.SimpleDiscoveryAgent$1.run(SimpleDiscoveryAgent.java:164)
		at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
		at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
		at java.lang.Thread.run(Thread.java:637)

Our logs contained repeated (and expected) messages indicating that a connection could not
be established with the remote broker.  The one thing that stands out from these logs is that
a new thread was created in the embedded broker VM on each attempt to connect to the remote
broker VM:

	[1259881226751][Thread-10] Could not start network bridge between: vm://embeddedBroker and:
tcp://localhost:61616 due to: java.net.ConnectException: Connection refused
	[1259881227757][Thread-11] Could not start network bridge between: vm://embeddedBroker and:
tcp://localhost:61616 due to: java.net.ConnectException: Connection refused
	[1259881229762][Thread-12] Could not start network bridge between: vm://embeddedBroker and:
tcp://localhost:61616 due to: java.net.ConnectException: Connection refused
	...
	[1259888976178][Thread-267] Could not start network bridge between: vm://embeddedBroker and:
tcp://localhost:61616 due to: java.net.ConnectException: Connection refused
	[1259889006398][Thread-268] Could not start network bridge between: vm://embeddedBroker and:
tcp://localhost:61616 due to: java.net.ConnectException: Connection refused
	[1259889036611][Thread-269] Could not start network bridge between: vm://embeddedBroker and:
tcp://localhost:61616 due to: java.net.ConnectException: Connection refused

The embedded broker VM is configured via Spring as follows:

	<amq:broker id="embeddedBroker" brokerName="embeddedBroker" useJmx="true" persistent="false"
useShutdownHook="true">
		<amq:managementContext>
			<amq:managementContext createConnector="false"/>
		</amq:managementContext>
		<amq:networkConnectors>
			<amq:networkConnector uri="static:(tcp://localhost:61616)"/>
		</amq:networkConnectors>
	</amq:broker>

Any help would be greatly appreciated.

Thanks,
Geoff.

[1] http://activemq.apache.org/networks-of-brokers.html

The messages are synced between brokers only if there are consumers of
the same queue in both brokers. 
If you have temporary queues, since they are broker specific, any
messages in those queues will be lost

-----Original Message-----
From: Sebastian Rodriguez [mailto:srodrigu85@gmail.com] 
Sent: Thursday, December 03, 2009 7:59 PM
To: users@activemq.apache.org
Subject: Re: Shutting down a broker in a network of brokers

I might be wrong on this one, but usually, in a network of brokers, the
messages are synced between brokers.
When one of the brokers goes down, the messages are not lost. The
producers
and consumers will switch automatically to an available broker,
transparently for the end user.

2009/12/4 yello_downunder <jseutter@gmail.com>

>
> I'm looking at using a network of brokers.  When shutting down a
broker in
> the network of brokers, how can you ensure that no messages are
trapped on
> the broker being shut down?  Do you have to remove all producers on
the
> network of brokers and wait for messages to be processed on all
brokers?
>
> --
> View this message in context:
>
http://old.nabble.com/Shutting-down-a-broker-in-a-network-of-brokers-tp2
6634351p26634351.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>


-- 
Sebastien Rodriguez

Yay!  Just found out I'll be attending the San Francisco event!

Anyone else able to make it out?


On Mon, Nov 30, 2009 at 7:24 AM, Rob Davies <rajdavies@gmail.com> wrote:
>
> If any folks are in New York on December 8th or near San Francisco on
> December 10th - there is a free Community day sponsored by Fuse Source -
> with talks on Apache ServiceMix, ActiveMQ and Camel.
> If you'd like to attend - you need to register - its all free and includes
> lunch. If you can't make it - James Strachan and myself will no doubt be
> found in a local bar afterwards - so why not pop by for a chat and a beer.
> Not being local, suggestions are welcome :)
>
> To register for the New York  event (Hyatt Hotel next to Grand Central) on
> December 8th - go here: http://form.fusesource.com/forms/registerny2009
> To register for the San Francisco event (Hyatt Hotel next to the er, Airport
> :( )  on December 10th - go here:
> http://form.fusesource.com/forms/registersf2009
>
> cheers,
>
> Rob
>
> Rob Davies
> http://twitter.com/rajdavies
> I work here: http://fusesource.com
> My Blog: http://rajdavies.blogspot.com/
> I'm writing this: http://www.manning.com/snyder/
>
>
>
>
>
>



-- 
Regards,
Hiram

Blog: http://hiramchirino.com

Open Source SOA
http://fusesource.com/

Hi folks,

this is probably easy but we not able to figure it out: we have producers
setting msg expiration and msgs ending up in DLQ upon expiration (with their
expiration reset to "never").

How can I set things up in a way such that expired msgs will simply
disappear for good automatically (without going into a DLQ together with
msgs discarded for more unexpected reasons)?

Cheers,
F.

I am using Mule and ActiveMQ together.  ActiveMQ version 5.2.0.  I am
noticing something I don't get in the logs.  I set the config in
activemq.xml to persistent=true at the broker level and created a
destination of type queue.  I set to journal persistance and I see in the
console that my message is received and it is being picked up by the
consumer, but it also appears to be removed (See Below).  The console would
also lead me to believe that active mq is treating my queue as a topic.  I
would appreciate any help/clarification:

- Adding destination: topic://ActiveMQ.Advisory.Producer.Queue.b2bqueue
DEBUG AbstractRegion                 - Adding destination:
temp-queue://ID:FA2275059.local-64357-1259934819940-0:0:1
DEBUG AbstractRegion                 - Adding destination:
topic://ActiveMQ.Advisory.TempQueue
DEBUG AMQMessageStore                - Journalled message add for:
ID:FA2275059.local-64357-1259934819940-0:0:1:1:1, at: offset = 19525, file =
1, size = 1327, type = 1
DEBUG AMQMessageStore                - Doing batch update... adding: 1
removing: 0 
DEBUG AMQMessageStore                - Batch update done.
DEBUG AbstractRegion                 - Adding consumer:
ID:FA2275059.local-64357-1259934819940-0:0:1:1
DEBUG AbstractRegion                 - Adding destination:
topic://ActiveMQ.Advisory.Consumer.Queue.ID:FA2275059.local-64357-1259934819940-0:0:1
DEBUG InactivityMonitor              - 10001 ms elapsed since last write
check.
DEBUG InactivityMonitor              - 9998 ms elapsed since last write
check.
DEBUG AbstractRegion                 - Removing consumer:
ID:FA2275059.local-64357-1259934819940-0:0:1:1
DEBUG AbstractRegion                 - Removing destination:
temp-queue://ID:FA2275059.local-64357-1259934819940-0:0:1
DEBUG AbstractRegion                 - Removing destination:
topic://ActiveMQ.Advisory.Consumer.Queue.ID:FA2275059.local-64357-1259934819940-0:0:1

-- 
View this message in context: http://old.nabble.com/Persisting-Queues-when-passed-through-Mule-tp26635892p26635892.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

INFO | Using Persistence Adapter:
org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter@578073
INFO | Database
C:\ATSL\TSL_JAVA_27-11-09\apache-activemq-5.3.0-bin\apache-activemq-5.3.0\bin\..\data\kahadb\lock
is locked... waiting 10 seconds for the database to be unlocked. Reason:
java.io.IOException: File
'C:\ATSL\TSL_JAVA_27-11-09\apache-activemq-5.3.0-bin\apache-activemq-5.3.0\bin\..\data\kahadb\lock'
could not be locked.

please help me
-- 
View this message in context: http://old.nabble.com/%5Cbin%5C..%5Cdata%5Ckahadb%5Clock%27-could-not-be-locked...-tp26635855p26635855.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Default apache-mq 5.3.0 comes with a non properly confgured https support.
If a user enables https transport into activemq.xml configuration file, 

<transportConnector name="https" uri="https://0.0.0.0:61617"/>

process enter in an infinite loop (as described into jetty docs).

Could you provide a working https configuration?

Thank you
-- 
View this message in context: http://old.nabble.com/HTTPS-configuration-not-working-tp26635829p26635829.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Hi,

as far as I can see, you message is marked as non-persistent, however
if you want to set explicit time to live you have to set
isExplicitQosEnabled(). See here
http://www.jarvana.com/jarvana/view/org/springframework/spring/1.2.9/spring-1.2.9-javadoc.jar!/org/springframework/jms/core/JmsTemplate.html#isExplicitQosEnabled()
for more info.

Cheers
--
Dejan Bosanac - http://twitter.com/dejanb

Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net



On Thu, Dec 3, 2009 at 11:03 PM, neillott <neilmatthewlott@yahoo.com> wrote:
>
> Hi,
>
> I'm using activemq 5.3.0.
>
> Essentially, I'd like to have a queue that is not persistent whose producers
> will send non-persistent messages.
>
> If I send a message to the queue through the activemq ui and mark it as
> persistent delivery=false and timetolive=10000 -- after 10 seconds it goes
> away.
>
> However, if I set up a java application using spring as follows:
>
>  <bean id="activeMQConnectionFactory"
> class="org.apache.activemq.ActiveMQConnectionFactory">
>        <property name="brokerURL" value="tcp://10.254.0.47:61616"/>
>        <property name="useAsyncSend" value="true"/>
>
>    </bean>
>
>    <bean id="cachingConnectionFactory"
> class="org.springframework.jms.connection.CachingConnectionFactory">
>        <property name="targetConnectionFactory"
> ref="activeMQConnectionFactory"/>
>        <property name="sessionCacheSize" value="100"/>
>        <property name="exceptionListener" ref="preludeExceptionListener"/>
>    </bean>
>
>    <bean id="jmsTemplate" class="org.springframework.jms.core.JmsTemplate">
>        <constructor-arg ref="cachingConnectionFactory"/>
>        <property name="deliveryPersistent" value="false"/>
>        <property name="deliveryMode" value="1"/>
>        <property name="timeToLive" value="20000"/>
>    </bean>
>
> --- and here's my sender
>
> public void send(final String message)
>   {
>
>      log.info("delivery mode {}, timeToLive {}",
> jmsTemplate.getDeliveryMode(), jmsTemplate.getTimeToLive());
> //      jmsTemplate.convertAndSend(QUEUE_NAME, message);
>
>
>      MessageCreator mc = new MessageCreator()
>      {
>         public Message createMessage(Session session) throws JMSException
>         {
>            TextMessage msg = session.createTextMessage();
>            msg.setJMSPriority(9);
>            msg.setText("This is easy!");
>            return msg;
>         }
>      };
>
>      jmsTemplate.send(QUEUE_NAME, mc);
>
>   }
>
> --
>
> The message gets delivered to activemq however it gets marked as persistent
> and it never expires.
>
> Here's the log messages:
>
> 2009-12-03 14:58:29,927  INFO [main] (PreludeNavigationSender.send:68) -
> delivery mode 1, timeToLive 20000
> 2009-12-03 14:58:29,936 DEBUG [main]
> (CachingConnectionFactory.getSession:152) - Created cached Session for mode
> 1: ActiveMQSession {id=ID:flicker-54570-1259877509487-0:0:3,started=true}
> 2009-12-03 14:58:29,936 DEBUG [main] (JmsTemplate.execute:469) - Executing
> callback on JMS Session: ActiveMQSession
> {id=ID:flicker-54570-1259877509487-0:0:3,started=true}
> 2009-12-03 14:58:29,940 DEBUG [main]
> (CachingConnectionFactory$CachedSessionInvocationHandler.invoke:244) -
> Created cached MessageProducer for destination
> [queue://preludenavigationout]: ActiveMQMessageProducer {
> value=ID:flicker-54570-1259877509487-0:0:3:1 }
> 2009-12-03 14:58:29,952 DEBUG [main] (JmsTemplate.doSend:572) - Sending
> created message: ActiveMQTextMessage {commandId = 0, responseRequired =
> false, messageId = null, originalDestination = null, originalTransactionId =
> null, producerId = null, destination = null, transactionId = null,
> expiration = 0, timestamp = 0, arrival = 0, brokerInTime = 0, brokerOutTime
> = 0, correlationId = null, replyTo = null, persistent = false, type = null,
> priority = 9, groupID = null, groupSequence = 0, targetConsumerId = null,
> compressed = false, userID = null, content = null, marshalledProperties =
> null, dataStructure = null, redeliveryCounter = 0, size = 0, properties =
> null, readOnlyProperties = false, readOnlyBody = false, droppable = false,
> text = This is easy!}
>
> Anyone have any ideas?
>
> Thanks,
>
> Neil
>
> --
> View this message in context: http://old.nabble.com/Failing-to-send-non-persistent-ttl-message-using-spring-java-tp26634035p26634035.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>

Hi Sebastian,

An easy way is to modify the bin/activemq script to pass across an
activemq.hostname parameter.

e.g.  in bin/activemq, add:

ACTIVEMQ_HOSTNAME=`hostname -f`

and then in the line :

exec "$JAVACMD" $ACTIVEMQ_DEBUG_OPTS $ACTIVEMQ_OPTS -Dactivemq.classpath="${
ACTIVEMQ_CLASSPATH}" -Dactivemq.home="${ACTIVEMQ_HOME}" -Dactivemq.base="${ACTIV
EMQ_BASE}" -jar "${ACTIVEMQ_HOME}/bin/run.jar" start $@


add in  "-Dactivemq.hostname=${ACTIVEMQ_HOSTNAME} ".


If you use Java Wrapper and an init.d you can do a similar logic - set
the hostname in the init.d script as before, and in the wrapper.conf
do something like:

wrapper.java.additional.3=-Dactivemq.hostname=%ACTIVEMQ_HOSTNAME%

We use the second method in production successfully.

cheers,

James.


2009/12/4 Sebastian Rodriguez <srodrigu85@gmail.com>:
> Dear all,
> In need your advice in the following configuration scenario: we are
> deploying ActiveMQ 5.3 in a big number of machines. The configuration is
> exactly the same for all the machines, the only difference is, of course,
> the broker name. As they need to be unique, they need to be changed in all
> the machines, creating a very repetitive yet time consuming task that would
> be to modify the activemq.xml file.
> Is there a way to use a environment variables in the configuration file (to
> put the hostname of the machine as the broker name)?
> I see there is already some configuration possible through the
> eg.springframework.beans.factory.config.PropertyPlaceholderConfigurer class,
> but those properties are static. I guess I can create a deploy script that
> created my own properties file that will put the hostname in it, but that
> property would only be created or refreshed when I deploy the service.
> This is not the ideal solution as the hostname might change in the machine
> life, so I'm seeking for your advice in the matter.
> Thank you very much for your help,
> --
> Sebastien Rodriguez
>

Dear all,
In need your advice in the following configuration scenario: we are
deploying ActiveMQ 5.3 in a big number of machines. The configuration is
exactly the same for all the machines, the only difference is, of course,
the broker name. As they need to be unique, they need to be changed in all
the machines, creating a very repetitive yet time consuming task that would
be to modify the activemq.xml file.
Is there a way to use a environment variables in the configuration file (to
put the hostname of the machine as the broker name)?
I see there is already some configuration possible through the
eg.springframework.beans.factory.config.PropertyPlaceholderConfigurer class,
but those properties are static. I guess I can create a deploy script that
created my own properties file that will put the hostname in it, but that
property would only be created or refreshed when I deploy the service.
This is not the ideal solution as the hostname might change in the machine
life, so I'm seeking for your advice in the matter.
Thank you very much for your help,
-- 
Sebastien Rodriguez

I might be wrong on this one, but usually, in a network of brokers, the
messages are synced between brokers.
When one of the brokers goes down, the messages are not lost. The producers
and consumers will switch automatically to an available broker,
transparently for the end user.

2009/12/4 yello_downunder <jseutter@gmail.com>

>
> I'm looking at using a network of brokers.  When shutting down a broker in
> the network of brokers, how can you ensure that no messages are trapped on
> the broker being shut down?  Do you have to remove all producers on the
> network of brokers and wait for messages to be processed on all brokers?
>
> --
> View this message in context:
> http://old.nabble.com/Shutting-down-a-broker-in-a-network-of-brokers-tp26634351p26634351.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>


-- 
Sebastien Rodriguez

I'm looking at using a network of brokers.  When shutting down a broker in
the network of brokers, how can you ensure that no messages are trapped on
the broker being shut down?  Do you have to remove all producers on the
network of brokers and wait for messages to be processed on all brokers?

-- 
View this message in context: http://old.nabble.com/Shutting-down-a-broker-in-a-network-of-brokers-tp26634351p26634351.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Hi,

I'm using activemq 5.3.0.

Essentially, I'd like to have a queue that is not persistent whose producers
will send non-persistent messages.

If I send a message to the queue through the activemq ui and mark it as
persistent delivery=false and timetolive=10000 -- after 10 seconds it goes
away.  

However, if I set up a java application using spring as follows:

 <bean id="activeMQConnectionFactory"
class="org.apache.activemq.ActiveMQConnectionFactory">
        <property name="brokerURL" value="tcp://10.254.0.47:61616"/>
        <property name="useAsyncSend" value="true"/>

    </bean>

    <bean id="cachingConnectionFactory"
class="org.springframework.jms.connection.CachingConnectionFactory">
        <property name="targetConnectionFactory"
ref="activeMQConnectionFactory"/>
        <property name="sessionCacheSize" value="100"/>
        <property name="exceptionListener" ref="preludeExceptionListener"/>
    </bean>

    <bean id="jmsTemplate" class="org.springframework.jms.core.JmsTemplate">
        <constructor-arg ref="cachingConnectionFactory"/>
        <property name="deliveryPersistent" value="false"/>
        <property name="deliveryMode" value="1"/>
        <property name="timeToLive" value="20000"/>
    </bean>

--- and here's my sender

public void send(final String message)
   {

      log.info("delivery mode {}, timeToLive {}",
jmsTemplate.getDeliveryMode(), jmsTemplate.getTimeToLive());
//      jmsTemplate.convertAndSend(QUEUE_NAME, message);


      MessageCreator mc = new MessageCreator()
      {
         public Message createMessage(Session session) throws JMSException
         {
            TextMessage msg = session.createTextMessage();
            msg.setJMSPriority(9);
            msg.setText("This is easy!");
            return msg;
         }
      };

      jmsTemplate.send(QUEUE_NAME, mc);

   }

--

The message gets delivered to activemq however it gets marked as persistent
and it never expires.

Here's the log messages:

2009-12-03 14:58:29,927  INFO [main] (PreludeNavigationSender.send:68) -
delivery mode 1, timeToLive 20000
2009-12-03 14:58:29,936 DEBUG [main]
(CachingConnectionFactory.getSession:152) - Created cached Session for mode
1: ActiveMQSession {id=ID:flicker-54570-1259877509487-0:0:3,started=true}
2009-12-03 14:58:29,936 DEBUG [main] (JmsTemplate.execute:469) - Executing
callback on JMS Session: ActiveMQSession
{id=ID:flicker-54570-1259877509487-0:0:3,started=true}
2009-12-03 14:58:29,940 DEBUG [main]
(CachingConnectionFactory$CachedSessionInvocationHandler.invoke:244) -
Created cached MessageProducer for destination
[queue://preludenavigationout]: ActiveMQMessageProducer {
value=ID:flicker-54570-1259877509487-0:0:3:1 }
2009-12-03 14:58:29,952 DEBUG [main] (JmsTemplate.doSend:572) - Sending
created message: ActiveMQTextMessage {commandId = 0, responseRequired =
false, messageId = null, originalDestination = null, originalTransactionId =
null, producerId = null, destination = null, transactionId = null,
expiration = 0, timestamp = 0, arrival = 0, brokerInTime = 0, brokerOutTime
= 0, correlationId = null, replyTo = null, persistent = false, type = null,
priority = 9, groupID = null, groupSequence = 0, targetConsumerId = null,
compressed = false, userID = null, content = null, marshalledProperties =
null, dataStructure = null, redeliveryCounter = 0, size = 0, properties =
null, readOnlyProperties = false, readOnlyBody = false, droppable = false,
text = This is easy!}

Anyone have any ideas?

Thanks,

Neil

-- 
View this message in context: http://old.nabble.com/Failing-to-send-non-persistent-ttl-message-using-spring-java-tp26634035p26634035.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Hey everyone,
Today ActiveMQ-CPP v3.1.0 RC1 is available for download.  This release
sees improvements in the Failover Transport as well as the welcome
addition of an Inactivity Monitor to better detect broken connections.
The threading code has been rewritten with an eye towards performance
and lower memory consumption as well.  Several other bits of code have
been tuned as well making this the fastest version of CMS yet.  Please
take some time to download the release candidate and try it out, report
any bugs you find so we can make this a great release.

See the release notes in the source archive for more information on
what's changed or refer to the official release page for 3.1.0, you
check it out here:
<http://activemq.apache.org/cms/activemq-cpp-310-release.html>

The download links on this page won't work until the release is
official.  For now, follow the instructions at the top to download the
release candidate:
<http://people.apache.org/~tabish/cms-3.1.0/activemq-cpp-library-3.1.0-RC1-src.tar.gz>

Regards,
Tim

Thanks for the clarification.

Then my next question is what is the advantage to having persistence turned
on for a broker in activemq if none of the topics or queues are durable and
the producers of messages are not asking for delivery persistence and all
the messages are asynchronous.
-- 
View this message in context: http://old.nabble.com/Slow-KahaDB-access-tp26594249p26629348.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Hi all, I've followed all the threads and configurations guide for
configuring HTTPS support
(activeMQ 5.3.0 + JBOSS)

I have activated jetty.xml file into broker-config.xml

<import resource="jetty.xml"/>

and configured jetty.xml as follow:

    <jetty>
    ..........
		<Call name="addConnector">
		<Arg>
		  <New class="org.mortbay.jetty.security.SslSocketConnector">
			<!-- <Set name="Port">61</Set> -->
			<Set name="maxIdleTime">30000</Set>
			<Set name="keystore">./keystore</Set>
			<Set name="password">password</Set>
			<Set name="keyPassword">password</Set>
			<Set name="truststore">./keystore</Set>
			<Set name="trustPassword">password</Set>
		  </New>
		</Arg>
	  </Call>
		
    </jetty>

keystore was created as described here: 

http://docs.codehaus.org/display/JETTY/How%20to%20configure%20SSL

What is wrong? 

Thank you!!
-- 
View this message in context: http://old.nabble.com/HTTPS-configuration---HELP%21-tp26628876p26628876.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Hi !

Which is the easiest way to check if the connection to a broker is active.
Using:

<bean id="amqConnectionFactory"
class="org.apache.activemq.pool.PooledConnectionFactory"
destroy-method="stop">
	    <property name="connectionFactory">
	      <bean class="org.apache.activemq.ActiveMQConnectionFactory">
	      	<property name="brokerURL" value="${jms.brokerurl}" />	   
	      </bean>
	    </property>
</bean>

<bean id="amqTransactionManager"
class="org.springframework.jms.connection.JmsTransactionManager">
	    <property name="connectionFactory" ref="amqConnectionFactory" />
	</bean>
	<bean id="amqJmsTemplate" class="org.springframework.jms.core.JmsTemplate">    
		<property name="connectionFactory" ref="amqConnectionFactory" />        
	</bean>	


In a monitor servlet code the the jmstemplate sends a message to a queue.
But
i seems to hang for a while. The socket seems to be open even after the
default
time of 30 seconds. Is there a way to check before try sending the message
to a queue. Or is there any other smart way to accomplish same thing ?

Thanks in advance.

Regards,

Daniel
-- 
View this message in context: http://old.nabble.com/Howto-check-if-connection-is-active-in-Pool-when-all-brokers-in-a-failover-chain-are-shutdown-tp26626661p26626661.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Can anyone please respond to this issue... :-((
-- 
View this message in context: http://old.nabble.com/Confirm-the-correct-usage-of-%22connectionFactoryNames%22-tp26591001p26623402.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

The problem is that they cannot be interpreted by the end user and even if
they could here is no clear corresponding lever to tweak at this time. It
makes sense to leave them in but with a default threshold of 0, such that
they must be enabled, by a knowledgeable user, with a limit that makes sense
for a given application environment.

2009/12/2 Fredrik Jonson <fredrik@jonson.org>

> Gary Tully wrote:
>
> >  Those log messages are developer debug aids that were added early on in
> the
> >  dev cycle and possibly should now be removed.
>
> If those messages can be interpreted by end user why not leave them in?
> Right
> now I agree that they might be of little use, because we haven't got any
> yard
> stick to measure against. It could become useful if someone could say,
> "well
> anything below 500 ms is nothing to worry" - or - "well, once you go above
> five
> seconds you really need to consider the configuration and the hardware".
>
> I understand that it all depends on the load, even so lets start somewhere.
> As I've seen mentioned that anything below 500 ms will be filtered ouy in
> the
> future, can we assume that's a "safe" level? And if so, where is a first
> rough
> upper bound where you would start to monitor the situation? 3 s? 5? 10? 30?
>
> Thanks
> --
> Fredrik Jonson
>
>


-- 
http://blog.garytully.com

Open Source Integration
http://fusesource.com

Hi,

web applications distributed with ActiveMQ are located in webapps/
folder. The REST API is distributed with the "demo" application, so
it's in "webapps/demo"

Cheers
--
Dejan Bosanac - http://twitter.com/dejanb

Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net



On Wed, Dec 2, 2009 at 10:42 PM, nisbus <nisbus@gmail.com> wrote:
>
> Hi,
>
> I want to use the REST interface to ActiveMQ from Silverlight but the
> requirement is that the root of the webserver have a clientaccesspolicy.xml
> file for Silverlight to be able to communicate with it.
>
> Where is the root of Jetty that drives the applets for REST?
>
> thanks,
>  nisbus
> --
> View this message in context: http://old.nabble.com/Jetty-and-clientAccessPolicy.xml-tp26616994p26616994.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>

>Are you noticing delays in producers or consumers or just a little worried
>about the INFO message?

My main concern was about the message.  I haven't seen any delays.

-- 
View this message in context: http://old.nabble.com/Slow-KahaDB-access-tp26594249p26617441.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Gary Tully wrote:

>  Those log messages are developer debug aids that were added early on in the
>  dev cycle and possibly should now be removed.
 
If those messages can be interpreted by end user why not leave them in? Right
now I agree that they might be of little use, because we haven't got any yard
stick to measure against. It could become useful if someone could say, "well
anything below 500 ms is nothing to worry" - or - "well, once you go above five
seconds you really need to consider the configuration and the hardware".

I understand that it all depends on the load, even so lets start somewhere.
As I've seen mentioned that anything below 500 ms will be filtered ouy in the
future, can we assume that's a "safe" level? And if so, where is a first rough
upper bound where you would start to monitor the situation? 3 s? 5? 10? 30?

Thanks
-- 
Fredrik Jonson

Hi, 
I am using the activemq ajax client to push data to a web browser. 

When polling starts, I have noticed that mouse icon is always showing the
hourglass and the browser status bar reads "Waiting for <myhost>" 

Help please. this doesn't look very nice and my users a going wonder why it
looks like the page is not loading fully.

--
jaguarg 
-- 
View this message in context: http://old.nabble.com/Help-please%3A-Hourglass-on-ajax-client-tp26617241p26617241.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Hi,

I want to use the REST interface to ActiveMQ from Silverlight but the
requirement is that the root of the webserver have a clientaccesspolicy.xml
file for Silverlight to be able to communicate with it.

Where is the root of Jetty that drives the applets for REST?

thanks,
  nisbus
-- 
View this message in context: http://old.nabble.com/Jetty-and-clientAccessPolicy.xml-tp26616994p26616994.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Hi,

When I use DB2 as database I am getting below errors and broker does not
start.

----------------------------------------------------------------
Caused by: com.ibm.db2.jcc.b.gm: [jcc][t4][2030][11211][3.50.152] A
communication error occurred during operations on the connection's
underlying socket, socket input stream, 

or socket output stream.  Error location: Reply.fill().  Message: Connection
reset. ERRORCODE=-4499, SQLSTATE=08001
        at com.ibm.db2.jcc.b.wc.a(wc.java:283)
...
009-11-24 19:59:45,997 ERROR [org.jboss.deployment.MainDeployer] Could not
initialise deployment:
file:/ABC/ApplicationContainer/server/default/deploy/activemq-ear-5.3.0.ear/

org.jboss.deployment.DeploymentException: exception in init of
file:/ABC/ApplicationContainer/server/default/deploy/activemq-ear-5.3.0.ear/activemq-ra.rar/db2jcc.jar;
- nested throwable: (java.lang.RuntimeException: java.io.IOException: bad
magic number: cba78dd8)

        at
org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:53)

----------------------------------------------------------------

1) Please note that I dont see any errors with other database
(Oracle,SQLServer,MySQL, etc. works fine).
2) If I *move* db2 jdbc jars to jboss server/default/lib then error goes
away and broker start properly.

Does anyone faced this issue?

Thanks,
PG
-- 
View this message in context: http://old.nabble.com/ActiveMQ-ear-deployed-in-jBoss---DB2-jdbc-jar-errors---Broker-does-not-start-tp26616899p26616899.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

I am trying to get ActiveMQ embedded into Jboss... followed the instructions
to the letter from the activemq site... when I try to deploy my MDB... i get
the following error...

and help would be greatly appreciated.

15:19:32,219 ERROR [JmsActivation] Unable to reconnect
org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@5dcbf8e5(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter@160630e1
destination=activemq/queue/outbound destinationType=javax.jms.Queue tx=true
durable=true clientID=ScanDomainConsumerMDBBean
subscription=ScanDomainConsumerMDBBean reconnect=10
provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1
maxSession=15 keepAlive=60000 useDLQ=true
DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler
DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5)
javax.jms.JMSException: Not Supported.
	at
org.apache.activemq.ra.ManagedConnectionProxy.createConnectionConsumer(ManagedConnectionProxy.java:253)
	at
org.jboss.resource.adapter.jms.inflow.JmsServerSessionPool.setupConsumer(JmsServerSessionPool.java:289)
	at
org.jboss.resource.adapter.jms.inflow.JmsServerSessionPool.start(JmsServerSessionPool.java:89)
	at
org.jboss.resource.adapter.jms.inflow.JmsActivation.setupSessionPool(JmsActivation.java:656)
	at
org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:359)
	at
org.jboss.resource.adapter.jms.inflow.JmsActivation.handleFailure(JmsActivation.java:292)
	at
org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:733)
	at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:205)
	at
org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260)
	at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:637)

-- 
View this message in context: http://old.nabble.com/javax.jms.JMSException%3A-Not-Supported-tp26615993p26615993.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Resolved: correct parametres is ...propertyName = "userName"
-- 
View this message in context: http://old.nabble.com/EJB3-authentication-issue-tp26611052p26611656.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Hi all, 
I have some problems with authentication.
I've configured the authentication with AMQ 5.3 + JBOSS. How can I
authenticate my MDBs??

I've tested with the standard annotations: 

	@ActivationConfigProperty(propertyName = "user", propertyValue = "admin"),
	@ActivationConfigProperty(propertyName = "password", propertyValue =
"admin")

buth this exception is raised.

org.jboss.deployment.DeploymentException: Error for ActivationSpec class
org.apache.activemq.ra.ActiveMQActivationSpec as JavaBean; - nested
throwable: (java.bean
s.IntrospectionException: No property found for: user on JavaBean:
ActiveMQActivationSpec{acknowledgeMode='Auto-acknowledge',
destinationType='javax.jms.Queue
', messageSelector='null', destination='queue/RawDataQueue',
clientId='null', subscriptionName='null',
subscriptionDurability='NonDurable'})
        at
org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:53)
        at
org.jboss.resource.deployment.ActivationSpecFactory.createActivationSpec(ActivationSpecFactory.java:135)
        at
org.jboss.resource.deployment.RARDeployment.createActivationSpec(RARDeployment.java:254)
        at
org.jboss.resource.deployment.RARDeployment.internalInvoke(RARDeployment.java:218)
        at
org.jboss.system.ServiceDynamicMBeanSupport.invoke(ServiceDynamicMBeanSupport.java:156)
        at
org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
        at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at
org.jboss.ejb3.JmxClientKernelAbstraction.invoke(JmxClientKernelAbstraction.java:44)

Without this annotations, the exception is (and is expected):

16:38:45,234 INFO  [TransportConnector] Connector vm://localhost Started
16:38:45,250 WARN  [TransportConnection] Failed to add Connection
java.lang.SecurityException: User name or password is invalid.
        at
org.apache.activemq.security.SimpleAuthenticationBroker.addConnection(SimpleAuthenticationBroker.java:52)
        at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:82)
        at
org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:89)

which is the correct property to use?? Or I have to set up a default
container username/password? Where?

Thank you in advance


       
-- 
View this message in context: http://old.nabble.com/EJB3-authentication-issue-tp26611052p26611052.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Those log messages are developer debug aids that were added early on in the
dev cycle and possibly should now be removed.
In addition, this one is a little misleading as the cleanup duration is
including the wait time to get exclusive access to the index, and not just
the index cleanup operation duration while it has the lock as it should be.
Are you noticing delays in producers or consumers or just a little worried
about the INFO message?


2009/12/1 neillott <neilmatthewlott@yahoo.com>

>
> Hi,
>
> I know this question was posted earlier, but can anyone help here?
>
> http://old.nabble.com/slow-KahaDB-access-td26172918.html#a26216649
>
> I'm seeing this in my activemq log:
>
> 2009-12-01 09:29:08,690 | INFO  | Slow KahaDB access: cleanup took 9789 |
> org.apache.activemq.store.kahadb.MessageDatabase | ActiveMQ Journal
> Checkpoint Worker
> 2009-12-01 09:30:36,376 | INFO  | Slow KahaDB access: cleanup took 1298 |
> org.apache.activemq.store.kahadb.MessageDatabase | ActiveMQ Journal
> Checkpoint Worker
> 2009-12-01 09:47:18,871 | INFO  | Slow KahaDB access: cleanup took 14058 |
> org.apache.activemq.store.kahadb.MessageDatabase | ActiveMQ Journal
> Checkpoint Worker
>
> When I benchmark the box I'm seeing this:
>
> [myserver] /usr/local/neil/activemq > java -classpath lib/kahadb-5.3.0.jar
> org.apache.kahadb.util.DiskBenchmark
> Benchmarking: /usr/local/neil/activemq/disk-benchmark.dat
> Writes:
>  128000 writes of size 4096 written in 18.521 seconds.
>  6911.0737 writes/second.
>  26.996382 megs/second.
>
> Sync Writes:
>  57936 writes of size 4096 written in 10.001 seconds.
>  5793.0205 writes/second.
>  22.628986 megs/second.
>
> Reads:
>  1960651 reads of size 4096 read in 10.001 seconds.
>  196045.5 writes/second.
>  765.80273 megs/second.
>
>
> What exactly do I need to do to get rid of the slow kahadb access messages?
>
> Thanks,
>
> Neil
> --
> View this message in context:
> http://old.nabble.com/Slow-KahaDB-access-tp26594249p26594249.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>


-- 
http://blog.garytully.com

Open Source Integration
http://fusesource.com

The reason why it does not work is that you forgot to add the attribute
start="true" to the broker declaration.
When the AMQConnectionFactory tries to connect to the broker it does not
find it (since you have not started it yet) and than creates and start a new
one using default values. The new broker will create the directory
activemq-data/localhost which will be the one actually used by your
application :)
Maybe it would be better to make the AMQConnectionFactory throwing an
Exception if it does not find the broker at the url specified
-- 
View this message in context: http://old.nabble.com/tmp_storage-created-even-with-presistence-turned-on--%28ActiveMQ-5.0%29-tp16193933p26608566.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Hi,

FWIW, I just documented how to configure the threshold on which the message
will be logged
http://cwiki.apache.org/confluence/display/ACTIVEMQ/KahaDB#KahaDB-SlowKahaDBaccesslogmessages

Cheers
--
Dejan Bosanac - http://twitter.com/dejanb

Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net


On Tue, Dec 1, 2009 at 5:56 PM, neillott <neilmatthewlott@yahoo.com> wrote:

>
> Hi,
>
> I know this question was posted earlier, but can anyone help here?
>
> http://old.nabble.com/slow-KahaDB-access-td26172918.html#a26216649
>
> I'm seeing this in my activemq log:
>
> 2009-12-01 09:29:08,690 | INFO  | Slow KahaDB access: cleanup took 9789 |
> org.apache.activemq.store.kahadb.MessageDatabase | ActiveMQ Journal
> Checkpoint Worker
> 2009-12-01 09:30:36,376 | INFO  | Slow KahaDB access: cleanup took 1298 |
> org.apache.activemq.store.kahadb.MessageDatabase | ActiveMQ Journal
> Checkpoint Worker
> 2009-12-01 09:47:18,871 | INFO  | Slow KahaDB access: cleanup took 14058 |
> org.apache.activemq.store.kahadb.MessageDatabase | ActiveMQ Journal
> Checkpoint Worker
>
> When I benchmark the box I'm seeing this:
>
> [myserver] /usr/local/neil/activemq > java -classpath lib/kahadb-5.3.0.jar
> org.apache.kahadb.util.DiskBenchmark
> Benchmarking: /usr/local/neil/activemq/disk-benchmark.dat
> Writes:
>  128000 writes of size 4096 written in 18.521 seconds.
>  6911.0737 writes/second.
>  26.996382 megs/second.
>
> Sync Writes:
>  57936 writes of size 4096 written in 10.001 seconds.
>  5793.0205 writes/second.
>  22.628986 megs/second.
>
> Reads:
>  1960651 reads of size 4096 read in 10.001 seconds.
>  196045.5 writes/second.
>  765.80273 megs/second.
>
>
> What exactly do I need to do to get rid of the slow kahadb access messages?
>
> Thanks,
>
> Neil
> --
> View this message in context:
> http://old.nabble.com/Slow-KahaDB-access-tp26594249p26594249.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>

Hi,

you can specify createConnector=false on a management context and in that
way you can only access JMX from the local machine (no ports will be open).
Jconsole will see this process nicely, but you'll have to use Sun JDK to
access JMX API exposed in this way.

Cheers
--
Dejan Bosanac - http://twitter.com/dejanb

Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net


On Tue, Dec 1, 2009 at 6:18 PM, Fred Moore <fred.moore77@gmail.com> wrote:

> Hi folks,
> I have a completely embedded broker instance running in the same JVM as my
> JMS applications, all applications use a VM transport connector so the
> "TCP/IP footprint" (i.e. used ports) of this system is currently zero.
>
> Now my additional requirement is to be able to remove some [unused] broker
> queues programmatically via a new service application running in the same
> JVM as the broker.
>
> Is there a way of performing this simple operation without having my broker
> listening on a TCP/IP port (and consequently introducing the need for
> locking down admin access with security credentials management etc)?
>
> For instance this wiki
> http://activemq.apache.org/how-do-i-delete-a-destination.html points to
> JMX
> which -- AFAIK -- requires listening on TCP/IP to start with.
>
> I'm I missing something obvious here?
> Thanks in advance.
> Cheers,
> F.
>

stock activemq.xml should be fine. The client ack in the tests is because
the limits are such that only one message can fit in the queue so that the
ack behavior is exactly deterministic w.r.t memory usage.
JMX instrumentation will help. Use jconsole and when the queue is drained,
what does the Broker say w.r.t to memory usage and for the queue w.r.t
cursor memory usage. Both should go to 0. If they are not at zero you may be
experiencing some of the known issues that effect memory management
accounting w.r.t the file based cursor in 5.3.0 that have been resolved on
trunk. If this is the case, I would recommend trying  a run with the latest
5.4-SNAPSHOT and if that shows the problem to progress to opening an issue
and attaching your test case.


2009/12/2 Geir Magnusson Jr. <geir@pobox.com>

> Thanks for the response.
>
> On Dec 2, 2009, at 4:38 AM, Gary Tully wrote:
>
> > can you post your activemq.xml?
>
> It's as distributed in 5.3.0
>
> > possibly compare you setup to what is known to work from the unit tests:
> > org.apache.activemq.ProducerFlowControlTest
> >
> >
> http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/ProducerFlowControlTest.java?view=markup
>
>
> Thx.  The only thing that jumps out at me is that
>
> a) I'm not ever calling setUseAsyncSend on the factory, but as my messages
> are non-persistent, I don't know if it matters.  I can try it though,
> although I'm loathe to just "try things" :)
> b) I use auto ack rather than client ack.  Does that make a diff?
>
> I did try OpenMQ with the same code, and everything just worked - ran about
> 10MM messages until I got bored. I would prefer to use ActiveMQ though.  Is
> the fact I have a stock activemq.xml relevant?  Is there any way I can ask
> the broker what it thinks about the state of affairs when this happens?  any
> verbose logging modes beyond the log message I mentioned?
>
> geir
>
>
> >
> > 2009/12/1 Geir Magnusson Jr. <geir@pobox.com>
> >
> >> I'm doing some simple stress experiments and am able to lockup 5.3.0.  I
> >> have a simple producer and consumer as described below.  The queue is
> >> non-perstent, moving small text messages.  Flailing about, I've set my
> >> producer window size to 1024000.
> >>
> >> Upshot is that I can flood the queue for about 250k to 300k messages
> >> overall, and the producer eventually gets stopped.  THe consumer seems
> to
> >> get all of them, at least according to the console which shows 0
> messages in
> >> queue, eventually.
> >>
> >> At this point, the producer never starts again, and even bouncing the
> >> producer doesn't get messages flowing again.  The only thing that works
> is
> >> bouncing the broker, but clearly that's a crappy solution.
> >>
> >> What am I doing wrong?
> >>
> >> geir
> >>
> >>
> >>
> >> Producer - single one, thread...
> >>
> >>       ActiveMQConnectionFactory factory = new
> >> ActiveMQConnectionFactory("tcp://10.0.0.2:61616");
> >>       factory.setProducerWindowSize(1024000);
> >>
> >>       Connection connection = factory.createConnection();
> >>       connection.start();
> >>
> >>       Session session = connection.createSession(false,
> >> Session.AUTO_ACKNOWLEDGE);
> >>       Queue queue = session.createQueue("svc");
> >>       MessageProducer producer = session.createProducer(queue);
> >>       producer.setDeliveryMode(DeliveryMode.NON_PERSISTENT);
> >>
> >>       while(true) {
> >>
> >>           while(true) {
> >>               TextMessage tm = session.createTextMessage(theMessage);
> >>               producer.send(tm);
> >>           }
> >>       }
> >>
> >> That simply floods the queue with small text messages.
> >>
> >> On the consumer side, I have 15 threads, each of which does something
> like
> >> :
> >>
> >>       ActiveMQConnectionFactory factory = new
> >> ActiveMQConnectionFactory(_brokerURL);
> >>
> >>       _connection = factory.createConnection();
> >>       Session _session = _connection.createSession(false,
> >> Session.AUTO_ACKNOWLEDGE);
> >>
> >>      Queue queue = _session.createQueue(name);
> >>
> >>      MessageConsumer consumer = _session.createConsumer(queue);
> >>
> >>      consumer.setMessageListener(new MessageHandlerAdapter(_session,
> >> msgHandler));
> >>
> >> where my MessageHandlerAdapter has a pretty boring onMessage() method.
> >>
> >> Things go fine until I see the now-dreaded
> >>
> >> INFO | Usage Manager memory limit reached on queue://svc. Producers will
> be
> >> throttled to the rate at which messages are removed from this
> destination to
> >> prevent flooding it. See
> >> http://activemq.apache.org/producer-flow-control.html for more info
> >>
> >>
> >>
> >>
> >>
> >
> >
> > --
> > http://blog.garytully.com
> >
> > Open Source Integration
> > http://fusesource.com
>
>


-- 
http://blog.garytully.com

Open Source Integration
http://fusesource.com

Hi All;

I am trying to create a new secure Queue at the runtime, and provides
users access to that Queue in runtime, without restarting the ActiveMQ
broker. (And if possible add new users in runtime as well).

Is this possible? For example, is it possible to do this through JMX
console or is there something equivalent.

I also looked at http://activemq.apache.org/security.html, and If I
get that right, methods describe in the document need a restart of the
message broker?

Thanks very much
Srinath


-- 
============================
Srinath Perera, Ph.D.
   WSO2 Inc. http://wso2.com
   Blog: http://srinathsview.blogspot.com/

Thanks for the response.

On Dec 2, 2009, at 4:38 AM, Gary Tully wrote:

> can you post your activemq.xml?

It's as distributed in 5.3.0

> possibly compare you setup to what is known to work from the unit tests:
> org.apache.activemq.ProducerFlowControlTest
> 
> http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/ProducerFlowControlTest.java?view=markup


Thx.  The only thing that jumps out at me is that 

a) I'm not ever calling setUseAsyncSend on the factory, but as my messages are non-persistent,
I don't know if it matters.  I can try it though, although I'm loathe to just "try things"
:)
b) I use auto ack rather than client ack.  Does that make a diff?

I did try OpenMQ with the same code, and everything just worked - ran about 10MM messages
until I got bored. I would prefer to use ActiveMQ though.  Is the fact I have a stock activemq.xml
relevant?  Is there any way I can ask the broker what it thinks about the state of affairs
when this happens?  any verbose logging modes beyond the log message I mentioned?

geir


> 
> 2009/12/1 Geir Magnusson Jr. <geir@pobox.com>
> 
>> I'm doing some simple stress experiments and am able to lockup 5.3.0.  I
>> have a simple producer and consumer as described below.  The queue is
>> non-perstent, moving small text messages.  Flailing about, I've set my
>> producer window size to 1024000.
>> 
>> Upshot is that I can flood the queue for about 250k to 300k messages
>> overall, and the producer eventually gets stopped.  THe consumer seems to
>> get all of them, at least according to the console which shows 0 messages in
>> queue, eventually.
>> 
>> At this point, the producer never starts again, and even bouncing the
>> producer doesn't get messages flowing again.  The only thing that works is
>> bouncing the broker, but clearly that's a crappy solution.
>> 
>> What am I doing wrong?
>> 
>> geir
>> 
>> 
>> 
>> Producer - single one, thread...
>> 
>>       ActiveMQConnectionFactory factory = new
>> ActiveMQConnectionFactory("tcp://10.0.0.2:61616");
>>       factory.setProducerWindowSize(1024000);
>> 
>>       Connection connection = factory.createConnection();
>>       connection.start();
>> 
>>       Session session = connection.createSession(false,
>> Session.AUTO_ACKNOWLEDGE);
>>       Queue queue = session.createQueue("svc");
>>       MessageProducer producer = session.createProducer(queue);
>>       producer.setDeliveryMode(DeliveryMode.NON_PERSISTENT);
>> 
>>       while(true) {
>> 
>>           while(true) {
>>               TextMessage tm = session.createTextMessage(theMessage);
>>               producer.send(tm);
>>           }
>>       }
>> 
>> That simply floods the queue with small text messages.
>> 
>> On the consumer side, I have 15 threads, each of which does something like
>> :
>> 
>>       ActiveMQConnectionFactory factory = new
>> ActiveMQConnectionFactory(_brokerURL);
>> 
>>       _connection = factory.createConnection();
>>       Session _session = _connection.createSession(false,
>> Session.AUTO_ACKNOWLEDGE);
>> 
>>      Queue queue = _session.createQueue(name);
>> 
>>      MessageConsumer consumer = _session.createConsumer(queue);
>> 
>>      consumer.setMessageListener(new MessageHandlerAdapter(_session,
>> msgHandler));
>> 
>> where my MessageHandlerAdapter has a pretty boring onMessage() method.
>> 
>> Things go fine until I see the now-dreaded
>> 
>> INFO | Usage Manager memory limit reached on queue://svc. Producers will be
>> throttled to the rate at which messages are removed from this destination to
>> prevent flooding it. See
>> http://activemq.apache.org/producer-flow-control.html for more info
>> 
>> 
>> 
>> 
>> 
> 
> 
> -- 
> http://blog.garytully.com
> 
> Open Source Integration
> http://fusesource.com

can you post your activemq.xml?
possibly compare you setup to what is known to work from the unit tests:
org.apache.activemq.ProducerFlowControlTest

http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/ProducerFlowControlTest.java?view=markup

2009/12/1 Geir Magnusson Jr. <geir@pobox.com>

> I'm doing some simple stress experiments and am able to lockup 5.3.0.  I
> have a simple producer and consumer as described below.  The queue is
> non-perstent, moving small text messages.  Flailing about, I've set my
> producer window size to 1024000.
>
> Upshot is that I can flood the queue for about 250k to 300k messages
> overall, and the producer eventually gets stopped.  THe consumer seems to
> get all of them, at least according to the console which shows 0 messages in
> queue, eventually.
>
> At this point, the producer never starts again, and even bouncing the
> producer doesn't get messages flowing again.  The only thing that works is
> bouncing the broker, but clearly that's a crappy solution.
>
> What am I doing wrong?
>
> geir
>
>
>
> Producer - single one, thread...
>
>        ActiveMQConnectionFactory factory = new
> ActiveMQConnectionFactory("tcp://10.0.0.2:61616");
>        factory.setProducerWindowSize(1024000);
>
>        Connection connection = factory.createConnection();
>        connection.start();
>
>        Session session = connection.createSession(false,
> Session.AUTO_ACKNOWLEDGE);
>        Queue queue = session.createQueue("svc");
>        MessageProducer producer = session.createProducer(queue);
>        producer.setDeliveryMode(DeliveryMode.NON_PERSISTENT);
>
>        while(true) {
>
>            while(true) {
>                TextMessage tm = session.createTextMessage(theMessage);
>                producer.send(tm);
>            }
>        }
>
> That simply floods the queue with small text messages.
>
> On the consumer side, I have 15 threads, each of which does something like
> :
>
>        ActiveMQConnectionFactory factory = new
> ActiveMQConnectionFactory(_brokerURL);
>
>        _connection = factory.createConnection();
>        Session _session = _connection.createSession(false,
> Session.AUTO_ACKNOWLEDGE);
>
>       Queue queue = _session.createQueue(name);
>
>       MessageConsumer consumer = _session.createConsumer(queue);
>
>       consumer.setMessageListener(new MessageHandlerAdapter(_session,
> msgHandler));
>
> where my MessageHandlerAdapter has a pretty boring onMessage() method.
>
> Things go fine until I see the now-dreaded
>
> INFO | Usage Manager memory limit reached on queue://svc. Producers will be
> throttled to the rate at which messages are removed from this destination to
> prevent flooding it. See
> http://activemq.apache.org/producer-flow-control.html for more info
>
>
>
>
>


-- 
http://blog.garytully.com

Open Source Integration
http://fusesource.com