[jira] Commented: (AMQ-688) Avoid blocking producers

[ https://issues.apache.org/activemq/browse/AMQ-688?page=comments#action_36391 ] james strachan commented on AMQ-688: BTW Christopher, feel free to start a discussion on the dev list on how we can start patching the code to implement what you need;

[jira] Created: (AMQ-757) MapMessage to support nested Map objects to create a typesafe hierarchial message such as used on RV etc

MapMessage to support nested Map objects to create a typesafe hierarchial message such as used on RV etc Key: AMQ-757 URL: https://issues.apache.org/activemq/browse/AMQ-757

[jira] Resolved: (AMQ-747) Redelivery backoff should add random delay for collision avoidance

[ https://issues.apache.org/activemq/browse/AMQ-747?page=all ] james strachan resolved AMQ-747: Resolution: Fixed Patch applied - many thanks! (we just missed 4.0.1 but will try release 4.1 real soon). Redelivery backoff should add random

[jira] Resolved: (AMQ-753) exposing the client IP Address

[ https://issues.apache.org/activemq/browse/AMQ-753?page=all ] james strachan resolved AMQ-753: Fix Version: 4.1 Resolution: Fixed Patch applied - many thanks! exposing the client IP Address -- Key:

[jira] Resolved: (AMQ-663) JMX management info about subscriptions is incomplete

[ https://issues.apache.org/activemq/browse/AMQ-663?page=all ] james strachan resolved AMQ-663: Resolution: Fixed fixed in SVN HEAD JMX management info about subscriptions is incomplete -

[jira] Resolved: (AMQ-757) MapMessage to support nested Map objects to create a typesafe hierarchial message such as used on RV etc

[ https://issues.apache.org/activemq/browse/AMQ-757?page=all ] james strachan resolved AMQ-757: Resolution: Fixed Supports nested Map and List types (of arbitrary nesting depth) on Message properties or MapMessage. For more details see...

[jira] Created: (AMQ-766) add jmdns.jar to lib/optional in the binary distro

add jmdns.jar to lib/optional in the binary distro -- Key: AMQ-766 URL: https://issues.apache.org/activemq/browse/AMQ-766 Project: ActiveMQ Type: Improvement Versions: 4.0.1 Reporter: james strachan

[jira] Created: (SM-478) allow URIs to be easily used by the ServiceMixClient

allow URIs to be easily used by the ServiceMixClient Key: SM-478 URL: https://issues.apache.org/activemq/browse/SM-478 Project: ServiceMix Type: Improvement Reporter: james strachan We have the ability to

[jira] Resolved: (SM-478) allow URIs to be easily used by the ServiceMixClient

[ https://issues.apache.org/activemq/browse/SM-478?page=all ] james strachan resolved SM-478: --- Fix Version: 3.0-M3 Resolution: Fixed Assign To: james strachan For more information see http://servicemix.org/site/client-api.html allow

[jira] Resolved: (AMQ-394) for non-durable topics add a configurable Policy to drop messages from slow consumers

[ https://issues.apache.org/activemq/browse/AMQ-394?page=all ] james strachan resolved AMQ-394: Resolution: Fixed For details see http://incubator.apache.org/activemq/slow-consumer-handling.html for non-durable topics add a configurable Policy

[jira] Reopened: (AMQ-394) for non-durable topics add a configurable Policy to drop messages from slow consumers

[ https://issues.apache.org/activemq/browse/AMQ-394?page=all ] james strachan reopened AMQ-394: changing fix version... for non-durable topics add a configurable Policy to drop messages from slow consumers

[jira] Resolved: (AMQ-394) for non-durable topics add a configurable Policy to drop messages from slow consumers

[ https://issues.apache.org/activemq/browse/AMQ-394?page=all ] james strachan resolved AMQ-394: Fix Version: 4.0.1 4.0 (was: 4.1) Resolution: Fixed for non-durable topics add a configurable Policy to drop

[jira] Resolved: (AMQ-391) message consumption is too slow, only 40/s

[ https://issues.apache.org/activemq/browse/AMQ-391?page=all ] james strachan resolved AMQ-391: Fix Version: 4.0.1 Resolution: Fixed This should be fixed in 4.0.1 now. If its not let us know and we can reopen the issue message consumption

[jira] Resolved: (AMQ-361) duplicate delivery, already consumed messages are reconsumed after server restart

[ https://issues.apache.org/activemq/browse/AMQ-361?page=all ] james strachan resolved AMQ-361: Fix Version: 4.0.1 Resolution: Fixed AFAIK this is all working now in 4.0.1 - let us know if you can still reproduce on 4.0.1 and we can reopen

[jira] Resolved: (AMQ-275) Could not enqueue message and Too many open files

[ https://issues.apache.org/activemq/browse/AMQ-275?page=all ] james strachan resolved AMQ-275: Fix Version: 4.0.1 (was: 3.2.5) Resolution: Fixed This issue is fixed now in 4.0.1 Could not enqueue message and Too many

[jira] Commented: (AMQ-729) Using a very simple producer and consumer messages are received in wrong order.

[ https://issues.apache.org/activemq/browse/AMQ-729?page=comments#action_36513 ] james strachan commented on AMQ-729: Can you reproduce this on 4.0.1? Using a very simple producer and consumer messages are received in wrong order.

[jira] Commented: (AMQ-319) ActiveMQ hangs when initial connection to broker fails using reliable transport

[ https://issues.apache.org/activemq/browse/AMQ-319?page=comments#action_36515 ] james strachan commented on AMQ-319: Eric - in 4.x you can configure the amount of time or number of tempts that the failover: transport will attempt before the connection

[jira] Updated: (AMQ-792) allow asynchronous dispatch to consumers in the broker for non-durable topics

[ https://issues.apache.org/activemq/browse/AMQ-792?page=all ] james strachan updated AMQ-792: --- Description: We typically use the current thread in the broker to dispatch to all the available non-durable consumers for performance - as this hugely reduces

[jira] Resolved: (AMQ-688) Avoid blocking producers

[ https://issues.apache.org/activemq/browse/AMQ-688?page=all ] james strachan resolved AMQ-688: Resolution: Duplicate AFAIK this issue is now complete with the exception of issue: http://issues.apache.org/activemq/browse/AMQ-791 which is still

[jira] Created: (AMQ-794) make the support of advisory messages optional (so that they can be disabled to reduce RAM and boost performance a little)

make the support of advisory messages optional (so that they can be disabled to reduce RAM and boost performance a little) -- Key: AMQ-794 URL:

[jira] Created: (AMQ-798) provide a new JMS header to indiciate the first message in a sequence being dispatched to a consumer

provide a new JMS header to indiciate the first message in a sequence being dispatched to a consumer Key: AMQ-798 URL: https://issues.apache.org/activemq/browse/AMQ-798

[jira] Resolved: (AMQ-798) provide a new JMS header to indiciate the first message in a sequence being dispatched to a consumer

[ https://issues.apache.org/activemq/browse/AMQ-798?page=all ] james strachan resolved AMQ-798: Fix Version: 4.1 Resolution: Fixed Now supported with the new boolean header JMSXGroupFirstForConsumer. For more details see...

[jira] Created: (XBEAN-23) xbean-spring does not work with spring 2.0-rc2

xbean-spring does not work with spring 2.0-rc2 -- Key: XBEAN-23 URL: http://issues.apache.org/jira/browse/XBEAN-23 Project: XBean Type: Bug Components: spring Versions: 2.4 Reporter: james strachan

[jira] Resolved: (XBEAN-23) xbean-spring does not work with spring 2.0-rc2

[ http://issues.apache.org/jira/browse/XBEAN-23?page=all ] james strachan resolved XBEAN-23: - Resolution: Fixed patch applied in trunk xbean-spring does not work with spring 2.0-rc2 -- Key:

[jira] Resolved: (XBEAN-21) org\apache\xbean\spring\context\XmlWebApplicationContext.java does not work

[ http://issues.apache.org/jira/browse/XBEAN-21?page=all ] james strachan resolved XBEAN-21: - Resolution: Fixed Path applied for this bug fix - many thanks Guillaume org\apache\xbean\spring\context\XmlWebApplicationContext.java does not work

[jira] Created: (AMQ-813) can get a shutdown hang when using embedded broker with VM transport along with the activemq-web module

can get a shutdown hang when using embedded broker with VM transport along with the activemq-web module --- Key: AMQ-813 URL: https://issues.apache.org/activemq/browse/AMQ-813

[jira] Updated: (XBEAN-22) Support for inverse class loading, exclusions and non overridable classes

[ http://issues.apache.org/jira/browse/XBEAN-22?page=all ] james strachan updated XBEAN-22: Fix Version/s: 2.6 (was: 2.5) Support for inverse class loading, exclusions and non overridable classes

[jira] Created: (AMQ-830) switch the C# code to use System.Runtime.InteropServices.Marshal.SizeOf) instead of sizeof() to avoid issues on .Net 1.1 (vs2003)

switch the C# code to use System.Runtime.InteropServices.Marshal.SizeOf) instead of sizeof() to avoid issues on .Net 1.1 (vs2003) - Key: AMQ-830

[jira] Updated: (AMQ-830) switch the C# code to use System.Runtime.InteropServices.Marshal.SizeOf) instead of sizeof() to avoid issues on .Net 1.1 (vs2003)

[ https://issues.apache.org/activemq/browse/AMQ-830?page=all ] james strachan updated AMQ-830: --- Description: For background see http://www.nabble.com/can-amq-dotnet-build-by-.net-framework1.1-%28vs2003%29-tf1958469.html#a5389861 switch the C# code to

[jira] Created: (AMQ-833) make the Subscription MBeans easier to view/navigate using jconsole

make the Subscription MBeans easier to view/navigate using jconsole --- Key: AMQ-833 URL: https://issues.apache.org/activemq/browse/AMQ-833 Project: ActiveMQ Issue Type:

[jira] Updated: (AMQ-833) make the Subscription MBeans easier to view/navigate using jconsole

[ https://issues.apache.org/activemq/browse/AMQ-833?page=all ] james strachan updated AMQ-833: --- Fix Version/s: 4.2 Affects Version/s: 4.0.1 (was: 4.2) make the Subscription MBeans easier to view/navigate using jconsole

[jira] Created: (AMQ-834) use the clientID rather than connectionID for the name of subscriptionIDs in JMX

use the clientID rather than connectionID for the name of subscriptionIDs in JMX Key: AMQ-834 URL: https://issues.apache.org/activemq/browse/AMQ-834 Project: ActiveMQ

[jira] Created: (AMQ-840) add spring aware ConnectionFactory implementations which automatically set the clientIDPrefix from the Spring Bean Name

add spring aware ConnectionFactory implementations which automatically set the clientIDPrefix from the Spring Bean Name Key: AMQ-840 URL:

[jira] Resolved: (AMQ-452) create a virtual Queue for durable topic subscriptions so that multiple consumers can consume in parallel from the same topic subscription with queue semantics, yet preservi

[ https://issues.apache.org/activemq/browse/AMQ-452?page=all ] james strachan resolved AMQ-452. Resolution: Fixed Assignee: james strachan (was: Rob Davies) For details on how it works see http://activemq.org/site/virtual-destinations.html

[jira] Commented: (AMQ-723) Generate Advisory Messages to setup tear down producer based on consumer activity

[ https://issues.apache.org/activemq/browse/AMQ-723?page=comments#action_36630 ] james strachan commented on AMQ-723: I added some documentation to the advisory messages page http://activemq.org/site/advisory-message.html basically each

[jira] Resolved: (AMQ-723) Generate Advisory Messages to setup tear down producer based on consumer activity

[ https://issues.apache.org/activemq/browse/AMQ-723?page=all ] james strachan resolved AMQ-723. Resolution: Fixed I think this is now resolved by just using the aforementioned selector (consumerCount=0) on the subscription to consumer advisories

[jira] Resolved: (AMQ-828) add some XML configuration way to force the creation of certain destinations on startup

[ https://issues.apache.org/activemq/browse/AMQ-828?page=all ] james strachan resolved AMQ-828. Resolution: Fixed For documentation and an example of how to use this feature see... http://activemq.org/site/configure-startup-destinations.html add some

[jira] Created: (AMQ-850) add the ability to timeout a prefetch buffer to prevent a single consumer grabbing messages

add the ability to timeout a prefetch buffer to prevent a single consumer grabbing messages --- Key: AMQ-850 URL: https://issues.apache.org/activemq/browse/AMQ-850

[jira] Created: (AMQ-851) move the XPath filtering components out of the activemq-core module into activemq-optional to reduce the dependencies of the activemq-core POM to only minimal stuff

move the XPath filtering components out of the activemq-core module into activemq-optional to reduce the dependencies of the activemq-core POM to only minimal stuff

[jira] Commented: (XBEAN-25) [RTC] Support for #null short hand for a null value

[ http://issues.apache.org/jira/browse/XBEAN-25?page=comments#action_12424791 ] james strachan commented on XBEAN-25: - +1 looks good to me [RTC] Support for #null short hand for a null value

[jira] Commented: (XBEAN-27) [RTC] Need a way to exclude classes from being parsed by qdox

[ http://issues.apache.org/jira/browse/XBEAN-27?page=comments#action_12424792 ] james strachan commented on XBEAN-27: - +1. Incidentally if we all nag Joe Walnes enough we might be able to persuade him to release a new qdox which can ignore

[jira] Commented: (XBEAN-22) [RTC] Support for inverse class loading, exclusions and non overridable classes

[ http://issues.apache.org/jira/browse/XBEAN-22?page=comments#action_12424794 ] james strachan commented on XBEAN-22: - +1 I like it [RTC] Support for inverse class loading, exclusions and non overridable classes

[jira] Commented: (XBEAN-29) [RTC] getClassLoaderFor used on spring based configuration with classpath does not return the custom classloader

[ http://issues.apache.org/jira/browse/XBEAN-29?page=comments#action_12424795 ] james strachan commented on XBEAN-29: - +1 looks good to me [RTC] getClassLoaderFor used on spring based configuration with classpath does not return the

[jira] Commented: (XBEAN-26) [RTC] Nested properties not evaluated for named constructor args

[ http://issues.apache.org/jira/browse/XBEAN-26?page=comments#action_12424796 ] james strachan commented on XBEAN-26: - +1 [RTC] Nested properties not evaluated for named constructor args

[jira] Commented: (XBEAN-24) [RTC] Support mixed nested properties and complex elements

[ http://issues.apache.org/jira/browse/XBEAN-24?page=comments#action_12424797 ] james strachan commented on XBEAN-24: - +1 (though I do find properties inside text of XML a tad of a hack :) [RTC] Support mixed nested properties and complex

[jira] Commented: (XBEAN-10) Add support for inline xml (bean properties as DOM nodes)

[ http://issues.apache.org/jira/browse/XBEAN-10?page=comments#action_12424798 ] james strachan commented on XBEAN-10: - Agreed. Also it might be nice to support other 'XML types' as well like SDO as well Add support for inline xml (bean

[jira] Created: (XBEAN-31) it would be great if the m2 plugin would automatically add the XSD and .xsd.html files as artifacts into the build

it would be great if the m2 plugin would automatically add the XSD and .xsd.html files as artifacts into the build -- Key: XBEAN-31 URL:

[jira] Created: (XBEAN-32) autogenerated XSDs are invalid - they use unknown 'xsd:string' types

autogenerated XSDs are invalid - they use unknown 'xsd:string' types Key: XBEAN-32 URL: http://issues.apache.org/jira/browse/XBEAN-32 Project: XBean Issue Type: Bug

[jira] Resolved: (XBEAN-32) autogenerated XSDs are invalid - they use unknown 'xsd:string' types

[ http://issues.apache.org/jira/browse/XBEAN-32?page=all ] james strachan resolved XBEAN-32. - Fix Version/s: 2.6 Resolution: Fixed Yes this turned out to be a trivial typo in Utils.java autogenerated XSDs are invalid - they use unknown

[jira] Commented: (XBEAN-31) [RTC] it would be great if the m2 plugin would automatically add the XSD and .xsd.html files as artifacts into the build

[ http://issues.apache.org/jira/browse/XBEAN-31?page=comments#action_12424869 ] james strachan commented on XBEAN-31: - +1 This is awesome! [RTC] it would be great if the m2 plugin would automatically add the XSD and .xsd.html files as

[jira] Created: (AMQ-864) nested map support in NMS

nested map support in NMS - Key: AMQ-864 URL: https://issues.apache.org/activemq/browse/AMQ-864 Project: ActiveMQ Issue Type: Improvement Components: NMS (C# client) Reporter: james strachan

[jira] Closed: (XBEAN-38) XFire initialisation problem with spring 2.0-rc2

[ http://issues.apache.org/jira/browse/XBEAN-38?page=all ] james strachan closed XBEAN-38. --- Fix Version/s: 2.5 Resolution: Fixed This was fixed in 2.5 XFire initialisation problem with spring 2.0-rc2

[jira] Created: (AMQ-868) consolidate the C++ clients in SVN more, removing old CMS code

consolidate the C++ clients in SVN more, removing old CMS code -- Key: AMQ-868 URL: https://issues.apache.org/activemq/browse/AMQ-868 Project: ActiveMQ Issue Type: New Feature

[jira] Assigned: (AMQ-656) Update of AMQ C++ client

[ https://issues.apache.org/activemq/browse/AMQ-656?page=all ] james strachan reassigned AMQ-656: -- Assignee: Timothy Bish Just wanted to make sure you were aware of this issue Update of AMQ C++ client Key:

[jira] Resolved: (AMQ-707) makefile plus some changes for the CMS C++ client

[ https://issues.apache.org/activemq/browse/AMQ-707?page=all ] james strachan resolved AMQ-707. Resolution: Fixed This is now resolved in the new C++ client (activemq-cpp) makefile plus some changes for the CMS C++ client

[jira] Resolved: (AMQ-411) enable XSD validation by default with ActiveMQ XML files

[ https://issues.apache.org/activemq/browse/AMQ-411?page=all ] james strachan resolved AMQ-411. Resolution: Fixed See this example which when using Spring 2.x's ApplicationContext implementations performs XSD validation (and IDE completion)

[jira] Resolved: (AMQ-846) Change the maven pom group id to org.apache.activemq and the version to be 4.1-incubator-SNAPSHOT

[ https://issues.apache.org/activemq/browse/AMQ-846?page=all ] james strachan resolved AMQ-846. Resolution: Fixed Change the maven pom group id to org.apache.activemq and the version to be 4.1-incubator-SNAPSHOT

[jira] Created: (AMQ-869) provide a broker-to-broker synchronization protocol so that an old master can be brought back online and synchronize up with a slave (which is running as a master) or to brin

provide a broker-to-broker synchronization protocol so that an old master can be brought back online and synchronize up with a slave (which is running as a master) or to bring an old slave back online

[jira] Resolved: (AMQ-856) log Endpoint connection to JMS broker failed: ... on error level

[ https://issues.apache.org/activemq/browse/AMQ-856?page=all ] james strachan resolved AMQ-856. Fix Version/s: 4.1 Resolution: Fixed log Endpoint connection to JMS broker failed: ... on error level

[jira] Resolved: (AMQ-855) Add support for prefetchSize = 0

[ https://issues.apache.org/activemq/browse/AMQ-855?page=all ] james strachan resolved AMQ-855. Resolution: Won't Fix I still don't see a valid use case for this change. Instead I think these issues are more applicable to the problem you are trying to

[jira] Closed: (XBEAN-38) XFire initialisation problem with spring 2.0-rc2

[ http://issues.apache.org/jira/browse/XBEAN-38?page=all ] james strachan closed XBEAN-38. --- You have invalid XML. change it to beans service xmlns=http://xfire.codehaus.org/config/1.0;

[jira] Commented: (AMQ-855) Add support for prefetchSize = 0

[ https://issues.apache.org/activemq/browse/AMQ-855?page=comments#action_36718 ] james strachan commented on AMQ-855: BTW just to be absolutely clear - here's how I think we should fix Vadim's use case. If we had full support for priority

[jira] Resolved: (AMQ-770) consumer.dispatchAsync defaults to false

[ https://issues.apache.org/activemq/browse/AMQ-770?page=all ] james strachan resolved AMQ-770. Fix Version/s: 4.1 Resolution: Fixed This was a documentation error. We default to false to minimise the number of threads used by default.

[jira] Resolved: (AMQ-871) Allow MessageEvictionStrategy to evict more than one MessageReference in evictMessage(LinkedList message) method

[ https://issues.apache.org/activemq/browse/AMQ-871?page=all ] james strachan resolved AMQ-871. Fix Version/s: 4.1 Resolution: Fixed Assignee: james strachan Patch applied with thanks! Incidentally for bad eviction strategies which do

[jira] Commented: (AMQ-850) add the ability to timeout a consumer to prevent a bad, hung or unused consumer consumer from grabbing messages

[ https://issues.apache.org/activemq/browse/AMQ-850?page=comments#action_36733 ] james strachan commented on AMQ-850: Vadim: agreed in the case where the consumer just never processes any messages and the receive() method is never called. A

[jira] Commented: (AMQ-850) add the ability to timeout a consumer to prevent a bad, hung or unused consumer consumer from grabbing messages

[ https://issues.apache.org/activemq/browse/AMQ-850?page=comments#action_36734 ] james strachan commented on AMQ-850: Sridhar: I don't quite follow your suggestion. We kinda do what you suggest - the broker maintains a record of how many

[jira] Created: (XBEAN-42) generated XSDs don't handle the spring ID/IDREF type for 'id' attributes

generated XSDs don't handle the spring ID/IDREF type for 'id' attributes Key: XBEAN-42 URL: http://issues.apache.org/jira/browse/XBEAN-42 Project: XBean Issue Type:

[jira] Closed: (XBEAN-42) generated XSDs don't handle the spring ID/IDREF type for 'id' attributes

[ http://issues.apache.org/jira/browse/XBEAN-42?page=all ] james strachan closed XBEAN-42. --- Fix Version/s: 2.6 Resolution: Fixed Turned out to be a trivial bug fix - we just need to add the following line to the generated XSDs... xs:attribute

[jira] Commented: (XBEAN-34) The id attribute defaults to the xbean tag name

[ http://issues.apache.org/jira/browse/XBEAN-34?page=comments#action_12427250 ] james strachan commented on XBEAN-34: - note that I don't think this would work in a validating XSD as spring 2 uses ID/IDREFs to validate IDs match up etc The

[jira] Commented: (XBEAN-34) The id attribute defaults to the xbean tag name

[ http://issues.apache.org/jira/browse/XBEAN-34?page=comments#action_12427251 ] james strachan commented on XBEAN-34: - Spring allows you to specify a 'name' instead of an 'id' - so maybe we should default 'name' to the name of the element?

[jira] Resolved: (AMQ-855) Add support for prefetchSize = 0

[ https://issues.apache.org/activemq/browse/AMQ-855?page=all ] james strachan resolved AMQ-855. Fix Version/s: 4.1 (was: 4.2) Resolution: Fixed I've just committed an implementation to the main trunk if you want to try it

[jira] Reopened: (AMQ-855) Add support for prefetchSize = 0

[ https://issues.apache.org/activemq/browse/AMQ-855?page=all ] james strachan reopened AMQ-855: The issue was resolved before Vadim attached more patches Add support for prefetchSize = 0

[jira] Updated: (AMQ-855) Add support for prefetchSize = 0

[ https://issues.apache.org/activemq/browse/AMQ-855?page=all ] james strachan updated AMQ-855: --- Patch Info: [Patch Available] setting the patch available flag Add support for prefetchSize = 0 Key:

[jira] Resolved: (AMQ-883) NMS asynchronous consumption of queued messages

[ https://issues.apache.org/activemq/browse/AMQ-883?page=all ] james strachan resolved AMQ-883. Fix Version/s: 4.1 Resolution: Fixed Thanks for the suggestions and ideas on how to fix it! :) I've added a bunch more test cases to AsyncConsumeTest

[jira] Resolved: (AMQ-865) C# Client's Listener doesn't receive messages if you don't explicitly call Subscribe

[ https://issues.apache.org/activemq/browse/AMQ-865?page=all ] james strachan resolved AMQ-865. Fix Version/s: 4.1 Resolution: Fixed Patch applied in SVN trunk if you want to try along with the test cases for this issue and the related AMQ-883

[jira] Created: (AMQ-893) on solaris you cannot easily kill a slave broker when using JDBC Master Slave

on solaris you cannot easily kill a slave broker when using JDBC Master Slave - Key: AMQ-893 URL: https://issues.apache.org/activemq/browse/AMQ-893 Project: ActiveMQ

[jira] Resolved: (AMQ-829) use some INFO level logging in failover: transport when a transport error occurs and when the transport is resumed

[ https://issues.apache.org/activemq/browse/AMQ-829?page=all ] james strachan resolved AMQ-829. Resolution: Fixed Done - we log using INFO level logging whenever a transport fails and reconnection starts use some INFO level logging in failover:

[jira] Resolved: (AMQ-630) After broker has shutdown, cannot shutdown a client application

[ http://jira.activemq.org/jira//browse/AMQ-630?page=all ] james strachan resolved AMQ-630: Resolution: Fixed Fix Version: 4.0 M5 We used to have an infinite blocking request-response when closing clients, letting the broker konw that the

[jira] Created: (AMQ-636) multicast discovery of network connectors can create 2 brokers in 1 JVM if the user changes the brokerName

multicast discovery of network connectors can create 2 brokers in 1 JVM if the user changes the brokerName -- Key: AMQ-636 URL: http://jira.activemq.org/jira//browse/AMQ-636

[jira] Created: (AMQ-635) ruby stomp client test failures against 4.x

ruby stomp client test failures against 4.x --- Key: AMQ-635 URL: http://jira.activemq.org/jira//browse/AMQ-635 Project: ActiveMQ Type: Bug Versions: 4.0 M4 Reporter: james strachan Assigned to: james strachan

[jira] Commented: (AMQ-637) Enhance ActiveMQInput/Outputstream to use a real TCP connection.

[ http://jira.activemq.org/jira//browse/AMQ-637?page=comments#action_35766 ] james strachan commented on AMQ-637: Sounds fine with me :) BTW is the idea that the socket will only be open for the duration of the input stream, so that the transfer is

[jira] Assigned: (AMQ-642) Add ability to monitor network connections on brokerclient

[ http://jira.activemq.org/jira//browse/AMQ-642?page=all ] james strachan reassigned AMQ-642: -- Assign To: james strachan Add ability to monitor network connections on brokerclient --

[jira] Resolved: (AMQ-600) Broker will not release a persistant clientId if a network connection is broken then restored at the TCP layer from a remote client

[ http://jira.activemq.org/jira//browse/AMQ-600?page=all ] james strachan resolved AMQ-600: Resolution: Fixed Fix Version: 4.0 M5 This should be now fixed in SVN HEAD - could you confirm using tomorrows SNAPSHOT build that your issues is

[jira] Resolved: (AMQ-602) Remote TCP Publish-only persistant clients are unable to reconnect when TCP/IP level discconect occurs

[ http://jira.activemq.org/jira//browse/AMQ-602?page=all ] james strachan resolved AMQ-602: Resolution: Fixed This looks to be the same as AMQ-600 Remote TCP Publish-only persistant clients are unable to reconnect when TCP/IP level discconect

[jira] Resolved: (AMQ-642) Add ability to monitor network connections on brokerclient

[ http://jira.activemq.org/jira//browse/AMQ-642?page=all ] james strachan resolved AMQ-642: Resolution: Fixed I've added addTransportListener()/removeTransportListener() methods to ActiveMQConnection which should do what you need :) Add

[jira] Resolved: (AMQ-623) Cleanup Failed When ActiveMQConnection.close() is called

[ http://jira.activemq.org/jira//browse/AMQ-623?page=all ] james strachan resolved AMQ-623: Resolution: Fixed Fix Version: 4.0 M5 I've just patched SVN HEAD to fix this issue AFAIK - any chance you could try out tomorrows SNAPSHOT build (or

[jira] Commented: (AMQ-638) no way to get broker-led replay of messages for messages ACK'd in a transaction after rollback

[ http://jira.activemq.org/jira//browse/AMQ-638?page=comments#action_35808 ] james strachan commented on AMQ-638: BTW I patched the ruby client to perform client side redelivery, so its a non-issue now for ruby clients no way to get broker-led replay

[jira] Commented: (AMQ-639) Broker is not re-connecting to a network of brokers after going down and then being brought back up

[ http://jira.activemq.org/jira//browse/AMQ-639?page=comments#action_35814 ] james strachan commented on AMQ-639: BTW I wonder if the exception you are getting is related to this fix... http://jira.activemq.org/jira/browse/AMQ-600 which was causing

[jira] Commented: (AMQ-639) Broker is not re-connecting to a network of brokers after going down and then being brought back up

[ http://jira.activemq.org/jira//browse/AMQ-639?page=comments#action_35815 ] james strachan commented on AMQ-639: (BTW that issue was fixed in the last hour or so in SVN) Broker is not re-connecting to a network of brokers after going down and then

[jira] Deleted: (AMQ-598) test

[ http://jira.activemq.org/jira//browse/AMQ-598?page=all ] james strachan deleted AMQ-598: --- test Key: AMQ-598 URL: http://jira.activemq.org/jira//browse/AMQ-598 Project: ActiveMQ Type: Bug Reporter: Hiram

[jira] Commented: (AMQ-531) XBean has a runtime issue with Spring 2.0M2

[ http://jira.activemq.org/jira//browse/AMQ-531?page=comments#action_35858 ] james strachan commented on AMQ-531: Still looks to be an issue with 2.0-M3 - Spring changed their binary protocol, so unless they provide us a similar hook, the only thing I

[jira] Commented: (AMQ-531) XBean has a runtime issue with Spring 2.0M2

[ http://jira.activemq.org/jira//browse/AMQ-531?page=comments#action_35859 ] james strachan commented on AMQ-531: If Spring are not going to maintain binary compatibility with XBean then maybe we should just ship a jar-jar'd version of Spring 1.2.x

[jira] Commented: (AMQ-643) maxInactivityDuration does not seem to work properly

[ http://jira.activemq.org/jira//browse/AMQ-643?page=comments#action_35888 ] james strachan commented on AMQ-643: We could always raise another feature request JIRA for the subscription dropping; also for nondurable messaging we have the option to drop

[jira] Resolved: (AMQ-655) Typo Timmer in thread name in JDBCPersistenceAdapter.java

[ http://jira.activemq.org/jira//browse/AMQ-655?page=all ] james strachan resolved AMQ-655: Resolution: Fixed patch applied - many thanks John Typo Timmer in thread name in JDBCPersistenceAdapter.java

[jira] Resolved: (AMQ-674) Composite Destination persisted messages never get cleaned up, halt message producers

[ https://issues.apache.org/activemq/browse/AMQ-674?page=all ] james strachan resolved AMQ-674: Fix Version: 4.0 RC1 Resolution: Fixed This is a known issue with the architecture of 3.x; once you hit queue full; the system generally pauses

[jira] Updated: (AMQ-669) Add a keepDurableSubsActive option to brokers so that durable subs eagerly loaded and kept in memory

[ https://issues.apache.org/activemq/browse/AMQ-669?page=all ] james strachan updated AMQ-669: --- Fix Version: 4.0 RC3 (was: 4.0 RC 2) Add a keepDurableSubsActive option to brokers so that durable subs eagerly loaded and kept in

[jira] Updated: (AMQ-660) Add support for MaxDB

[ https://issues.apache.org/activemq/browse/AMQ-660?page=all ] james strachan updated AMQ-660: --- Fix Version: 4.0 RC3 (was: 4.0 RC 2) Add support for MaxDB - Key: AMQ-660 URL:

[jira] Updated: (AMQ-651) Deadlock in ActiveMQ close processing of Resource Adapter

[ https://issues.apache.org/activemq/browse/AMQ-651?page=all ] james strachan updated AMQ-651: --- Fix Version: 4.0 RC3 (was: 4.0 RC 2) Deadlock in ActiveMQ close processing of Resource Adapter

[jira] Updated: (AMQ-648) Changing the default JMX URL

[ https://issues.apache.org/activemq/browse/AMQ-648?page=all ] james strachan updated AMQ-648: --- Fix Version: 4.0 RC3 (was: 4.0 RC 2) Changing the default JMX URL Key: AMQ-648 URL:

[jira] Updated: (AMQ-631) verify that HttpsTransportBrokerTest won't hang on other environment

[ https://issues.apache.org/activemq/browse/AMQ-631?page=all ] james strachan updated AMQ-631: --- Fix Version: 4.0 RC3 (was: 4.0 RC 2) verify that HttpsTransportBrokerTest won't hang on other environment

  1   2   3   4   >