[
https://issues.apache.org/activemq/browse/AMQ-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-1191.
-
Resolution: Fixed
resolved by adding patch to sqlserver specific database locker implementation.
reworked the resolution of AMQ-1191 to split out the locker implementation
for ms sqlserver. The current snapshot should now work with Oracle without
modification.
2009/7/24 Gary Tully gary.tu...@gmail.com
yea, exactly like that, where bean id=mydblocker is an instance of your
[
https://issues.apache.org/activemq/browse/AMQ-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-2324:
Fix Version/s: (was: 5.3.0)
5.4.0
This behavior won't be changed for 5.3 as we
[
https://issues.apache.org/activemq/browse/AMQ-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-2075.
-
Resolution: Fixed
Fix Version/s: 5.3.0
BrokerInfo on a new connection is dispatched async and
[
https://issues.apache.org/activemq/browse/AMQ-2158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reopened AMQ-2158:
-
think this has got to be left at debug level as limiting memory usage is a
typical use case and this warn
[
https://issues.apache.org/activemq/browse/AMQ-2158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-2158.
-
Resolution: Won't Fix
reverted the additional warn level logging as it is too verbose in a production
[
https://issues.apache.org/activemq/browse/AMQ-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kyle Anderson updated AMQ-2334:
---
Description:
Shared master/slave setup, described here
[
https://issues.apache.org/activemq/browse/AMQ-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=53022#action_53022
]
Gary Tully commented on AMQ-2334:
-
that seems like a reasonable (and smart) solution but it may
[
https://issues.apache.org/activemq/browse/AMQ-1846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Davies resolved AMQ-1846.
-
Resolution: Fixed
Fix Version/s: (was: 5.4.0)
5.3.0
Fixed by SVN
[
https://issues.apache.org/activemq/browse/AMQ-2333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=53024#action_53024
]
Marcus Malcom commented on AMQ-2333:
This just happened w/ only 142 messages in a queue
[
https://issues.apache.org/activemq/browse/AMQ-2333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Malcom updated AMQ-2333:
---
Summary: Active MQ performance issues when there are more than a 100
queue'd up messages (was:
[
https://issues.apache.org/activemq/browse/AMQ-2333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Malcom updated AMQ-2333:
---
Summary: Active MQ performance issues when there are more than 100 queue'd
up messages (was:
[
https://issues.apache.org/activemq/browse/AMQ-2333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Malcom updated AMQ-2333:
---
Priority: Critical (was: Major)
Active MQ performance issues when there are more than 100
13 matches
Mail list logo