[jira] [Commented] (AMQ-5188) AMQ broker throws OutOfMemoryError even when global flow-control memoryUsage limit is imposed
[ https://issues.apache.org/jira/browse/AMQ-5188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14001601#comment-14001601 ] Michael Samson commented on AMQ-5188: - Found it https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/apache-activemq/5.10-SNAPSHOT/ AMQ broker throws OutOfMemoryError even when global flow-control memoryUsage limit is imposed - Key: AMQ-5188 URL: https://issues.apache.org/jira/browse/AMQ-5188 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.8.0 Environment: AMQ 5.8.0 broker running on 64-bit Linux AMQP Qpid (.26) JMS producers running on 64-bin Linux Reporter: Michael Samson Attachments: AMQ_heap1.png, AMQ_heap2.png, QpidProducerAMQOutOfMemory.java, activemq.xml, qpid-producer.tar * 5.8.0 broker was configured with persistence=false and a global memoryUsage limit=700 mb/ * 5.8.0 broker JVM memory was set to default of 1G * No active consumers * 10 Qpid (version .26) AMQP producers sent messages to 10 broker queues until flow control was reached * Over time the AMQP connections/producers were closed and recreated and they reattempted to send messages. As this cycle continues, eventually ActiveMQ threw OutOfMemoryErrors. I grabbed a heap dump and ActiveMQTextMessages consumed 874M of the heap. Taking a closer look, it appears that each org.apache.activemq.broker.region.Queue's messagesWaitingForSpace map grows unbounded and causes the OutOfMemory. I will attach a sample maven program that reproduces the problem along with my activemq configuration, heap screenshots, etc. Are their any workarounds to this issue? It is a use case for our customers if their queue consumers die for an extended period of time. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (AMQ-5188) AMQ broker throws OutOfMemoryError even when global flow-control memoryUsage limit is imposed
[ https://issues.apache.org/jira/browse/AMQ-5188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14001599#comment-14001599 ] Michael Samson commented on AMQ-5188: - Could you provide a link where I can download the 5.10-SNAPSHOT tar.gz ? AMQ broker throws OutOfMemoryError even when global flow-control memoryUsage limit is imposed - Key: AMQ-5188 URL: https://issues.apache.org/jira/browse/AMQ-5188 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.8.0 Environment: AMQ 5.8.0 broker running on 64-bit Linux AMQP Qpid (.26) JMS producers running on 64-bin Linux Reporter: Michael Samson Attachments: AMQ_heap1.png, AMQ_heap2.png, QpidProducerAMQOutOfMemory.java, activemq.xml, qpid-producer.tar * 5.8.0 broker was configured with persistence=false and a global memoryUsage limit=700 mb/ * 5.8.0 broker JVM memory was set to default of 1G * No active consumers * 10 Qpid (version .26) AMQP producers sent messages to 10 broker queues until flow control was reached * Over time the AMQP connections/producers were closed and recreated and they reattempted to send messages. As this cycle continues, eventually ActiveMQ threw OutOfMemoryErrors. I grabbed a heap dump and ActiveMQTextMessages consumed 874M of the heap. Taking a closer look, it appears that each org.apache.activemq.broker.region.Queue's messagesWaitingForSpace map grows unbounded and causes the OutOfMemory. I will attach a sample maven program that reproduces the problem along with my activemq configuration, heap screenshots, etc. Are their any workarounds to this issue? It is a use case for our customers if their queue consumers die for an extended period of time. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AMQ-5188) AMQ broker throws OutOfMemoryError even when global flow-control memoryUsage limit is imposed
[ https://issues.apache.org/jira/browse/AMQ-5188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Samson updated AMQ-5188: Attachment: activemq-5.10.xml Attaching configuration used with 5.10-SNAPSHOT. AMQ broker throws OutOfMemoryError even when global flow-control memoryUsage limit is imposed - Key: AMQ-5188 URL: https://issues.apache.org/jira/browse/AMQ-5188 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.8.0 Environment: AMQ 5.8.0 broker running on 64-bit Linux AMQP Qpid (.26) JMS producers running on 64-bin Linux Reporter: Michael Samson Attachments: AMQ_heap1.png, AMQ_heap2.png, QpidProducerAMQOutOfMemory.java, activemq-5.10.xml, activemq.xml, qpid-producer.tar * 5.8.0 broker was configured with persistence=false and a global memoryUsage limit=700 mb/ * 5.8.0 broker JVM memory was set to default of 1G * No active consumers * 10 Qpid (version .26) AMQP producers sent messages to 10 broker queues until flow control was reached * Over time the AMQP connections/producers were closed and recreated and they reattempted to send messages. As this cycle continues, eventually ActiveMQ threw OutOfMemoryErrors. I grabbed a heap dump and ActiveMQTextMessages consumed 874M of the heap. Taking a closer look, it appears that each org.apache.activemq.broker.region.Queue's messagesWaitingForSpace map grows unbounded and causes the OutOfMemory. I will attach a sample maven program that reproduces the problem along with my activemq configuration, heap screenshots, etc. Are their any workarounds to this issue? It is a use case for our customers if their queue consumers die for an extended period of time. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (AMQ-5188) AMQ broker throws OutOfMemoryError even when global flow-control memoryUsage limit is imposed
[ https://issues.apache.org/jira/browse/AMQ-5188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14001631#comment-14001631 ] Michael Samson commented on AMQ-5188: - I reproduced the OutOfMemoryError using 5.10-SNAPSHOT. See attached activemq-5.10.xml for configuration. I also added system=manager to users.properties and system to admins groups in groups.properties. AMQ broker throws OutOfMemoryError even when global flow-control memoryUsage limit is imposed - Key: AMQ-5188 URL: https://issues.apache.org/jira/browse/AMQ-5188 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.8.0 Environment: AMQ 5.8.0 broker running on 64-bit Linux AMQP Qpid (.26) JMS producers running on 64-bin Linux Reporter: Michael Samson Attachments: AMQ_heap1.png, AMQ_heap2.png, QpidProducerAMQOutOfMemory.java, activemq-5.10.xml, activemq.xml, qpid-producer.tar * 5.8.0 broker was configured with persistence=false and a global memoryUsage limit=700 mb/ * 5.8.0 broker JVM memory was set to default of 1G * No active consumers * 10 Qpid (version .26) AMQP producers sent messages to 10 broker queues until flow control was reached * Over time the AMQP connections/producers were closed and recreated and they reattempted to send messages. As this cycle continues, eventually ActiveMQ threw OutOfMemoryErrors. I grabbed a heap dump and ActiveMQTextMessages consumed 874M of the heap. Taking a closer look, it appears that each org.apache.activemq.broker.region.Queue's messagesWaitingForSpace map grows unbounded and causes the OutOfMemory. I will attach a sample maven program that reproduces the problem along with my activemq configuration, heap screenshots, etc. Are their any workarounds to this issue? It is a use case for our customers if their queue consumers die for an extended period of time. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (AMQ-5189) Rollback on XASession when closing back to pool
[ https://issues.apache.org/jira/browse/AMQ-5189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14001747#comment-14001747 ] Chris Geer commented on AMQ-5189: - I think this issue was fixed in 5.9. Can you confirm it's an issue in the newer versions because or provide a test case because I'm not seeing the issue currently. Rollback on XASession when closing back to pool --- Key: AMQ-5189 URL: https://issues.apache.org/jira/browse/AMQ-5189 Project: ActiveMQ Issue Type: Bug Components: activemq-pool Affects Versions: 5.7.0, 5.8.0, 5.9.0, 5.9.1 Environment: Windows, UNIX Reporter: Benjamin Graf If you have a pool of XASession under load (heavy load might be necessary) I register sometimes following Exception Cannot rollback() inside an XASession in afterCompletion synchronisation. After some analysis and patching with logging I recognized that the session object is returned back to pool before setting the xa flag back to false. This leads to the effect that this session gets be used again by another thread while the earlier one switches the xa flag to false. -- This message was sent by Atlassian JIRA (v6.2#6252)
Re: ActiveMQ 5.10 release date?
Since this issue is resolved. Any dates for ActiveMQ 5.10 ? -- View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-5-10-release-date-tp4678366p4681253.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
ActiveMQ Websphere 8.5 long polling
Dear All The activemq long polling (using the reverse ajax + servlet3 continuation + asynchronous context) is working correctly under tomcat and weblogic. when deploying under websphere 8.5 we are getting an error with long polling ajax request : java.lang.IllegalStateException: called setTimeout after the container-initiated dispatch which called startAsync has returned Caused by: java.lang.IllegalStateException: called setTimeout after the container-initiated dispatch which called startAsync has returned at com.ibm.ws.webcontainer.async.AsyncContextImpl.setTimeout(AsyncContextImpl.java:640) at org.eclipse.jetty.continuation.Servlet3Continuation.setTimeout(Servlet3Continuation.java:179) at org.apache.activemq.web.MessageListenerServlet.doMessages(MessageListenerServlet.java:325) Please any advise? is there a specific configuration to be done for websphere 8.5? Thank you -- View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-Websphere-8-5-long-polling-tp4681242.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
[jira] [Commented] (AMQ-5160) Wildcard subscriptions bypass Authentication / Authorization
[ https://issues.apache.org/jira/browse/AMQ-5160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14001995#comment-14001995 ] Dhiraj Bokde commented on AMQ-5160: --- Hi [~surfnerd], Thanks for validating PR22. If you tested with PR24 that should be good, since it includes commits from PR22. We could just as well apply PR24 directly to ActiveMQ trunk. Also, are you testing Virtual Topics too, it is a pretty cool feature I added. I've written a post about it at http://rockablogbaby.blogspot.com/2014/05/scalable-iot-integration-using-apache.html Regards, Dhiraj. Wildcard subscriptions bypass Authentication / Authorization Key: AMQ-5160 URL: https://issues.apache.org/jira/browse/AMQ-5160 Project: ActiveMQ Issue Type: Bug Components: MQTT Affects Versions: 5.9.1 Reporter: Surf Priority: Critical Labels: authentication, authorization, mqtt, security Fix For: 5.10.0 Attachments: activemq.xml, groups.properties, login.config, patch.txt, users.properties I am using MQTT on AMQ 5.9.1 After latest MQTT hardening from [~dhirajsb] , there is an issue of MQTT retained messages. Simple case: Set Authentication / Authorization for two different TOPICS. Send retained message to one topic. Try to subscribe # with other second user. It will show retained messages published by TOPIC 1. here i have attached test configurations. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (AMQ-5187) Virtual destination consumers do not support retroactive message recovery
[ https://issues.apache.org/jira/browse/AMQ-5187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14001997#comment-14001997 ] Dhiraj Bokde commented on AMQ-5187: --- I've also written a post about this fix at http://rockablogbaby.blogspot.com/2014/05/scalable-iot-integration-using-apache.html Virtual destination consumers do not support retroactive message recovery - Key: AMQ-5187 URL: https://issues.apache.org/jira/browse/AMQ-5187 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.9.1 Reporter: Dhiraj Bokde Virtual destinations intercept messages sent by producers and pass them onto consumers, but when consumers connect to mapped destinations, they do not receive retroactive messages. This is particularly required for MQTT clients using virtual topics to send retained messages to consumer queues. -- This message was sent by Atlassian JIRA (v6.2#6252)
Re: Discussion: JMS 2.0 API support
Hmm, from the deafening silence I must assume that either of the two things happened: 1. People didn't read my post for some reason (and hence I am replying to my own post to refresh this post), or 2. There is no appetite supporting JMS 2.0 in ActiveMQ and hence people ignored my post. Anyways, if I won't see any feedback or comments to this post, I have to assume that ActiveMQ will be a dead-end with regards to JMS 2.0 (and future versions of JMS). Thanks, -Uli -- View this message in context: http://activemq.2283324.n4.nabble.com/Discussion-JMS-2-0-API-support-tp4681089p4681256.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: Discussion: JMS 2.0 API support
On Tue, May 13, 2014 at 8:01 PM, uromahn ulr...@ulrichromahn.net wrote: Hi Folks, just wanted to throw a bone out seeing if anyone catches it and responds. I was wondering whether ActiveMQ has any intention to support the JMS 2.0 API specification which is part of JEE7 and has been released almost a year ago (May 21, 2013). JMS 2.0 has some significant improvements over JMS 1.1 and I believe supporting it in ActiveMQ soon may improve its popularity within the Java community. Based on my current investigation, the only options for JMS 2.0 support seem to be HornetQ (JBoss) and Open MQ (Glassfish) and Fiorano MQ. So, is there any interest in supporting JMS 2.0 in the near future? I would love to contribute but my current day-job just doesn't give me enough time. :( JMS 2.0 is not on the radar for ActiveMQ 5.10. And I think people are too busy with getting the final fixes and whatnot needed for that release. I suggest you log a JIRA ticket about JMS 2.0 support, if not already there. And use its voting system, so people can say they want this. Also what is there in JMS 2.0 from broker point of view. eg for client there is a simpler api. But what is there on the broker side? Also a lot of other protocols these days get attention than just JMS. eg MQTT, AMQP, etc. IMHO these are more important in the future, than traditional JMS. And most clients/brokers is already 1.1 compliant. So I don't see this as a show stopper that 2.0 must be support in the very near future. But sure it would be great for ActiveMQ to support that too. Ideas, comments, suggestions? -Uli -- View this message in context: http://activemq.2283324.n4.nabble.com/Discussion-JMS-2-0-API-support-tp4681089.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. -- Claus Ibsen - Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
Re: Discussion: JMS 2.0 API support
On May 19, 2014, at 1:35 PM, uromahn ulr...@ulrichromahn.net wrote: Hmm, from the deafening silence I must assume that either of the two things happened: 1. People didn't read my post for some reason (and hence I am replying to my own post to refresh this post), or 2. There is no appetite supporting JMS 2.0 in ActiveMQ and hence people ignored my post. As Claus stated, there hasn’t really been any demand for JMS 2.0 support so far. One reason is that, at this point, ActiveMQ still supports Java6. The JMS 2.0 spec mandates the use of some Java7 features and API’s (AutoClosable for example) which would likely require ActiveMQ to drop support for Java6. I’m not saying that won’t happen, but right now, that’s not on the 5.10 agenda and most of the ActiveMQ folks are really trying to get that out before tackling the “what next” kind of questions. That said, if you are interested in starting to pursue updating things to support JMS 2.0, we’d be happy to accept contributions. A branch on github that we could look at after 5.10 goes out would certainly be welcome. Note: there is also a issue about obtaining access to the JMS 2.0 TCK for testing compliance. That’s a completely separate issue, but if 100% compliance is important, it’s something that would need to be figured out. Dan Anyways, if I won't see any feedback or comments to this post, I have to assume that ActiveMQ will be a dead-end with regards to JMS 2.0 (and future versions of JMS). Thanks, -Uli -- View this message in context: http://activemq.2283324.n4.nabble.com/Discussion-JMS-2-0-API-support-tp4681089p4681256.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
[jira] [Commented] (AMQ-5189) Rollback on XASession when closing back to pool
[ https://issues.apache.org/jira/browse/AMQ-5189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14002100#comment-14002100 ] Benjamin Graf commented on AMQ-5189: Since this problem is not deterministic its quite hard to deliver a test case. But if you look at the code you can see that this problem does still exist in trunk code. Look at XaConnectionPool line 106 where the close operation on the PooledSession object is invoked which returns itself back into the pool in line 152. But the Synchronization object of XaConnectionPool does still change values after that in line 107 and 108 while the pool object might be used again in another thread. So it is obvious that a collition can occured! Rollback on XASession when closing back to pool --- Key: AMQ-5189 URL: https://issues.apache.org/jira/browse/AMQ-5189 Project: ActiveMQ Issue Type: Bug Components: activemq-pool Affects Versions: 5.7.0, 5.8.0, 5.9.0, 5.9.1 Environment: Windows, UNIX Reporter: Benjamin Graf If you have a pool of XASession under load (heavy load might be necessary) I register sometimes following Exception Cannot rollback() inside an XASession in afterCompletion synchronisation. After some analysis and patching with logging I recognized that the session object is returned back to pool before setting the xa flag back to false. This leads to the effect that this session gets be used again by another thread while the earlier one switches the xa flag to false. -- This message was sent by Atlassian JIRA (v6.2#6252)
Re: ActiveMQ Websphere 8.5 long polling
Hi, I'm learning push technology and what I've learned is when doing reverse ajax using push technology on the serverside you will need to use servlet modified using NIO. Probably the reason why it works on Tomcat is because it implements the Comet API. To get a client to be notified through push notification you will need an event listener which must be linked to the Comet API. Every time events occur it sends back information from the server to the browser. Some interesting technologies you can try is DWR, Google Gears, or a new one called Atmospherehttps://github.com/Atmosphere/atmosphere. Please correct me if im wrong. This error seems to be coming from the serverside. Since it works in tomcat, weblogic. I have not used websphere but I want to make sure your request is processed. Can you login to jira and open a ticket for this so it is not forgotten. Thanks, Zak On Mon, May 19, 2014 at 4:37 AM, tony nabil.fegh...@hotmail.com wrote: Dear All The activemq long polling (using the reverse ajax + servlet3 continuation + asynchronous context) is working correctly under tomcat and weblogic. when deploying under websphere 8.5 we are getting an error with long polling ajax request : java.lang.IllegalStateException: called setTimeout after the container-initiated dispatch which called startAsync has returned Caused by: java.lang.IllegalStateException: called setTimeout after the container-initiated dispatch which called startAsync has returned at com.ibm.ws.webcontainer.async.AsyncContextImpl.setTimeout(AsyncContextImpl.java:640) at org.eclipse.jetty.continuation.Servlet3Continuation.setTimeout(Servlet3Continuation.java:179) at org.apache.activemq.web.MessageListenerServlet.doMessages(MessageListenerServlet.java:325) Please any advise? is there a specific configuration to be done for websphere 8.5? Thank you -- View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-Websphere-8-5-long-polling-tp4681242.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
[jira] [Created] (AMQ-5191) Add information about Job Scheduler persistence to Configuring Broker Persistence book
Burning Luffy created AMQ-5191: -- Summary: Add information about Job Scheduler persistence to Configuring Broker Persistence book Key: AMQ-5191 URL: https://issues.apache.org/jira/browse/AMQ-5191 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.9.0 Reporter: Burning Luffy Priority: Minor As the feature AMQ-3024 has been resolved in ActiveMQ 5.9.0. But we have no such a guide to describe how to configure that. Please add a page for this to User Manual. . -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AMQ-5191) Add information about Job Scheduler persistence to Configuring Broker Persistence book
[ https://issues.apache.org/jira/browse/AMQ-5191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burning Luffy updated AMQ-5191: --- Description: As the feature AMQ-3024 has been resolved in ActiveMQ 5.9.0. But we have no such a guide to describe how to enable that. Please add a page for this to User Manual. . (was: As the feature AMQ-3024 has been resolved in ActiveMQ 5.9.0. But we have no such a guide to describe how to configure that. Please add a page for this to User Manual. .) Add information about Job Scheduler persistence to Configuring Broker Persistence book --- Key: AMQ-5191 URL: https://issues.apache.org/jira/browse/AMQ-5191 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.9.0 Reporter: Burning Luffy Priority: Minor As the feature AMQ-3024 has been resolved in ActiveMQ 5.9.0. But we have no such a guide to describe how to enable that. Please add a page for this to User Manual. . -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (AMQ-5192) Add a statistic for showing how many messages every scheduler job triggered
Burning Luffy created AMQ-5192: -- Summary: Add a statistic for showing how many messages every scheduler job triggered Key: AMQ-5192 URL: https://issues.apache.org/jira/browse/AMQ-5192 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.8.0 Reporter: Burning Luffy Is there anyway we can see how many messages are scheduled for re-delivery per queue? At the moment the best we can do is get the number of scheduled jobs via JMX, which is not queue-specific. Is it possible to programmatically query the KahaDB to inspect the scheduled redelivery jobs? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AMQ-5192) Add a statistic for showing how many messages every scheduler job triggered
[ https://issues.apache.org/jira/browse/AMQ-5192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated AMQ-5192: - Component/s: Job Scheduler JMX Issue Type: Improvement (was: Bug) Add a statistic for showing how many messages every scheduler job triggered --- Key: AMQ-5192 URL: https://issues.apache.org/jira/browse/AMQ-5192 Project: ActiveMQ Issue Type: Improvement Components: Broker, JMX, Job Scheduler Affects Versions: 5.8.0 Reporter: Burning Luffy Is there anyway we can see how many messages are scheduled for re-delivery per queue? At the moment the best we can do is get the number of scheduled jobs via JMX, which is not queue-specific. Is it possible to programmatically query the KahaDB to inspect the scheduled redelivery jobs? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AMQ-5191) Add information about Job Scheduler persistence to Configuring Broker Persistence book
[ https://issues.apache.org/jira/browse/AMQ-5191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated AMQ-5191: - Component/s: (was: Job Scheduler) (was: JMX) (was: Broker) Documentation Add information about Job Scheduler persistence to Configuring Broker Persistence book --- Key: AMQ-5191 URL: https://issues.apache.org/jira/browse/AMQ-5191 Project: ActiveMQ Issue Type: Improvement Components: Documentation Affects Versions: 5.9.0 Reporter: Burning Luffy Priority: Minor As the feature AMQ-3024 has been resolved in ActiveMQ 5.9.0. But we have no such a guide to describe how to enable that. Please add a page for this to User Manual. . -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AMQ-5191) Add information about Job Scheduler persistence to Configuring Broker Persistence book
[ https://issues.apache.org/jira/browse/AMQ-5191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated AMQ-5191: - Component/s: Job Scheduler JMX Issue Type: Improvement (was: Bug) Add information about Job Scheduler persistence to Configuring Broker Persistence book --- Key: AMQ-5191 URL: https://issues.apache.org/jira/browse/AMQ-5191 Project: ActiveMQ Issue Type: Improvement Components: Documentation Affects Versions: 5.9.0 Reporter: Burning Luffy Priority: Minor As the feature AMQ-3024 has been resolved in ActiveMQ 5.9.0. But we have no such a guide to describe how to enable that. Please add a page for this to User Manual. . -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (AMQ-5191) Add information about Job Scheduler persistence to Configuring Broker Persistence book
[ https://issues.apache.org/jira/browse/AMQ-5191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14002823#comment-14002823 ] Claus Ibsen commented on AMQ-5191: -- You are welcome to sketch up a draft for the documentation, and attach to this JIRA. Then we can get it add to the docs. Add information about Job Scheduler persistence to Configuring Broker Persistence book --- Key: AMQ-5191 URL: https://issues.apache.org/jira/browse/AMQ-5191 Project: ActiveMQ Issue Type: Improvement Components: Documentation Affects Versions: 5.9.0 Reporter: Burning Luffy Priority: Minor As the feature AMQ-3024 has been resolved in ActiveMQ 5.9.0. But we have no such a guide to describe how to enable that. Please add a page for this to User Manual. . -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (AMQ-5191) Add information about Job Scheduler persistence to Configuring Broker Persistence book
[ https://issues.apache.org/jira/browse/AMQ-5191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14002824#comment-14002824 ] Claus Ibsen commented on AMQ-5191: -- And btw where in the user manual do you intended this should be added? eg can you provide a link etc? Add information about Job Scheduler persistence to Configuring Broker Persistence book --- Key: AMQ-5191 URL: https://issues.apache.org/jira/browse/AMQ-5191 Project: ActiveMQ Issue Type: Improvement Components: Documentation Affects Versions: 5.9.0 Reporter: Burning Luffy Priority: Minor As the feature AMQ-3024 has been resolved in ActiveMQ 5.9.0. But we have no such a guide to describe how to enable that. Please add a page for this to User Manual. . -- This message was sent by Atlassian JIRA (v6.2#6252)
