http://blog.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://comments.gmane.org/gmane.comp.java.activemq.devel/31825 <pre>Babak Vahdat created AMQ-3861: --------------------------------- Summary: Offer a way to not set a transaction manager in activemq-camel Key: AMQ-3861 URL: https://issues.apache.org/jira/browse/AMQ-3861 Project: ActiveMQ Issue Type: Improvement Affects Versions: 5.6.0 Environment: See CAMEL-5055 for the details. Reporter: Babak Vahdat -- 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> Babak Vahdat (JIRA 2012-05-26T15:23:23 http://comments.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://comments.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://comments.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://comments.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://comments.gmane.org/gmane.comp.java.activemq.devel/31799 <pre>Claus Ibsen created AMQ-3859: -------------------------------- Summary: To tight version range in activemq features file Key: AMQ-3859 URL: https://issues.apache.org/jira/browse/AMQ-3859 Project: ActiveMQ Issue Type: Improvement Affects Versions: 5.6.0 Reporter: Claus Ibsen Fix For: 5.7.0 See the feature file https://issues.apache.org/jira/browse/KARAF-1497?focusedCommentId=13282170#comment-13282170 Notice that the activemq-camel feature is hardcoded to 2.9.2 version of Camel {code:xml} &lt;feature name="activemq-camel" version="5.6.0" resolver="(obr)"&gt; &lt;feature version="5.6.0"&gt;activemq&lt;/feature&gt; &lt;feature version="2.9.2"&gt;camel-jms&lt;/feature&gt; &lt;bundle&gt;mvn:org.apache.activemq/activemq-camel/5.6.0&lt;/bundle&gt; &lt;/feature&gt; {code} That should be a version range IMHO. But I can't remember if Karaf supports this. But basically it should be something alike, if supported by Karaf: &lt;feature version="[2.9,3)"&gt;camel-jms&lt;/feat</pre> Claus Ibsen (JIRA 2012-05-24T04:12:40 http://comments.gmane.org/gmane.comp.java.activemq.devel/31797 <pre>Helen Huang created AMQCPP-405: ---------------------------------- Summary: CMS sender thread hangs after restarting broker Key: AMQCPP-405 URL: https://issues.apache.org/jira/browse/AMQCPP-405 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: Critical Fix For: 3.4.1 The sender thread in CMS hangs after we retarted the message broker. The thread is 548 in the attached dump file. This is a critical issue that blocks the release of our product that is scheduled in a few days. We hope you can resolve it soon. Really appreciate your help! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: </pre> Helen Huang (JIRA 2012-05-23T22:01:43 http://comments.gmane.org/gmane.comp.java.activemq.devel/31795 <pre>See &lt;https://builds.apache.org/job/ActiveMQ/964/changes&gt; </pre> Apache Jenkins Server 2012-05-23T20:35:00 http://comments.gmane.org/gmane.comp.java.activemq.devel/31790 <pre>Gary Tully created AMQ-3858: ------------------------------- Summary: Failure to resolve local jmx url for sunJvm can result in npe Key: AMQ-3858 URL: https://issues.apache.org/jira/browse/AMQ-3858 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.6.0 Reporter: Gary Tully Fix For: 5.7.0 calls to ./bin/activemq restart can result in this NPE which is ugly. It should fallback to the default jmxurl in this case. {code}Connecting to pid: 47706 ERROR: java.lang.NullPointerException java.lang.NullPointerException at javax.management.remote.JMXServiceURL.&lt;init&gt;(JMXServiceURL.java:122) at org.apache.activemq.console.command.AbstractJmxCommand.handleOption(AbstractJmxCommand.java:350) at org.apache.activemq.console.command.ShutdownCommand.handleOption(ShutdownCommand.java:156) at org.apache.activemq.console.command.AbstractCommand.parseOptions(AbstractCommand.java:73) at org.apache.ac</pre> Gary Tully (JIRA 2012-05-23T15:54:40 http://comments.gmane.org/gmane.comp.java.activemq.devel/31785 <pre>Hi, Disclaimer: I am not really a Java dev. I've obtained the latest source from SVN, built it using mvn command line. Then I generated the eclipse metadata using eclipse:eclipse. It was a hassle, but only because of my corporate proxy (had to keep refreshing the repository URLs in Internet Explorer otherwise Maven was being kicked with a 407 by the proxy). Once I got the eclipse projects imported, I successfully built. I tried setting up a run configuration that executes the console Main class with parameter "start". This failed initially because of missing resources ("activemq.xsd"). I found that enabling maven dependency management on all projects rectified this. Next problem I get is this whilst attempting to run: &lt;snip&gt;j Caused by: java.lang.ClassNotFoundException: org.springframework.beans.BeansException Checking the CLASSPATH, I see why: a lot of JARs including spring-beans aren't on it. Looking in maven's dependency tree and pom.xml I see why: &lt;dependency&gt; &lt;groupId&gt;org.sprin</pre> gauche 2012-05-23T07:28:21 http://comments.gmane.org/gmane.comp.java.activemq.devel/31782 <pre>Alan Hudson created AMQ-3857: -------------------------------- Summary: MessageServlet get messages does not return JMS Message Properties Key: AMQ-3857 URL: https://issues.apache.org/jira/browse/AMQ-3857 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.6.0, 5.5.0 Reporter: Alan Hudson When using GET to get a message it does not return any of the JMS message properties. I can easily see how to add that code, but I'm not sure what the correct way to return them is. They could go into the response headers via setResponseHeaders or the returned XML format could be changed to support properties and the header. Sadly this would likely break most existing clients. We'd like to use the REST API to enable some web clients to fully participate in a messaging system that is primarily Java based. If we can come to agreement on how we want to return properties then I'd be happy to code up a</pre> Alan Hudson (JIRA 2012-05-23T00:22:40 http://comments.gmane.org/gmane.comp.java.activemq.devel/31781 <pre>Alan Hudson created AMQ-3856: -------------------------------- Summary: MessageServlet assumes TextMessages contain Text Key: AMQ-3856 URL: https://issues.apache.org/jira/browse/AMQ-3856 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.6.0, 5.5.1 Environment: all Reporter: Alan Hudson Fix For: 5.7.0 writeMessageResponse assumes that a text message will contain non null text. It does a txt.startsWith which crashes with TextMessages with no body. It can be fixed with this code: protected void writeMessageResponse(PrintWriter writer, Message message) throws JMSException, IOException { if (message instanceof TextMessage) { TextMessage textMsg = (TextMessage)message; String txt = textMsg.getText(); if (txt != null) { if (txt.startsWith("&lt;?")) { txt = txt.substring(txt.inde</pre> Alan Hudson (JIRA 2012-05-22T21:56:41 http://comments.gmane.org/gmane.comp.java.activemq.devel/31780 <pre>I have the SVN anonymous check-out and imported into IntelliJ. Trying to build but apparently the following package is not found: import org.apache.activemq.selector.SelectorParser; When I look, all I find is an activemq &gt; selector &gt; Package.html whereas the other packages have .java source files. Not sure what I've missed at this point. Please advise. James </pre> James Green 2012-05-22T20:27:27 http://comments.gmane.org/gmane.comp.java.activemq.devel/31774 <pre> [ https://issues.apache.org/jira/browse/AMQ-873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=13281046#comment-13281046 ] Donnchadh Ó Donnabháin commented on AMQ-873: -------------------------------------------- See https://queue.acm.org/detail.cfm?id=2209336 and http://www.rabbitmq.com/blog/2012/05/11/some-queuing-theory-throughput-latency-and-bandwidth/ . -- 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> Donnchadh Ó Donnabháin (JIRA 2012-05-22T15:44:42 http://comments.gmane.org/gmane.comp.java.activemq.devel/31771 <pre>Rob Davies created AMQ-3855: ------------------------------- Summary: MQTT doesn't translate wildcards to ActiveMQ wildcards Key: AMQ-3855 URL: https://issues.apache.org/jira/browse/AMQ-3855 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.6.0 Reporter: Rob Davies Assignee: Rob Davies Fix For: 5.7.0 Currently, subscribing to ActiveMQ JMS messages over MQTT won't work if you do foo/+ you would expect to receive a JMS or STOMP message sent to foo.bar. -- 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> Rob Davies (JIRA 2012-05-22T15:23:40 http://comments.gmane.org/gmane.comp.java.activemq.devel/31767 <pre>Andreas Ländle created AMQNET-384: ------------------------------------- Summary: Configuration of wireFormat via URL doesn't work Key: AMQNET-384 URL: https://issues.apache.org/jira/browse/AMQNET-384 Project: ActiveMQ .Net Issue Type: Bug Components: Stomp Affects Versions: 1.5.2 Reporter: Andreas Ländle Assignee: Jim Gomes The configuration of the STOMP wireformat doesn't work as described here: http://activemq.apache.org/nms/stomp-uri-configuration.html (btw: there is a type 'wireFormat.maxInactivityDurationInitalDelay' - the second 'i' in 'Inital' is missing). If you take a look in TcpTransportFactory.cs lines 118-120 it's obvious - the class StompWireFormat simple has no fields/properties named 'maxInactivityDuration' or 'maxInactivityDurationInitialDelay'. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: http</pre> Andreas Ländle (JIRA 2012-05-22T12:12:42 http://comments.gmane.org/gmane.comp.java.activemq.devel/31759 <pre>Dejan Bosanac created AMQ-3854: ---------------------------------- Summary: Referencing old spring xsd in configuration files Key: AMQ-3854 URL: https://issues.apache.org/jira/browse/AMQ-3854 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.6.0 Reporter: Dejan Bosanac Just noticed that we still reference http://www.springframework.org/schema/beans/spring-beans-2.0.xsd in config files although we upgraded to 3.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> Dejan Bosanac (JIRA 2012-05-21T15:22:40 http://comments.gmane.org/gmane.comp.java.activemq.devel/31754 <pre>Chris Geer created AMQ-3853: ------------------------------- Summary: Missing import in activemq-web-console Key: AMQ-3853 URL: https://issues.apache.org/jira/browse/AMQ-3853 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.6.0 Reporter: Chris Geer Running activemq-web-console in Karaf generates these errors: Caused by: java.lang.ClassNotFoundException: javax.servlet.ServletContextListener not found by org.apache.activemq.activemq-web-console [118] Caused by: java.lang.ClassNotFoundException: javax.servlet.Filter not found by org.apache.activemq.activemq-web-console [118] Caused by: java.lang.ClassNotFoundException: javax.servlet.http.HttpServlet not found by org.apache.activemq.activemq-web-console [118] It looks like activemq-web-console imports the following servlet packages: javax.servlet.jsp;version="[2.1,3)", javax.servlet.jsp.el;version="[2.1,3)", javax.servlet.jsp.tagext;version="[2.1,3)", So</pre> Chris Geer (JIRA 2012-05-20T23:35:41 http://comments.gmane.org/gmane.comp.java.activemq.devel/31753 <pre>James Green created AMQ-3852: -------------------------------- Summary: Stomp transport allows durable topic subscriber to subscribe to a queue Key: AMQ-3852 URL: https://issues.apache.org/jira/browse/AMQ-3852 Project: ActiveMQ Issue Type: Bug Components: stomp Affects Versions: 5.5.0 Reporter: James Green Priority: Minor See also AMQ-2879 the stack-trace to which recently re-emerged in our production logs. The issue was traced to a developer having copy-pasted some PHP script that created a durable topic subscriber but in his clone he subscribed to a queue not a topic. He wasn't to know... Question is how to prevent clients getting into this situation. Can the transport disconnect the client and log an error to the console, or must it allow the connection, potentially lulling the client developer into a false sense of functioning code? Might also want to review the documentation and potentially t</pre> James Green (JIRA 2012-05-20T19:25:40 http://comments.gmane.org/gmane.comp.java.activemq.devel/31735 <pre>Chris Robison created AMQ-3851: ---------------------------------- Summary: Infinite TemqQueue advisory messages Key: AMQ-3851 URL: https://issues.apache.org/jira/browse/AMQ-3851 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.6.0 Reporter: Chris Robison I'm seeing a behavior that looks like a race condition of some kind. I have two brokers (MSSD5D101, MSTMIP103). MSSD5D101 has a duplex network connector connecting it to MSTMIP103. The two machines are in different US states so there is a VPN in between. I have two consumer services that reply to queued messages. One consumer (WISD5P101) connects to MSSD5D101 and the other consumer (POSD5P101) connects to MSTMIP103. I also have a web portal that sends messages out to different queues expecting a response. The web portal, and two consumers are all .NET based. What is happening is that after some number of messages, something goes crazy</pre> Chris Robison (JIRA 2012-05-18T20:59:12 http://comments.gmane.org/gmane.comp.java.activemq.devel/31732 <pre>Michal Troicki created AMQ-3850: ----------------------------------- Summary: Missing org.apache.activemq.pool.PooledConnectionFactory Key: AMQ-3850 URL: https://issues.apache.org/jira/browse/AMQ-3850 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.6.0 Environment: Activemq 5.6.0 Reporter: Michal Troicki Missing org.apache.activemq.pool.PooledConnectionFactory in 5.6.0 release. -- 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> Michal Troicki (JIRA 2012-05-18T19:45:07 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.java.activemq.devel