[jira] [Created] (AMQ-4327) XMPP Connector does not work with ActiveMQ 5.7
lokesh created AMQ-4327: --- Summary: XMPP Connector does not work with ActiveMQ 5.7 Key: AMQ-4327 URL: https://issues.apache.org/jira/browse/AMQ-4327 Project: ActiveMQ Issue Type: Bug Components: Transport Affects Versions: 5.7.0 Environment: Windows Reporter: lokesh Fix For: 5.x Hi, When I send a message to xmpp queue. I get the following exception. I am using activemq version 5.7 SLF4J: Failed to load class org.slf4j.impl.StaticLoggerBinder. SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. Caught: javax.jms.JMSException: Could not create Transport. Reason: java.io.IOException: Transport scheme NOT recognized: [xmpp] javax.jms.JMSException: Could not create Transport. Reason: java.io.IOException: Transport scheme NOT recognized: [xmpp] at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:35) at org.apache.activemq.ActiveMQConnectionFactory.createTransport(ActiveMQConnectionFactory.java:252) at org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:265) at org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:238) at org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:184) at App$HelloWorldProducer.run(App.java:41) at java.lang.Thread.run(Thread.java:662) Caused by: java.io.IOException: Transport scheme NOT recognized: [xmpp] at org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:27) at org.apache.activemq.transport.TransportFactory.findTransportFactory(TransportFactory.java:196) at org.apache.activemq.transport.TransportFactory.connect(TransportFactory.java:66) at org.apache.activemq.ActiveMQConnectionFactory.createTransport(ActiveMQConnectionFactory.java:250) ... 5 more Caused by: java.io.IOException: Could not find factory class for resource: META-INF/services/org/apache/activemq/transport/xmpp at org.apache.activemq.util.FactoryFinder$StandaloneObjectFactory.loadProperties(FactoryFinder.java:96) at org.apache.activemq.util.FactoryFinder$StandaloneObjectFactory.create(FactoryFinder.java:58) at org.apache.activemq.util.FactoryFinder.newInstance(FactoryFinder.java:146) at org.apache.activemq.transport.TransportFactory.findTransportFactory(TransportFactory.java:193) ... 7 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (AMQ-4328) Cross talk over duplex network connection can lead to blocking
Gary Tully created AMQ-4328:
---
Summary: Cross talk over duplex network connection can lead to
blocking
Key: AMQ-4328
URL: https://issues.apache.org/jira/browse/AMQ-4328
Project: ActiveMQ
Issue Type: Bug
Components: activemq-camel
Affects Versions: 5.8.0, 5.7.0
Reporter: Gary Tully
Assignee: Gary Tully
Fix For: 5.9.0
with active forwarding in both directions a duplex network connector can block.
in 5.8, threads of the form:{code}ActiveMQ BrokerService[xx] Task-10 daemon
prio=10 tid=0xb35d1c00 nid=0xc64 runnable [0xb3369000]
java.lang.Thread.State: RUNNABLE
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at
org.apache.activemq.transport.tcp.TcpBufferedOutputStream.flush(TcpBufferedOutputStream.java:115)
at java.io.DataOutputStream.flush(DataOutputStream.java:106)
at
org.apache.activemq.transport.tcp.TcpTransport.oneway(TcpTransport.java:176)
at
org.apache.activemq.transport.AbstractInactivityMonitor.doOnewaySend(AbstractInactivityMonitor.java:322)
at
org.apache.activemq.transport.AbstractInactivityMonitor.oneway(AbstractInactivityMonitor.java:304)
at
org.apache.activemq.transport.TransportFilter.oneway(TransportFilter.java:85)
at
org.apache.activemq.transport.WireFormatNegotiator.oneway(WireFormatNegotiator.java:104)
at
org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:68)
at
org.apache.activemq.transport.ResponseCorrelator.asyncRequest(ResponseCorrelator.java:81)
at
org.apache.activemq.network.DemandForwardingBridgeSupport.serviceLocalCommand(DemandForwardingBridgeSupport.java:994)
at
org.apache.activemq.network.DemandForwardingBridgeSupport$2.onCommand(DemandForwardingBridgeSupport.java:201)
at
org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:116)
at
org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
at
org.apache.activemq.transport.vm.VMTransport.doDispatch(VMTransport.java:138)
at
org.apache.activemq.transport.vm.VMTransport.dispatch(VMTransport.java:127)
- locked 0x647f4650 (a java.util.concurrent.atomic.AtomicBoolean)
at
org.apache.activemq.transport.vm.VMTransport.oneway(VMTransport.java:104)
at
org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:68)
at
org.apache.activemq.transport.ResponseCorrelator.oneway(ResponseCorrelator.java:60)
at
org.apache.activemq.broker.TransportConnection.dispatch(TransportConnection.java:1378)
at
org.apache.activemq.broker.TransportConnection.processDispatch(TransportConnection.java:897)
at
org.apache.activemq.broker.TransportConnection.iterate(TransportConnection.java:943)
at
org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:129)
at
org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:47)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
ActiveMQ Transport: tcp:///xx:61616@40803 prio=10 tid=0xb3525400 nid=0xbec
waiting on condition [0xb3276000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for 0x64657028 (a
java.util.concurrent.locks.ReentrantLock$NonfairSync)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:156)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:811)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:842)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1178)
at
java.util.concurrent.locks.ReentrantLock$NonfairSync.lock(ReentrantLock.java:186)
at java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:262)
at
org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:66)
at
org.apache.activemq.transport.ResponseCorrelator.oneway(ResponseCorrelator.java:60)
at
org.apache.activemq.network.DemandForwardingBridgeSupport$7.onCompletion(DemandForwardingBridgeSupport.java:630)
at
org.apache.activemq.transport.FutureResponse.set(FutureResponse.java:65)
at
org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:109)
at
org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
[jira] [Updated] (AMQ-4328) Cross talk over duplex network connection can lead to blocking
[
https://issues.apache.org/jira/browse/AMQ-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-4328:
Component/s: (was: activemq-camel)
Connector
Cross talk over duplex network connection can lead to blocking
--
Key: AMQ-4328
URL: https://issues.apache.org/jira/browse/AMQ-4328
Project: ActiveMQ
Issue Type: Bug
Components: Connector
Affects Versions: 5.7.0, 5.8.0
Reporter: Gary Tully
Assignee: Gary Tully
Labels: bridge, duplex, hang, network
Fix For: 5.9.0
with active forwarding in both directions a duplex network connector can
block. in 5.8, threads of the form:{code}ActiveMQ BrokerService[xx] Task-10
daemon prio=10 tid=0xb35d1c00 nid=0xc64 runnable [0xb3369000]
java.lang.Thread.State: RUNNABLE
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at
org.apache.activemq.transport.tcp.TcpBufferedOutputStream.flush(TcpBufferedOutputStream.java:115)
at java.io.DataOutputStream.flush(DataOutputStream.java:106)
at
org.apache.activemq.transport.tcp.TcpTransport.oneway(TcpTransport.java:176)
at
org.apache.activemq.transport.AbstractInactivityMonitor.doOnewaySend(AbstractInactivityMonitor.java:322)
at
org.apache.activemq.transport.AbstractInactivityMonitor.oneway(AbstractInactivityMonitor.java:304)
at
org.apache.activemq.transport.TransportFilter.oneway(TransportFilter.java:85)
at
org.apache.activemq.transport.WireFormatNegotiator.oneway(WireFormatNegotiator.java:104)
at
org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:68)
at
org.apache.activemq.transport.ResponseCorrelator.asyncRequest(ResponseCorrelator.java:81)
at
org.apache.activemq.network.DemandForwardingBridgeSupport.serviceLocalCommand(DemandForwardingBridgeSupport.java:994)
at
org.apache.activemq.network.DemandForwardingBridgeSupport$2.onCommand(DemandForwardingBridgeSupport.java:201)
at
org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:116)
at
org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
at
org.apache.activemq.transport.vm.VMTransport.doDispatch(VMTransport.java:138)
at
org.apache.activemq.transport.vm.VMTransport.dispatch(VMTransport.java:127)
- locked 0x647f4650 (a java.util.concurrent.atomic.AtomicBoolean)
at
org.apache.activemq.transport.vm.VMTransport.oneway(VMTransport.java:104)
at
org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:68)
at
org.apache.activemq.transport.ResponseCorrelator.oneway(ResponseCorrelator.java:60)
at
org.apache.activemq.broker.TransportConnection.dispatch(TransportConnection.java:1378)
at
org.apache.activemq.broker.TransportConnection.processDispatch(TransportConnection.java:897)
at
org.apache.activemq.broker.TransportConnection.iterate(TransportConnection.java:943)
at
org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:129)
at
org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:47)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
ActiveMQ Transport: tcp:///xx:61616@40803 prio=10 tid=0xb3525400 nid=0xbec
waiting on condition [0xb3276000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for 0x64657028 (a
java.util.concurrent.locks.ReentrantLock$NonfairSync)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:156)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:811)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:842)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1178)
at
java.util.concurrent.locks.ReentrantLock$NonfairSync.lock(ReentrantLock.java:186)
at java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:262)
at
org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:66)
at
org.apache.activemq.transport.ResponseCorrelator.oneway(ResponseCorrelator.java:60)
at
[jira] [Resolved] (AMQ-4328) Cross talk over duplex network connection can lead to blocking
[
https://issues.apache.org/jira/browse/AMQ-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-4328.
-
Resolution: Fixed
fix and test in http://svn.apache.org/r1447323
Cross talk over duplex network connection can lead to blocking
--
Key: AMQ-4328
URL: https://issues.apache.org/jira/browse/AMQ-4328
Project: ActiveMQ
Issue Type: Bug
Components: Connector
Affects Versions: 5.7.0, 5.8.0
Reporter: Gary Tully
Assignee: Gary Tully
Labels: bridge, duplex, hang, network
Fix For: 5.9.0
with active forwarding in both directions a duplex network connector can
block. in 5.8, threads of the form:{code}ActiveMQ BrokerService[xx] Task-10
daemon prio=10 tid=0xb35d1c00 nid=0xc64 runnable [0xb3369000]
java.lang.Thread.State: RUNNABLE
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at
org.apache.activemq.transport.tcp.TcpBufferedOutputStream.flush(TcpBufferedOutputStream.java:115)
at java.io.DataOutputStream.flush(DataOutputStream.java:106)
at
org.apache.activemq.transport.tcp.TcpTransport.oneway(TcpTransport.java:176)
at
org.apache.activemq.transport.AbstractInactivityMonitor.doOnewaySend(AbstractInactivityMonitor.java:322)
at
org.apache.activemq.transport.AbstractInactivityMonitor.oneway(AbstractInactivityMonitor.java:304)
at
org.apache.activemq.transport.TransportFilter.oneway(TransportFilter.java:85)
at
org.apache.activemq.transport.WireFormatNegotiator.oneway(WireFormatNegotiator.java:104)
at
org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:68)
at
org.apache.activemq.transport.ResponseCorrelator.asyncRequest(ResponseCorrelator.java:81)
at
org.apache.activemq.network.DemandForwardingBridgeSupport.serviceLocalCommand(DemandForwardingBridgeSupport.java:994)
at
org.apache.activemq.network.DemandForwardingBridgeSupport$2.onCommand(DemandForwardingBridgeSupport.java:201)
at
org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:116)
at
org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
at
org.apache.activemq.transport.vm.VMTransport.doDispatch(VMTransport.java:138)
at
org.apache.activemq.transport.vm.VMTransport.dispatch(VMTransport.java:127)
- locked 0x647f4650 (a java.util.concurrent.atomic.AtomicBoolean)
at
org.apache.activemq.transport.vm.VMTransport.oneway(VMTransport.java:104)
at
org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:68)
at
org.apache.activemq.transport.ResponseCorrelator.oneway(ResponseCorrelator.java:60)
at
org.apache.activemq.broker.TransportConnection.dispatch(TransportConnection.java:1378)
at
org.apache.activemq.broker.TransportConnection.processDispatch(TransportConnection.java:897)
at
org.apache.activemq.broker.TransportConnection.iterate(TransportConnection.java:943)
at
org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:129)
at
org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:47)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
ActiveMQ Transport: tcp:///xx:61616@40803 prio=10 tid=0xb3525400 nid=0xbec
waiting on condition [0xb3276000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for 0x64657028 (a
java.util.concurrent.locks.ReentrantLock$NonfairSync)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:156)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:811)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:842)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1178)
at
java.util.concurrent.locks.ReentrantLock$NonfairSync.lock(ReentrantLock.java:186)
at java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:262)
at
org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:66)
at
org.apache.activemq.transport.ResponseCorrelator.oneway(ResponseCorrelator.java:60)
at
[jira] [Created] (AMQCPP-464) Deadlock during normal task termination
Scott Weaver created AMQCPP-464: --- Summary: Deadlock during normal task termination Key: AMQCPP-464 URL: https://issues.apache.org/jira/browse/AMQCPP-464 Project: ActiveMQ C++ Client Issue Type: Bug Components: Decaf Affects Versions: 3.6.0 Environment: Windows XP VS2005 Reporter: Scott Weaver Assignee: Timothy Bish Priority: Critical Normal task termination hangs occasionally. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQCPP-464) Deadlock during normal task termination
[ https://issues.apache.org/jira/browse/AMQCPP-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Weaver updated AMQCPP-464: Attachment: CrashHang_Report__CMStressD.exe__02182013132527878.mht Thread 0 is attempting join of thread 2 which is parked in a connection destructor. Deadlock during normal task termination --- Key: AMQCPP-464 URL: https://issues.apache.org/jira/browse/AMQCPP-464 Project: ActiveMQ C++ Client Issue Type: Bug Components: Decaf Affects Versions: 3.6.0 Environment: Windows XP VS2005 Reporter: Scott Weaver Assignee: Timothy Bish Priority: Critical Attachments: CrashHang_Report__CMStressD.exe__02182013132527878.mht Normal task termination hangs occasionally. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQCPP-464) Deadlock during normal task termination
[ https://issues.apache.org/jira/browse/AMQCPP-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13580799#comment-13580799 ] Timothy Bish commented on AMQCPP-464: - Can't say from the stack what happened to cause the lock. Best bet is to break into the debugger and attempt to examine the AbstractQueueSynchronizer of the ThreadPoolExecutor that is being shutdown to see who owns the lock since the shutdown method is waiting for the 'mainlock' to become unlocked so it can have a go. The lock owner is always the head pointer in the AQS and the owner pointer Thread is stored in that Node. Deadlock during normal task termination --- Key: AMQCPP-464 URL: https://issues.apache.org/jira/browse/AMQCPP-464 Project: ActiveMQ C++ Client Issue Type: Bug Components: Decaf Affects Versions: 3.6.0 Environment: Windows XP VS2005 Reporter: Scott Weaver Assignee: Timothy Bish Priority: Critical Attachments: CrashHang_Report__CMStressD.exe__02182013132527878.mht Normal task termination hangs occasionally. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (AMQ-4329) AMQ2149Test
Kevin Earls created AMQ-4329:
Summary: AMQ2149Test
Key: AMQ-4329
URL: https://issues.apache.org/jira/browse/AMQ-4329
Project: ActiveMQ
Issue Type: Bug
Components: Test Cases
Environment: Mac, JDK7
Reporter: Kevin Earls
Note: The KahaDB version of this test (AMQ2149KahaDBTest) is working correctly.
This test has two cases that fail, testQueueTransactionalOrderWithRestart, and
testOrderWithRestart. testQueueTransactionalOrderWithRestart fails after the
server is restarted with the following exception
junit.framework.AssertionFailedError: queue://test.dest.0 received 6 expected
5681
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.TestCase.fail(TestCase.java:227)
at
org.apache.activemq.bugs.AMQ2149Test$Receiver.onMessage(AMQ2149Test.java:201)
at
org.apache.activemq.ActiveMQMessageConsumer.dispatch(ActiveMQMessageConsumer.java:1321)
at
org.apache.activemq.ActiveMQSessionExecutor.dispatch(ActiveMQSessionExecutor.java:131)
at
org.apache.activemq.ActiveMQSessionExecutor.iterate(ActiveMQSessionExecutor.java:202)
at
org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:129)
at
org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:47)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
The testOrderWithRestart case works correctly when run on it's own, and only
fails if run after testQueueTransactionalOrderWithRestart with messages like
the following:
2013-02-18 15:41:25,528 [ Session Task-1] - WARN AMQ2149Test
- queue://test.dest.0 received 6082 in msg:
ID:Kevins-MacBook-Pro.local-60920-1361220011508-5:1:1:1:6083 expected 0, l\
astId: null, message:ActiveMQTextMessage {commandId = 6087, responseRequired =
true, messageId = ID:Kevins-MacBook-Pro.local-60920-1361220011508-5:1:1:1:6083,
originalDestination = null, originalTran\
sactionId = null, producerId =
ID:Kevins-MacBook-Pro.local-60920-1361220011508-5:1:1:1, destination =
queue://test.dest.0, transactionId = null, expiration = 0, timestamp =
1361220082802, arrival = 0\
, brokerInTime = 1361220085522, brokerOutTime = 1361220085522, correlationId =
null, replyTo = null, persistent = true, type = null, priority = 4, groupID =
null, groupSequence = 0, targetConsumerId \
= null, compressed = false, userID = null, content = null, marshalledProperties
= org.apache.activemq.util.ByteSequence@d3bf5f8, dataStructure = null,
redeliveryCounter = 0, size = 0, properties = {s\
eqNum=6082}, readOnlyProperties = true, readOnlyBody = true, droppable = false,
text = 186704152740050035096258373992406547145203959...321183574477}
2013-02-18 15:41:25,528 [ Session Task-1] - ERROR AMQ2149Test
- queue://test.dest.0 onMessage error
junit.framework.AssertionFailedError: queue://test.dest.0 received 6082
expected 0
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.TestCase.fail(TestCase.java:227)
at
org.apache.activemq.bugs.AMQ2149Test$Receiver.onMessage(AMQ2149Test.java:201)
at
org.apache.activemq.ActiveMQMessageConsumer.dispatch(ActiveMQMessageConsumer.java:1321)
at
org.apache.activemq.ActiveMQSessionExecutor.dispatch(ActiveMQSessionExecutor.java:131)
at
org.apache.activemq.ActiveMQSessionExecutor.iterate(ActiveMQSessionExecutor.java:202)
at
org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:129)
at
org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:47)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
It looks like messages send by testQueueTransactionalOrderWithRestart are not
cleaned up when that test fails.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (AMQ-4330) Removal of Master/Slave removed isSlave() JMX api
Matt Pavlovich created AMQ-4330: --- Summary: Removal of Master/Slave removed isSlave() JMX api Key: AMQ-4330 URL: https://issues.apache.org/jira/browse/AMQ-4330 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.8.0 Environment: All Reporter: Matt Pavlovich The task to remove the Master/Slave functionality (AMQ-4165) also removed the isSlave() attribute from the Broker. This attribute is also used when a broker is polling a shared datastore using the master+slave polling model. Several large user groups will be impacted by this, as they have scripts that monitor this attribute in order to re-balance brokers after maintenance or failure scenarios. Please reinstate. Thanks -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQCPP-464) Deadlock during normal task termination
[ https://issues.apache.org/jira/browse/AMQCPP-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13580836#comment-13580836 ] Scott Weaver commented on AMQCPP-464: - The head node of the AQS has a waitStatus of -1, a valid next value, and all the other pointers (including thread) are NULL. Deadlock during normal task termination --- Key: AMQCPP-464 URL: https://issues.apache.org/jira/browse/AMQCPP-464 Project: ActiveMQ C++ Client Issue Type: Bug Components: Decaf Affects Versions: 3.6.0 Environment: Windows XP VS2005 Reporter: Scott Weaver Assignee: Timothy Bish Priority: Critical Attachments: CrashHang_Report__CMStressD.exe__02182013132527878.mht Normal task termination hangs occasionally. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (AMQ-4331) MessageSelectorTest fails because of dated config file
Kevin Earls created AMQ-4331: Summary: MessageSelectorTest fails because of dated config file Key: AMQ-4331 URL: https://issues.apache.org/jira/browse/AMQ-4331 Project: ActiveMQ Issue Type: Bug Components: Test Cases Reporter: Kevin Earls Priority: Minor The activemq.xml file used by this test contained: persistenceAdapter kahaPersistenceAdapter directory=file:target/amq1095 maxDataFileLength=20/ /persistenceAdapter which is no longer valid. I fixed the test by changing it to persistenceAdapter kahaDB directory=file:target/amq1095/ /persistenceAdapter -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQ-4331) MessageSelectorTest fails because of dated config file
[ https://issues.apache.org/jira/browse/AMQ-4331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Earls updated AMQ-4331: - Attachment: AMQ4331.patch MessageSelectorTest fails because of dated config file -- Key: AMQ-4331 URL: https://issues.apache.org/jira/browse/AMQ-4331 Project: ActiveMQ Issue Type: Bug Components: Test Cases Reporter: Kevin Earls Priority: Minor Attachments: AMQ4331.patch The activemq.xml file used by this test contained: persistenceAdapter kahaPersistenceAdapter directory=file:target/amq1095 maxDataFileLength=20/ /persistenceAdapter which is no longer valid. I fixed the test by changing it to persistenceAdapter kahaDB directory=file:target/amq1095/ /persistenceAdapter -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (AMQ-4331) MessageSelectorTest fails because of dated config file
[ https://issues.apache.org/jira/browse/AMQ-4331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-4331. --- Resolution: Fixed patch applied, thanks. MessageSelectorTest fails because of dated config file -- Key: AMQ-4331 URL: https://issues.apache.org/jira/browse/AMQ-4331 Project: ActiveMQ Issue Type: Bug Components: Test Cases Reporter: Kevin Earls Priority: Minor Attachments: AMQ4331.patch The activemq.xml file used by this test contained: persistenceAdapter kahaPersistenceAdapter directory=file:target/amq1095 maxDataFileLength=20/ /persistenceAdapter which is no longer valid. I fixed the test by changing it to persistenceAdapter kahaDB directory=file:target/amq1095/ /persistenceAdapter -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQCPP-464) Deadlock during normal task termination
[ https://issues.apache.org/jira/browse/AMQCPP-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13580892#comment-13580892 ] Scott Weaver commented on AMQCPP-464: - I don't know if it will help but the second node is also signalled (waitStatus = -1) and is thread 7 in the dump while the third and last node on the queue is thread 2 in the dump and is the one that is being joined with thread 0 in the dump. The third and last node on the queue has waitStatus = 0. Deadlock during normal task termination --- Key: AMQCPP-464 URL: https://issues.apache.org/jira/browse/AMQCPP-464 Project: ActiveMQ C++ Client Issue Type: Bug Components: Decaf Affects Versions: 3.6.0 Environment: Windows XP VS2005 Reporter: Scott Weaver Assignee: Timothy Bish Priority: Critical Attachments: CrashHang_Report__CMStressD.exe__02182013132527878.mht Normal task termination hangs occasionally. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQCPP-464) Deadlock during normal task termination
[ https://issues.apache.org/jira/browse/AMQCPP-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13580897#comment-13580897 ] Timothy Bish commented on AMQCPP-464: - Currently on line 458 (setHead) of AbstractQueuedSynchronizer.cpp we set the thread pointer to NULL, don't really need to but we do. You can comment that out and then you'll see who currently owns the lock during this deadlock. The second thread is at waitStatus = -1 meaning its waiting to be signaled that the thread holding the lock is done, and the third on is zero for reason I can't remember right now but should be fine since its second in line to get the lock. Deadlock during normal task termination --- Key: AMQCPP-464 URL: https://issues.apache.org/jira/browse/AMQCPP-464 Project: ActiveMQ C++ Client Issue Type: Bug Components: Decaf Affects Versions: 3.6.0 Environment: Windows XP VS2005 Reporter: Scott Weaver Assignee: Timothy Bish Priority: Critical Attachments: CrashHang_Report__CMStressD.exe__02182013132527878.mht Normal task termination hangs occasionally. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQ-4326) Virtual destination and network of brokers
[ https://issues.apache.org/jira/browse/AMQ-4326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian updated AMQ-4326: --- Attachment: topic_normal.PNG queue_burst.PNG Virtual destination and network of brokers -- Key: AMQ-4326 URL: https://issues.apache.org/jira/browse/AMQ-4326 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.5.1, 5.6.0, 5.7.0, 5.8.0 Reporter: Brian Priority: Critical Attachments: broker1-activemq.xml, broker2-activemq.xml, broker3-activemq.xml, queue_burst.PNG, setup.png, topic_normal.PNG --- Symptom --- In a network of brokers with a forwarded queue, The queue consumer experiences message bursts (the message flow is iregular) and messages received are out of order. --- Setup --- See attached image from setup - We have 3 brokers linked via network of brokers. - Brokers 1 and 2 share a topic which is also forwarded to a queue. - Brokers 1 and 2 has a producer and consumer to the topic - Both producers send messages at a rate of at least 15 messages per second. - Broker 3 is connected to the network via the queue -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQ-4326) Virtual destination and network of brokers
[ https://issues.apache.org/jira/browse/AMQ-4326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian updated AMQ-4326: --- Description: --- Symptom --- In a network of brokers with a forwarded queue, the queue consumer experiences message bursts even though the producers are sending at a constant rate. Also the messages received by the queue consumer are out of order. See queue_burst.png for the messages bursts in broker 3. The expected result is constant traffic topic_normal.png. --- Setup --- See attached image from setup - We have 3 brokers linked via network of brokers. - Brokers 1 and 2 share a topic which is also forwarded to a queue. - Brokers 1 and 2 has a producer and consumer to the topic - Both producers send messages at a rate of at least 15 messages per second. - Broker 3 is connected to the network via the queue was: --- Symptom --- In a network of brokers with a forwarded queue, The queue consumer experiences message bursts (the message flow is iregular) and messages received are out of order. --- Setup --- See attached image from setup - We have 3 brokers linked via network of brokers. - Brokers 1 and 2 share a topic which is also forwarded to a queue. - Brokers 1 and 2 has a producer and consumer to the topic - Both producers send messages at a rate of at least 15 messages per second. - Broker 3 is connected to the network via the queue Virtual destination and network of brokers -- Key: AMQ-4326 URL: https://issues.apache.org/jira/browse/AMQ-4326 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.5.1, 5.6.0, 5.7.0, 5.8.0 Reporter: Brian Priority: Critical Attachments: broker1-activemq.xml, broker2-activemq.xml, broker3-activemq.xml, queue_burst.PNG, setup.png, topic_normal.PNG --- Symptom --- In a network of brokers with a forwarded queue, the queue consumer experiences message bursts even though the producers are sending at a constant rate. Also the messages received by the queue consumer are out of order. See queue_burst.png for the messages bursts in broker 3. The expected result is constant traffic topic_normal.png. --- Setup --- See attached image from setup - We have 3 brokers linked via network of brokers. - Brokers 1 and 2 share a topic which is also forwarded to a queue. - Brokers 1 and 2 has a producer and consumer to the topic - Both producers send messages at a rate of at least 15 messages per second. - Broker 3 is connected to the network via the queue -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
