[jira] Updated: (QPID-2273) Java client can't negotiate to 0-9
[ https://issues.apache.org/jira/browse/QPID-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-2273: -- Attachment: (was: protocol_negotiation_madness.diff) Java client can't negotiate to 0-9 -- Key: QPID-2273 URL: https://issues.apache.org/jira/browse/QPID-2273 Project: Qpid Issue Type: Bug Components: Java Client Affects Versions: 0.6 Reporter: Aidan Skinner Assignee: Aidan Skinner Priority: Blocker Fix For: 0.6 Attachments: 0001-QPID-2273-make-protocol-negotiation-saner.patch, protocol_negotiation_madness_2.diff For instance, if you try connecting a trunk client to a 0.5 broker it fails. This is due to the delegate using the wrong ProtocolVersion. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2273) Java client can't negotiate to 0-9
[ https://issues.apache.org/jira/browse/QPID-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-2273: -- Attachment: protocol_negotiation_madness_2.diff Updated patch with the correct 091 negotiation in... Passed the Rabbit and standalone Java tests for me Java client can't negotiate to 0-9 -- Key: QPID-2273 URL: https://issues.apache.org/jira/browse/QPID-2273 Project: Qpid Issue Type: Bug Components: Java Client Affects Versions: 0.6 Reporter: Aidan Skinner Assignee: Aidan Skinner Priority: Blocker Fix For: 0.6 Attachments: 0001-QPID-2273-make-protocol-negotiation-saner.patch, protocol_negotiation_madness_2.diff For instance, if you try connecting a trunk client to a 0.5 broker it fails. This is due to the delegate using the wrong ProtocolVersion. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-2289) Copy constructor for qpid::messaging::Message does not copy headers etc
[ https://issues.apache.org/jira/browse/QPID-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-2289. -- Resolution: Fixed Fixed by r891636. Copy constructor for qpid::messaging::Message does not copy headers etc --- Key: QPID-2289 URL: https://issues.apache.org/jira/browse/QPID-2289 Project: Qpid Issue Type: Bug Components: C++ Client Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.6 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-2290) Unauthorised-access exception raised when sending message from JMS on connection authenticated using PLAIN mechanism
Unauthorised-access exception raised when sending message from JMS on connection authenticated using PLAIN mechanism - Key: QPID-2290 URL: https://issues.apache.org/jira/browse/QPID-2290 Project: Qpid Issue Type: Bug Components: C++ Broker Reporter: Gordon Sim Priority: Blocker Email from prat...@adobe.com on user list states: when I enable auth=yes, I get the following: 2009-12-16 18:33:18 error qpid/amqp_0_10/SessionHandler.cpp:97: Execution exception: unauthorized-access: authorised user id : prat...@qpid but user id in message decla red as prattrs (qpid/broker/SemanticState.cpp:435) I believe this is a result of the change brought in by r819819 to address QPID-2129. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-1830) BytesMessage is unreadable
[ https://issues.apache.org/jira/browse/QPID-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12791902#action_12791902 ] Aidan Skinner commented on QPID-1830: - I don't think dumping the data in toString is necessarily the right thing, particularly for a byte message that might contain all manner of control characters etc. From http://java.sun.com/j2se/1.4.2/docs/api/java/lang/Object.html#toString%28%29 it says textually represent, how about byte message message-id of size bytes ? BytesMessage is unreadable -- Key: QPID-1830 URL: https://issues.apache.org/jira/browse/QPID-1830 Project: Qpid Issue Type: Bug Components: Java Client Affects Versions: 0.6, 0.7 Reporter: Aidan Skinner Assignee: Rajith Attapattu Priority: Critical Fix For: 0.6 This can easily be seen running the interop coordinator: 2009-04-28 14:24:38,377 INFO [main] distributedtesting.Coordinator (Coordinator.java:285) - Found distributed test case: org.apache.qpid.interop.testcases.InteropTestCase4P2PMessageSize javax.jms.MessageNotReadableException: You need to call reset() to make the message readable at org.apache.qpid.client.message.AbstractJMSMessage.checkReadable(AbstractJMSMessage.java:433) at org.apache.qpid.client.message.AbstractBytesMessage.toBodyString(AbstractBytesMessage.java:89) at org.apache.qpid.client.message.AbstractJMSMessage.toString(AbstractJMSMessage.java:371) at java.lang.String.valueOf(String.java:2827) at java.lang.StringBuilder.append(StringBuilder.java:115) at org.apache.qpid.test.utils.ConversationFactory$Conversation.send(ConversationFactory.java:263) at org.apache.qpid.test.framework.distributedtesting.Coordinator.start(Coordinator.java:366) at org.apache.qpid.test.framework.distributedtesting.Coordinator.main(Coordinator.java:315) 2009-04-28 14:24:39,690 INFO [main] distributedtesting.Coordinator (Coordinator.java:330) - javax.jms.MessageNotReadableException: You need to call reset() to make the message readable java.lang.RuntimeException: javax.jms.MessageNotReadableException: You need to call reset() to make the message readable at org.apache.qpid.client.message.AbstractJMSMessage.toString(AbstractJMSMessage.java:407) at java.lang.String.valueOf(String.java:2827) at java.lang.StringBuilder.append(StringBuilder.java:115) at org.apache.qpid.test.utils.ConversationFactory$Conversation.send(ConversationFactory.java:263) at org.apache.qpid.test.framework.distributedtesting.Coordinator.start(Coordinator.java:366) at org.apache.qpid.test.framework.distributedtesting.Coordinator.main(Coordinator.java:315) Caused by: javax.jms.MessageNotReadableException: You need to call reset() to make the message readable at org.apache.qpid.client.message.AbstractJMSMessage.checkReadable(AbstractJMSMessage.java:433) at org.apache.qpid.client.message.AbstractBytesMessage.toBodyString(AbstractBytesMessage.java:89) at org.apache.qpid.client.message.AbstractJMSMessage.toString(AbstractJMSMessage.java:371) ... 5 more This works on the 0.5-release branch, so is presumably a recentish break. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: 0.6 Release Plans from now onwards
Hi Andrew, Thanks for the update. I've been trying to wade through code reviews/tidy ups to get the JIRAs in a better state. Anyone willing to pitch in on the Java reviews would be much appreciated. Marnie On Tue, Dec 15, 2009 at 10:26 PM, Andrew Stitcher astitc...@redhat.comwrote: As I said in my beta release message I'd like to produce a release candidate at the end of this week. On the closing bugs front there are a couple of issues still (but nothing that looks deadly as far as I can tell): Essentially we have 2 blockers and 2 critical bugs. 2 Java bugs and 2 bugs for the WCF code. QPID-2273 (http://issues.apache.org/jira/browse/QPID-2273), QPID-1830 (http://issues.apache.org/jira/browse/QPID-1830) - Aidan can you give some status on these bugs? Are they going to be finished in the next couple of days? Is there much risk in the fixes? QPID-2260 (http://issues.apache.org/jira/browse/QPID-2260), QPID-2247 (http://issues.apache.org/jira/browse/QPID-2247) - These are more problematic as they don't have anyone assigned to them. It could be that Cliff is working on them, but as he isn't a commiter he can't be assigned the bugs in Jira. Cliff can you comment on these bugs? Are they truly as important as blocker/critical? If so unless there are patches attached to the jiras very soon I think we'll have to omit the specific WCF source code from this release (of course it will still be in the big source tarball). To be honest I'm really sure it's quite mature enough in any case. Assuming that we can clear these issues up (one way or another) in the next couple of days - I plan to release rc1 on Thursday/Friday this week. I will create a (preemptive) subversion tag at that point. From that point I'd like to *freeze* checkins to the tree for 2 weeks taking us effectively to the new year. If we haven't actually voted to release by then I suggest we move the branch tag to whatever the most recent qpid checkin is and do all subsequent release work on a branch, and unfreeze the trunk. This way we should have the minimum frozen time and still be able to progress. Regards Andrew - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Sender flow control via resource-limit-exceeded
Andrew Stitcher wrote: On Wed, 2009-12-16 at 09:56 -0500, Alan Conway wrote: I'm looking at some code that does sender flow control as follows: - set a queue size limit - sender catches 'resource-limit-exceeded' exception, sleeps for a bit, creates a new session re-tries The essential problem with this approach is that the queue size is not directly caused by any single producer. So it's entirely possible in general for a producer that is producing at a low rate to be entirely killed by another producer sending messages into the same queue. The only way that this overall scheme can work fairly is if there is a 1-1 producer-queue mapping. If that is the case then it should work. Why wouldn't we use flow control as specified by the protocol? It doesn't help you figure out *who* to flow control, but once you've made that decision, it provides a much better way to actually flow control an individual producer. --Rafael - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-1830) BytesMessage is unreadable
[ https://issues.apache.org/jira/browse/QPID-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12791941#action_12791941 ] Rajith Attapattu commented on QPID-1830: Control characters are properly handled and we only print the first 100 bytes. We also print all the headers. Just printing the message id is not enough for debugging etc. As I mentioned the checkReadable() could be removed from the toBodyString(). **It will solve the problem**. BytesMessage is unreadable -- Key: QPID-1830 URL: https://issues.apache.org/jira/browse/QPID-1830 Project: Qpid Issue Type: Bug Components: Java Client Affects Versions: 0.6, 0.7 Reporter: Aidan Skinner Assignee: Rajith Attapattu Priority: Critical Fix For: 0.6 This can easily be seen running the interop coordinator: 2009-04-28 14:24:38,377 INFO [main] distributedtesting.Coordinator (Coordinator.java:285) - Found distributed test case: org.apache.qpid.interop.testcases.InteropTestCase4P2PMessageSize javax.jms.MessageNotReadableException: You need to call reset() to make the message readable at org.apache.qpid.client.message.AbstractJMSMessage.checkReadable(AbstractJMSMessage.java:433) at org.apache.qpid.client.message.AbstractBytesMessage.toBodyString(AbstractBytesMessage.java:89) at org.apache.qpid.client.message.AbstractJMSMessage.toString(AbstractJMSMessage.java:371) at java.lang.String.valueOf(String.java:2827) at java.lang.StringBuilder.append(StringBuilder.java:115) at org.apache.qpid.test.utils.ConversationFactory$Conversation.send(ConversationFactory.java:263) at org.apache.qpid.test.framework.distributedtesting.Coordinator.start(Coordinator.java:366) at org.apache.qpid.test.framework.distributedtesting.Coordinator.main(Coordinator.java:315) 2009-04-28 14:24:39,690 INFO [main] distributedtesting.Coordinator (Coordinator.java:330) - javax.jms.MessageNotReadableException: You need to call reset() to make the message readable java.lang.RuntimeException: javax.jms.MessageNotReadableException: You need to call reset() to make the message readable at org.apache.qpid.client.message.AbstractJMSMessage.toString(AbstractJMSMessage.java:407) at java.lang.String.valueOf(String.java:2827) at java.lang.StringBuilder.append(StringBuilder.java:115) at org.apache.qpid.test.utils.ConversationFactory$Conversation.send(ConversationFactory.java:263) at org.apache.qpid.test.framework.distributedtesting.Coordinator.start(Coordinator.java:366) at org.apache.qpid.test.framework.distributedtesting.Coordinator.main(Coordinator.java:315) Caused by: javax.jms.MessageNotReadableException: You need to call reset() to make the message readable at org.apache.qpid.client.message.AbstractJMSMessage.checkReadable(AbstractJMSMessage.java:433) at org.apache.qpid.client.message.AbstractBytesMessage.toBodyString(AbstractBytesMessage.java:89) at org.apache.qpid.client.message.AbstractJMSMessage.toString(AbstractJMSMessage.java:371) ... 5 more This works on the 0.5-release branch, so is presumably a recentish break. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Could we please exclude the following tests until they are fixed?
Looks like there are no objections so far :). So unless somebody screams in the next few hours, I am going to add these tests to the exclude lists by the end of the day. Rajith On Wed, Dec 16, 2009 at 4:07 PM, Rajith Attapattu rajit...@gmail.com wrote: The following tests exhibits randomly failures for the last 2 months or so. Would anybody object if we add those tests (temporarily) to the exclude lists until they are properly fixed ? We need to ensure our builds are green and if we continue to have random failures we run the risk of people ignoring them after a while. And in some cases a genuine test failure may escape our attention due to this. FailoverBeforeConsumingRecoverTest QPID-2225 SimpleACLTest.testClientPublishInvalidQueueSuccess - QPID-2262 MINANetworkDriverTest - QPID-2224 Regards, Rajith Attapattu Red Hat http://rajith.2rlabs.com/ -- Regards, Rajith Attapattu Red Hat http://rajith.2rlabs.com/ - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-2279) Removal of trivial unused stuff
[ https://issues.apache.org/jira/browse/QPID-2279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved QPID-2279. --- Resolution: Fixed Removal of trivial unused stuff --- Key: QPID-2279 URL: https://issues.apache.org/jira/browse/QPID-2279 Project: Qpid Issue Type: Improvement Components: C++ Broker, C++ Client Reporter: Andrew Stitcher Assignee: Andrew Stitcher Priority: Trivial Fix For: 0.6 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2029) Clustering and Management don't work well together
[ https://issues.apache.org/jira/browse/QPID-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated QPID-2029: -- Fix Version/s: (was: 0.6) 0.7 Clustering and Management don't work well together -- Key: QPID-2029 URL: https://issues.apache.org/jira/browse/QPID-2029 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.5 Reporter: Ted Ross Assignee: Ted Ross Fix For: 0.7 Several aspects of management of the C++ broker are not well integrated with clustering. 1) object-ids assigned to management objects are not synchronized across nodes of a cluster. 2) persistent object-ids are not synchronized across nodes of a cluster. 3) cached data within the QMF broker are not synchronized. 4) next-object-id and reboot-sequence are not synchronized. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-500) Fix public API to match standard .NET Conventions
[ https://issues.apache.org/jira/browse/QPID-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-500. Resolution: Fixed This is as done as it's gonna get. Nobody should use the 0-8 impl for new work really... Fix public API to match standard .NET Conventions - Key: QPID-500 URL: https://issues.apache.org/jira/browse/QPID-500 Project: Qpid Issue Type: Improvement Components: Dot Net Client Affects Versions: M2, M2.1, M3, M4, 0.5, 0.6 Reporter: Tomas Restrepo Assignee: Aidan Skinner Fix For: 0.6 Attachments: QPID-500.diff Currently the public API of the .NET client is mixture of the original Java Client JMS-Based API and some .NET specific functionality. This makes the API be very inconvenient to use for a .NET developer and feel very unnatural (while still not being faithful to the original Java API). Proposed changes: - Make public delegates used in message consumers and connection exceptions into proper events that use signatures matcing the .NET guidelines. - Make naming of public classes consistent (i.e. AmqChannel - AMQChannel) - Ensure that the IConnection interface contains all useful methods and properties in AMQConnection to make it easier to code to the interface and not the implementation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-2128) Transaction support for the WCF channel
[ https://issues.apache.org/jira/browse/QPID-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Huston resolved QPID-2128. Resolution: Fixed Patches QPID-2128-2.patch, cppbld.patch and interop.tx.patch applied to trunk r891783. Transaction support for the WCF channel --- Key: QPID-2128 URL: https://issues.apache.org/jira/browse/QPID-2128 Project: Qpid Issue Type: New Feature Components: WCF/C++ Client Affects Versions: 0.6 Environment: Windows Reporter: Cliff Jansen Assignee: Steve Huston Priority: Critical Fix For: 0.6 Attachments: cppbld.patch, interop.tx.patch, QPID-2128-2.patch, qpid2128_1.patch, wcfbld.patch Transaction support is currently lacking from the WCF channel. As an initial implementation, full distributed transaction support from within .NET is proposed using the dtx AMQP classes and creating a plugin to the MSDTC infrastructure to drive recovery. Added performance from promotable transaction enlistment is deferred to a later date. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-2291) WCF channel tests fixed on NUnit 2.5.2
WCF channel tests fixed on NUnit 2.5.2 -- Key: QPID-2291 URL: https://issues.apache.org/jira/browse/QPID-2291 Project: Qpid Issue Type: Bug Components: WCF/C++ Client Affects Versions: 0.6 Environment: Windows, Visual Studio 2008, NUnit 2.5.3 Reporter: Steve Huston Assignee: Steve Huston Priority: Minor Fix For: 0.6 The Channel Functional tests refer specifically to NUnit 2.5.2, preventing its use with, say, NUnit 2.5.3. The specific NUnit version number need not be specified. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2291) WCF channel tests fixed on NUnit 2.5.2
[ https://issues.apache.org/jira/browse/QPID-2291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Huston updated QPID-2291: --- Attachment: QPID-2291.patch Patch for review. WCF channel tests fixed on NUnit 2.5.2 -- Key: QPID-2291 URL: https://issues.apache.org/jira/browse/QPID-2291 Project: Qpid Issue Type: Bug Components: WCF/C++ Client Affects Versions: 0.6 Environment: Windows, Visual Studio 2008, NUnit 2.5.3 Reporter: Steve Huston Assignee: Steve Huston Priority: Minor Fix For: 0.6 Attachments: QPID-2291.patch The Channel Functional tests refer specifically to NUnit 2.5.2, preventing its use with, say, NUnit 2.5.3. The specific NUnit version number need not be specified. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Qpid dont save durable queues
Hi, I'm running qpidd-0.5 at CentOS 5 x86_64 and I'm trying to configure durable queues, I make the commands but when restart the service, the information was lost. The daemon is running with root user, I tought was a fs permission thing, but isnt this. qpid-config add exchange topic foo.topic --durable qpid-config add queue foo01 --durable --order lvq qpid-config --durable bind foo.topic foo01 foo.information.* Some tip about this behavior ? Thanks,
Re: Qpid dont save durable queues
Rodrigo K. Ferreira wrote: Hi, I'm running qpidd-0.5 at CentOS 5 x86_64 and I'm trying to configure durable queues, I make the commands but when restart the service, the information was lost. The daemon is running with root user, I tought was a fs permission thing, but isnt this. qpid-config add exchange topic foo.topic --durable qpid-config add queue foo01 --durable --order lvq qpid-config --durable bind foo.topic foo01 foo.information.* Some tip about this behavior ? Thanks, You need to load a store, there is one on trunk for windows and for linux you can pick it up here: http://qpidcomponents.org/ Carl. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
RE: Qpid dont save durable queues
I'm running qpidd-0.5 at CentOS 5 x86_64 and I'm trying to configure durable queues, I make the commands but when restart the service, the information was lost. The daemon is running with root user, I tought was a fs permission thing, but isnt this. qpid-config add exchange topic foo.topic --durable qpid-config add queue foo01 --durable --order lvq qpid-config --durable bind foo.topic foo01 foo.information.* Some tip about this behavior ? Did you build and load the store module? -Steve -- Steve Huston, Riverace Corporation Total Lifecycle Support for Your Networked Applications http://www.riverace.com - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Assigned: (QPID-2290) Unauthorised-access exception raised when sending message from JMS on connection authenticated using PLAIN mechanism
[ https://issues.apache.org/jira/browse/QPID-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher reassigned QPID-2290: - Assignee: Ted Ross Could you look at this and form an opinion whther the fix for QPID-2129 is the underlying cause. As we are in release mode the sooner the better! Unauthorised-access exception raised when sending message from JMS on connection authenticated using PLAIN mechanism - Key: QPID-2290 URL: https://issues.apache.org/jira/browse/QPID-2290 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.6 Reporter: Gordon Sim Assignee: Ted Ross Priority: Blocker Fix For: 0.6 Email from prat...@adobe.com on user list states: when I enable auth=yes, I get the following: 2009-12-16 18:33:18 error qpid/amqp_0_10/SessionHandler.cpp:97: Execution exception: unauthorized-access: authorised user id : prat...@qpid but user id in message decla red as prattrs (qpid/broker/SemanticState.cpp:435) I believe this is a result of the change brought in by r819819 to address QPID-2129. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-2292) the Message class is missing some properties, e.g. the redelivered flag
the Message class is missing some properties, e.g. the redelivered flag --- Key: QPID-2292 URL: https://issues.apache.org/jira/browse/QPID-2292 Project: Qpid Issue Type: Bug Affects Versions: 0.6 Reporter: Rafael H. Schloming Assignee: Rafael H. Schloming Fix For: 0.6 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-2230) Interoperability test for binary and text messages
[ https://issues.apache.org/jira/browse/QPID-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Huston resolved QPID-2230. Resolution: Fixed Assignee: Steve Huston Patch applied to trunk r891795. Interoperability test for binary and text messages -- Key: QPID-2230 URL: https://issues.apache.org/jira/browse/QPID-2230 Project: Qpid Issue Type: Test Components: WCF/C++ Client Affects Versions: M4 Environment: Windows WCF client Reporter: Cliff Jansen Assignee: Steve Huston Fix For: 0.6 Attachments: QPID-2230.patch A program to test the interoperability of the WCF client and the C++ client would be useful. This would include text and binary data as a first step towards QPID-2226 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Assigned: (QPID-1864) java 0-10 client sometimes releases messages in non queue order on rollback
[ https://issues.apache.org/jira/browse/QPID-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher reassigned QPID-1864: - Assignee: Martin Ritchie (was: Rafael H. Schloming) It's unclear what the current state of this is or whether there are any separate Jiras linked from this java 0-10 client sometimes releases messages in non queue order on rollback --- Key: QPID-1864 URL: https://issues.apache.org/jira/browse/QPID-1864 Project: Qpid Issue Type: Bug Components: Java Client Affects Versions: 0.6 Reporter: Rafael H. Schloming Assignee: Martin Ritchie Fix For: 0.7 Attachments: TEST-org.apache.qpid.test.client.RollbackOrderTest.testOrderingAfterRollback.out On rollback, the java client sometimes releases messages from the dispatch thread. These messages are released in an unpredictable order relative to the messages released from the main thread. Also, the messages released from the BMC.rollbackPendingMessages() are released individually and in the opposite order of what would preserve queue order in a single consumer scenario. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-1864) java 0-10 client sometimes releases messages in non queue order on rollback
[ https://issues.apache.org/jira/browse/QPID-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated QPID-1864: -- Fix Version/s: (was: 0.6) 0.7 java 0-10 client sometimes releases messages in non queue order on rollback --- Key: QPID-1864 URL: https://issues.apache.org/jira/browse/QPID-1864 Project: Qpid Issue Type: Bug Components: Java Client Affects Versions: 0.6 Reporter: Rafael H. Schloming Assignee: Martin Ritchie Fix For: 0.7 Attachments: TEST-org.apache.qpid.test.client.RollbackOrderTest.testOrderingAfterRollback.out On rollback, the java client sometimes releases messages from the dispatch thread. These messages are released in an unpredictable order relative to the messages released from the main thread. Also, the messages released from the BMC.rollbackPendingMessages() are released individually and in the opposite order of what would preserve queue order in a single consumer scenario. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Assigned: (QPID-2290) Unauthorised-access exception raised when sending message from JMS on connection authenticated using PLAIN mechanism
[ https://issues.apache.org/jira/browse/QPID-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu reassigned QPID-2290: -- Assignee: Rajith Attapattu (was: Ted Ross) Unauthorised-access exception raised when sending message from JMS on connection authenticated using PLAIN mechanism - Key: QPID-2290 URL: https://issues.apache.org/jira/browse/QPID-2290 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.6 Reporter: Gordon Sim Assignee: Rajith Attapattu Priority: Blocker Fix For: 0.6 Email from prat...@adobe.com on user list states: when I enable auth=yes, I get the following: 2009-12-16 18:33:18 error qpid/amqp_0_10/SessionHandler.cpp:97: Execution exception: unauthorized-access: authorised user id : prat...@qpid but user id in message decla red as prattrs (qpid/broker/SemanticState.cpp:435) I believe this is a result of the change brought in by r819819 to address QPID-2129. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-1830) BytesMessage is unreadable
[ https://issues.apache.org/jira/browse/QPID-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu resolved QPID-1830. Resolution: Fixed I have committed a fix at rev 891805 on Qpid trunk. The checkReadable() is removed from the toBodyString() allowing the toString() to be called anytime. If there is no content an empty string is printed. BytesMessage is unreadable -- Key: QPID-1830 URL: https://issues.apache.org/jira/browse/QPID-1830 Project: Qpid Issue Type: Bug Components: Java Client Affects Versions: 0.6, 0.7 Reporter: Aidan Skinner Assignee: Rajith Attapattu Priority: Critical Fix For: 0.6 This can easily be seen running the interop coordinator: 2009-04-28 14:24:38,377 INFO [main] distributedtesting.Coordinator (Coordinator.java:285) - Found distributed test case: org.apache.qpid.interop.testcases.InteropTestCase4P2PMessageSize javax.jms.MessageNotReadableException: You need to call reset() to make the message readable at org.apache.qpid.client.message.AbstractJMSMessage.checkReadable(AbstractJMSMessage.java:433) at org.apache.qpid.client.message.AbstractBytesMessage.toBodyString(AbstractBytesMessage.java:89) at org.apache.qpid.client.message.AbstractJMSMessage.toString(AbstractJMSMessage.java:371) at java.lang.String.valueOf(String.java:2827) at java.lang.StringBuilder.append(StringBuilder.java:115) at org.apache.qpid.test.utils.ConversationFactory$Conversation.send(ConversationFactory.java:263) at org.apache.qpid.test.framework.distributedtesting.Coordinator.start(Coordinator.java:366) at org.apache.qpid.test.framework.distributedtesting.Coordinator.main(Coordinator.java:315) 2009-04-28 14:24:39,690 INFO [main] distributedtesting.Coordinator (Coordinator.java:330) - javax.jms.MessageNotReadableException: You need to call reset() to make the message readable java.lang.RuntimeException: javax.jms.MessageNotReadableException: You need to call reset() to make the message readable at org.apache.qpid.client.message.AbstractJMSMessage.toString(AbstractJMSMessage.java:407) at java.lang.String.valueOf(String.java:2827) at java.lang.StringBuilder.append(StringBuilder.java:115) at org.apache.qpid.test.utils.ConversationFactory$Conversation.send(ConversationFactory.java:263) at org.apache.qpid.test.framework.distributedtesting.Coordinator.start(Coordinator.java:366) at org.apache.qpid.test.framework.distributedtesting.Coordinator.main(Coordinator.java:315) Caused by: javax.jms.MessageNotReadableException: You need to call reset() to make the message readable at org.apache.qpid.client.message.AbstractJMSMessage.checkReadable(AbstractJMSMessage.java:433) at org.apache.qpid.client.message.AbstractBytesMessage.toBodyString(AbstractBytesMessage.java:89) at org.apache.qpid.client.message.AbstractJMSMessage.toString(AbstractJMSMessage.java:371) ... 5 more This works on the 0.5-release branch, so is presumably a recentish break. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Qpid dont save durable queues
mmm... is that... I'm working in compile that module. Thanks a lot. On Thu, Dec 17, 2009 at 2:32 PM, Steve Huston shus...@riverace.com wrote: I'm running qpidd-0.5 at CentOS 5 x86_64 and I'm trying to configure durable queues, I make the commands but when restart the service, the information was lost. The daemon is running with root user, I tought was a fs permission thing, but isnt this. qpid-config add exchange topic foo.topic --durable qpid-config add queue foo01 --durable --order lvq qpid-config --durable bind foo.topic foo01 foo.information.* Some tip about this behavior ? Did you build and load the store module? -Steve -- Steve Huston, Riverace Corporation Total Lifecycle Support for Your Networked Applications http://www.riverace.com - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:users-subscr...@qpid.apache.org
[jira] Updated: (QPID-2292) the Message class is missing some properties, e.g. the redelivered flag
[ https://issues.apache.org/jira/browse/QPID-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming updated QPID-2292: -- Component/s: Python Client the Message class is missing some properties, e.g. the redelivered flag --- Key: QPID-2292 URL: https://issues.apache.org/jira/browse/QPID-2292 Project: Qpid Issue Type: Bug Components: Python Client Affects Versions: 0.6 Reporter: Rafael H. Schloming Assignee: Rafael H. Schloming Fix For: 0.6 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-2293) MessageReplyTracker loses messages if an exception is thrown during replay()
MessageReplyTracker loses messages if an exception is thrown during replay() - Key: QPID-2293 URL: https://issues.apache.org/jira/browse/QPID-2293 Project: Qpid Issue Type: Bug Components: C++ Client Affects Versions: 0.5 Reporter: Alan Conway Assignee: Alan Conway Fix For: 0.6 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-2293) MessageReplyTracker loses messages if an exception is thrown during replay()
[ https://issues.apache.org/jira/browse/QPID-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved QPID-2293. --- Resolution: Fixed Fixed in r891886 MessageReplyTracker loses messages if an exception is thrown during replay() - Key: QPID-2293 URL: https://issues.apache.org/jira/browse/QPID-2293 Project: Qpid Issue Type: Bug Components: C++ Client Affects Versions: 0.5 Reporter: Alan Conway Assignee: Alan Conway Fix For: 0.6 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-2290) Unauthorised-access exception raised when sending message from JMS on connection authenticated using PLAIN mechanism
[ https://issues.apache.org/jira/browse/QPID-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12792149#action_12792149 ] Sandy Pratt commented on QPID-2290: --- I was able to work around this issue by changing line 57 of org.apache.qpid.client.BasicMessageProducer_0_10 as follows: userIDBytes = Strings.toUTF8(_userID + @QPID); from userIDBytes = Strings.toUTF8(_userID); My auth-realm on the server is the default (QPID). Unauthorised-access exception raised when sending message from JMS on connection authenticated using PLAIN mechanism - Key: QPID-2290 URL: https://issues.apache.org/jira/browse/QPID-2290 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.6 Reporter: Gordon Sim Assignee: Rajith Attapattu Priority: Blocker Fix For: 0.6 Email from prat...@adobe.com on user list states: when I enable auth=yes, I get the following: 2009-12-16 18:33:18 error qpid/amqp_0_10/SessionHandler.cpp:97: Execution exception: unauthorized-access: authorised user id : prat...@qpid but user id in message decla red as prattrs (qpid/broker/SemanticState.cpp:435) I believe this is a result of the change brought in by r819819 to address QPID-2129. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-2210) broker coredumps on shutting down when rdma module is loaded
[ https://issues.apache.org/jira/browse/QPID-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved QPID-2210. --- Resolution: Fixed This turned out to be a double free from within SocketAddress because the SocketAddress is copied on its way into RdmaIO and there was no non default copy constructor. Added copy constructor and assignment operator to preserve the correct value semantics. broker coredumps on shutting down when rdma module is loaded Key: QPID-2210 URL: https://issues.apache.org/jira/browse/QPID-2210 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.6 Reporter: Gordon Sim Assignee: Andrew Stitcher Fix For: 0.6 $ ./src/qpidd --auth no --no-module-dir --load-module ./src/.libs/rdma.so 2009-11-19 12:32:17 notice SASL disabled: No Authentication Performed 2009-11-19 12:32:17 notice Listening on TCP port 5672 2009-11-19 12:32:17 notice Rdma: Listening on RDMA port 5672 2009-11-19 12:32:17 notice Broker running 2009-11-19 12:32:18 notice Shut down= Ctrl-C to shutdown broker Segmentation fault (core dumped) Core was generated by `/home/gordon/qpid/cpp/src/.libs/lt-qpidd --auth no --no-module-dir --load-modul'. Program terminated with signal 11, Segmentation fault. [New process 7935] [New process 7951] #0 0x0035bb07270e in free () from /lib64/libc.so.6 (gdb) bt #0 0x0035bb07270e in free () from /lib64/libc.so.6 #1 0x0035bb0babf0 in freeaddrinfo () from /lib64/libc.so.6 #2 0x2abd0575b2bf in ~SocketAddress (this=0x3111c88) at qpid/sys/posix/SocketAddress.cpp:58 #3 0x2abd05d01a86 in ~Listener (this=0x3111b10) at ./qpid/sys/rdma/RdmaIO.h:176 #4 0x2abd05ae8a61 in ~RdmaIOProtocolFactory (this=0x310ed10) at /usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/memory:259 #5 0x2abd052ff9c2 in std::_Rb_treestd::string, std::pairstd::string const, boost::shared_ptrqpid::sys::ProtocolFactory , std::_Select1ststd::pairstd::string const, boost::shared_ptrqpid::sys::ProtocolFactory , std::lessstd::string, std::allocatorstd::pairstd::string const, boost::shared_ptrqpid::sys::ProtocolFactory ::_M_erase (this=0x310acb8, __x=0x31116d0) at /usr/include/boost/detail/sp_counted_base_gcc_x86.hpp:145 #6 0x2abd052f84a7 in ~Broker (this=0x310ab00) at /usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stl_tree.h:578 #7 0x004072d9 in QpiddBroker::execute (this=value optimized out, options=value optimized out) at ./qpid/RefCounted.h:42 #8 0x0040578f in main (argc=6, argv=0x7fff622649b8) at qpidd.cpp:80 Last observed on r882182. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
c++/trivial: Why doesn't Rdma::AsynchIO subclass qpid::sys::AsynchIO?
Hi, I'm a newb reading through the C++ qpid broker and client code, trying to wrap my brain around the basic structure. One sorta-trivial question I have is: Any reason Rdma::AsynchIO doesn't subclass qpid::sys::AsynchIO like windows::AsynchIO and qpid::sys::AsynchIO do? Another comment: naming all these classes AsynchIO makes it hard to grep the code IMHO. Also, if there are any developer/code docs on this part of the code, please send a link. Thanks, Aaron - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-2295) Clustered broker crashes with inconsistency error
Clustered broker crashes with inconsistency error - Key: QPID-2295 URL: https://issues.apache.org/jira/browse/QPID-2295 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.6 Environment: RHEL 5.4 on VMWare, 32 bit Reporter: Sandy Pratt When running two brokers in a cluster, one of them will fail with a message like the following: 2009-12-17 14:04:23 error qpid/amqp_0_10/SessionHandler.cpp:97: Execution exception: invalid-argument: na1md...@qpid.f16efd17-e55d-4a40-b9b0-c506a4df5f3e: confirmed (805+0) but only sent (800+0) (qpid/SessionState.cpp:151) 2009-12-17 14:04:23 critical qpid/cluster/ErrorCheck.cpp:87: cluster(10.59.174.211:3060 READY/error) local error 126323 did not occur on member 10.59.174.186:32003: invalid-argument: na1md...@qpid.f16efd17-e55d-4a40-b9b0-c506a4df5f3e: confirmed (805+0) but only sent (800+0) (qpid/SessionState.cpp:151) 2009-12-17 14:04:23 error ./qpid/cluster/PollableQueue.h:58: Error delivering frames: local error did not occur on all cluster members : invalid-argument: na1md...@qpid.f16efd17-e55d-4a40-b9b0-c506a4df5f3e: confirmed (805+0) but only sent (800+0) (qpid/SessionState.cpp:151) (qpid/cluster/ErrorCheck.cpp:89) 2009-12-17 14:04:23 notice qpid/cluster/Cluster.cpp:369: cluster(10.59.174.211:3060 LEFT/error) leaving cluster na1m-dev1 2009-12-17 14:04:23 notice qpid/broker/Broker.cpp:340: Shut down ... 2009-12-17 14:25:00 error qpid/amqp_0_10/SessionHandler.cpp:97: Execution exception: invalid-argument: na1md...@qpid.28265958-4239-4fdf-8772-f6630a7f01fe: confirmed (742+0) but only sent (729+0) (qpid/SessionState.cpp:151) 2009-12-17 14:25:00 critical qpid/cluster/ErrorCheck.cpp:87: cluster(10.59.174.211:3874 READY/error) local error 151214 did not occur on member 10.59.174.186:32003: invalid-argument: na1md...@qpid.28265958-4239-4fdf-8772-f6630a7f01fe: confirmed (742+0) but only sent (729+0) (qpid/SessionState.cpp:151) 2009-12-17 14:25:00 error ./qpid/cluster/PollableQueue.h:58: Error delivering frames: local error did not occur on all cluster members : invalid-argument: na1md...@qpid.28265958-4239-4fdf-8772-f6630a7f01fe: confirmed (742+0) but only sent (729+0) (qpid/SessionState.cpp:151) (qpid/cluster/ErrorCheck.cpp:89) 2009-12-17 14:25:00 notice qpid/cluster/Cluster.cpp:369: cluster(10.59.174.211:3874 LEFT/error) leaving cluster na1m-dev1 2009-12-17 14:25:00 notice qpid/broker/Broker.cpp:340: Shut down qpidd.conf looks like this: data-dir=/usr/local/adobe/qpid-data #no-module-dir=1 #load-module=/usr/local/adobe/qpid/lib/qpid/daemon/cluster.so #load-module=/usr/local/adobe/qpid/lib/qpid/daemon/msgstore.so cluster-mechanism=PLAIN #cluster-mechanism=ANONYMOUS cluster-name=na1m-dev1 cluster-username=na1mdev1 cluster-password=*** log-to-file=/usr/local/adobe/qpid-data/qpidd.log log-source=1 trace=0 auth=1 #acl-file=/usr/local/adobe/qpid-data/qpidd.acl wait=60 The client is the Java JMS client from 0.6beta1. The connection strings are as follows: connectionfactory.qpidConnectionFactory = amqp://na1mdev1:*...@test/?brokerlist='tcp://na1m-dev1.services.adobe.com:443?ssl='true',connectdelay='1000',connecttimeout='5000'',failover='roundrobin?cyclecount='999'' destination.recvQueue=direct:test-prattrs?durable='true' destination.sendQueue=direct:test-prattrs?durable='true' Qpid was built from trunk at the following revision: [prat...@localhost qpid]$ svn info Path: . URL: http://svn.apache.org/repos/asf/qpid/trunk/qpid Repository Root: http://svn.apache.org/repos/asf Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68 Revision: 891406 Node Kind: directory Schedule: normal Last Changed Author: aconway Last Changed Rev: 891395 Last Changed Date: 2009-12-16 11:31:20 -0800 (Wed, 16 Dec 2009) The messaging store was built from trunk at the following revision: [prat...@localhost cpp]$ svn info Path: . URL: http://anonsvn.jboss.org/repos/rhmessaging/store/trunk/cpp Repository Root: http://anonsvn.jboss.org/repos/rhmessaging Repository UUID: 06e15bec-b515-0410-bef0-cc27a458cf48 Revision: 3750 Node Kind: directory Schedule: normal Last Changed Author: kpvdr Last Changed Rev: 3747 Last Changed Date: 2009-12-16 10:24:45 -0800 (Wed, 16 Dec 2009) I'll work on packaging up driver code for external consumption. Basically though, what I'm doing to drive qpid is establishing 8 send and 8 receiving connections, with either a producer or consumer on each one, and a separate thread for each. Message bodies are randomly generated 1000 character strings. Each sender thread sends 1000 or these messages, for a total of 8000 messages sent. All the messages get through because the primary survives in good health. The total length of the sending period for each of the above failures was about 20 seconds, at a rate of about 450 messages per second. -- This message is
Re: c++/trivial: Why doesn't Rdma::AsynchIO subclass qpid::sys::AsynchIO?
On Thu, 2009-12-17 at 14:07 -0800, aaron wrote: Hi, I'm a newb reading through the C++ qpid broker and client code, trying to wrap my brain around the basic structure. One sorta-trivial question I have is: Any reason Rdma::AsynchIO doesn't subclass qpid::sys::AsynchIO like windows::AsynchIO and qpid::sys::AsynchIO do? Basically because it doesn't implement the same interface. It would be nice, and the plan is to refactor into a state where this is possible, but currently the code is as it is! Another comment: naming all these classes AsynchIO makes it hard to grep the code IMHO. The qpid::sys::AsynchIO class is the interface and the stuff in qpid::sys::posix and qpid::sys:windows implements the interface. Also, if there are any developer/code docs on this part of the code, please send a link. None really - the code is its documentation at this point. Steve Huston may have some more information on his blog, as he did write about some of the work he did porting the code to Windows, but that will be about tcp rather than rdma. Andrew - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2260) Build of Release configuration fails
[ https://issues.apache.org/jira/browse/QPID-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cliff Jansen updated QPID-2260: --- Attachment: QPID-2260-0.patch I inserted the logic to handle release and 64 bit builds. I also updated the Interop.dll build steps so that they mimic the steps in the CMake build of qpidclient.dll as closely as possible as a first step towards using CMake for the whole process. Build of Release configuration fails Key: QPID-2260 URL: https://issues.apache.org/jira/browse/QPID-2260 Project: Qpid Issue Type: Bug Components: WCF/C++ Client Affects Versions: 0.6 Environment: Windows Reporter: Cliff Jansen Assignee: Steve Huston Priority: Blocker Fix For: 0.6 Attachments: QPID-2260-0.patch Original Estimate: 48h Remaining Estimate: 48h Locations for the Release intermediaries are not properly resolved. This is known issue #1 in the ReadMe.txt file and prevents non-debug versions of the code from building without user intervention. This should be easy to fix. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Could we please add the JIRA number to commit messages when possible?
I was trying to track a change in the c++ code and found the change had been committed as part of a large checkin with no mention of it whatsoever. It would be great if we have a JIRA covering the issue and just mentioning it in the commit message. (In this instance there was actually a JIRA covering this issue). This would at least help so you could grep for it in the svn log. This will help someone who is new or someone who doesn't work on the code base on a daily basis. I am not asking to open a JIRA for every single commit, but creating one where it makes sense and then actually referencing it in the commit message is very helpful. Regards, Rajith Attapattu Red Hat http://rajith.2rlabs.com/ - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-2260) Build of Release configuration fails
[ https://issues.apache.org/jira/browse/QPID-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12792267#action_12792267 ] Steve Huston commented on QPID-2260: After applying the patch I can build Debug ok, but get an error building Release: -- Build started: Project: AmqpTypes, Configuration: Release Any CPU -- c:\WINDOWS\Microsoft.NET\Framework\v3.5\Csc.exe /noconfig /nowarn:1701,1702 /errorreport:prompt /warn:4 /define:TRACE /reference:c:\Program Files\Reference Assemblies\Microsoft\Framework\v3.5\System.Core.dll /reference:c:\Program Files\Reference Assemblies\Microsoft\Framework\v3.5\System.Data.DataSetExtensions.dll /reference:c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Data.dll /reference:c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.dll /reference:c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Xml.dll /reference:c:\Program Files\Reference Assemblies\Microsoft\Framework\v3.5\System.Xml.Linq.dll /debug:pdbonly /filealign:512 /keyfile:..\..\..\wcfnet.snk /optimize+ /out:obj\Release\Apache.Qpid.AmqpTypes.dll /target:library AmqpBoolean.cs AmqpInt.cs AmqpProperties.cs AmqpString.cs AmqpType.cs AmqpUbyte.cs Properties\AssemblyInfo.cs PropertyName.cs Compile complete -- 0 errors, 0 warnings AmqpTypes - C:\qpid\trunk\qpid\wcf\src\Apache\Qpid\AmqpTypes\bin\Release\Apache.Qpid.AmqpTypes.dll cd C:\qpid\trunk\qpid\wcf\src\Apache\Qpid\AmqpTypes\bin\Release del Apache.Qpid.AmqpTypes.dll del Apache.Qpid.AmqpTypes.pdb cd C:\qpid\trunk\qpid\wcf\src\Apache\Qpid\AmqpTypes\obj\Release del Apache.Qpid.AmqpTypes.dll del Apache.Qpid.AmqpTypes.pdb cd C:\qpid\trunk\qpid\wcf\src\Apache\Qpid\AmqpTypes\ CreateNetModule.bat Release generating Release netmodule Microsoft (R) Visual C# 2008 Compiler version 3.5.30729.1 for Microsoft (R) .NET Framework version 3.5 Copyright (C) Microsoft Corporation. All rights reserved. EXEC : error CS0006: Metadata file 'C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\v3.5\System.Core.dll' could not be found EXEC : error CS0006: Metadata file 'C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\v3.5\System.Data.DataSetExtensions.dll' could not be found EXEC : error CS0006: Metadata file 'C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\v3.5\System.Xml.Linq.dll' could not be found c:\WINDOWS\Microsoft.NET\Framework\v3.5\Microsoft.Common.targets(3397,13): error MSB3073: The command cd C:\qpid\trunk\qpid\wcf\src\Apache\Qpid\AmqpTypes\bin\Release c:\WINDOWS\Microsoft.NET\Framework\v3.5\Microsoft.Common.targets(3397,13): error MSB3073: del Apache.Qpid.AmqpTypes.dll c:\WINDOWS\Microsoft.NET\Framework\v3.5\Microsoft.Common.targets(3397,13): error MSB3073: del Apache.Qpid.AmqpTypes.pdb c:\WINDOWS\Microsoft.NET\Framework\v3.5\Microsoft.Common.targets(3397,13): error MSB3073: cd C:\qpid\trunk\qpid\wcf\src\Apache\Qpid\AmqpTypes\obj\Release c:\WINDOWS\Microsoft.NET\Framework\v3.5\Microsoft.Common.targets(3397,13): error MSB3073: del Apache.Qpid.AmqpTypes.dll c:\WINDOWS\Microsoft.NET\Framework\v3.5\Microsoft.Common.targets(3397,13): error MSB3073: del Apache.Qpid.AmqpTypes.pdb c:\WINDOWS\Microsoft.NET\Framework\v3.5\Microsoft.Common.targets(3397,13): error MSB3073: cd C:\qpid\trunk\qpid\wcf\src\Apache\Qpid\AmqpTypes\ c:\WINDOWS\Microsoft.NET\Framework\v3.5\Microsoft.Common.targets(3397,13): error MSB3073: CreateNetModule.bat Release exited with code 1. Done building project AmqpTypes.csproj -- FAILED. I think this may be from the Release part of CreateNetModule.bat having explicit Program Files (x86) references in it while the Debug part has %programfiles% (I'm trying this build on a 32-bit system). What do you think? Build of Release configuration fails Key: QPID-2260 URL: https://issues.apache.org/jira/browse/QPID-2260 Project: Qpid Issue Type: Bug Components: WCF/C++ Client Affects Versions: 0.6 Environment: Windows Reporter: Cliff Jansen Assignee: Steve Huston Priority: Blocker Fix For: 0.6 Attachments: QPID-2260-0.patch Original Estimate: 48h Remaining Estimate: 48h Locations for the Release intermediaries are not properly resolved. This is known issue #1 in the ReadMe.txt file and prevents non-debug versions of the code from building without user intervention. This should be easy to fix. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-2291) WCF channel tests fixed on NUnit 2.5.2
[ https://issues.apache.org/jira/browse/QPID-2291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Huston resolved QPID-2291. Resolution: Fixed Patch applied on trunk r892057 WCF channel tests fixed on NUnit 2.5.2 -- Key: QPID-2291 URL: https://issues.apache.org/jira/browse/QPID-2291 Project: Qpid Issue Type: Bug Components: WCF/C++ Client Affects Versions: 0.6 Environment: Windows, Visual Studio 2008, NUnit 2.5.3 Reporter: Steve Huston Assignee: Steve Huston Priority: Minor Fix For: 0.6 Attachments: QPID-2291.patch The Channel Functional tests refer specifically to NUnit 2.5.2, preventing its use with, say, NUnit 2.5.3. The specific NUnit version number need not be specified. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-2260) Build of Release configuration fails
[ https://issues.apache.org/jira/browse/QPID-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12792273#action_12792273 ] Steve Huston commented on QPID-2260: FYI, changing the Program Files (x86) refs to %programfiles% lets the Release build complete without errors. Is this the right thing to do? Build of Release configuration fails Key: QPID-2260 URL: https://issues.apache.org/jira/browse/QPID-2260 Project: Qpid Issue Type: Bug Components: WCF/C++ Client Affects Versions: 0.6 Environment: Windows Reporter: Cliff Jansen Assignee: Steve Huston Priority: Blocker Fix For: 0.6 Attachments: QPID-2260-0.patch Original Estimate: 48h Remaining Estimate: 48h Locations for the Release intermediaries are not properly resolved. This is known issue #1 in the ReadMe.txt file and prevents non-debug versions of the code from building without user intervention. This should be easy to fix. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-2260) Build of Release configuration fails
[ https://issues.apache.org/jira/browse/QPID-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12792280#action_12792280 ] Cliff Jansen commented on QPID-2260: Yes indeed. Good catch. Thanks. Build of Release configuration fails Key: QPID-2260 URL: https://issues.apache.org/jira/browse/QPID-2260 Project: Qpid Issue Type: Bug Components: WCF/C++ Client Affects Versions: 0.6 Environment: Windows Reporter: Cliff Jansen Assignee: Steve Huston Priority: Blocker Fix For: 0.6 Attachments: QPID-2260-0.patch Original Estimate: 48h Remaining Estimate: 48h Locations for the Release intermediaries are not properly resolved. This is known issue #1 in the ReadMe.txt file and prevents non-debug versions of the code from building without user intervention. This should be easy to fix. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2295) Clustered broker crashes with inconsistency error
[ https://issues.apache.org/jira/browse/QPID-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Pratt updated QPID-2295: -- Attachment: qpid-driver.zip Attached the code I've been using to drive qpid for testing. The test *should* build and run when you do ant test-spam, although the logging will be a bit verbose and you might have to kill the child vm manually in case of a failure. In practice, I usually invoke the test through Eclipse; the ant target is included to show how the test is invoked. Feel free to send me questions. Clustered broker crashes with inconsistency error - Key: QPID-2295 URL: https://issues.apache.org/jira/browse/QPID-2295 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.6 Environment: RHEL 5.4 on VMWare, 32 bit Reporter: Sandy Pratt Attachments: qpid-driver.zip When running two brokers in a cluster, one of them will fail with a message like the following: 2009-12-17 14:04:23 error qpid/amqp_0_10/SessionHandler.cpp:97: Execution exception: invalid-argument: na1md...@qpid.f16efd17-e55d-4a40-b9b0-c506a4df5f3e: confirmed (805+0) but only sent (800+0) (qpid/SessionState.cpp:151) 2009-12-17 14:04:23 critical qpid/cluster/ErrorCheck.cpp:87: cluster(10.59.174.211:3060 READY/error) local error 126323 did not occur on member 10.59.174.186:32003: invalid-argument: na1md...@qpid.f16efd17-e55d-4a40-b9b0-c506a4df5f3e: confirmed (805+0) but only sent (800+0) (qpid/SessionState.cpp:151) 2009-12-17 14:04:23 error ./qpid/cluster/PollableQueue.h:58: Error delivering frames: local error did not occur on all cluster members : invalid-argument: na1md...@qpid.f16efd17-e55d-4a40-b9b0-c506a4df5f3e: confirmed (805+0) but only sent (800+0) (qpid/SessionState.cpp:151) (qpid/cluster/ErrorCheck.cpp:89) 2009-12-17 14:04:23 notice qpid/cluster/Cluster.cpp:369: cluster(10.59.174.211:3060 LEFT/error) leaving cluster na1m-dev1 2009-12-17 14:04:23 notice qpid/broker/Broker.cpp:340: Shut down ... 2009-12-17 14:25:00 error qpid/amqp_0_10/SessionHandler.cpp:97: Execution exception: invalid-argument: na1md...@qpid.28265958-4239-4fdf-8772-f6630a7f01fe: confirmed (742+0) but only sent (729+0) (qpid/SessionState.cpp:151) 2009-12-17 14:25:00 critical qpid/cluster/ErrorCheck.cpp:87: cluster(10.59.174.211:3874 READY/error) local error 151214 did not occur on member 10.59.174.186:32003: invalid-argument: na1md...@qpid.28265958-4239-4fdf-8772-f6630a7f01fe: confirmed (742+0) but only sent (729+0) (qpid/SessionState.cpp:151) 2009-12-17 14:25:00 error ./qpid/cluster/PollableQueue.h:58: Error delivering frames: local error did not occur on all cluster members : invalid-argument: na1md...@qpid.28265958-4239-4fdf-8772-f6630a7f01fe: confirmed (742+0) but only sent (729+0) (qpid/SessionState.cpp:151) (qpid/cluster/ErrorCheck.cpp:89) 2009-12-17 14:25:00 notice qpid/cluster/Cluster.cpp:369: cluster(10.59.174.211:3874 LEFT/error) leaving cluster na1m-dev1 2009-12-17 14:25:00 notice qpid/broker/Broker.cpp:340: Shut down qpidd.conf looks like this: data-dir=/usr/local/adobe/qpid-data #no-module-dir=1 #load-module=/usr/local/adobe/qpid/lib/qpid/daemon/cluster.so #load-module=/usr/local/adobe/qpid/lib/qpid/daemon/msgstore.so cluster-mechanism=PLAIN #cluster-mechanism=ANONYMOUS cluster-name=na1m-dev1 cluster-username=na1mdev1 cluster-password=*** log-to-file=/usr/local/adobe/qpid-data/qpidd.log log-source=1 trace=0 auth=1 #acl-file=/usr/local/adobe/qpid-data/qpidd.acl wait=60 The client is the Java JMS client from 0.6beta1. The connection strings are as follows: connectionfactory.qpidConnectionFactory = amqp://na1mdev1:*...@test/?brokerlist='tcp://na1m-dev1.services.adobe.com:443?ssl='true',connectdelay='1000',connecttimeout='5000'',failover='roundrobin?cyclecount='999'' destination.recvQueue=direct:test-prattrs?durable='true' destination.sendQueue=direct:test-prattrs?durable='true' Qpid was built from trunk at the following revision: [prat...@localhost qpid]$ svn info Path: . URL: http://svn.apache.org/repos/asf/qpid/trunk/qpid Repository Root: http://svn.apache.org/repos/asf Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68 Revision: 891406 Node Kind: directory Schedule: normal Last Changed Author: aconway Last Changed Rev: 891395 Last Changed Date: 2009-12-16 11:31:20 -0800 (Wed, 16 Dec 2009) The messaging store was built from trunk at the following revision: [prat...@localhost cpp]$ svn info Path: . URL: http://anonsvn.jboss.org/repos/rhmessaging/store/trunk/cpp Repository Root: http://anonsvn.jboss.org/repos/rhmessaging Repository UUID: 06e15bec-b515-0410-bef0-cc27a458cf48 Revision: 3750 Node Kind: directory Schedule: normal Last Changed Author: kpvdr Last
[jira] Resolved: (QPID-2260) Build of Release configuration fails
[ https://issues.apache.org/jira/browse/QPID-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Huston resolved QPID-2260. Resolution: Fixed Corrected patch applied; trunk r892103. Build of Release configuration fails Key: QPID-2260 URL: https://issues.apache.org/jira/browse/QPID-2260 Project: Qpid Issue Type: Bug Components: WCF/C++ Client Affects Versions: 0.6 Environment: Windows Reporter: Cliff Jansen Assignee: Steve Huston Priority: Blocker Fix For: 0.6 Attachments: QPID-2260-0.patch Original Estimate: 48h Remaining Estimate: 48h Locations for the Release intermediaries are not properly resolved. This is known issue #1 in the ReadMe.txt file and prevents non-debug versions of the code from building without user intervention. This should be easy to fix. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2175) C++ broker should use use...@domain when authenticating messages.
[ https://issues.apache.org/jira/browse/QPID-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-2175: --- Affects Version/s: 0.5 Fix Version/s: 0.7 C++ broker should use use...@domain when authenticating messages. - Key: QPID-2175 URL: https://issues.apache.org/jira/browse/QPID-2175 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.5 Reporter: Rajith Attapattu Assignee: Rajith Attapattu Fix For: 0.7 The c++ broker currently strips the domain from the user id when authenticating messages. This is to accommodate the java client issue defined in QPID-2174 Once that is fixed the c++ broker should take the domain into account when authenticating messages. If a message contains a user id without a domain, the broker should use the realm as the default domain. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-2290) Unauthorised-access exception raised when sending message from JMS on connection authenticated using PLAIN mechanism
[ https://issues.apache.org/jira/browse/QPID-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12792323#action_12792323 ] Rajith Attapattu commented on QPID-2290: Sandy we can't modify the JMS client to add a domain to the userID as it will cause problems when the client is used against the java broker. The Java broker does not have any notion of a domain associated with a userID. Anyways I believe the proper fix is for the c++ broker to use the default realm as the domain when authenticating a message that has a userID with a domain. Unauthorised-access exception raised when sending message from JMS on connection authenticated using PLAIN mechanism - Key: QPID-2290 URL: https://issues.apache.org/jira/browse/QPID-2290 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.6 Reporter: Gordon Sim Assignee: Rajith Attapattu Priority: Blocker Fix For: 0.6 Email from prat...@adobe.com on user list states: when I enable auth=yes, I get the following: 2009-12-16 18:33:18 error qpid/amqp_0_10/SessionHandler.cpp:97: Execution exception: unauthorized-access: authorised user id : prat...@qpid but user id in message decla red as prattrs (qpid/broker/SemanticState.cpp:435) I believe this is a result of the change brought in by r819819 to address QPID-2129. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-2290) Unauthorised-access exception raised when sending message from JMS on connection authenticated using PLAIN mechanism
[ https://issues.apache.org/jira/browse/QPID-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu resolved QPID-2290. Resolution: Fixed I added a fix for this where the broker now uses the default realm as the domain if the userID supplied in the message doesn't contain a domain. This is added at rev 892123 in Qpid trunk. Unauthorised-access exception raised when sending message from JMS on connection authenticated using PLAIN mechanism - Key: QPID-2290 URL: https://issues.apache.org/jira/browse/QPID-2290 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.6 Reporter: Gordon Sim Assignee: Rajith Attapattu Priority: Blocker Fix For: 0.6 Email from prat...@adobe.com on user list states: when I enable auth=yes, I get the following: 2009-12-16 18:33:18 error qpid/amqp_0_10/SessionHandler.cpp:97: Execution exception: unauthorized-access: authorised user id : prat...@qpid but user id in message decla red as prattrs (qpid/broker/SemanticState.cpp:435) I believe this is a result of the change brought in by r819819 to address QPID-2129. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2175) C++ broker should use use...@domain when authenticating messages.
[ https://issues.apache.org/jira/browse/QPID-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-2175: --- Fix Version/s: (was: 0.7) 0.6 C++ broker should use use...@domain when authenticating messages. - Key: QPID-2175 URL: https://issues.apache.org/jira/browse/QPID-2175 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.5 Reporter: Rajith Attapattu Assignee: Rajith Attapattu Fix For: 0.6 The c++ broker currently strips the domain from the user id when authenticating messages. This is to accommodate the java client issue defined in QPID-2174 Once that is fixed the c++ broker should take the domain into account when authenticating messages. If a message contains a user id without a domain, the broker should use the realm as the default domain. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
