[jira] [Updated] (AMQ-5695) KahaDB not cleaning up log files
[ https://issues.apache.org/jira/browse/AMQ-5695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef updated AMQ-5695: --- Assignee: (was: Arthur Naseef) > KahaDB not cleaning up log files > > > Key: AMQ-5695 > URL: https://issues.apache.org/jira/browse/AMQ-5695 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 5.11.1 >Reporter: Stefan Warten > > Since we have upgraded ActiveMQ from 5.10.0 to 5.11.1, KahaDB is not cleaning > up log files properly. It seems to keep all of them. It helped once to > restart the service and minutes later, ActiveMQ cleaned up 95% of log files > but mostly it is not cleaning up at all. > When partition was full, I stopped ActiveMQ, copied the KahaDB to another > host and started it with empty queues again. Then I forwarded all messages > from that other host back. Even when all messages were forwarded and all > queues were empty, the old KahaDB log files were not cleaned up. > I stopped ActiveMQ, removed db.data and db.redo to rebuild index which took > around 3h (350GB of log files) but still, the log files are not cleaned up. > [...] > 2015-03-30 18:21:55,532 | INFO | @13786:158508, 32130 entries recovered > .. | org.apache.activemq.store.kahadb.MessageDatabase | WrapperSimpleAppMain > 2015-03-30 18:22:02,090 | INFO | Recovery replayed 321378917 operations from > the journal in 9226.159 seconds. | > org.apache.activemq.store.kahadb.MessageDatabase | WrapperSimpleAppMain > 2015-03-30 18:22:02,402 | INFO | installing runtimeConfiguration plugin | > org.apache.activemq.plugin.RuntimeConfigurationPlugin | WrapperSimpleAppMain > 2015-03-30 18:22:04,576 | INFO | Apache ActiveMQ 5.11.1 > (prd-mig-02-sat.example.com, > ID:prd-mig-02-sat.example.com-26260-1427730492201-1:1) is starting | > org.apache.activemq.broker.BrokerService | WrapperSimpleAppMain > 2015-03-30 18:22:04,946 | INFO | pending local transactions: [] | > org.apache.activemq.store.kahadb.MultiKahaDBTransactionStore | > WrapperSimpleAppMain > 2015-03-30 18:22:08,488 | INFO | Configuration class path resource > [activemq.xml] | org.apache.activemq.plugin.RuntimeConfigurationBroker | > WrapperSimpleAppMain > 2015-03-30 18:22:12,198 | INFO | Listening for connections at: > nio://prd-mig-02-sat.example.com:61616?transport.reuseAddress=true | > org.apache.activemq.transport.TransportServerThreadSupport | > WrapperSimpleAppMain > 2015-03-30 18:22:12,199 | INFO | Connector openwire started | > org.apache.activemq.broker.TransportConnector | WrapperSimpleAppMain > 2015-03-30 18:22:12,232 | INFO | Listening for connections at: > stomp+nio://prd-mig-02-sat.example.com:61613?transport.closeAsync=false=true > | org.apache.activemq.transport.TransportServerThreadSupport | > WrapperSimpleAppMain > 2015-03-30 18:22:12,234 | INFO | Connector stomp started | > org.apache.activemq.broker.TransportConnector | WrapperSimpleAppMain > 2015-03-30 18:22:12,237 | INFO | Establishing network connection from > vm://prd-mig-02-sat.example.com?async=false=true to > tcp://172.42.15.40:61616 | > org.apache.activemq.network.DiscoveryNetworkConnector | WrapperSimpleAppMain > 2015-03-30 18:22:12,286 | INFO | Connector vm://prd-mig-02-sat.example.com > started | org.apache.activemq.broker.TransportConnector | WrapperSimpleAppMain > 2015-03-30 18:22:12,318 | INFO | Establishing network connection from > vm://prd-mig-02-sat.example.com?async=false=true to > tcp://172.42.15.39:61616 | > org.apache.activemq.network.DiscoveryNetworkConnector | WrapperSimpleAppMain > 2015-03-30 18:22:12,321 | INFO | Network Connector > DiscoveryNetworkConnector:FORWARDER:BrokerService[prd-mig-02-sat.example.com] > started | org.apache.activemq.network.NetworkConnector | WrapperSimpleAppMain > 2015-03-30 18:22:12,325 | INFO | Apache ActiveMQ 5.11.1 > (prd-mig-02-sat.example.com, > ID:prd-mig-02-sat.example.com-26260-1427730492201-1:1) started | > org.apache.activemq.broker.BrokerService | WrapperSimpleAppMain > 2015-03-30 18:22:12,326 | INFO | For help or more information please see: > http://activemq.apache.org | org.apache.activemq.broker.BrokerService | > WrapperSimpleAppMain > 2015-03-30 18:22:12,381 | INFO | Network connection between > vm://prd-mig-02-sat.example.com#0 and tcp:///172.42.15.40:61616@58567 > (prdvip-amq-01-sat.example.com) has been established. | > org.apache.activemq.network.DemandForwardingBridgeSupport | > triggerStartAsyncNetworkBridgeCreation: > remoteBroker=tcp:///172.42.15.40:61616@58567, localBroker= > vm://prd-mig-02-sat.example.com#0 > 2015-03-30 18:22:12,381 | INFO | Network connection between > vm://prd-mig-02-sat.example.com#2 and tcp:///172.42.15.39:61616@4523 > (prdvip-amq-02-sat.example.com) has been established. | > org.apache.activemq.network.DemandForwardingBridgeSupport | >
[jira] [Closed] (AMQ-6038) Amq 5.12.1 Failing to start with Oracle Data Store
[ https://issues.apache.org/jira/browse/AMQ-6038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon closed AMQ-6038. --- Resolution: Not A Problem > Amq 5.12.1 Failing to start with Oracle Data Store > -- > > Key: AMQ-6038 > URL: https://issues.apache.org/jira/browse/AMQ-6038 > Project: ActiveMQ > Issue Type: Bug > Environment: linux amq 5.12.1 (upgrading from 5.9.1) >Reporter: Elazar Rosenthal > > We have a working amq 5.9.1 with an oracle data store > when trying to upgrade to amq 5.12.1 we get the following error on startup > Is there a way I can fix this > Error: > 2015-11-10 11:07:54,050 | INFO | Refreshing > org.apache.activemq.xbean.XBeanBrokerFactory$1@5034c75a: startup date [Tue > Nov 10 11:07:54 EST 2015]; root of context hierarchy | > org.apache.activemq.xbean.XBeanBrokerFactory$1 | main > 2015-11-10 11:07:55,145 | WARN | Exception encountered during context > initialization - cancelling refresh attempt | > org.apache.activemq.xbean.XBeanBrokerFactory$1 | main > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'org.apache.activemq.xbean.XBeanBrokerService#0' defined in class > path resource [activemq.xml]: Cannot create inner bean '(inner > bean)#71809907' of type > [org.apache.activemq.store.jdbc.JDBCPersistenceAdapter] while setting bean > property 'persistenceAdapter'; nested exception is > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name '(inner bean)#71809907' defined in class path resource > [activemq.xml]: Cannot resolve reference to bean 'oracle-ds' while setting > bean property 'dataSource'; nested exception is > org.springframework.beans.factory.CannotLoadBeanClassException: Cannot find > class [org.apache.commons.dbcp.BasicDataSource] for bean with name > 'oracle-ds' defined in class path resource [activemq.xml]; nested exception > is java.lang.ClassNotFoundException: org.apache.commons.dbcp.BasicDataSource > at > org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:287)[spring-beans-3.2.11.RELEASE.jar:3.2.11.RELEASE] > > at > org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:129)[spring-beans-3.2.11.RELEASE.jar:3.2.11.RELEASE] > > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1419)[spring-beans-3.2.11.RELEASE.jar:3.2.11.RELEASE] > > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1160)[spring-beans-3.2.11.RELEASE.jar:3.2.11.RELEASE] > > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519)[spring-beans-3.2.11.RELEASE.jar:3.2.11.RELEASE] > > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458)[spring-beans-3.2.11.RELEASE.jar:3.2.11.RELEASE] > > at > org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:293)[spring-beans-3.2.11.RELEASE.jar:3.2.11.RELEASE] > > at > org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:223)[spring-beans-3.2.11.RELEASE.jar:3.2.11.RELEASE] > > at > org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:290)[spring-beans-3.2.11.RELEASE.jar:3.2.11.RELEASE] > > at > org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:191)[spring-beans-3.2.11.RELEASE.jar:3.2.11.RELEASE] > > at > org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:636)[spring-beans-3.2.11.RELEASE.jar:3.2.11.RELEASE] > > at > org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:934)[spring-context-3.2.11.RELEASE.jar:3.2.11.RELEASE] > > at > org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:479)[spring-context-3.2.11.RELEASE.jar:3.2.11.RELEASE] > > at > org.apache.xbean.spring.context.ResourceXmlApplicationContext.(ResourceXmlApplicationContext.java:64)[xbean-spring-3.18.jar:3.18] > > at > org.apache.xbean.spring.context.ResourceXmlApplicationContext.(ResourceXmlApplicationContext.java:52)[xbean-spring-3.18.jar:3.18] > > at >
[jira] [Commented] (AMQ-6027) Dynamic network demand should support Virtual Destination consumers
[
https://issues.apache.org/jira/browse/AMQ-6027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14998687#comment-14998687
]
ASF subversion and git services commented on AMQ-6027:
--
Commit 0c846cf8f6bcb999f98d499a717e922cbd04c6d2 in activemq's branch
refs/heads/master from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=0c846cf ]
https://issues.apache.org/jira/browse/AMQ-6027
Tweaking test case to apply virtual destination updates immediately
> Dynamic network demand should support Virtual Destination consumers
> ---
>
> Key: AMQ-6027
> URL: https://issues.apache.org/jira/browse/AMQ-6027
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Broker
>Affects Versions: 5.12.1
>Reporter: Christopher L. Shannon
>Assignee: Christopher L. Shannon
> Fix For: 5.13.0
>
>
> Currently the broker supports the notion of
> {{dynamicallyIncludedDestinations}}, where messages will only be sent across
> a network of brokers if there is a consumer that exists on that destination.
> This is good because it reduces the amount of traffic if there are no
> consumers, however it doesn't take into account any virtual/composite
> destinations that might exist or the consumers on those virtual/composite
> destinations. I'd like to be able to create demand and have messages flow
> based on Virtual Destination creation, either on start up or dynamically by
> the runtime configuration plugins, or by new consumers on a Virtual
> Destination.
> So for example, if there are two brokers networked and on Broker A messages
> are published to a topic, normally those messages only get passed to Broker B
> if there is a consumer on that topic when setting
> dynamicallyIncludedDestinations to true. I want to have an option so that a
> virtual destination setup on Broker B that forwards that topic to a queue
> will trigger messages to start flowing from Broker A to Broker B.
> Messages could start flowing either simply based on the existence of the
> Virtual Destination (likely used for the case of a topic forwarding to a
> queue, so messages accumulate on the queue) or based on there being a
> consumer on the forwarded destination (likely used for the case of a queue
> forwarding to a topic).
> I've done some prototyping work here already and my plan is to keep track of
> Virtual Destination consumers (configurable by the existence of the virtual
> destination or by the fact that a real consumer exists on it) and to create a
> new advisory topic where the broker can publish consumer advisories to. The
> prefix could be called something like:
> ActiveMQ.Advisory.VirtualDestination.Consumer.Topic
> ActiveMQ.Advisory.VirtualDestination.Consumer.Queue
> Advisory messages can be sent either when virtual destinations are
> created/destroyed (kind of a dummy consumer) or when a real consumer comes
> online for a virtual destination. Then a remote broker could optionally
> listen for those advisory messages and create or destroy a
> DemandSubscription, just like is currently done for normal consumers.
> The default behavior out of the box would be to keep this behavior turned
> off, but it could optionally be turned on through configuration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMQ-6038) Amq 5.12.1 Failing to start with Oracle Data Store
[ https://issues.apache.org/jira/browse/AMQ-6038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14998862#comment-14998862 ] Elazar Rosenthal commented on AMQ-6038: --- That seems to be the fix I will test further thanks > Amq 5.12.1 Failing to start with Oracle Data Store > -- > > Key: AMQ-6038 > URL: https://issues.apache.org/jira/browse/AMQ-6038 > Project: ActiveMQ > Issue Type: Bug > Environment: linux amq 5.12.1 (upgrading from 5.9.1) >Reporter: Elazar Rosenthal > > We have a working amq 5.9.1 with an oracle data store > when trying to upgrade to amq 5.12.1 we get the following error on startup > Is there a way I can fix this > Error: > 2015-11-10 11:07:54,050 | INFO | Refreshing > org.apache.activemq.xbean.XBeanBrokerFactory$1@5034c75a: startup date [Tue > Nov 10 11:07:54 EST 2015]; root of context hierarchy | > org.apache.activemq.xbean.XBeanBrokerFactory$1 | main > 2015-11-10 11:07:55,145 | WARN | Exception encountered during context > initialization - cancelling refresh attempt | > org.apache.activemq.xbean.XBeanBrokerFactory$1 | main > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'org.apache.activemq.xbean.XBeanBrokerService#0' defined in class > path resource [activemq.xml]: Cannot create inner bean '(inner > bean)#71809907' of type > [org.apache.activemq.store.jdbc.JDBCPersistenceAdapter] while setting bean > property 'persistenceAdapter'; nested exception is > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name '(inner bean)#71809907' defined in class path resource > [activemq.xml]: Cannot resolve reference to bean 'oracle-ds' while setting > bean property 'dataSource'; nested exception is > org.springframework.beans.factory.CannotLoadBeanClassException: Cannot find > class [org.apache.commons.dbcp.BasicDataSource] for bean with name > 'oracle-ds' defined in class path resource [activemq.xml]; nested exception > is java.lang.ClassNotFoundException: org.apache.commons.dbcp.BasicDataSource > at > org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:287)[spring-beans-3.2.11.RELEASE.jar:3.2.11.RELEASE] > > at > org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:129)[spring-beans-3.2.11.RELEASE.jar:3.2.11.RELEASE] > > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1419)[spring-beans-3.2.11.RELEASE.jar:3.2.11.RELEASE] > > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1160)[spring-beans-3.2.11.RELEASE.jar:3.2.11.RELEASE] > > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519)[spring-beans-3.2.11.RELEASE.jar:3.2.11.RELEASE] > > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458)[spring-beans-3.2.11.RELEASE.jar:3.2.11.RELEASE] > > at > org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:293)[spring-beans-3.2.11.RELEASE.jar:3.2.11.RELEASE] > > at > org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:223)[spring-beans-3.2.11.RELEASE.jar:3.2.11.RELEASE] > > at > org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:290)[spring-beans-3.2.11.RELEASE.jar:3.2.11.RELEASE] > > at > org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:191)[spring-beans-3.2.11.RELEASE.jar:3.2.11.RELEASE] > > at > org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:636)[spring-beans-3.2.11.RELEASE.jar:3.2.11.RELEASE] > > at > org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:934)[spring-context-3.2.11.RELEASE.jar:3.2.11.RELEASE] > > at > org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:479)[spring-context-3.2.11.RELEASE.jar:3.2.11.RELEASE] > > at > org.apache.xbean.spring.context.ResourceXmlApplicationContext.(ResourceXmlApplicationContext.java:64)[xbean-spring-3.18.jar:3.18] > > at >
[jira] [Created] (AMQ-6039) KahaDB data log archiving does not work accross different physical file systems
Timothy Bish created AMQ-6039: - Summary: KahaDB data log archiving does not work accross different physical file systems Key: AMQ-6039 URL: https://issues.apache.org/jira/browse/AMQ-6039 Project: ActiveMQ Issue Type: Bug Components: KahaDB Affects Versions: 5.11.3, 5.12.1, 5.12.0, 5.11.2, 5.11.1 Reporter: Timothy Bish Assignee: Timothy Bish Fix For: 5.13.0 The utility class IOHelper uses a trivial rename operation in its move method for files being moved to another directory. This operation can fail when the target of the move is on a different file system. The method needs to fall back to a deep copy / remove style operation when the rename attempt fails in order to ensure the file can move. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMQ-6038) Amq 5.12.1 Failing to start with Oracle Data Store
[ https://issues.apache.org/jira/browse/AMQ-6038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14998843#comment-14998843 ] Christopher L. Shannon commented on AMQ-6038: - This probably related to AMQ-5958. Commons Pool2 is now used. Try switching org.apache.commons.dbcp.BasicDataSource to org.apache.commons.dbcp2.BasicDataSource The documentation on the website needs to be updated to reflect this change. > Amq 5.12.1 Failing to start with Oracle Data Store > -- > > Key: AMQ-6038 > URL: https://issues.apache.org/jira/browse/AMQ-6038 > Project: ActiveMQ > Issue Type: Bug > Environment: linux amq 5.12.1 (upgrading from 5.9.1) >Reporter: Elazar Rosenthal > > We have a working amq 5.9.1 with an oracle data store > when trying to upgrade to amq 5.12.1 we get the following error on startup > Is there a way I can fix this > Error: > 2015-11-10 11:07:54,050 | INFO | Refreshing > org.apache.activemq.xbean.XBeanBrokerFactory$1@5034c75a: startup date [Tue > Nov 10 11:07:54 EST 2015]; root of context hierarchy | > org.apache.activemq.xbean.XBeanBrokerFactory$1 | main > 2015-11-10 11:07:55,145 | WARN | Exception encountered during context > initialization - cancelling refresh attempt | > org.apache.activemq.xbean.XBeanBrokerFactory$1 | main > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'org.apache.activemq.xbean.XBeanBrokerService#0' defined in class > path resource [activemq.xml]: Cannot create inner bean '(inner > bean)#71809907' of type > [org.apache.activemq.store.jdbc.JDBCPersistenceAdapter] while setting bean > property 'persistenceAdapter'; nested exception is > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name '(inner bean)#71809907' defined in class path resource > [activemq.xml]: Cannot resolve reference to bean 'oracle-ds' while setting > bean property 'dataSource'; nested exception is > org.springframework.beans.factory.CannotLoadBeanClassException: Cannot find > class [org.apache.commons.dbcp.BasicDataSource] for bean with name > 'oracle-ds' defined in class path resource [activemq.xml]; nested exception > is java.lang.ClassNotFoundException: org.apache.commons.dbcp.BasicDataSource > at > org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:287)[spring-beans-3.2.11.RELEASE.jar:3.2.11.RELEASE] > > at > org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:129)[spring-beans-3.2.11.RELEASE.jar:3.2.11.RELEASE] > > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1419)[spring-beans-3.2.11.RELEASE.jar:3.2.11.RELEASE] > > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1160)[spring-beans-3.2.11.RELEASE.jar:3.2.11.RELEASE] > > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519)[spring-beans-3.2.11.RELEASE.jar:3.2.11.RELEASE] > > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458)[spring-beans-3.2.11.RELEASE.jar:3.2.11.RELEASE] > > at > org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:293)[spring-beans-3.2.11.RELEASE.jar:3.2.11.RELEASE] > > at > org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:223)[spring-beans-3.2.11.RELEASE.jar:3.2.11.RELEASE] > > at > org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:290)[spring-beans-3.2.11.RELEASE.jar:3.2.11.RELEASE] > > at > org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:191)[spring-beans-3.2.11.RELEASE.jar:3.2.11.RELEASE] > > at > org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:636)[spring-beans-3.2.11.RELEASE.jar:3.2.11.RELEASE] > > at > org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:934)[spring-context-3.2.11.RELEASE.jar:3.2.11.RELEASE] > > at > org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:479)[spring-context-3.2.11.RELEASE.jar:3.2.11.RELEASE] > > at >
[jira] [Resolved] (AMQ-6039) KahaDB data log archiving does not work accross different physical file systems
[ https://issues.apache.org/jira/browse/AMQ-6039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-6039. --- Resolution: Fixed > KahaDB data log archiving does not work accross different physical file > systems > --- > > Key: AMQ-6039 > URL: https://issues.apache.org/jira/browse/AMQ-6039 > Project: ActiveMQ > Issue Type: Bug > Components: KahaDB >Affects Versions: 5.11.1, 5.11.2, 5.12.0, 5.12.1, 5.11.3 >Reporter: Timothy Bish >Assignee: Timothy Bish > Fix For: 5.13.0 > > > The utility class IOHelper uses a trivial rename operation in its move method > for files being moved to another directory. This operation can fail when the > target of the move is on a different file system. The method needs to fall > back to a deep copy / remove style operation when the rename attempt fails in > order to ensure the file can move. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (AMQ-5408) jaasDualAuthenticationPlugin with client authentication not working for networkConnector
[ https://issues.apache.org/jira/browse/AMQ-5408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-5408. - Resolution: Duplicate Appears to duplicate AMQ-5943, test with a current nightly and if the problem remains then please reopen. > jaasDualAuthenticationPlugin with client authentication not working for > networkConnector > > > Key: AMQ-5408 > URL: https://issues.apache.org/jira/browse/AMQ-5408 > Project: ActiveMQ > Issue Type: Bug > Components: Transport >Affects Versions: 5.10.0 > Environment: Windows, Java 1.7 >Reporter: Henrik Karlsson > Attachments: conf.zip > > > When using jaasDualAuthentication with username/password for tcp connections > and certification authentication for ssl, this works just fine then > connection as a client. But when I try to setup a network connector over ssl > with certification authentication it fails to connect with this error: > java.lang.SecurityException: User name [null] or password is invalid. > I also tried with nio+ssl with the same result > If I change to jaasCertificateAuthentication it works for ssl connections but > the non ssl fails (as expected) > When I use nio+ssl with jaasCertificateAuthentication this also fails with > this error: > java.lang.SecurityException: Unable to authenticate transport without SSL > certificate. > But after failing 3 times it finally connects successfully on the 4:th > attempt. > So it seems that jaasDualAuthentication doesn't work with Certificate > Authentication. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMQ-6027) Dynamic network demand should support Virtual Destination consumers
[
https://issues.apache.org/jira/browse/AMQ-6027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14999165#comment-14999165
]
Christopher L. Shannon commented on AMQ-6027:
-
I added a section on this feature to
http://activemq.apache.org/networks-of-brokers.html. It's under the subtitle
{{Dynamic networks and Virtual Destinations}}. It still needs some polishing
and some more detail but it's a good start.
> Dynamic network demand should support Virtual Destination consumers
> ---
>
> Key: AMQ-6027
> URL: https://issues.apache.org/jira/browse/AMQ-6027
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Broker
>Affects Versions: 5.12.1
>Reporter: Christopher L. Shannon
>Assignee: Christopher L. Shannon
> Fix For: 5.13.0
>
>
> Currently the broker supports the notion of
> {{dynamicallyIncludedDestinations}}, where messages will only be sent across
> a network of brokers if there is a consumer that exists on that destination.
> This is good because it reduces the amount of traffic if there are no
> consumers, however it doesn't take into account any virtual/composite
> destinations that might exist or the consumers on those virtual/composite
> destinations. I'd like to be able to create demand and have messages flow
> based on Virtual Destination creation, either on start up or dynamically by
> the runtime configuration plugins, or by new consumers on a Virtual
> Destination.
> So for example, if there are two brokers networked and on Broker A messages
> are published to a topic, normally those messages only get passed to Broker B
> if there is a consumer on that topic when setting
> dynamicallyIncludedDestinations to true. I want to have an option so that a
> virtual destination setup on Broker B that forwards that topic to a queue
> will trigger messages to start flowing from Broker A to Broker B.
> Messages could start flowing either simply based on the existence of the
> Virtual Destination (likely used for the case of a topic forwarding to a
> queue, so messages accumulate on the queue) or based on there being a
> consumer on the forwarded destination (likely used for the case of a queue
> forwarding to a topic).
> I've done some prototyping work here already and my plan is to keep track of
> Virtual Destination consumers (configurable by the existence of the virtual
> destination or by the fact that a real consumer exists on it) and to create a
> new advisory topic where the broker can publish consumer advisories to. The
> prefix could be called something like:
> ActiveMQ.Advisory.VirtualDestination.Consumer.Topic
> ActiveMQ.Advisory.VirtualDestination.Consumer.Queue
> Advisory messages can be sent either when virtual destinations are
> created/destroyed (kind of a dummy consumer) or when a real consumer comes
> online for a virtual destination. Then a remote broker could optionally
> listen for those advisory messages and create or destroy a
> DemandSubscription, just like is currently done for normal consumers.
> The default behavior out of the box would be to keep this behavior turned
> off, but it could optionally be turned on through configuration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMQ-6027) Dynamic network demand should support Virtual Destination consumers
[
https://issues.apache.org/jira/browse/AMQ-6027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14999110#comment-14999110
]
ASF subversion and git services commented on AMQ-6027:
--
Commit 3ef6a9f7693972c7001f82375b684998ae3f46b9 in activemq's branch
refs/heads/master from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=3ef6a9f ]
https://issues.apache.org/jira/browse/AMQ-6027
Fixing unit test to pass assertion
> Dynamic network demand should support Virtual Destination consumers
> ---
>
> Key: AMQ-6027
> URL: https://issues.apache.org/jira/browse/AMQ-6027
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Broker
>Affects Versions: 5.12.1
>Reporter: Christopher L. Shannon
>Assignee: Christopher L. Shannon
> Fix For: 5.13.0
>
>
> Currently the broker supports the notion of
> {{dynamicallyIncludedDestinations}}, where messages will only be sent across
> a network of brokers if there is a consumer that exists on that destination.
> This is good because it reduces the amount of traffic if there are no
> consumers, however it doesn't take into account any virtual/composite
> destinations that might exist or the consumers on those virtual/composite
> destinations. I'd like to be able to create demand and have messages flow
> based on Virtual Destination creation, either on start up or dynamically by
> the runtime configuration plugins, or by new consumers on a Virtual
> Destination.
> So for example, if there are two brokers networked and on Broker A messages
> are published to a topic, normally those messages only get passed to Broker B
> if there is a consumer on that topic when setting
> dynamicallyIncludedDestinations to true. I want to have an option so that a
> virtual destination setup on Broker B that forwards that topic to a queue
> will trigger messages to start flowing from Broker A to Broker B.
> Messages could start flowing either simply based on the existence of the
> Virtual Destination (likely used for the case of a topic forwarding to a
> queue, so messages accumulate on the queue) or based on there being a
> consumer on the forwarded destination (likely used for the case of a queue
> forwarding to a topic).
> I've done some prototyping work here already and my plan is to keep track of
> Virtual Destination consumers (configurable by the existence of the virtual
> destination or by the fact that a real consumer exists on it) and to create a
> new advisory topic where the broker can publish consumer advisories to. The
> prefix could be called something like:
> ActiveMQ.Advisory.VirtualDestination.Consumer.Topic
> ActiveMQ.Advisory.VirtualDestination.Consumer.Queue
> Advisory messages can be sent either when virtual destinations are
> created/destroyed (kind of a dummy consumer) or when a real consumer comes
> online for a virtual destination. Then a remote broker could optionally
> listen for those advisory messages and create or destroy a
> DemandSubscription, just like is currently done for normal consumers.
> The default behavior out of the box would be to keep this behavior turned
> off, but it could optionally be turned on through configuration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMQ-5695) KahaDB not cleaning up log files
[ https://issues.apache.org/jira/browse/AMQ-5695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef updated AMQ-5695: --- Priority: Blocker (was: Major) > KahaDB not cleaning up log files > > > Key: AMQ-5695 > URL: https://issues.apache.org/jira/browse/AMQ-5695 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 5.11.1 >Reporter: Stefan Warten >Priority: Blocker > > Since we have upgraded ActiveMQ from 5.10.0 to 5.11.1, KahaDB is not cleaning > up log files properly. It seems to keep all of them. It helped once to > restart the service and minutes later, ActiveMQ cleaned up 95% of log files > but mostly it is not cleaning up at all. > When partition was full, I stopped ActiveMQ, copied the KahaDB to another > host and started it with empty queues again. Then I forwarded all messages > from that other host back. Even when all messages were forwarded and all > queues were empty, the old KahaDB log files were not cleaned up. > I stopped ActiveMQ, removed db.data and db.redo to rebuild index which took > around 3h (350GB of log files) but still, the log files are not cleaned up. > [...] > 2015-03-30 18:21:55,532 | INFO | @13786:158508, 32130 entries recovered > .. | org.apache.activemq.store.kahadb.MessageDatabase | WrapperSimpleAppMain > 2015-03-30 18:22:02,090 | INFO | Recovery replayed 321378917 operations from > the journal in 9226.159 seconds. | > org.apache.activemq.store.kahadb.MessageDatabase | WrapperSimpleAppMain > 2015-03-30 18:22:02,402 | INFO | installing runtimeConfiguration plugin | > org.apache.activemq.plugin.RuntimeConfigurationPlugin | WrapperSimpleAppMain > 2015-03-30 18:22:04,576 | INFO | Apache ActiveMQ 5.11.1 > (prd-mig-02-sat.example.com, > ID:prd-mig-02-sat.example.com-26260-1427730492201-1:1) is starting | > org.apache.activemq.broker.BrokerService | WrapperSimpleAppMain > 2015-03-30 18:22:04,946 | INFO | pending local transactions: [] | > org.apache.activemq.store.kahadb.MultiKahaDBTransactionStore | > WrapperSimpleAppMain > 2015-03-30 18:22:08,488 | INFO | Configuration class path resource > [activemq.xml] | org.apache.activemq.plugin.RuntimeConfigurationBroker | > WrapperSimpleAppMain > 2015-03-30 18:22:12,198 | INFO | Listening for connections at: > nio://prd-mig-02-sat.example.com:61616?transport.reuseAddress=true | > org.apache.activemq.transport.TransportServerThreadSupport | > WrapperSimpleAppMain > 2015-03-30 18:22:12,199 | INFO | Connector openwire started | > org.apache.activemq.broker.TransportConnector | WrapperSimpleAppMain > 2015-03-30 18:22:12,232 | INFO | Listening for connections at: > stomp+nio://prd-mig-02-sat.example.com:61613?transport.closeAsync=false=true > | org.apache.activemq.transport.TransportServerThreadSupport | > WrapperSimpleAppMain > 2015-03-30 18:22:12,234 | INFO | Connector stomp started | > org.apache.activemq.broker.TransportConnector | WrapperSimpleAppMain > 2015-03-30 18:22:12,237 | INFO | Establishing network connection from > vm://prd-mig-02-sat.example.com?async=false=true to > tcp://172.42.15.40:61616 | > org.apache.activemq.network.DiscoveryNetworkConnector | WrapperSimpleAppMain > 2015-03-30 18:22:12,286 | INFO | Connector vm://prd-mig-02-sat.example.com > started | org.apache.activemq.broker.TransportConnector | WrapperSimpleAppMain > 2015-03-30 18:22:12,318 | INFO | Establishing network connection from > vm://prd-mig-02-sat.example.com?async=false=true to > tcp://172.42.15.39:61616 | > org.apache.activemq.network.DiscoveryNetworkConnector | WrapperSimpleAppMain > 2015-03-30 18:22:12,321 | INFO | Network Connector > DiscoveryNetworkConnector:FORWARDER:BrokerService[prd-mig-02-sat.example.com] > started | org.apache.activemq.network.NetworkConnector | WrapperSimpleAppMain > 2015-03-30 18:22:12,325 | INFO | Apache ActiveMQ 5.11.1 > (prd-mig-02-sat.example.com, > ID:prd-mig-02-sat.example.com-26260-1427730492201-1:1) started | > org.apache.activemq.broker.BrokerService | WrapperSimpleAppMain > 2015-03-30 18:22:12,326 | INFO | For help or more information please see: > http://activemq.apache.org | org.apache.activemq.broker.BrokerService | > WrapperSimpleAppMain > 2015-03-30 18:22:12,381 | INFO | Network connection between > vm://prd-mig-02-sat.example.com#0 and tcp:///172.42.15.40:61616@58567 > (prdvip-amq-01-sat.example.com) has been established. | > org.apache.activemq.network.DemandForwardingBridgeSupport | > triggerStartAsyncNetworkBridgeCreation: > remoteBroker=tcp:///172.42.15.40:61616@58567, localBroker= > vm://prd-mig-02-sat.example.com#0 > 2015-03-30 18:22:12,381 | INFO | Network connection between > vm://prd-mig-02-sat.example.com#2 and tcp:///172.42.15.39:61616@4523 > (prdvip-amq-02-sat.example.com) has been established. | >
[jira] [Updated] (ARTEMIS-302) Improve resilience of XA Transactions during failover and reconnection
[ https://issues.apache.org/jira/browse/ARTEMIS-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-302: Summary: Improve resilience of XA Transactions during failover and reconnection (was: Improve resilience of XA Transactions to failures) > Improve resilience of XA Transactions during failover and reconnection > -- > > Key: ARTEMIS-302 > URL: https://issues.apache.org/jira/browse/ARTEMIS-302 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: clebert suconic >Assignee: clebert suconic > Fix For: 1.2.0 > > > I have debugged a production case recently where I had to add Logs. > I ended up finding ARTEMIS-301 in the process, and I also added some extra > checks to avoid some scenarios that could eventually happen in a production > system during reconnections and failover. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMQ-6000) Pause/resume feature of ActiveMQ not resuming properly
[ https://issues.apache.org/jira/browse/AMQ-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14999315#comment-14999315 ] ASF subversion and git services commented on AMQ-6000: -- Commit 078a101cf735ae23ebf96b3bbe3f53003dccc0c7 in activemq's branch refs/heads/master from [~tabish121] [ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=078a101 ] https://issues.apache.org/jira/browse/AMQ-6000 Fix and test, wakeup queue dispatch when resume is called. > Pause/resume feature of ActiveMQ not resuming properly > -- > > Key: AMQ-6000 > URL: https://issues.apache.org/jira/browse/AMQ-6000 > Project: ActiveMQ > Issue Type: Bug > Components: Broker, JMX >Affects Versions: 5.12.0 >Reporter: M Rahimi > Labels: features > Fix For: 5.13.0 > > > The problem is that, when you *resume* the message delivery, > # If there is a message entering the queue: the broker will immediately send > the pending messages to the consumer which is totally OK. > # But if no message _enters_ the queue: the pending messages in the queue > will not be sent to the consumers until the expiration checking is performed > on the queue (which by default is 30 seconds and can be controlled by the > _expireMessagesPeriod_ attribute) and non-expired messages will be sent to > the consumers afterwards. > Obviously we can change the _expireMessagesPeriod_ to limit this delay, but > when you need a milisec precision, performing the expiration check every > milisec will not make sense. > How is it possible to force the queue to start sending messages immediately > after resumption? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMQ-6000) Pause/resume feature of ActiveMQ not resuming properly
[ https://issues.apache.org/jira/browse/AMQ-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-6000. --- Resolution: Fixed Assignee: Timothy Bish Fix Version/s: 5.13.0 > Pause/resume feature of ActiveMQ not resuming properly > -- > > Key: AMQ-6000 > URL: https://issues.apache.org/jira/browse/AMQ-6000 > Project: ActiveMQ > Issue Type: Bug > Components: Broker, JMX >Affects Versions: 5.12.0 >Reporter: M Rahimi >Assignee: Timothy Bish > Labels: features > Fix For: 5.13.0 > > > The problem is that, when you *resume* the message delivery, > # If there is a message entering the queue: the broker will immediately send > the pending messages to the consumer which is totally OK. > # But if no message _enters_ the queue: the pending messages in the queue > will not be sent to the consumers until the expiration checking is performed > on the queue (which by default is 30 seconds and can be controlled by the > _expireMessagesPeriod_ attribute) and non-expired messages will be sent to > the consumers afterwards. > Obviously we can change the _expireMessagesPeriod_ to limit this delay, but > when you need a milisec precision, performing the expiration check every > milisec will not make sense. > How is it possible to force the queue to start sending messages immediately > after resumption? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMQ-6037) AMQP: Add support for sending scheduled message using message annotations
[ https://issues.apache.org/jira/browse/AMQ-6037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14999557#comment-14999557 ] ASF subversion and git services commented on AMQ-6037: -- Commit 5d353e241b0ba76ad1a0b42ef5c7a2ae54106860 in activemq's branch refs/heads/master from [~tabish121] [ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=5d353e2 ] https://issues.apache.org/jira/browse/AMQ-6037 Add support for amqp style variants of the ActiveMQ job scheduler options set in message annotations. > AMQP: Add support for sending scheduled message using message annotations > - > > Key: AMQ-6037 > URL: https://issues.apache.org/jira/browse/AMQ-6037 > Project: ActiveMQ > Issue Type: New Feature > Components: AMQP >Affects Versions: 5.12.0, 5.12.1 >Reporter: Timothy Bish >Assignee: Timothy Bish > Fix For: 5.13.0 > > > Add support for reading scheduled message instructions from specific Message > Annotations that are mapped into values that work with the built-in broker > scheduler feature. > ||Annotation Name||Description|| > |x-opt-delivery-time|Analogous to the JMS 2.0 delivery time message property. > Value is set in milliseconds > since the Unix Epoch.| > |x-opt-delivery-delay|Time in Milliseconds to wait before dispatching the > message.| > |x-opt-delivery-repeat|Number of time to reschedule a message sent with a > fixed delay.| > |x-opt-delivery-period|The time in ms to wait between successive repeats of a > scheduled message.| > |x-opt-delivery-cron|A CronTab entry that controls how a message is > scheduled.| -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMQ-6037) AMQP: Add support for sending scheduled message using message annotations
[ https://issues.apache.org/jira/browse/AMQ-6037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-6037: -- Description: Add support for reading scheduled message instructions from specific Message Annotations that are mapped into values that work with the built-in broker scheduler feature. ||Annotation Name||Description|| |x-opt-delivery-time|Analogous to the JMS 2.0 delivery time message property. Value is set in milliseconds since the Unix Epoch.| |x-opt-delivery-delay|Time in Milliseconds to wait before dispatching the message.| |x-opt-delivery-repeat|Number of time to reschedule a message sent with a fixed delay.| |x-opt-delivery-period|The time in ms to wait between successive repeats of a scheduled message.| |x-opt-delivery-cron|A CronTab entry that controls how a message is scheduled.| was: Add support for reading scheduled message instructions from specific Message Annotations that are mapped into values that work with the built-in broker scheduler feature. ||Annotation Name||Description|| |x-opt-delivery-time|Analogous to the JMS 2.0 delivery time message property. Value is set in milliseconds since the Unix Epoch.| > AMQP: Add support for sending scheduled message using message annotations > - > > Key: AMQ-6037 > URL: https://issues.apache.org/jira/browse/AMQ-6037 > Project: ActiveMQ > Issue Type: New Feature > Components: AMQP >Affects Versions: 5.12.0, 5.12.1 >Reporter: Timothy Bish >Assignee: Timothy Bish > Fix For: 5.13.0 > > > Add support for reading scheduled message instructions from specific Message > Annotations that are mapped into values that work with the built-in broker > scheduler feature. > ||Annotation Name||Description|| > |x-opt-delivery-time|Analogous to the JMS 2.0 delivery time message property. > Value is set in milliseconds > since the Unix Epoch.| > |x-opt-delivery-delay|Time in Milliseconds to wait before dispatching the > message.| > |x-opt-delivery-repeat|Number of time to reschedule a message sent with a > fixed delay.| > |x-opt-delivery-period|The time in ms to wait between successive repeats of a > scheduled message.| > |x-opt-delivery-cron|A CronTab entry that controls how a message is > scheduled.| -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMQ-6040) The amq down every week
Jim created AMQ-6040:
Summary: The amq down every week
Key: AMQ-6040
URL: https://issues.apache.org/jira/browse/AMQ-6040
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 5.11.1
Environment: OS：linux
AMQ version：5.1.11
JDK Version：1.7
Reporter: Jim
Hello，i have 3 servers with amq ，and they organize a HA cluster with
zookeeper。
but almost every day，i get this log：
2015-11-03 21:59:58,921 | WARN | Unexpected session error:
java.net.ConnectException: connect refuse |
org.apache.activemq.leveldb.replicated.SlaveLevelDBStore |
hawtdispatch-DEFAULT-1
and the cluster will weekly outages without any log。
Who can help me solve this problem？
My configuration(activemq.xml) is as follows
http://www.springframework.org/schema/beans;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
http://activemq.apache.org/schema/core
http://activemq.apache.org/schema/core/activemq-core.xsd;>
file:${activemq.conf}/credentials.properties
http://activemq.apache.org/schema/core;
brokerName="cmfBroker" dataDirectory="${activemq.data}">
http://www.springframework.org/schema/beans;
class="org.apache.activemq.hooks.SpringContextHook" />
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMQ-6040) The amq cluster outages every week
[
https://issues.apache.org/jira/browse/AMQ-6040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim updated AMQ-6040:
-
Summary: The amq cluster outages every week (was: The amq down every week)
> The amq cluster outages every week
> ---
>
> Key: AMQ-6040
> URL: https://issues.apache.org/jira/browse/AMQ-6040
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.11.1
> Environment: OS：linux
> AMQ version：5.1.11
> JDK Version：1.7
>Reporter: Jim
>
> Hello，i have 3 servers with amq ，and they organize a HA cluster with
> zookeeper。
> but almost every day，i get this log：
> 2015-11-03 21:59:58,921 | WARN | Unexpected session error:
> java.net.ConnectException: connect refuse |
> org.apache.activemq.leveldb.replicated.SlaveLevelDBStore |
> hawtdispatch-DEFAULT-1
> and the cluster will weekly outages without any log。
> Who can help me solve this problem？
> My configuration(activemq.xml) is as follows
>
>
>xmlns="http://www.springframework.org/schema/beans;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd
> http://activemq.apache.org/schema/core
> http://activemq.apache.org/schema/core/activemq-core.xsd;>
>
> class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
>
> file:${activemq.conf}/credentials.properties
>
>
>
>lazy-init="false" scope="singleton"
> init-method="start" destroy-method="stop">
>
>
> http://activemq.apache.org/schema/core;
> brokerName="cmfBroker" dataDirectory="${activemq.data}">
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>directory="${activemq.data}/leveldb"
> replicas="3"
> bind="tcp://0.0.0.0:0"
> zkAddress="192.168.8.155:2181,192.168.8.156:2181,192.168.8.157:2181"
> zkPassword=""
> zkPath="/activemq/leveldb-stores"
> sync="local_disk"
> hostname="192.168.8.155"/>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> uri="tcp://0.0.0.0:61616?maximumConnections=1000wireFormat.maxFrameSize=104857600"/>
> uri="amqp://0.0.0.0:5672?maximumConnections=1000wireFormat.maxFrameSize=104857600"/>
> uri="stomp://0.0.0.0:61613?maximumConnections=1000wireFormat.maxFrameSize=104857600"/>
> uri="mqtt://0.0.0.0:1883?maximumConnections=1000wireFormat.maxFrameSize=104857600"/>
> uri="ws://0.0.0.0:61614?maximumConnections=1000wireFormat.maxFrameSize=104857600"/>
>
>
>
> http://www.springframework.org/schema/beans;
> class="org.apache.activemq.hooks.SpringContextHook" />
>
>
>
>
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMQ-6041) Activemq have a deadLock in running for a long time
lee created AMQ-6041: Summary: Activemq have a deadLock in running for a long time Key: AMQ-6041 URL: https://issues.apache.org/jira/browse/AMQ-6041 Project: ActiveMQ Issue Type: Bug Components: activemq-leveldb-store Affects Versions: 5.11.0 Environment: development and product Reporter: lee my activemq is a Cluster that has three activemq single instance and using replicated stored levelDB . when the cluster is running for a long time ( a few days),this situation is that JVM Old Generation is filled，and eden and one of survivor 0 or 1 is filled., but not privider service and all of port include 61616 is dead when producer is calling. this time three instance's process is running , about half an hour , zookeeper is selected and another instance start all port and providers services i see this stack trace in jstack, the content is follow: at java.lang.Thread.run(Thread.java:745) "qtp2054301670-138 Selector0" prio=10 tid=0x7f5e3cccd800 nid=0xffb runnable [0x7f5db3cfb000] java.lang.Thread.State: RUNNABLE at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method) at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:269) at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:79) at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:87) - locked <0xb5628fe0> (a sun.nio.ch.Util$2) - locked <0xb5628fc8> (a java.util.Collections$UnmodifiableSet) - locked <0xb55fb490> (a sun.nio.ch.EPollSelectorImpl) at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:98) at org.eclipse.jetty.io.nio.SelectorManager$SelectSet.doSelect(SelectorManager.java:569) at org.eclipse.jetty.io.nio.SelectorManager$1.run(SelectorManager.java:290) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543) at java.lang.Thread.run(Thread.java:745) "HashSessionScavenger-2" daemon prio=10 tid=0x7f5e3cc5a800 nid=0xff7 in Object.wait() [0x7f5e08156000] java.lang.Thread.State: TIMED_WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0xb5621138> (a java.util.TaskQueue) at java.util.TimerThread.mainLoop(Timer.java:552) - locked <0xb5621138> (a java.util.TaskQueue) at java.util.TimerThread.run(Timer.java:505) "HashSessionScavenger-1" daemon prio=10 tid=0x7f5e3cc63000 nid=0xff6 in Object.wait() [0x7f5e08257000] java.lang.Thread.State: TIMED_WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0xb5621168> (a java.util.TaskQueue) at java.util.TimerThread.mainLoop(Timer.java:552) - locked <0xb5621168> (a java.util.TaskQueue) at java.util.TimerThread.run(Timer.java:505) "HashSessionScavenger-0" daemon prio=10 tid=0x7f5e3cbac000 nid=0xff5 in Object.wait() [0x7f5e08358000] java.lang.Thread.State: TIMED_WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0xb5621198> (a java.util.TaskQueue) at java.util.TimerThread.mainLoop(Timer.java:552) - locked <0xb5621198> (a java.util.TaskQueue) at java.util.TimerThread.run(Timer.java:505) "qtp819231520-130" prio=10 tid=0x7f5e3cb2a800 nid=0xff1 waiting on condition [0x7f5e08459000] java.lang.Thread.State: TIMED_WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for <0xb563b640> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226) at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2082) at org.eclipse.jetty.util.BlockingArrayQueue.poll(BlockingArrayQueue.java:342) at org.eclipse.jetty.util.thread.QueuedThreadPool.idleJobPoll(QueuedThreadPool.java:526) at org.eclipse.jetty.util.thread.QueuedThreadPool.access$600(QueuedThreadPool.java:44) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:572) at java.lang.Thread.run(Thread.java:745) "qtp819231520-129" prio=10 tid=0x7f5e3cb28800 nid=0xff0 waiting on condition [0x7f5e0855a000] java.lang.Thread.State: TIMED_WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for <0xb563b640> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226) at
