[jira] Created: (AMQ-957) Problem with Broker shutdown in 4.0.2

Problem with Broker shutdown in 4.0.2 - Key: AMQ-957 URL: https://issues.apache.org/activemq/browse/AMQ-957 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 4.0.2

[jira] Updated: (AMQ-608) Change logging level of some DemandForwardingBridge log messages.

[ https://issues.apache.org/activemq/browse/AMQ-608?page=all ] Kevin Yaussy updated AMQ-608: - Attachment: InactivityMonitor.patch2 > Change logging level of some DemandForwardingBridge log messages. > -

[jira] Updated: (AMQ-608) Change logging level of some DemandForwardingBridge log messages.

[ https://issues.apache.org/activemq/browse/AMQ-608?page=all ] Kevin Yaussy updated AMQ-608: - Attachment: DemandForwardingBridgeSupport.patch FailoverTransport.patch InactivityMonitor.patch Hope this is the way to attach the p

[jira] Reopened: (AMQ-608) Change logging level of some DemandForwardingBridge log messages.

[ https://issues.apache.org/activemq/browse/AMQ-608?page=all ] Kevin Yaussy reopened AMQ-608: -- Hiram, Very sorry that I did not look at the 4.0.1 source until the last couple days. I'd like to submit patches this time (I don't have svn, but I will attac

[jira] Created: (AMQ-771) org.apache.activemq.broker.TransportConnection::stop should not attempt to send a message over the connection.

org.apache.activemq.broker.TransportConnection::stop should not attempt to send a message over the connection. -- Key: AMQ-771 URL: https://issues.apache.org/activemq/brow

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

consumer.dispatchAsync defaults to false Key: AMQ-770 URL: https://issues.apache.org/activemq/browse/AMQ-770 Project: ActiveMQ Type: Bug Components: JMS client Versions: 4.0, 4.0.1 Reporter: Kevin Yaussy P

[jira] Commented: (AMQ-657) FailoverTransport inhibits exception-listener and transport-listener

[ https://issues.apache.org/activemq/browse/AMQ-657?page=comments#action_36412 ] Kevin Yaussy commented on AMQ-657: -- Looks like this is working fine now. Thanks! > FailoverTransport inhibits exception-listener and transport-listener >

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

[ http://jira.activemq.org/jira//browse/AMQ-643?page=all ] Kevin Yaussy updated AMQ-643: - Attachment: amq2.xml amq1.xml Attached are my broker XML configs. We run embedded brokers, but have external access to them (i.e. the tcp connectivity

[jira] Commented: (AMQ-608) Change logging level of some DemandForwardingBridge log messages.

[ http://jira.activemq.org/jira//browse/AMQ-608?page=comments#action_35849 ] Kevin Yaussy commented on AMQ-608: -- Any chance of these changes getting into 4.0 RC1? > Change logging level of some DemandForwardingBridge log messages. >

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

[ http://jira.activemq.org/jira//browse/AMQ-643?page=comments#action_35847 ] Kevin Yaussy commented on AMQ-643: -- So, in the case of the client setting the maxInactivityDuration value on its connector url, you are saying that the broker must have a maxInact

[jira] Commented: (AMQ-632) TaskRunnerFactory from broker is not carried along to Broker-to-Broker connections

[ http://jira.activemq.org/jira//browse/AMQ-632?page=comments#action_35772 ] Kevin Yaussy commented on AMQ-632: -- Yes, I need to be able to set some properties, including dispatchAsync, for DemandForwardingBridge. However, the link you give above configure