[jira] Commented: (AMQ-1079) Slave Fail Error when Receiving message on a MasterSlave configuration
[ https://issues.apache.org/activemq/browse/AMQ-1079?page=comments#action_37679 ] William Blackburn commented on AMQ-1079: I should have mentioned that we are using the 4.1 release. I just retested with the latest 4.2 snapshot and the problem still occurs, same config as above. > Slave Fail Error when Receiving message on a MasterSlave configuration > -- > > Key: AMQ-1079 > URL: https://issues.apache.org/activemq/browse/AMQ-1079 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 4.2.0 > Environment: Windows XP, jdk1.5 >Reporter: Marlon Santos > Fix For: 4.2.0 > > Attachments: ConsumerTool.java, MasterSlave.java, ProducerTool.java > > > A slave fail error is caught while receiving message from master broker on a > master slave configuration. > I included the java files that I used. Running this through xbean/xml config > also produces the same error. > SEVERE: Slave Failed > java.lang.AssertionError: Unsupported Method > at > org.apache.activemq.transport.TransportSupport.request(TransportSupport.java:71) > at > org.apache.activemq.transport.TransportFilter.request(TransportFilter.java:88) > at > org.apache.activemq.transport.TransportFilter.request(TransportFilter.java:88) > at > org.apache.activemq.transport.MutexTransport.request(MutexTransport.java:49) > at > org.apache.activemq.broker.ft.MasterBroker.sendSyncToSlave(MasterBroker.java:363) > at > org.apache.activemq.broker.ft.MasterBroker.sendToSlave(MasterBroker.java:345) > at > org.apache.activemq.broker.ft.MasterBroker.acknowledge(MasterBroker.java:320) > at > org.apache.activemq.broker.MutableBrokerFilter.acknowledge(MutableBrokerFilter.java:88) > at > org.apache.activemq.broker.TransportConnection.processMessageAck(TransportConnection.java:491) > at org.apache.activemq.command.MessageAck.visit(MessageAck.java:179) > at > org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:287) > at > org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:178) > at > org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:65) > at > org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:133) > at > org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122) > at > org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:84) > at > org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:137) > at java.lang.Thread.run(Thread.java:595) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-1079) Slave Fail Error when Receiving message on a MasterSlave configuration
[ https://issues.apache.org/activemq/browse/AMQ-1079?page=comments#action_37678 ] William Blackburn commented on AMQ-1079: Please, ActiveMQ developers, please comment on this issue - it is a showstopper for us. Even the knowledge that you are unable to reproduce would be helpful, because we could then provide more data or test-cases. Our story is as follows: We configure the master and slave according to the instructions on the site. They both start up OK, and we can see from the logs that the slave attaches to the master. But, as soon as the first connection is made to the master, the slave dies. When the client attempts to failover, the slave can't accept the connection of course, and everything fails. The master log looks like: INFO DefaultDatabaseLocker - Attempting to acquire the exclusive lock to become the Master broker INFO DefaultDatabaseLocker - Becoming the master on dataSource: [EMAIL PROTECTED] INFO JournalPersistenceAdapter - Journal Recovery Started from: Active Journal: using 5 x 20.0 Megs at: /Users/wblackburn/activemq-4.1.0-master/activemq-data/journal INFO JournalPersistenceAdapter - Journal Recovered: 0 message(s) in transactions recovered. INFO TransportServerThreadSupport - Listening for connections at: tcp://fastgt.local:61617 INFO TransportConnector - Connector openwire Started INFO BrokerService - ActiveMQ JMS Message Broker (localhost, ID:fastgt.local-50799-1166058345810-1:0) started INFO TransportConnection- Slave Broker localhost is attached ERROR MasterBroker - Slave Failed java.lang.AssertionError: Unsupported Method at org.apache.activemq.transport.TransportSupport.request(TransportSupport.java:71) at org.apache.activemq.transport.TransportFilter.request(TransportFilter.java:88) at org.apache.activemq.transport.TransportFilter.request(TransportFilter.java:88) at org.apache.activemq.transport.MutexTransport.request(MutexTransport.java:49) at org.apache.activemq.broker.ft.MasterBroker.sendSyncToSlave(MasterBroker.java:363) at org.apache.activemq.broker.ft.MasterBroker.sendToSlave(MasterBroker.java:345) at org.apache.activemq.broker.ft.MasterBroker.acknowledge(MasterBroker.java:320) at org.apache.activemq.broker.MutableBrokerFilter.acknowledge(MutableBrokerFilter.java:88) at org.apache.activemq.broker.TransportConnection.processMessageAck(TransportConnection.java:488) at org.apache.activemq.command.MessageAck.visit(MessageAck.java:179) at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:284) at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:177) at org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:65) at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:133) at org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122) at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:84) at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:137) at java.lang.Thread.run(Thread.java:613) ERROR MasterBroker - Slave Failed master config is: http://activemq.org/config/1.0";> The slave log looks like: INFO DefaultDatabaseLocker - Attempting to acquire the exclusive lock to become the Master broker INFO DefaultDatabaseLocker - Becoming the master on dataSource: [EMAIL PROTECTED] INFO JournalPersistenceAdapter - Journal Recovery Started from: Active Journal: using 5 x 20.0 Megs at: /Users/wblackburn/activemq-4.1.0-slave/activemq-data/journal INFO JournalPersistenceAdapter - Journal Recovered: 0 message(s) in transactions recovered. INFO TransportServerThreadSupport - Listening for connections at: tcp://fastgt.local:61618 INFO TransportConnector - Connector openwire Started INFO TransportConnector - Connector vm://localhost Started INFO MasterConnector- Starting a network connection between vm://localhost#0 and tcp://null:0 has been established. INFO BrokerService - ActiveMQ JMS Message Broker (localhost, ID:fastgt.local-50808-1166058365982-2:0) started INFO MasterConnector- Slave connection between vm://localhost#0 and tcp://localhost/127.0.0.1:61617 has been established. Slave config is: http://activemq.org/config/1.0"; masterConnectorURI="tcp://localhost:61617" shutdownOnMasterFailure="false">
[jira] Commented: (AMQ-1092) Deadlock when ActiveMQ 4.X is run as an embedded broker inside JBoss 4.X with "vm://localhost" configured in the ra.xml file
[ https://issues.apache.org/activemq/browse/AMQ-1092?page=comments#action_37677 ] Luis A Lopez-Rivera commented on AMQ-1092: -- Additional information: Tests are with XA Transactions. > Deadlock when ActiveMQ 4.X is run as an embedded broker inside JBoss 4.X with > "vm://localhost" configured in > the ra.xml file. > > > Key: AMQ-1092 > URL: https://issues.apache.org/activemq/browse/AMQ-1092 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 4.1.0, 4.0.1, 4.0.2 > Environment: Tested OSes: Windows 2000 Pro, Window XP Pro x64, Linux > Java: 1.5 SDK & 1.4 SDK > J2EE Server: JBoss 4.03.S1 & 4.0.4GA >Reporter: Luis A Lopez-Rivera > Attachments: deadlock.txt, javastack.txt > > > Deadlock occurs when ActiveMQ 4.X is run as an embedded broker inside JBoss > 4.X with "vm://localhost" > configured in the ra.xml file. If "tcp://localhost:61616" is used instead of > "vm://localhost" then everything works fine. > The deadlock seems to occur when two messages are being handled (one is being > produced and one being consumed). If I prevent two messages from being > handled at the same time (one produced and one consumed) then the deadlock > does not occur. > This situation can be reproduced every single time tested. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-1093) Client deadlock during failover
[ https://issues.apache.org/activemq/browse/AMQ-1093?page=all ] james strachan resolved AMQ-1093. - Fix Version/s: 4.2.0 Resolution: Fixed I've just committed a patch to trunk for this which I think resolves the issue. There's no test case to easily verify its resolved though (its a tad hard to recreate) so I wonder could you try and see if this is now fixed - if not let us know and we can reopen this issue > Client deadlock during failover > --- > > Key: AMQ-1093 > URL: https://issues.apache.org/activemq/browse/AMQ-1093 > Project: ActiveMQ > Issue Type: Bug > Components: Transport >Affects Versions: 4.1.0 > Environment: Linux 2.6, java 1.5.0 >Reporter: Danielius Jurna >Priority: Critical > Fix For: 4.2.0 > > > In 4.1.0 there's deadlock on connection failover. There is the scenario: > 1. Client consumes message using message listener > 2. Conection is lost > 3. Client sends message to another queue from messagle listener and waits > until connection is restored. > 4. Reconnect task blocks on reconnecting. > > This bug is new to 4.1.0. The problem is in ActiveMQMessageConsumre.dispatch > . There is new lock on unconsumedMessages.getMutex() . So the reconnect task > cannot invoke ActiveMQMessageConsumre.clearMessagesInProgress(), because lock > is acquired by message listener, which waits untill message is sent (untill > connection is resumed). Here is stack traces: > > "ActiveMQ Session Task" daemon prio=1 tid=0x002b27774260 nid=0x4778 in > Object.wait() [0x40ef3000..0x40ef4db0] > at java.lang.Object.wait(Native Method) > - waiting on <0x002b0020a7c8> (a > edu.emory.mathcs.backport.java.util.concurrent.locks.CondVar) > at java.lang.Object.wait(Object.java:474) > at > edu.emory.mathcs.backport.java.util.concurrent.locks.CondVar.await(CondVar.java:75) > > - locked <0x002b0020a7c8> (a > edu.emory.mathcs.backport.java.util.concurrent.locks.CondVar) > at > edu.emory.mathcs.backport.java.util.concurrent.ArrayBlockingQueue.take(ArrayBlockingQueue.java:318) > > at > org.apache.activemq.transport.FutureResponse.getResult(FutureResponse.java:42) > > at > org.apache.activemq.transport.ResponseCorrelator.request(ResponseCorrelator.java:75) > > at > org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1171) > > at > org.apache.activemq.ActiveMQSession.send(ActiveMQSession.java:1548) > at > org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:465) > > at > org.apache.activemq.pool.PooledProducer.send(PooledProducer.java:75) > - locked <0x002b173fa480> (a > org.apache.activemq.ActiveMQMessageProducer) > at > org.apache.activemq.pool.PooledProducer.send(PooledProducer.java:60) > at > org.springframework.jms.core.JmsTemplate.doSend(JmsTemplate.java:537) > at > org.springframework.jms.core.JmsTemplate.doSend(JmsTemplate.java:513) > at > org.springframework.jms.core.JmsTemplate$2.doInJms(JmsTemplate.java:479) > at > org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:430) > at > org.springframework.jms.core.JmsTemplate.send(JmsTemplate.java:477) > at > lt.elitnet.dbp.das.impl.storage.HI2StorageImpl.storeHI2Message(HI2StorageImpl.java:57) > > at > lt.elitnet.dbp.das.impl.hi2.HI2PersistanceBase.saveIRIContent(HI2PersistanceBase.java:77) > > at sun.reflect.GeneratedMethodAccessor185.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > > at java.lang.reflect.Method.invoke(Method.java:585) > at > org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:318) > > at > org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:203) > > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:162) > > at > org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:107) > > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:185) > > at > org.springframework.orm.hibernate3.HibernateInterceptor.invoke(HibernateInterceptor.java:104) > > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:185) > > at > lt.elitnet.dbp.das.impl.alarming.DataBaseConnectionAlarmsPublisher.invoke(DataBaseConnectionAlarmsPublisher.java:59) > > at > org.springframework.aop.framework.Refle
XMPP question
Hi, we're using ActiveMQ for our project now. Currently we're using 4.02. I read from the web site that ActiveMQ 4.1 supports XMPP. Our application needs to send IM to jabber. Can I use ActiveMQ supplied jar to send IM to jabber server(not ActiveMQ Broker)? or ActiveMQ supplied jar can only connect to ActiveMQ? Can you please let me know my options? Thanks a lot!
