Re: Expired messages not moved to dead letter queue.

Check: http://issues.apache.org/activemq/browse/AMQ-1796 -- View this message in context: http://www.nabble.com/Expired-messages-not-moved-to-dead-letter-queue.-tp18608013p18627682.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: DurableConduitBridge.createDemandSubscription() for queues

Created AMQ-1822 for this issue. -- View this message in context: http://www.nabble.com/DurableConduitBridge.createDemandSubscription%28%29-for-queues-tp17753931p18065021.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: DurableConduitBridge.createDemandSubscription() for queues

rajdavies wrote: The current behaviour in networks is correct - in that they are intended to create store and forward networks, and still send messages when there are no active subscribers on the receiving broker. To get the behaviour you require - where messages are forwarded only

Re: queue.send throws ResourceAllocationException without checking usageManager when sendFailIfNoSpace is set in AMQ 4.1.2

Created AMQ-1789 for this issue. -- View this message in context: http://www.nabble.com/queue.send-throws-ResourceAllocationException-without-checking-usageManager-when-sendFailIfNoSpace-is-set-in-AMQ-4.1.2-tp17751662p17771954.html Sent from the ActiveMQ - User mailing list archive at

Re: deadlock on message expiration

Created AMQ-1788 for this issue. -- View this message in context: http://www.nabble.com/deadlock-on-message-expiration-tp17644346p17771984.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

queue.send throws ResourceAllocationException without checking usageManager when sendFailIfNoSpace is set in AMQ 4.1.2

Affected version: AMQ 4.1.2 org.apache.activemq.broker.region.Queue send(ConnectionContext, Message) method always throws ResourceAllocationException if sendFailIfNoSpace is set, producerFlowControl is enabled, message response is not required and network connection is not used to connect to

DurableConduitBridge.createDemandSubscription() for queues

I have the following problem when using network of brokers connected via DurableConduitBridge: - when consumer on (non temporary) queue is created on node1, DemandSubscription is created on node2 (e.g. NC_node1-broker_inboundlocalhost; this is expected) - problem: when this consumer is closed,

deadlock on message expiration

Detected deadlock in AMQ 5.1.0 between transport thread (removing consumer) and QueueThread (sending expired messages to DLQ): Name: VMTransport State: BLOCKED on [EMAIL PROTECTED] owned by: QueueThread:queue://some_queue Total blocked: 31 Total waited: 525 Stack trace: at

jboss integration: jmx monitoring (solved Failed to start jmx connector)

Found a way to monitor amq mbeans via jboss jmx-console. Instructions given on wiki (Integrating Apache ActiveMQ with JBoss) resulted with: [ManagementContext ] Failed to start jmx connector: Cannot bind to URL [rmi://localhost:1099/jmxrmi]: javax.naming.CommunicationException [Root exception

Re: Locked trying to write to journal

Manuel Teira-2 wrote: Hello. I've just detected a lock problem using activemq-core 4.0.2 that seems to be related with journal writing logic. I was able to get a stack of the running process, where we can see that a lot of threads (56 to be precise) are waiting to lock the journal