http://permalink.gmane.org/gmane.comp.java.activemq.devel hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.java.activemq.devel/31822 <pre> [ https://issues.apache.org/jira/browse/AMQ-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-3736. ----------------------------- Resolution: Incomplete No feedback on resolution using newer version, assuming that its fixed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Timothy Bish (JIRA 2012-05-25T22:36:23 http://permalink.gmane.org/gmane.comp.java.activemq.devel/31821 <pre>Yes, v1.5.5 seems to be working. I will start using that version. Thanks for your help! -- View this message in context: http://activemq.2283324.n4.nabble.com/Apache-NMS-1-5-0-Broker-5-4-2-Compatibility-tp4652717p4652721.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. </pre> rasitha 2012-05-25T19:43:14 http://permalink.gmane.org/gmane.comp.java.activemq.devel/31820 <pre>Mikhail Melamud created AMQ-3860: ------------------------------------ Summary: doAddMessageReference missing setting priority into prepared statement therefore using wrong index for message itself Key: AMQ-3860 URL: https://issues.apache.org/jira/browse/AMQ-3860 Project: ActiveMQ Issue Type: Bug Components: Message Store Affects Versions: 5.6.0, 5.5.0, 5.4.2 Reporter: Mikhail Melamud Not sure in what cases ActiveMQDestination() is actually called, but getAddMessageStatement() returns statement with 7 params to set... public void doAddMessageReference(TransactionContext c, long sequence, MessageId messageID, ActiveMQDestination destination, long expirationTime, String messageRef) throws SQLException, IOException { PreparedStatement s = c.getAddMessageStatement(); cleanupExclusiveLock.readLock().lock(); try { if (s == null) { s = c.getConne</pre> Mikhail Melamud (JIRA 2012-05-25T15:59:22 http://permalink.gmane.org/gmane.comp.java.activemq.devel/31819 <pre>On Fri, 2012-05-25 at 08:45 -0700, rasitha wrote: Sounds like you might be seeing https://issues.apache.org/jira/browse/AMQNET-341 I'd recommend you move up to NMS.ActiveMQ v1.5.5 </pre> Timothy Bish 2012-05-25T15:57:29 http://permalink.gmane.org/gmane.comp.java.activemq.devel/31818 <pre>Hi, I recently upgraded my .Net solution to a newer version of NMS drivers and I'm seeing an issue where consumers stop processing messages when the broker is restarted. Consumers are using failover protocol and it is not an issue on the old driver. Broker version: 5.4.2 Old Version: Apache.NMS - 1.4.0 Apache.NMS.ActiveMQ - 1.4.1 New version: Apache.NMS - 1.5.0 Apache.NMS.ActiveMQ - 1.5.2 Does anyone know if there's a known compatibility issue with the new driver on 5.4.2 broker? Upgrading the broker is not an option at this time and I'm looking to roll back the drivers. But if there's a known workaround for the new drivers, please let me know. Thanks! -- View this message in context: http://activemq.2283324.n4.nabble.com/Apache-NMS-1-5-0-Broker-5-4-2-Compatibility-tp4652717.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. </pre> rasitha 2012-05-25T15:45:47 http://permalink.gmane.org/gmane.comp.java.activemq.devel/31817 <pre> [ https://issues.apache.org/jira/browse/AMQCPP-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=13283546#comment-13283546 ] Helen Huang edited comment on AMQCPP-407 at 5/25/12 3:45 PM: ------------------------------------------------------------- I compared the ActiveMQConnection.cpp files and did not find any difference. Additional synchronization might be needed. was (Author: hhuang): I compared the ActiveMQConnection.cpp files and did not find any difference. From the call stack, it looks like this connection has been deleted by another thread... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Helen Huang (JIRA 2012-05-25T15:45:24 http://permalink.gmane.org/gmane.comp.java.activemq.devel/31816 <pre> [ https://issues.apache.org/jira/browse/AMQCPP-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=13283546#comment-13283546 ] Helen Huang commented on AMQCPP-407: ------------------------------------ I compared the ActiveMQConnection.cpp files and did not find any difference. From the call stack, it looks like this connection has been deleted by another thread... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Helen Huang (JIRA 2012-05-25T15:37:23 http://permalink.gmane.org/gmane.comp.java.activemq.devel/31815 <pre> [ https://issues.apache.org/jira/browse/AMQCPP-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=13283424#comment-13283424 ] Timothy Bish commented on AMQCPP-407: ------------------------------------- You can diff yours against the latest 3.4.3 SNAPSHOT src located here to see the most recent changes. http://people.apache.org/~tabish/cms-3.4.x/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Timothy Bish (JIRA 2012-05-25T13:58:25 http://permalink.gmane.org/gmane.comp.java.activemq.devel/31814 <pre> [ https://issues.apache.org/jira/browse/AMQCPP-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=13283417#comment-13283417 ] Helen Huang commented on AMQCPP-407: ------------------------------------ Hi Timothy, our CMS build does include the threading fixes in ActiveMQConnection.cpp for https://issues.apache.org/jira/browse/AMQCPP-388. Have you made any other changes recently? Thanks! Helen -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Helen Huang (JIRA 2012-05-25T13:52:24 http://permalink.gmane.org/gmane.comp.java.activemq.devel/31813 <pre> [ https://issues.apache.org/jira/browse/AMQ-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-3856. ------------------------------- Resolution: Fixed Fixed in trunk, also added checks for the ObjectMessage case. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Timothy Bish (JIRA 2012-05-25T13:34:23 http://permalink.gmane.org/gmane.comp.java.activemq.devel/31812 <pre> [ https://issues.apache.org/jira/browse/AMQ-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guilhem RAMBAL reopened AMQ-3843: --------------------------------- This is a workaround, to work as 5.5.0 you need sun jdk instead of jre, because of tools.jar usage. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Guilhem RAMBAL (JIRA 2012-05-25T13:20:23 http://permalink.gmane.org/gmane.comp.java.activemq.devel/31811 <pre> [ https://issues.apache.org/jira/browse/AMQCPP-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=13282819#comment-13282819 ] Timothy Bish commented on AMQCPP-407: ------------------------------------- Recommend moving to v3.4.2 as it incorporates some threading fixes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Timothy Bish (JIRA 2012-05-24T22:54:10 http://permalink.gmane.org/gmane.comp.java.activemq.devel/31810 <pre>Helen Huang created AMQCPP-407: ---------------------------------- Summary: Application crashes after stopping message broker Key: AMQCPP-407 URL: https://issues.apache.org/jira/browse/AMQCPP-407 Project: ActiveMQ C++ Client Issue Type: Bug Components: CMS Impl Affects Versions: 3.4.1 Environment: Windows xp service pack 3, ActiveMQ broker 5.3.1, apr 1.4.2, apr-util 1.3.9, apr iconv 1.2.1 Reporter: Helen Huang Assignee: Timothy Bish Priority: Blocker Fix For: 3.4.1 Stopping the message broker would crash our application. The following is the call stack of the fault thread. Thread 0 - System ID 672 Entry point msvcr80!endthreadex+61 Create time 5/24/2012 1:53:56 PM Time spent in user mode 0 Days 0:0:0.46 Time spent in kernel mode 0 Days 0:0:0.78 Function Arg 1 Arg 2 Arg 3 Source kernel32!InterlockedDecrement+9 00000000 0000</pre> Helen Huang (JIRA 2012-05-24T20:54:12 http://permalink.gmane.org/gmane.comp.java.activemq.devel/31809 <pre> [ https://issues.apache.org/jira/browse/AMQCPP-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=13282595#comment-13282595 ] Helen Huang commented on AMQCPP-405: ------------------------------------ I am wondering if we will need to set the connection.sendTimeout value when the inactivity monitor is on. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Helen Huang (JIRA 2012-05-24T16:20:29 http://permalink.gmane.org/gmane.comp.java.activemq.devel/31808 <pre> [ https://issues.apache.org/jira/browse/AMQCPP-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=13282594#comment-13282594 ] Helen Huang commented on AMQCPP-405: ------------------------------------ We take the default settings for the inactivity monitor... I think it is enabled by default. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Helen Huang (JIRA 2012-05-24T16:18:29 http://permalink.gmane.org/gmane.comp.java.activemq.devel/31807 <pre> [ https://issues.apache.org/jira/browse/AMQCPP-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=13282556#comment-13282556 ] Timothy Bish commented on AMQCPP-405: ------------------------------------- Have you disabled the inactivity monitor? Its possible that if the inactivity monitor is disabled and the transport doesn't detect the socket drop that you could get stuck in the same scenario. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Timothy Bish (JIRA 2012-05-24T15:34:34 http://permalink.gmane.org/gmane.comp.java.activemq.devel/31806 <pre> [ https://issues.apache.org/jira/browse/AMQCPP-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=13282555#comment-13282555 ] Helen Huang commented on AMQCPP-405: ------------------------------------ Thank you very much for your quick response Timothy! I looked at the log files we have, and it appears that the broker was not ever turned on during the test after the disconnection. Also we are not using the failover protocal. Our url is: "tcp://%MessageBrokerIP%:%MessageBrokerPort%". Could the sender thread be blocked the same way as you have described in this case? I read the CMS configuration web page again, I think we can probably try to avoid the problem by using the "connection.sendTimeout" option. We will let you know how it goes. Thanks a lot for your help! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdmin</pre> Helen Huang (JIRA 2012-05-24T15:14:39 http://permalink.gmane.org/gmane.comp.java.activemq.devel/31805 <pre> [ https://issues.apache.org/jira/browse/AMQCPP-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQCPP-406. --------------------------------- Resolution: Fixed Fix applied in trunk and the 3.4.x fixes branch. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Timothy Bish (JIRA 2012-05-24T15:05:56 http://permalink.gmane.org/gmane.comp.java.activemq.devel/31804 <pre>Timothy Bish created AMQCPP-406: ----------------------------------- Summary: TcpTransport can leak memory if the connect method fails midway through Key: AMQCPP-406 URL: https://issues.apache.org/jira/browse/AMQCPP-406 Project: ActiveMQ C++ Client Issue Type: Bug Components: Transports Affects Versions: 3.4.2, 3.5.0 Reporter: Timothy Bish Assignee: Timothy Bish Fix For: 3.5.0, 3.4.3 the Input and OutputStream chains that are built inside TcpTransport connect can leak if an exception is thrown before the get assigned into the class level pointer instance. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Timothy Bish (JIRA 2012-05-24T14:58:55 http://permalink.gmane.org/gmane.comp.java.activemq.devel/31803 <pre> [ https://issues.apache.org/jira/browse/AMQCPP-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQCPP-402. --------------------------------- Resolution: Fixed this is fixed in trunk and the 3.4.x branch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Timothy Bish (JIRA 2012-05-24T14:56:54 http://permalink.gmane.org/gmane.comp.java.activemq.devel/31802 <pre> [ https://issues.apache.org/jira/browse/AMQCPP-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=13282496#comment-13282496 ] Timothy Bish commented on AMQCPP-405: ------------------------------------- It looks as though the thread is blocked waiting for a response from the broker, which can happen when the failure occurs. Has the client actually reconnected? If not then this will remain blocked until it does unless you configure a timeout on the failover transport. You may also want to switch to v3.4.2 which incorporates some additional failover fixes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Timothy Bish (JIRA 2012-05-24T13:24:58 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.java.activemq.devel