[jira] Updated: (QPID-2239) [.Net 0-10] Close() method is hanging indefinetely
[ https://issues.apache.org/jira/browse/QPID-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner updated QPID-2239: Priority: Critical (was: Major) [.Net 0-10] Close() method is hanging indefinetely -- Key: QPID-2239 URL: https://issues.apache.org/jira/browse/QPID-2239 Project: Qpid Issue Type: Bug Components: Dot Net Client Affects Versions: 0.5 Reporter: Julien Lavigne du Cadet Priority: Critical Step to reproduce : - open a connection to the broker - close the connection = wait till timeout -- 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-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 ] Aidan Skinner resolved QPID-2273. - Resolution: Fixed Works with 0.5 as well. Win. 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] 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
[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] Commented: (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:comment-tabpanelfocusedCommentId=12791749#action_12791749 ] Aidan Skinner commented on QPID-2273: - That patch breaks RabbitMQ 0-9-1 tests, I think because we always report the highest available version and not the one that they ask for. I can't really see why that changes with that patch though. Quite confused... 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.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 ] Aidan Skinner updated QPID-2273: Attachment: (was: 0001-QPID-2273-set-the-protocol-version-on-the-connectio.patch) 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 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 ] Aidan Skinner updated QPID-2273: Attachment: 0001-QPID-2273-make-protocol-negotiation-saner.patch This patch fixes the problem 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 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 ] Aidan Skinner updated QPID-2273: Attachment: (was: 0001-QPID-2273-make-protocol-negotiation-saner.-This-cau.patch) 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 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] Assigned: (QPID-1830) BytesMessage is unreadable
[ https://issues.apache.org/jira/browse/QPID-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner reassigned QPID-1830: --- Assignee: Rajith Attapattu (was: Aidan Skinner) This was caused by r756228, could you fix please? Thanks, - Aidan 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
[jira] Updated: (QPID-1830) BytesMessage is unreadable
[ https://issues.apache.org/jira/browse/QPID-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner updated QPID-1830: Affects Version/s: 0.7 Fix Version/s: (was: 0.7) 0.6 Moving back to 0.6, this is quite important. I'm actively working on this. 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 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
[jira] Created: (QPID-2273) Java client can't negotiate to 0-9
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 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 ] Aidan Skinner updated QPID-2273: Attachment: 0001-QPID-2273-set-the-protocol-version-on-the-connectio.patch simple patch. This causes issues with the java profile, the 0-10 negotiation seems to break down for some reason... 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-set-the-protocol-version-on-the-connectio.patch 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 ] Aidan Skinner updated QPID-2273: Attachment: 0001-QPID-2273-make-protocol-negotiation-saner.-This-cau.patch 2nd patch, this does some refactoring which should make life easier. However, it also causes problems with the brokers 0-10 instantation. 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.-This-cau.patch, 0001-QPID-2273-set-the-protocol-version-on-the-connectio.patch 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-2238) [.Net 0-10] Recursive call to ToString method causes a stack overflow exception
[ https://issues.apache.org/jira/browse/QPID-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2238. - Resolution: Fixed Commited, thanks for the patch! [.Net 0-10] Recursive call to ToString method causes a stack overflow exception --- Key: QPID-2238 URL: https://issues.apache.org/jira/browse/QPID-2238 Project: Qpid Issue Type: Bug Components: Dot Net Client Affects Versions: 0.5 Reporter: Julien Lavigne du Cadet Attachments: Recursive ToString.patch See patch below -- 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-2237) UUID are not decoded properly by the .Net 0-10 api
[ https://issues.apache.org/jira/browse/QPID-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2237. - Resolution: Fixed Fix Version/s: 0.6 comitted, thanks for the patch! UUID are not decoded properly by the .Net 0-10 api -- Key: QPID-2237 URL: https://issues.apache.org/jira/browse/QPID-2237 Project: Qpid Issue Type: Improvement Components: Dot Net Client Affects Versions: 0.5 Reporter: Julien Lavigne du Cadet Fix For: 0.6 Attachments: UUID decoding.patch See patch below -- 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-2238) [.Net 0-10] Recursive call to ToString method causes a stack overflow exception
[ https://issues.apache.org/jira/browse/QPID-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner updated QPID-2238: Fix Version/s: 0.6 [.Net 0-10] Recursive call to ToString method causes a stack overflow exception --- Key: QPID-2238 URL: https://issues.apache.org/jira/browse/QPID-2238 Project: Qpid Issue Type: Bug Components: Dot Net Client Affects Versions: 0.5 Reporter: Julien Lavigne du Cadet Fix For: 0.6 Attachments: Recursive ToString.patch See patch below -- 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-2240) [.Net 0-10] When authentication fails on connect(), the api should raise an exception
[
https://issues.apache.org/jira/browse/QPID-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12787228#action_12787228
]
Aidan Skinner commented on QPID-2240:
-
I think this patch is OK in principle, a couple of minor nits:
chunks of commented out code, these should just be removed instead.
Qpid style preference is to always use braces for one line blocks:
if (foo) {
bar()
}
instead of
if (foo)
bar()
Other than that I don't see a problem with it, it's definitely better than
leaving the bugs unfixed. It'd be good to get another set of eyes on it though
since I'm not *hugely* familiar with this part of the codebase.
[.Net 0-10] When authentication fails on connect(), the api should raise an
exception
--
Key: QPID-2240
URL: https://issues.apache.org/jira/browse/QPID-2240
Project: Qpid
Issue Type: Bug
Components: Dot Net Client
Affects Versions: 0.5
Reporter: Julien Lavigne du Cadet
Attachments: qpid-dotnet.patch
--
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-1987) Patch for 0.10 C# API
[ https://issues.apache.org/jira/browse/QPID-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner updated QPID-1987: Affects Version/s: 0.6 0.5 Fix Version/s: 0.6 Patch for 0.10 C# API - Key: QPID-1987 URL: https://issues.apache.org/jira/browse/QPID-1987 Project: Qpid Issue Type: Improvement Components: Dot Net Client Affects Versions: 0.5, 0.6 Reporter: Julien Lavigne du Cadet Assignee: Aidan Skinner Priority: Critical Fix For: 0.6 Attachments: qpid-.net.patch, qpid-dotnet - build.patch Please find attached a patch correcting the following issues : - Fixes UUID.randomUUID() which is not thread-safe (QPID-1972) - Fixes public API to match standard .NET conventions (QPID-500) - Fixes code generation to match standard .NET conventions - Fixes ToString() methods that don't override base classes - Fixes blocking TearingDown in unit tests - Use a .config file for tests/samples - Adds interface to Invoker, Session and ClientSession to allow easy mocking of the API - Make the console solution compiling under Visual Studio 2008 I'm more than happy to discuss any of this by email or through JIRA. Please let me know if there's no plan (or nobody available) to evaluate this patch for inclusion. If that is the case, I will consider forking the API to continue fixing the API. -- 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-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 updated QPID-500: --- Affects Version/s: 0.6 M2.1 M3 M4 0.5 Fix Version/s: 0.6 Assignee: Aidan Skinner 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] Updated: (QPID-2224) Repeated random failures for MINANetworkDriverTest
[ https://issues.apache.org/jira/browse/QPID-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner updated QPID-2224: Priority: Minor (was: Major) Repeated random failures for MINANetworkDriverTest -- Key: QPID-2224 URL: https://issues.apache.org/jira/browse/QPID-2224 Project: Qpid Issue Type: Bug Components: Java Tests Reporter: Rajith Attapattu Assignee: Aidan Skinner Priority: Minor Fix For: 0.6 The MINANetworkDriverTest has repeated random test failures for last month and half or so. IIRC there two tests that behaved this way. I will capture the logs for each different failure and add as and when they occur. -- 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-1972) UUID.randomUUID() is not thread-safe
[ https://issues.apache.org/jira/browse/QPID-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1972. - Resolution: Fixed I've applied Julien's patch from QPID-1987 UUID.randomUUID() is not thread-safe Key: QPID-1972 URL: https://issues.apache.org/jira/browse/QPID-1972 Project: Qpid Issue Type: Bug Components: Dot Net Client Affects Versions: M3, M4, 0.5 Environment: .net API Reporter: Julien Lavigne du Cadet Priority: Critical Fix For: 0.6 UUID.randomUUID is not thread-safe because it's using a static random object. However, recreating a random object each time the method is called is not an option because 2 successive calls might result in the same UUID. Please find attached in the next comment a patch that fixes the issue by introducing a UUIDGenerator class. Now, to get a random UUID, you first need to instantiate a UUIDGenerator and request it through it. That way there's no need to lock in the UUID class. Please note that this patch is BREAKING COMPABILITY with previous versions of the API ! The patch is also fixing 2 others issues : - test.config is not included in the unit test project which result in half of the unit tests failing - the management console is not compiling with vs 2008 and .Net 2.0 -- 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-1987) Patch for 0.10 C# API
[ https://issues.apache.org/jira/browse/QPID-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1987. - Resolution: Fixed Patches applied. Patch for 0.10 C# API - Key: QPID-1987 URL: https://issues.apache.org/jira/browse/QPID-1987 Project: Qpid Issue Type: Improvement Components: Dot Net Client Affects Versions: 0.5, 0.6 Reporter: Julien Lavigne du Cadet Assignee: Aidan Skinner Priority: Critical Fix For: 0.6 Attachments: qpid-.net.patch, qpid-dotnet - build.patch Please find attached a patch correcting the following issues : - Fixes UUID.randomUUID() which is not thread-safe (QPID-1972) - Fixes public API to match standard .NET conventions (QPID-500) - Fixes code generation to match standard .NET conventions - Fixes ToString() methods that don't override base classes - Fixes blocking TearingDown in unit tests - Use a .config file for tests/samples - Adds interface to Invoker, Session and ClientSession to allow easy mocking of the API - Make the console solution compiling under Visual Studio 2008 I'm more than happy to discuss any of this by email or through JIRA. Please let me know if there's no plan (or nobody available) to evaluate this patch for inclusion. If that is the case, I will consider forking the API to continue fixing the API. -- 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-1987) Patch for 0.10 C# API
[ https://issues.apache.org/jira/browse/QPID-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12784576#action_12784576 ] Aidan Skinner commented on QPID-1987: - UberFAIL that we haven't gotten this in. Patch looks ok, but i don't have a windows install handy just now. Will try to make sure this goes into 0.6. Patch for 0.10 C# API - Key: QPID-1987 URL: https://issues.apache.org/jira/browse/QPID-1987 Project: Qpid Issue Type: Improvement Components: Dot Net Client Reporter: Julien Lavigne du Cadet Assignee: Aidan Skinner Priority: Critical Attachments: qpid-.net.patch, qpid-dotnet - build.patch Please find attached a patch correcting the following issues : - Fixes UUID.randomUUID() which is not thread-safe (QPID-1972) - Fixes public API to match standard .NET conventions (QPID-500) - Fixes code generation to match standard .NET conventions - Fixes ToString() methods that don't override base classes - Fixes blocking TearingDown in unit tests - Use a .config file for tests/samples - Adds interface to Invoker, Session and ClientSession to allow easy mocking of the API - Make the console solution compiling under Visual Studio 2008 I'm more than happy to discuss any of this by email or through JIRA. Please let me know if there's no plan (or nobody available) to evaluate this patch for inclusion. If that is the case, I will consider forking the API to continue fixing the API. -- 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-2192) Client and common print stack to stdout
[ https://issues.apache.org/jira/browse/QPID-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2192. - Resolution: Fixed Client and common print stack to stdout --- Key: QPID-2192 URL: https://issues.apache.org/jira/browse/QPID-2192 Project: Qpid Issue Type: Bug Affects Versions: M1, M2, M2.1, M3, M4, 0.5, 0.6 Reporter: Aidan Skinner Fix For: 0.6 Both client/ and common/ print stack traces to stdout on occasion. Neithor should do this, they should all throw an appropriate exception higher up that the caller can deal with appropriately. -- 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-2184) updated ip whitelisting / firewall config doesnt take effect after SIGHUP or reloadSecurityConfiguration() JMX method
[ https://issues.apache.org/jira/browse/QPID-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2184. - Resolution: Fixed Fixed in r835115 updated ip whitelisting / firewall config doesnt take effect after SIGHUP or reloadSecurityConfiguration() JMX method - Key: QPID-2184 URL: https://issues.apache.org/jira/browse/QPID-2184 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.6 Reporter: Robbie Gemmell Assignee: Aidan Skinner Fix For: 0.6 Attachments: 0001-QPID-2184-add-test-for-reloading-firewall-config-in.patch, 0002-QPID-2184-add-a-test-case-for-the-firewall-config-u.patch updated ip whitelisting / firewall config doesnt take effect after SIGHUP or reloadSecurityConfiguration() via JMX. Changing an existing rule or adding a new rule to reverse the current allow/deny behaviour against a particular client machine does not take effect against new client connections, depsite the SIGHUP / JMX invoked security configuration reload occurring and completing without any Exceptions. Restarting the broker with the updated configuration in place results in the expected behaviour being attained. -- 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-2193) Allow deleting the first message on a queue through the JMX Management Console when connected to older brokers
[ https://issues.apache.org/jira/browse/QPID-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12775383#action_12775383 ] Aidan Skinner commented on QPID-2193: - That seems quite dangerous to me. If we can't guarantee which message is going to be deleted, or even detect which one we're going to delete I don't think we should offer this. Just because we've always let people shoot their foot off in the past doesn't mean we should continue to do so. If they really, really to keep doing that they can always use an older release. Allow deleting the first message on a queue through the JMX Management Console when connected to older brokers --- Key: QPID-2193 URL: https://issues.apache.org/jira/browse/QPID-2193 Project: Qpid Issue Type: New Feature Components: Java Management : JMX Console Affects Versions: 0.6 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Priority: Minor Fix For: 0.6 Java brokers previous to 0.6 do not support deletion of arbitrary messages, only the 'first message on the queue' at any given time. This was not exposed in the updated console due for release with 0.6 (where the broker now does support deletion of arbitrary messages). This decision was made because by its very nature the method cannot guarantee which message would be deleted when it is executed, as any queue activity could alter which message is at the head of the queue. However, users may have come to expect this method to be present, and so it should be exposed for older brokers that lack the ability to exactly specify which messages should be deleted. -- 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-2184) updated ip whitelisting / firewall config doesnt take effect after SIGHUP or reloadSecurityConfiguration() JMX method
[ https://issues.apache.org/jira/browse/QPID-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12776178#action_12776178 ] Aidan Skinner commented on QPID-2184: - This works for per-virtualhost firewall sections, but not for server-wide ones. Although the existing unit tests do exercise this, they check in an ever so slightly different manner. updated ip whitelisting / firewall config doesnt take effect after SIGHUP or reloadSecurityConfiguration() JMX method - Key: QPID-2184 URL: https://issues.apache.org/jira/browse/QPID-2184 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.6 Reporter: Robbie Gemmell Assignee: Aidan Skinner Fix For: 0.6 Attachments: 0001-QPID-2184-add-test-for-reloading-firewall-config-in.patch, 0002-QPID-2184-add-a-test-case-for-the-firewall-config-u.patch updated ip whitelisting / firewall config doesnt take effect after SIGHUP or reloadSecurityConfiguration() via JMX. Changing an existing rule or adding a new rule to reverse the current allow/deny behaviour against a particular client machine does not take effect against new client connections, depsite the SIGHUP / JMX invoked security configuration reload occurring and completing without any Exceptions. Restarting the broker with the updated configuration in place results in the expected behaviour being attained. -- 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-2184) updated ip whitelisting / firewall config doesnt take effect after SIGHUP or reloadSecurityConfiguration() JMX method
[ https://issues.apache.org/jira/browse/QPID-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner updated QPID-2184: Attachment: 0002-QPID-2184-add-a-test-case-for-the-firewall-config-u.patch 0001-QPID-2184-add-test-for-reloading-firewall-config-in.patch Patches with test case for this problem. Still working on a solution. updated ip whitelisting / firewall config doesnt take effect after SIGHUP or reloadSecurityConfiguration() JMX method - Key: QPID-2184 URL: https://issues.apache.org/jira/browse/QPID-2184 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.6 Reporter: Robbie Gemmell Assignee: Aidan Skinner Fix For: 0.6 Attachments: 0001-QPID-2184-add-test-for-reloading-firewall-config-in.patch, 0002-QPID-2184-add-a-test-case-for-the-firewall-config-u.patch updated ip whitelisting / firewall config doesnt take effect after SIGHUP or reloadSecurityConfiguration() via JMX. Changing an existing rule or adding a new rule to reverse the current allow/deny behaviour against a particular client machine does not take effect against new client connections, depsite the SIGHUP / JMX invoked security configuration reload occurring and completing without any Exceptions. Restarting the broker with the updated configuration in place results in the expected behaviour being attained. -- 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-2184) updated ip whitelisting / firewall config doesnt take effect after SIGHUP or reloadSecurityConfiguration() JMX method
[ https://issues.apache.org/jira/browse/QPID-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner reassigned QPID-2184: --- Assignee: Aidan Skinner updated ip whitelisting / firewall config doesnt take effect after SIGHUP or reloadSecurityConfiguration() JMX method - Key: QPID-2184 URL: https://issues.apache.org/jira/browse/QPID-2184 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.6 Reporter: Robbie Gemmell Assignee: Aidan Skinner Fix For: 0.6 updated ip whitelisting / firewall config doesnt take effect after SIGHUP or reloadSecurityConfiguration() via JMX. Changing an existing rule or adding a new rule to reverse the current allow/deny behaviour against a particular client machine does not take effect against new client connections, depsite the SIGHUP / JMX invoked security configuration reload occurring and completing without any Exceptions. Restarting the broker with the updated configuration in place results in the expected behaviour being attained. -- 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-1764) Create Abstract base class to perform new reference counting for TransactionLog
[ https://issues.apache.org/jira/browse/QPID-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner updated QPID-1764: Status: Open (was: Ready To Review) Create Abstract base class to perform new reference counting for TransactionLog --- Key: QPID-1764 URL: https://issues.apache.org/jira/browse/QPID-1764 Project: Qpid Issue Type: Bug Components: Performance Reporter: Martin Ritchie Assignee: Aidan Skinner Priority: Blocker Fix For: 0.6 Summary: Summary the introduction of the new TransactionLog interface over the old MessageStore has resulted in each of the old Stores performing their own reference counting. As a result they all suffer from: a) Being different implementations b) Not being fully tested by existing test frameworks. By creating a single reference counting TransactionLog base class that delegates the simple storage and retreival tasks to the underlying Stores the stores can be simpler and the testing more complete. Current testing has already shown that performance has knocked 5% by the MemoryMessageStore's implementation of reference counting when it should not need to be doing any reference counting. This was brought up during the FtD Code review http://cwiki.apache.org/confluence/display/qpid/FtD+Code+Review+Notes -- 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] Closed: (QPID-1764) Create Abstract base class to perform new reference counting for TransactionLog
[ https://issues.apache.org/jira/browse/QPID-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner closed QPID-1764. --- Resolution: Won't Fix This has been backed out and is not really relevant anymore Create Abstract base class to perform new reference counting for TransactionLog --- Key: QPID-1764 URL: https://issues.apache.org/jira/browse/QPID-1764 Project: Qpid Issue Type: Bug Components: Performance Reporter: Martin Ritchie Assignee: Aidan Skinner Priority: Blocker Fix For: 0.6 Summary: Summary the introduction of the new TransactionLog interface over the old MessageStore has resulted in each of the old Stores performing their own reference counting. As a result they all suffer from: a) Being different implementations b) Not being fully tested by existing test frameworks. By creating a single reference counting TransactionLog base class that delegates the simple storage and retreival tasks to the underlying Stores the stores can be simpler and the testing more complete. Current testing has already shown that performance has knocked 5% by the MemoryMessageStore's implementation of reference counting when it should not need to be doing any reference counting. This was brought up during the FtD Code review http://cwiki.apache.org/confluence/display/qpid/FtD+Code+Review+Notes -- 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-2006) enable opening queues and exchanges directly from other mbean views
[ https://issues.apache.org/jira/browse/QPID-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2006. - Resolution: Fixed Yep enable opening queues and exchanges directly from other mbean views --- Key: QPID-2006 URL: https://issues.apache.org/jira/browse/QPID-2006 Project: Qpid Issue Type: Improvement Components: Java Management : JMX Console Affects Versions: 0.6 Reporter: Robbie Gemmell Assignee: Aidan Skinner Priority: Minor Fix For: 0.6 Some of the mbeans (eg VirtualHostManager and Exchanges) list queues in their results. As it is now possible to open mbeans without adding them to the navigation tree it would be useful if you could double click on the queue etc names in other mbeans and have them open for viewing. -- 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] Closed: (QPID-2023) Import org.apache.mina.common.ByteBuffer and use that instead
[ https://issues.apache.org/jira/browse/QPID-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner closed QPID-2023. --- Resolution: Fixed We should just skip this step really and instead remove our dependence on the MINA behaviuor. It'll be easier. Import org.apache.mina.common.ByteBuffer and use that instead - Key: QPID-2023 URL: https://issues.apache.org/jira/browse/QPID-2023 Project: Qpid Issue Type: Sub-task Components: Java Broker, Java Common Affects Versions: 0.5 Reporter: Aidan Skinner Assignee: Aidan Skinner Fix For: 0.6 see http://cwiki.apache.org/confluence/display/qpid/Port+server+to+new+interface#Portservertonewinterface-AddQpidByteBuffer -- 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-1996) Notifications view clears the table and forces deselection at every refresh
[ https://issues.apache.org/jira/browse/QPID-1996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1996. - Resolution: Fixed OK Notifications view clears the table and forces deselection at every refresh --- Key: QPID-1996 URL: https://issues.apache.org/jira/browse/QPID-1996 Project: Qpid Issue Type: Bug Components: Java Management : JMX Console Affects Versions: 0.6 Reporter: Robbie Gemmell Assignee: Aidan Skinner Fix For: 0.6 Notifications view clears the table and forces deselection at every refresh -- 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-2154) New Network IO Layer has doesn't appear to clean up connections on connection close.
[ https://issues.apache.org/jira/browse/QPID-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12770754#action_12770754 ] Aidan Skinner commented on QPID-2154: - I can't see any way for the connection to be added twice, I think it's more likely that the _virtualHost is null, which I guess is possible, if unlikely. It might be better to make this a little less fragile by storing a pointer to the connectionRegistry itself in setVirtualHost. Is this happening regularly, or was it a once off? New Network IO Layer has doesn't appear to clean up connections on connection close. Key: QPID-2154 URL: https://issues.apache.org/jira/browse/QPID-2154 Project: Qpid Issue Type: Bug Components: Java Broker Reporter: Martin Ritchie Assignee: Aidan Skinner Fix For: 0.6 Attachments: MessageDisappearTail.txt The new AMQProtocolEngine appears does not appear to reliably clear the ConnectionRegistry when closing connections. The Missing test run over the weekend genereated 25GB of log which appears to be the Broker stuck in the ConnectionRegistry.close() loop. This would suggest that the new IO layer is not correctly notifying and/or removing the closed connection from the ConnectionRegistry. -- 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-2154) New Network IO Layer has doesn't appear to clean up connections on connection close.
[ https://issues.apache.org/jira/browse/QPID-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner reassigned QPID-2154: --- Assignee: Martin Ritchie (was: Aidan Skinner) Hrm, Jira doesn't have a NEEDINFO status... New Network IO Layer has doesn't appear to clean up connections on connection close. Key: QPID-2154 URL: https://issues.apache.org/jira/browse/QPID-2154 Project: Qpid Issue Type: Bug Components: Java Broker Reporter: Martin Ritchie Assignee: Martin Ritchie Fix For: 0.6 Attachments: MessageDisappearTail.txt The new AMQProtocolEngine appears does not appear to reliably clear the ConnectionRegistry when closing connections. The Missing test run over the weekend genereated 25GB of log which appears to be the Broker stuck in the ConnectionRegistry.close() loop. This would suggest that the new IO layer is not correctly notifying and/or removing the closed connection from the ConnectionRegistry. -- 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] Closed: (QPID-1863) Expiry does not work on exclusive queues
[ https://issues.apache.org/jira/browse/QPID-1863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner closed QPID-1863. --- Resolution: Cannot Reproduce Expiry does not work on exclusive queues Key: QPID-1863 URL: https://issues.apache.org/jira/browse/QPID-1863 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.5, 0.6 Reporter: Aidan Skinner Assignee: Aidan Skinner Fix For: 0.6 Expiry doesn't work on exclusive queues because all messages are acquired. -- 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-2154) New Network IO Layer has doesn't appear to clean up connections on connection close.
[ https://issues.apache.org/jira/browse/QPID-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner reassigned QPID-2154: --- Assignee: Aidan Skinner New Network IO Layer has doesn't appear to clean up connections on connection close. Key: QPID-2154 URL: https://issues.apache.org/jira/browse/QPID-2154 Project: Qpid Issue Type: Bug Components: Java Broker Reporter: Martin Ritchie Assignee: Aidan Skinner Fix For: 0.6 Attachments: MessageDisappearTail.txt The new AMQProtocolEngine appears does not appear to reliably clear the ConnectionRegistry when closing connections. The Missing test run over the weekend genereated 25GB of log which appears to be the Broker stuck in the ConnectionRegistry.close() loop. This would suggest that the new IO layer is not correctly notifying and/or removing the closed connection from the ConnectionRegistry. -- 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-2010) Implement NetworkDriver and ProtocolEngine to decouple MINA dependency from protocol processing
[ https://issues.apache.org/jira/browse/QPID-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2010. - Resolution: Fixed Implement NetworkDriver and ProtocolEngine to decouple MINA dependency from protocol processing --- Key: QPID-2010 URL: https://issues.apache.org/jira/browse/QPID-2010 Project: Qpid Issue Type: Improvement Components: Java Broker, Java Common Affects Versions: 0.6 Reporter: Aidan Skinner Assignee: Aidan Skinner Fix For: 0.6 We should implement the changes describedin http://cwiki.apache.org/confluence/display/qpid/Port+server+to+new+interface to decouple MINA from the Protocol processing -- 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-2025) Implement AMQProtocolEngine
[ https://issues.apache.org/jira/browse/QPID-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2025. - Resolution: Fixed Implement AMQProtocolEngine --- Key: QPID-2025 URL: https://issues.apache.org/jira/browse/QPID-2025 Project: Qpid Issue Type: Sub-task Components: Java Broker Affects Versions: 0.5 Reporter: Aidan Skinner Assignee: Aidan Skinner Fix For: 0.6 See http://cwiki.apache.org/confluence/display/qpid/Port+server+to+new+interface#Portservertonewinterface-ImplementationofProtocolEngine for details -- 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-1921) System test persistent storage
[ https://issues.apache.org/jira/browse/QPID-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1921. - Resolution: Fixed System test persistent storage -- Key: QPID-1921 URL: https://issues.apache.org/jira/browse/QPID-1921 Project: Qpid Issue Type: Test Components: Java Tests Affects Versions: 0.6 Reporter: Aidan Skinner Assignee: Aidan Skinner Fix For: 0.6 There is no high level system test for persistent stores -- 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-1962) FirewallPluginTest.testSingleHostWilcardRule is dependent on 127.0.0.1 resolving to localhost
[ https://issues.apache.org/jira/browse/QPID-1962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1962. - Resolution: Fixed FirewallPluginTest.testSingleHostWilcardRule is dependent on 127.0.0.1 resolving to localhost - Key: QPID-1962 URL: https://issues.apache.org/jira/browse/QPID-1962 Project: Qpid Issue Type: Bug Components: Java Tests Affects Versions: 0.6 Reporter: Aidan Skinner Assignee: Aidan Skinner Fix For: 0.6 And that isn't necessarily always true. Sometimes people have /etc/hosts set right. -- 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-1626) Pluggable authorization modules
[ https://issues.apache.org/jira/browse/QPID-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1626. - Resolution: Fixed Pluggable authorization modules --- Key: QPID-1626 URL: https://issues.apache.org/jira/browse/QPID-1626 Project: Qpid Issue Type: Improvement Components: Java Broker Reporter: Aidan Skinner Assignee: Aidan Skinner Fix For: 0.6 Authorization is almost, but not quite, pluggable atm. A sketch design is at http://qpid.apache.org/java-authorization-plugins.html and broadly involves implementing an AuthorizationManager which talks to a collection of plugins to authorize requests. -- 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-2026) Add NetworkConfiguration type
[ https://issues.apache.org/jira/browse/QPID-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2026. - Resolution: Fixed Add NetworkConfiguration type - Key: QPID-2026 URL: https://issues.apache.org/jira/browse/QPID-2026 Project: Qpid Issue Type: Sub-task Components: Java Broker Affects Versions: 0.5 Reporter: Aidan Skinner Assignee: Aidan Skinner Fix For: 0.6 See http://cwiki.apache.org/confluence/display/qpid/Port+server+to+new+interface#Portservertonewinterface-ImplementNetworkConfiguration for details -- 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-2105) Client should use NetworkDriver/ProtocolEngine interfaces
[ https://issues.apache.org/jira/browse/QPID-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2105. - Resolution: Fixed Client should use NetworkDriver/ProtocolEngine interfaces - Key: QPID-2105 URL: https://issues.apache.org/jira/browse/QPID-2105 Project: Qpid Issue Type: Improvement Components: Java Client, Java Common Affects Versions: 0.6 Reporter: Aidan Skinner Assignee: Aidan Skinner Fix For: 0.6 The client should use the spiffy new NetworkDriver/ProtocolEngine interfaces to make the seperation between protocol handling the transport layer cleaner. -- 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-2111) SelectorTest is split into two and doesn't test runtime selector exceptions
[ https://issues.apache.org/jira/browse/QPID-2111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2111. - Resolution: Fixed SelectorTest is split into two and doesn't test runtime selector exceptions --- Key: QPID-2111 URL: https://issues.apache.org/jira/browse/QPID-2111 Project: Qpid Issue Type: Improvement Components: Java Tests Affects Versions: 0.6 Reporter: Aidan Skinner Assignee: Aidan Skinner Priority: Minor Fix For: 0.6 SelectorTest exists in two places and only tests parse-time selector errors, not if a runtime error occurs such as trying a mathmatical operation on a string property. -- 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-2111) SelectorTest is split into two and doesn't test runtime selector exceptions
SelectorTest is split into two and doesn't test runtime selector exceptions --- Key: QPID-2111 URL: https://issues.apache.org/jira/browse/QPID-2111 Project: Qpid Issue Type: Improvement Components: Java Tests Affects Versions: 0.6 Reporter: Aidan Skinner Assignee: Aidan Skinner Priority: Minor Fix For: 0.6 SelectorTest exists in two places and only tests parse-time selector errors, not if a runtime error occurs such as trying a mathmatical operation on a string property. -- 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-2105) Client should use NetworkDriver/ProtocolEngine interfaces
Client should use NetworkDriver/ProtocolEngine interfaces - Key: QPID-2105 URL: https://issues.apache.org/jira/browse/QPID-2105 Project: Qpid Issue Type: Improvement Components: Java Client, Java Common Affects Versions: 0.6 Reporter: Aidan Skinner Assignee: Aidan Skinner Fix For: 0.6 The client should use the spiffy new NetworkDriver/ProtocolEngine interfaces to make the seperation between protocol handling the transport layer cleaner. -- 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-2106) Broker viciously closes connections when a client is asked to close a channel
Broker viciously closes connections when a client is asked to close a channel - Key: QPID-2106 URL: https://issues.apache.org/jira/browse/QPID-2106 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.6 Reporter: Aidan Skinner Assignee: Aidan Skinner Fix For: 0.6 The broker will basically always close a connection when it's asked a channel to close since it issues the ChannelClose and then will close the connection if the next frame it recieves on that channel is not ChannelCloseOk. It's quite likely that there will be frames that it has not processed that the client sent before the broker issues ChannelClose, it will immediately shut the connection. A better thing to do is to ignore incoming frames that aren't ChannelCloseOk and close the connection only if it hasn't been removed for a while. -- 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-2073) reduce the minimum vertical footprint of the QueueOperations tab to better suit use with a 1024x768 screen resolution
[ https://issues.apache.org/jira/browse/QPID-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2073. - Resolution: Fixed reduce the minimum vertical footprint of the QueueOperations tab to better suit use with a 1024x768 screen resolution - Key: QPID-2073 URL: https://issues.apache.org/jira/browse/QPID-2073 Project: Qpid Issue Type: Improvement Components: Java Management : JMX Console Affects Versions: 0.6 Reporter: Robbie Gemmell Assignee: Aidan Skinner Fix For: 0.6 reduce the minimum vertical footprint of the QueueOperations tab to better suit use with a 1024x768 screen resolution -- 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-2070) open the default queue mbean when double clicking a channel entry
[ https://issues.apache.org/jira/browse/QPID-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2070. - Resolution: Fixed open the default queue mbean when double clicking a channel entry - Key: QPID-2070 URL: https://issues.apache.org/jira/browse/QPID-2070 Project: Qpid Issue Type: Improvement Components: Java Management : JMX Console Affects Versions: 0.6 Reporter: Robbie Gemmell Assignee: Aidan Skinner Priority: Minor Fix For: 0.6 The Connection Operations tab does not allow double clicking a Channel entry with a default queue name in order to open the queue mbean, as other views do support. This should be added. -- 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-2060) LogMonitorTest.testWaitForMessage_Found fails
[ https://issues.apache.org/jira/browse/QPID-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2060. - Resolution: Fixed LogMonitorTest.testWaitForMessage_Found fails - Key: QPID-2060 URL: https://issues.apache.org/jira/browse/QPID-2060 Project: Qpid Issue Type: Bug Components: Java Tests Affects Versions: 0.6 Reporter: Aidan Skinner Assignee: Aidan Skinner Fix For: 0.6 Testcase: testWaitForMessage_Found took 2.177 sec FAILED Message was not logged junit.framework.AssertionFailedError: Message was not logged at org.apache.qpid.util.LogMonitorTest.testWaitForMessage_Found(LogMonitorTest.java:176) -- 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-2069) Headers Exchange MBean rejects new bindings that contains keys with an empty value
[ https://issues.apache.org/jira/browse/QPID-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2069. - Resolution: Fixed Headers Exchange MBean rejects new bindings that contains keys with an empty value -- Key: QPID-2069 URL: https://issues.apache.org/jira/browse/QPID-2069 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: M2.1, M3, M4, 0.5 Reporter: Robbie Gemmell Assignee: Aidan Skinner Priority: Minor Fix For: 0.6 The HeadersExchange MBean places invalid restrictions on the input when creating new bindings. The MBean rejects new bindings that contain empty values for a key, but the HeaderBinding places no such restriction on its input and explicitly defines this input to be valid; an empty or null value for a given key indicates the key should be matched on presence alone. -- 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-2068) add a key-value based dialog for creating headers exchange bindings
[ https://issues.apache.org/jira/browse/QPID-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2068. - Resolution: Fixed add a key-value based dialog for creating headers exchange bindings --- Key: QPID-2068 URL: https://issues.apache.org/jira/browse/QPID-2068 Project: Qpid Issue Type: Improvement Components: Java Management : JMX Console Affects Versions: 0.6 Reporter: Robbie Gemmell Assignee: Aidan Skinner Priority: Minor Fix For: 0.6 The new console UI currently requires users to type in new bindings for a headers exchange in the format: key=value,key=value which is not obvious and can be error prone, leading to creation of an incorrect binding. The old UI made a custom area of text fields to gather the keys and values, this should be updated and added to the new UI. Default values will be added for the 'x-match' key that must be set to configure the matching behaviour of the binding. Incorrect restrictions placed on the value of a key in the old UI will be removed, as it is valid to specify an empty or null value for a given key, indicating the key should be matched on presence alone. -- 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-1981) Expose message copying ability through JMX
[ https://issues.apache.org/jira/browse/QPID-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1981. - Resolution: Fixed Expose message copying ability through JMX -- Key: QPID-1981 URL: https://issues.apache.org/jira/browse/QPID-1981 Project: Qpid Issue Type: New Feature Components: Java Broker, Java Management : JMX Console Reporter: Robbie Gemmell Assignee: Aidan Skinner Fix For: 0.6 The Queue implementations support the ability of copying messages to another queue, but this is not exposed through the relevant JMX MBean. This should be exposed as JMX operation and supported in the new management console UI. -- 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-1990) provide ability to determine queue order of messages when viewing via JMX
[ https://issues.apache.org/jira/browse/QPID-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1990. - Resolution: Fixed provide ability to determine queue order of messages when viewing via JMX - Key: QPID-1990 URL: https://issues.apache.org/jira/browse/QPID-1990 Project: Qpid Issue Type: New Feature Components: Java Broker, Java Management : JMX Console Affects Versions: M2.1, M3, M4, 0.5 Reporter: Robbie Gemmell Assignee: Aidan Skinner Fix For: 0.6 It is not currently possible to determine the queue order of messages (which may not equal their respective IDs due to moving messages etc) from the results returned by the JMX interface, as the TabularData OpenData container does not provide ordering. A 'queue position' field will be added to the result set to allow sorting by queue order in future -- 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-2056) the Add To Favourites and Open Queue buttons stop working after changing the attribute selection on the Queues selection view
[ https://issues.apache.org/jira/browse/QPID-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2056. - Resolution: Fixed the Add To Favourites and Open Queue buttons stop working after changing the attribute selection on the Queues selection view - Key: QPID-2056 URL: https://issues.apache.org/jira/browse/QPID-2056 Project: Qpid Issue Type: Bug Components: Java Management : JMX Console Affects Versions: 0.6 Reporter: Robbie Gemmell Assignee: Aidan Skinner Priority: Minor Fix For: 0.6 the Add To Favourites and Open Queue buttons stop working after changing the attribute selection on the Queues selection view. This is because changing the attributes involves recreating the table and the selection listeners are no longer attached to the table in view. -- 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-1980) Java broker does not parse protection I/O configuration with expected XML structure
[ https://issues.apache.org/jira/browse/QPID-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1980. - Resolution: Fixed Java broker does not parse protection I/O configuration with expected XML structure --- Key: QPID-1980 URL: https://issues.apache.org/jira/browse/QPID-1980 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.5 Reporter: Keith Chow Assignee: Aidan Skinner Priority: Minor Attachments: ServerConfiguration.java.diff The following is the default 0.5 java broker config.xml structure for protection I/O related configuration. broker connector qpidniofalse/qpidnio protectio enabledfalse/enabled /protectio /connector /broker But ServerConfiguration expects a config value with key broker.connector.protectio.enabled, which makes the broker. prefix appears to be extraneous if the default config's XML structure is correct. -- 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-2059) SubscriptionLoggingTest fails intermittently
[ https://issues.apache.org/jira/browse/QPID-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2059. - Resolution: Fixed SubscriptionLoggingTest fails intermittently Key: QPID-2059 URL: https://issues.apache.org/jira/browse/QPID-2059 Project: Qpid Issue Type: Bug Components: Java Tests Affects Versions: 0.6 Reporter: Aidan Skinner Assignee: Aidan Skinner Fix For: 0.6 SubscriptionLoggingTest sometimes fails with: junit.framework.AssertionFailedError: Result set not expected size: expected:3 but was:1 at org.apache.qpid.server.logging.SubscriptionLoggingTest.testSubscriptionSuspend(SubscriptionLoggingTest.java:363) at org.apache.qpid.test.utils.QpidTestCase.runBare(QpidTestCase.java:224) at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:270) -- 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-1991) remove the containing Type folders for the top-level single mbeans in the server navigation tree
[ https://issues.apache.org/jira/browse/QPID-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1991. - Resolution: Fixed remove the containing Type folders for the top-level single mbeans in the server navigation tree Key: QPID-1991 URL: https://issues.apache.org/jira/browse/QPID-1991 Project: Qpid Issue Type: Improvement Components: Java Management : JMX Console Affects Versions: M2.1, M3, M4, 0.5 Reporter: Robbie Gemmell Assignee: Aidan Skinner Fix For: 0.6 There are mbeans presented at the top level of the server navigation tree, eg User Management, Logging Management etc. These are contained in a folder indicating their type, which makes the navigation tree larger and more cumbersome to interact with, and so they should be removed to expose the mbean directly. -- 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-1994) auto-refresh mechanism can generate NPE during application shutdown
[ https://issues.apache.org/jira/browse/QPID-1994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1994. - Resolution: Fixed auto-refresh mechanism can generate NPE during application shutdown --- Key: QPID-1994 URL: https://issues.apache.org/jira/browse/QPID-1994 Project: Qpid Issue Type: Bug Components: Java Management : JMX Console Affects Versions: 0.6 Reporter: Robbie Gemmell Assignee: Aidan Skinner Priority: Minor Fix For: 0.6 The automated refreshing mechanism can generate a NullPointerException if the application shutdown is timed such that a refresh is attempted during the shutdown process. -- 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-1999) the Clear button in each VirtualHost Notifications area still clears all server-wide Notifications
[ https://issues.apache.org/jira/browse/QPID-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1999. - Resolution: Fixed the Clear button in each VirtualHost Notifications area still clears all server-wide Notifications -- Key: QPID-1999 URL: https://issues.apache.org/jira/browse/QPID-1999 Project: Qpid Issue Type: Bug Components: Java Management : JMX Console Affects Versions: 0.6 Reporter: Robbie Gemmell Assignee: Aidan Skinner Fix For: 0.6 The VirtualHost Notifications areas usedto display all Notifications for the entire server, but have now been restricted to those only for the specific VirtualHost in question. However, the clear button in each VirtualHost Notifications area still clears all server-wide Notifications as before. -- 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-2000) retrieving attributes for the queue selection list takes excessively long with large numbers of queues
[ https://issues.apache.org/jira/browse/QPID-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2000. - Resolution: Fixed retrieving attributes for the queue selection list takes excessively long with large numbers of queues -- Key: QPID-2000 URL: https://issues.apache.org/jira/browse/QPID-2000 Project: Qpid Issue Type: Improvement Components: Java Management : JMX Console Affects Versions: M2, M2.1, M3, M4, 0.5 Reporter: Robbie Gemmell Assignee: Aidan Skinner Priority: Critical Fix For: 0.6 Retrieving attributes for the queue selection list takes excessively long with a large (eg 10k) number of queues, freezing the interface for several seconds. This is due to the sheer number of RPC calls that have to be made to retrieve the data, so a method will be added to the JMX mbeans to allow collection of the information in a single call, and the console adapted accordingly. -- 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-2005) change the Fanout Exchange JMX bindings() results to return a single binding entry with all bound queues
[ https://issues.apache.org/jira/browse/QPID-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2005. - Resolution: Fixed change the Fanout Exchange JMX bindings() results to return a single binding entry with all bound queues Key: QPID-2005 URL: https://issues.apache.org/jira/browse/QPID-2005 Project: Qpid Issue Type: Improvement Components: Java Broker, Java Management : JMX Console Affects Versions: M2.1, M3, M4, 0.5 Reporter: Robbie Gemmell Assignee: Aidan Skinner Fix For: 0.6 The Fanout Exchange JMX MBean currently returns a series of CompositeData elements containing the queue name and an array also containing the queue name. This produces a results view whereby there is a 'binding key' for every queue bound to the exchange (when infact no binding key at all is used for the exchange), each associated with the single queue. To be more representative of the actual process within the exchange, this will be changed to return a single CompositeData element within the TabularData which contains a 'wildcard binding' with all the queue names in the associated list, indicating all bound queues are enqueued to. -- 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-2003) Coverage report is unable to show generated files
[ https://issues.apache.org/jira/browse/QPID-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2003. - Resolution: Fixed Coverage report is unable to show generated files - Key: QPID-2003 URL: https://issues.apache.org/jira/browse/QPID-2003 Project: Qpid Issue Type: Bug Components: Build Tools Affects Versions: 0.6 Reporter: Martin Ritchie Assignee: Aidan Skinner Fix For: 0.6 Summary: When viewing the coverage report (ant coverage-report) coverage is provided for generated file however the marked up source is not show for generated classes as the scratch space is not added to the list of files for cobertura to process. -- 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-2007) new UI dialogs open in the upper left corner of the screen on Windows
[ https://issues.apache.org/jira/browse/QPID-2007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2007. - Resolution: Fixed new UI dialogs open in the upper left corner of the screen on Windows - Key: QPID-2007 URL: https://issues.apache.org/jira/browse/QPID-2007 Project: Qpid Issue Type: Bug Components: Java Management : JMX Console Affects Versions: 0.6 Reporter: Robbie Gemmell Assignee: Aidan Skinner Priority: Minor Fix For: 0.6 Several parts of the new UI include custom dialogs for taking user input. On Linux these new shells open in the centre of the parent however, in WIndows they instead open at or near the upper left corner of the screen the application is running. They should instead be centred on the application or the monitor. -- 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-2009) password fields are not masked in the new UserManagement UI
[ https://issues.apache.org/jira/browse/QPID-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2009. - Resolution: Fixed password fields are not masked in the new UserManagement UI --- Key: QPID-2009 URL: https://issues.apache.org/jira/browse/QPID-2009 Project: Qpid Issue Type: Bug Components: Java Management : JMX Console Affects Versions: 0.6 Reporter: Robbie Gemmell Assignee: Aidan Skinner Priority: Minor Fix For: 0.6 password fields are not masked in the new UserManagement UI -- 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-2008) queue names are not sorted when presented for user selection in some new UI dialogs
[ https://issues.apache.org/jira/browse/QPID-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2008. - Resolution: Fixed queue names are not sorted when presented for user selection in some new UI dialogs --- Key: QPID-2008 URL: https://issues.apache.org/jira/browse/QPID-2008 Project: Qpid Issue Type: Bug Components: Java Management : JMX Console Affects Versions: 0.6 Reporter: Robbie Gemmell Assignee: Aidan Skinner Priority: Minor Fix For: 0.6 queue names are not sorted when presented for user selection in some new UI dialogs -- 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-2013) Previous/Next N Message button in queue browser should take current size as step size
[ https://issues.apache.org/jira/browse/QPID-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2013. - Resolution: Fixed Previous/Next N Message button in queue browser should take current size as step size - Key: QPID-2013 URL: https://issues.apache.org/jira/browse/QPID-2013 Project: Qpid Issue Type: Improvement Components: Java Management : JMX Console Affects Versions: 0.6 Reporter: Aidan Skinner Assignee: Aidan Skinner Fix For: 0.6 It would be clearer to calculate the size of the currently displayed range of messages and use that for the size of messages the next/previous buttons step through. So if you displayed messages 20-30 you'd have previous 10 and next 10 buttons. -- 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-2014) Clear notifications should prompt when clearing all of them
[ https://issues.apache.org/jira/browse/QPID-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2014. - Resolution: Fixed Clear notifications should prompt when clearing all of them --- Key: QPID-2014 URL: https://issues.apache.org/jira/browse/QPID-2014 Project: Qpid Issue Type: Improvement Components: Java Management : JMX Console Affects Versions: 0.6 Reporter: Aidan Skinner Assignee: Aidan Skinner Fix For: 0.6 The clear notifications button removes all the notifications if none are selected. This is a good choice of behaviour, but could be made safer with a are you sure? yes/no prompt in case of user error. -- 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-2016) Reload Log4J configuration file
[ https://issues.apache.org/jira/browse/QPID-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2016. - Resolution: Fixed Reload Log4J configuration file --- Key: QPID-2016 URL: https://issues.apache.org/jira/browse/QPID-2016 Project: Qpid Issue Type: Improvement Components: Java Broker, Java Management : JMX Console Affects Versions: 0.6 Reporter: Aidan Skinner Assignee: Aidan Skinner Fix For: 0.6 After changing the log4j configuration file through the management console it would be good to be able to force a reload of the file without having to have the watch interval configured. -- 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-2015) Add ability to configure attributes shown on queue list
[ https://issues.apache.org/jira/browse/QPID-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2015. - Resolution: Fixed Add ability to configure attributes shown on queue list --- Key: QPID-2015 URL: https://issues.apache.org/jira/browse/QPID-2015 Project: Qpid Issue Type: Improvement Components: Java Management : JMX Console Affects Versions: 0.6 Reporter: Aidan Skinner Assignee: Aidan Skinner Fix For: 0.6 The information about a queue displayed on the VirtualHost queue list view that a user would find useful varies by use case. It would be good to provide a means for any queue attribute to be added or removed from this view. The list of attributes should be persisted between invocations of the management console and should be shared across all instances of the queue view, not just per virtualhost or per broker. -- 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-2018) Clear queue doesn't clear acquired messages which is a little confusing if that's all there is.
[ https://issues.apache.org/jira/browse/QPID-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2018. - Resolution: Fixed Clear queue doesn't clear acquired messages which is a little confusing if that's all there is. --- Key: QPID-2018 URL: https://issues.apache.org/jira/browse/QPID-2018 Project: Qpid Issue Type: Bug Components: Java Broker, Java Management : JMX Console Affects Versions: M2.1, M3, M4, 0.5 Reporter: Aidan Skinner Assignee: Aidan Skinner Priority: Minor Fix For: 0.6 The clear queue button prompts but doesn't actually clear the queue. I suspect because all the messages have been acquired by consumers. This should probably display a better error message if there are acquired messages which can't be cleared. An int return of uncleared ones maybe? -- 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-2021) provide new icons to distinguish the various 'manager' mbeans
[ https://issues.apache.org/jira/browse/QPID-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2021. - Resolution: Fixed provide new icons to distinguish the various 'manager' mbeans - Key: QPID-2021 URL: https://issues.apache.org/jira/browse/QPID-2021 Project: Qpid Issue Type: Improvement Components: Java Management : JMX Console Affects Versions: M2.1, M3, M4 Reporter: Robbie Gemmell Assignee: Aidan Skinner Priority: Trivial Fix For: 0.6 The console currently uses the same icon for all the mbean objects in the navigation tree. It would be helpful if the various 'manager' mbeans were visually identifiable. -- 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-2032) AddUser operation in the new UserManagement UI does not MD5 hash the password when connected to pre-0.5 brokers
[ https://issues.apache.org/jira/browse/QPID-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2032. - Resolution: Fixed AddUser operation in the new UserManagement UI does not MD5 hash the password when connected to pre-0.5 brokers --- Key: QPID-2032 URL: https://issues.apache.org/jira/browse/QPID-2032 Project: Qpid Issue Type: Bug Components: Java Management : JMX Console Affects Versions: 0.6 Reporter: Robbie Gemmell Assignee: Aidan Skinner Priority: Critical Fix For: 0.6 Older brokers (pre 0.5) require the user password to be presented by the console in MD5 hashed format. This was changed to plain text in 0.5 when the PlainPasswordFilePrincipleDatabase was updated to allow manipulation using the management console. As a result, the console must detect the broker management API version and send the appropriate content when creating users on older brokers. The new UI is currently not doing this (although does when altering the password). -- 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-2037) navigation tree node doesnt auto-expand upon connection when adding a new server
[ https://issues.apache.org/jira/browse/QPID-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2037. - Resolution: Fixed navigation tree node doesnt auto-expand upon connection when adding a new server Key: QPID-2037 URL: https://issues.apache.org/jira/browse/QPID-2037 Project: Qpid Issue Type: Bug Components: Java Management : JMX Console Affects Versions: 0.5, 0.6 Reporter: Robbie Gemmell Assignee: Aidan Skinner Priority: Minor Fix For: 0.6 The navigation tree node for a server doesnt auto-expand upon connection when adding a new server, but does when reconnecting an existing server. -- 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-2039) the JMX ConnectorServer is not closed during shutdown of the JMXManagedObjectRegistry
[ https://issues.apache.org/jira/browse/QPID-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2039. - Resolution: Fixed the JMX ConnectorServer is not closed during shutdown of the JMXManagedObjectRegistry - Key: QPID-2039 URL: https://issues.apache.org/jira/browse/QPID-2039 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: M2.1, M3, M4, 0.5 Reporter: Robbie Gemmell Assignee: Aidan Skinner Fix For: 0.6 the JMX ConnectorServer is not closed during shutdown of the JMXManagedObjectRegistry -- 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-2040) failed update to the PlainPasswordFilePrincipalDatabase on disk may go unnoticed, preventing broker restart
[ https://issues.apache.org/jira/browse/QPID-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2040. - Resolution: Fixed failed update to the PlainPasswordFilePrincipalDatabase on disk may go unnoticed, preventing broker restart --- Key: QPID-2040 URL: https://issues.apache.org/jira/browse/QPID-2040 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.5 Reporter: Robbie Gemmell Assignee: Aidan Skinner Priority: Critical Fix For: 0.6 failed update to the PlainPasswordFilePrincipalDatabase on disk may go unnoticed, preventing broker restart Certain use of the File.renameTo() function is not accompanied by a check of the boolean result, meaning a failed rename can leave the file in the wrong location, but the cached nature of the PlainPasswordFilePrincipalDatabase masks the failure until another operation is attempted upon it that needs the output of the previously failed update. This has been observed in a situation where the OS Temp dir is on one (local) file system, and the broker configuration is on another (remote NFS) filesystem, which caused the rename to fail unnoticed. -- 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-2044) create a new JMX management console user guide
[ https://issues.apache.org/jira/browse/QPID-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2044. - Resolution: Fixed create a new JMX management console user guide -- Key: QPID-2044 URL: https://issues.apache.org/jira/browse/QPID-2044 Project: Qpid Issue Type: Task Components: Java Management : JMX Console Reporter: Robbie Gemmell Assignee: Aidan Skinner Fix For: 0.6 The updated UI for the console has rendered the user guide even further out of date, and a new one should be created. -- 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-2042) update to the management access rights may not be saved to disk, but still report success
[ https://issues.apache.org/jira/browse/QPID-2042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2042. - Resolution: Fixed update to the management access rights may not be saved to disk, but still report success - Key: QPID-2042 URL: https://issues.apache.org/jira/browse/QPID-2042 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.5 Reporter: Robbie Gemmell Assignee: Aidan Skinner Priority: Critical Fix For: 0.6 update to the management access rights may not be saved to disk, but still report success Certain use of the File.renameTo() function is not accompanied by a check of the boolean result, meaning a failed rename can leave the new file in the wrong location. As a result the existing file may not be replaced without indication of error, though the cached rights will have been updated, meaning the update would appear successful but simply be temporary. This has been observed in a situation where the OS Temp dir is on one (local) file system, and the broker configuration is on another (remote NFS) filesystem, which caused the rename to fail unnoticed. -- 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-2052) allow setting a Log4J logger to inherit its level from an ancestor
[ https://issues.apache.org/jira/browse/QPID-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2052. - Resolution: Fixed allow setting a Log4J logger to inherit its level from an ancestor -- Key: QPID-2052 URL: https://issues.apache.org/jira/browse/QPID-2052 Project: Qpid Issue Type: Improvement Components: Java Broker Affects Versions: 0.5 Reporter: Robbie Gemmell Assignee: Aidan Skinner Fix For: 0.6 allow setting a Log4J logger to inherit its level from an ancestor -- 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-2077) ManagementActorLoggingTest fails to tearDown cleanly
[ https://issues.apache.org/jira/browse/QPID-2077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2077. - Resolution: Fixed ManagementActorLoggingTest fails to tearDown cleanly Key: QPID-2077 URL: https://issues.apache.org/jira/browse/QPID-2077 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.6 Reporter: Martin Ritchie Assignee: Aidan Skinner ManagementActorLoggingTest fails to tearDown cleanly: TestName: testConnectionCloseViaManagement Duration: 2.389 Error closing connection: org.apache.qpid.AMQException: Woken up due to class javax.jms.JMSException javax.jms.JMSException: Error closing connection: org.apache.qpid.AMQException: Woken up due to class javax.jms.JMSException at org.apache.qpid.client.AMQConnection.doClose(AMQConnection.java:1046) at org.apache.qpid.client.AMQConnection.close(AMQConnection.java:981) at org.apache.qpid.client.AMQConnection.close(AMQConnection.java:972) at org.apache.qpid.client.AMQConnection.close(AMQConnection.java:967) at org.apache.qpid.test.utils.QpidTestCase.tearDown(QpidTestCase.java:875) at org.apache.qpid.server.logging.AbstractTestLogging.tearDown(AbstractTestLogging.java:48) at org.apache.qpid.management.jmx.ManagementActorLoggingTest.tearDown(ManagementActorLoggingTest.java:76) at org.apache.qpid.test.utils.QpidTestCase.runBare(QpidTestCase.java:224) at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:270) -- 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-2059) SubscriptionLoggingTest fails intermittently
SubscriptionLoggingTest fails intermittently Key: QPID-2059 URL: https://issues.apache.org/jira/browse/QPID-2059 Project: Qpid Issue Type: Bug Components: Java Tests Affects Versions: 0.6 Reporter: Aidan Skinner Assignee: Aidan Skinner Fix For: 0.6 SubscriptionLoggingTest sometimes fails with: junit.framework.AssertionFailedError: Result set not expected size: expected:3 but was:1 at org.apache.qpid.server.logging.SubscriptionLoggingTest.testSubscriptionSuspend(SubscriptionLoggingTest.java:363) at org.apache.qpid.test.utils.QpidTestCase.runBare(QpidTestCase.java:224) at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:270) -- 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-2024) Add MINANetworkDriver
[ https://issues.apache.org/jira/browse/QPID-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner updated QPID-2024: Status: Ready To Review (was: In Progress) Add MINANetworkDriver - Key: QPID-2024 URL: https://issues.apache.org/jira/browse/QPID-2024 Project: Qpid Issue Type: Sub-task Affects Versions: 0.5 Reporter: Aidan Skinner Assignee: Aidan Skinner Fix For: 0.6 see http://cwiki.apache.org/confluence/display/qpid/Port+server+to+new+interface#Portservertonewinterface-ImplementNetworkDriver for details -- 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-1777) JNDI problem with white spaces
[ https://issues.apache.org/jira/browse/QPID-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1777. - Resolution: Fixed JNDI problem with white spaces -- Key: QPID-1777 URL: https://issues.apache.org/jira/browse/QPID-1777 Project: Qpid Issue Type: Bug Components: Java Client Environment: all Reporter: Ffrench Mathilde Assignee: Rajith Attapattu Trailing spaces in queue and topic definitions are not discarded. This leads to other errors as users think the Queue name is myQueue (while the real queue name is myQueue where are trailing spaces) and tries to use that name with management tools and fails to delete, purge ..etc Ex when defining in JNDI properties file if there are trailling spaces as follows. queue.myqueue = my_queue topic.mytopic = my_topic topic.mytopic2 = my_bk1XX, my_bk2XX, my_bk3XX where are trailing spaces. The created queue names are as follows my_queue instead of my_queue -- 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-1875) Can't create durable queues that use amq.topic due to error in BindingURLParser.
[ https://issues.apache.org/jira/browse/QPID-1875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1875. - Resolution: Fixed Can't create durable queues that use amq.topic due to error in BindingURLParser. Key: QPID-1875 URL: https://issues.apache.org/jira/browse/QPID-1875 Project: Qpid Issue Type: Bug Components: Java Client Reporter: Rajith Attapattu Assignee: Rajith Attapattu Priority: Minor Fix For: 0.6 In BindingURLParser, process options method, line 420 has the following error queueName = _bindingURL.getOption(BindingURL.OPTION_CLIENTID + : + BindingURL.OPTION_SUBSCRIPTION); This results in the queue name being null and the subsequent queue-declare failing. It should be corrected to the following queueName = _bindingURL.getOption(BindingURL.OPTION_CLIENTID + : + BindingURL.OPTION_SUBSCRIPTION); However I am not sure if forcing a particular pattern for the queue name and treating it as a durable subscription if the exchange is amq.topic and queue is durable is correct either. This will create confusion as when they tried to work with this queue using mgt-tools or connect with other non java clients, it may not be obvious that the queue name was generated in this case. The users should have the freedom to define a queue name of their choice. There is a clear path to create durable subscriptions in the JMS API. So I don't think we need to force it in the jndi.properties format. -- 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-1887) JMS TTL not working
[ https://issues.apache.org/jira/browse/QPID-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1887. - Resolution: Fixed JMS TTL not working --- Key: QPID-1887 URL: https://issues.apache.org/jira/browse/QPID-1887 Project: Qpid Issue Type: Bug Components: Java Client Affects Versions: M4 Reporter: Rajith Attapattu Assignee: Rajith Attapattu Fix For: 0.6 Even ff ttl is set in the message producer, it does not get set properly in the message properties. Hence the broker is not expiring them. In the 0-10 codepath, the JMS client was incorrectly setting the expiration field instead of the ttl field. This is also related to QPID-1575 -- 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-1854) If a SocketTimeoutException is thrown due to an idle conneciton, the IoSender thread does not get closed.
[ https://issues.apache.org/jira/browse/QPID-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1854. - Resolution: Fixed If a SocketTimeoutException is thrown due to an idle conneciton, the IoSender thread does not get closed. - Key: QPID-1854 URL: https://issues.apache.org/jira/browse/QPID-1854 Project: Qpid Issue Type: Bug Components: Java Client Affects Versions: M4 Reporter: Rajith Attapattu Assignee: Rajith Attapattu Priority: Critical Fix For: 0.6 If SocketTimeoutException is thrown due to heartbeats not received then the java client does not close the IoSender properly. This can be verified by running the java client with failover and obtaining a thread dump after each failover attempt. -- 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-1853) IoReceiver is not closing the socket if a SocketTimeoutException thrown
[ https://issues.apache.org/jira/browse/QPID-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1853. - Resolution: Fixed IoReceiver is not closing the socket if a SocketTimeoutException thrown --- Key: QPID-1853 URL: https://issues.apache.org/jira/browse/QPID-1853 Project: Qpid Issue Type: Bug Components: Java Client Affects Versions: M4 Reporter: Rajith Attapattu Assignee: Rajith Attapattu Priority: Critical Fix For: 0.6 If a SocketTimeoutException is thrown then the IoReceiver does not close the socket connection. For that matter if the while loop in the run method of the IoReceiver does not exit normally due to an exception (that does not result in the socket being closed) then the socket connection remains open. This causes tcp connections to remain open. Eventually due to failover triggered by heartbeats not sent (which results in SocketTimeoutException) the number of connections keeps growing. -- 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-1966) add status bar for feedback reports
[ https://issues.apache.org/jira/browse/QPID-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1966. - Resolution: Fixed Nice work! :) add status bar for feedback reports --- Key: QPID-1966 URL: https://issues.apache.org/jira/browse/QPID-1966 Project: Qpid Issue Type: Sub-task Components: Java Management : JMX Console Reporter: Robbie Gemmell Assignee: Aidan Skinner add status bar for feedback reports -- 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-1969) per-virtualhost notification areas show all notifications sent by the server
[ https://issues.apache.org/jira/browse/QPID-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1969. - Resolution: Fixed Looks good per-virtualhost notification areas show all notifications sent by the server Key: QPID-1969 URL: https://issues.apache.org/jira/browse/QPID-1969 Project: Qpid Issue Type: Sub-task Components: Java Management : JMX Console Affects Versions: M2.1, M3, M4, 0.5 Reporter: Robbie Gemmell Assignee: Aidan Skinner Fix For: 0.6 The console offers per-virtualhost notification areas, however these show all notifications sent by the server instead of just those related to the virtual host being examined -- 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-1968) expose ability to delete arbitrary message from queue
[ https://issues.apache.org/jira/browse/QPID-1968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1968. - Resolution: Fixed expose ability to delete arbitrary message from queue - Key: QPID-1968 URL: https://issues.apache.org/jira/browse/QPID-1968 Project: Qpid Issue Type: Sub-task Components: Java Broker, Java Management : JMX Console Reporter: Robbie Gemmell Assignee: Aidan Skinner Fix For: 0.6 Currently you can only delete the first message on a queue. It would be useful if you could instead delete an arbitrary message of your choice. The queue implementation supports this but it is not currently exposed through JMX. It will be exposed as an operation and support added to the new management console UI. -- 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-2023) Import org.apache.mina.common.ByteBuffer and use that instead
Import org.apache.mina.common.ByteBuffer and use that instead - Key: QPID-2023 URL: https://issues.apache.org/jira/browse/QPID-2023 Project: Qpid Issue Type: Sub-task Components: Java Broker, Java Common Affects Versions: 0.5 Reporter: Aidan Skinner Assignee: Aidan Skinner Fix For: 0.6 see http://cwiki.apache.org/confluence/display/qpid/Port+server+to+new+interface#Portservertonewinterface-AddQpidByteBuffer -- 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-2027) Transport layer selection in o.a.q.server.Main
Transport layer selection in o.a.q.server.Main -- Key: QPID-2027 URL: https://issues.apache.org/jira/browse/QPID-2027 Project: Qpid Issue Type: Sub-task Affects Versions: 0.5 Reporter: Aidan Skinner Assignee: Aidan Skinner Fix For: 0.6 See http://cwiki.apache.org/confluence/display/qpid/Port+server+to+new+interface#Portservertonewinterface-Transportlayerselectionino.a.q.server.Main for details -- 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-1943) create a new view for the Exchange mbeans
[ https://issues.apache.org/jira/browse/QPID-1943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1943. - Resolution: Fixed create a new view for the Exchange mbeans - Key: QPID-1943 URL: https://issues.apache.org/jira/browse/QPID-1943 Project: Qpid Issue Type: Sub-task Components: Java Management : JMX Console Reporter: Robbie Gemmell Assignee: Aidan Skinner -- 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-1944) create a new view for the Connection mbeans
[ https://issues.apache.org/jira/browse/QPID-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1944. - Resolution: Fixed This is svn r793533 and r793534 although Jira seems not to have picked up the commits. create a new view for the Connection mbeans --- Key: QPID-1944 URL: https://issues.apache.org/jira/browse/QPID-1944 Project: Qpid Issue Type: Sub-task Components: Java Management : JMX Console Reporter: Robbie Gemmell Assignee: Aidan Skinner -- 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-1945) create a new view for the VirtualHostManager mbeans
[ https://issues.apache.org/jira/browse/QPID-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1945. - Resolution: Fixed create a new view for the VirtualHostManager mbeans --- Key: QPID-1945 URL: https://issues.apache.org/jira/browse/QPID-1945 Project: Qpid Issue Type: Sub-task Components: Java Management : JMX Console Reporter: Robbie Gemmell Assignee: Aidan Skinner -- 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-1946) add an mbean to present system information, including API versioning for the JMX interface
[ https://issues.apache.org/jira/browse/QPID-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1946. - Resolution: Fixed add an mbean to present system information, including API versioning for the JMX interface -- Key: QPID-1946 URL: https://issues.apache.org/jira/browse/QPID-1946 Project: Qpid Issue Type: Sub-task Components: Java Broker, Java Management : JMX Console Reporter: Robbie Gemmell Assignee: Aidan Skinner -- 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-1947) enable automated update to negate need for users to manually refresh the data
[ https://issues.apache.org/jira/browse/QPID-1947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1947. - Resolution: Fixed enable automated update to negate need for users to manually refresh the data - Key: QPID-1947 URL: https://issues.apache.org/jira/browse/QPID-1947 Project: Qpid Issue Type: Sub-task Components: Java Management : JMX Console Reporter: Robbie Gemmell Assignee: Aidan Skinner -- 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-1961) widen viewMessages(int From, int To) AMQQueueMBean method to use Long values
[ https://issues.apache.org/jira/browse/QPID-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1961. - Resolution: Fixed widen viewMessages(int From, int To) AMQQueueMBean method to use Long values Key: QPID-1961 URL: https://issues.apache.org/jira/browse/QPID-1961 Project: Qpid Issue Type: Sub-task Components: Java Broker, Java Management : JMX Console Affects Versions: M2.1, M3, M4, 0.5 Reporter: Robbie Gemmell Assignee: Aidan Skinner Priority: Minor Fix For: 0.6 The viewMessages() operation is inherently limited to viewing the first 2^31 undelivered messages on the queue at any given time due to its use of int parameters. Equally, getMessageCount() returns an int value. However, the SimpleAMQQueue implementation is not limited to 2^31 messages and so there is potential that not all messages can be viewed. This should be rectified by increasing the parameter range to Long. The viewMessages() implementation will then be limited to viewing ANY 2^31 messages on the queue as the TabularData OpenData result sets used to support generic JMX clients are also fixed in size by an int index. -- 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
