Re: Qpid slogan?
That works for me, but possibly only me. Marnie On Wed, Jan 28, 2009 at 7:58 PM, Robert Greig robert.j.gr...@gmail.comwrote: 2009/1/28 Robert Godfrey rob.j.godf...@gmail.com: Sorry - been away for a couple of days and just caught up with this thread now. Ditto - been unable to read the list for quite a while. Now... time to think of some battle cries... How about: Qpid - no bollocks, just messages RG - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Assigned: (QPID-949) Implement Flow To Disk
[ https://issues.apache.org/jira/browse/QPID-949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marnie McCormack reassigned QPID-949: - Assignee: Martin Ritchie (was: Marnie McCormack) Implement Flow To Disk -- Key: QPID-949 URL: https://issues.apache.org/jira/browse/QPID-949 Project: Qpid Issue Type: New Feature Components: Java Broker Affects Versions: M2.1 Reporter: Marnie McCormack Assignee: Martin Ritchie Fix For: M5 Currently, the Java Broker can do one of two things with a message it has to deliver: 1. Keep transient messages in memory until delivered 2. Write persistent messages to a message store (like BDB) and keep in memory until delivery complete This means that the broker is not able to avoid OoM exceptions i.e. send enough messages to the broker, especially if your consumers are not active, and you could bring the broker done once it explodes its available heap. RG to add more details and design proposal here please :-) -- 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
M5 - JIRAs/Scope
All, If you are working on (or plan to work on) the Java side for M5 - please can you scope anything you intend to do into M5 please ? Martin, Aidan I have scoped the items we're working on into M5 (and are posting about the design for new features). Aside from that, there are two other JIRAs in M5 on the Java side. If this is really the scope/plan for M5, then our roadmap needs revised for this release !! It'd be good to have some discussions about some of the bigger ticket items proposed for M5, but currently these don't appear to be on anyone's list for M5 ? C++ JIRAs for M5 would be good too, but not so dear to my heart ! FYI the Eclipse Management Console items are progressing separately to M5 as we're hoping (as raised before Xmas on the list) for a separate release of that component pre-M5. Regards, Marnie
Re: Qpid slogan?
Sorry, tea-break made me think of a load more!: QPID: Queue This! (a la Matrix: Dodge This! - will appeal to techies) QPID: Quite Perfect Innate Design (or some variant) In a similar vein: QPID: Quite Possibly Iconic Design(or variant - Probably?) This one sounds like someone else's (so apologies in advance) QPID: Quick, Purposeful, Innate Design Ah... my tea's run out... -- Mark On Thu, Jan 29, 2009 at 10:21 AM, Mark Atwell mark.atw...@gmail.com wrote: If you're looking for a T-shirt-like/mug logo how about a play on 'The Classic': I'm with QPid! This also almost works with the arrow-like AMQP logo! BTW is the capitalisation of QPid settled on 'Qpid'? Or possibly: AMQP?: I'm with QPid! AMQP?: I love QPid!(opportunity to go with some Eros/cherub-type-stuff?) QPid loves AMQP BTW I'm not even going to go near the Kenny Everett Show character thing for fear of offence! -- Mark On Wed, Jan 28, 2009 at 1:59 PM, Robert Godfrey rob.j.godf...@gmail.comwrote: Sorry - been away for a couple of days and just caught up with this thread now. 2009/1/27 Jonathan Robie jonathan.ro...@redhat.com: It's OK to differ ;- But let me explain my reasoning: the whole point of a slogan is to establish identity so people know what it is. AMQP and messaging are fundamental to what Qpid is. I think it's interesting here to look at a quick definition (from http://www.thefreedictionary.com/slogan): 1. A phrase expressing the aims or nature of an enterprise, organization, or candidate; a motto. 2. A phrase used repeatedly, as in advertising or promotion: all the slogans and shibboleths coined out of the ideals of the peoples for the uses of imperialism Margaret Sanger. 3. A battle cry of a Scottish clan. What we seem to be arguing about here is whether we want a slogan that fulfils definition 1. or definition 2. (although perhaps the Glasgow contingent would like to make some suggestions fulfil definition 3.) Personally I think that right now we want to have a catchy advertising slogan to draw people in, along with logos etc that work well on marketing material (I want a Qpid t-shirt :-) ). Much as I agree that something like Qpid: Open Source AMQP Messaging succinctly describes the aims of the project, I don't think it draws in people to take a look. Furthermore it does nothing to help people remember the name Qpid. We *do* also need to make sure that in searches for AMQP and Enterprise Messaging, Qpid features highly. However I think there's a fair probability that if you've heard of AMQP you've probably heard of Qpid. So I would probably argue that we need (at least) two different slogans... And of the two I think that advertising and drawing people is is what we are currently more in need of. We need to get the name Qpid out there so that people remember it (even if they don't know what is does)... Now... time to think of some battle cries... -- Rob - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Qpid slogan?
Qpid: The force is with you Qpid: Warp Factor X (I'm not enough of a trekkie to have a better idea) On Thu, Jan 29, 2009 at 10:45 AM, Mark Atwell mark.atw...@gmail.com wrote: Sorry, tea-break made me think of a load more!: QPID: Queue This! (a la Matrix: Dodge This! - will appeal to techies) QPID: Quite Perfect Innate Design (or some variant) In a similar vein: QPID: Quite Possibly Iconic Design(or variant - Probably?) This one sounds like someone else's (so apologies in advance) QPID: Quick, Purposeful, Innate Design Ah... my tea's run out... -- Mark On Thu, Jan 29, 2009 at 10:21 AM, Mark Atwell mark.atw...@gmail.com wrote: If you're looking for a T-shirt-like/mug logo how about a play on 'The Classic': I'm with QPid! This also almost works with the arrow-like AMQP logo! BTW is the capitalisation of QPid settled on 'Qpid'? Or possibly: AMQP?: I'm with QPid! AMQP?: I love QPid!(opportunity to go with some Eros/cherub-type-stuff?) QPid loves AMQP BTW I'm not even going to go near the Kenny Everett Show character thing for fear of offence! -- Mark On Wed, Jan 28, 2009 at 1:59 PM, Robert Godfrey rob.j.godf...@gmail.com wrote: Sorry - been away for a couple of days and just caught up with this thread now. 2009/1/27 Jonathan Robie jonathan.ro...@redhat.com: It's OK to differ ;- But let me explain my reasoning: the whole point of a slogan is to establish identity so people know what it is. AMQP and messaging are fundamental to what Qpid is. I think it's interesting here to look at a quick definition (from http://www.thefreedictionary.com/slogan): 1. A phrase expressing the aims or nature of an enterprise, organization, or candidate; a motto. 2. A phrase used repeatedly, as in advertising or promotion: all the slogans and shibboleths coined out of the ideals of the peoples for the uses of imperialism Margaret Sanger. 3. A battle cry of a Scottish clan. What we seem to be arguing about here is whether we want a slogan that fulfils definition 1. or definition 2. (although perhaps the Glasgow contingent would like to make some suggestions fulfil definition 3.) Personally I think that right now we want to have a catchy advertising slogan to draw people in, along with logos etc that work well on marketing material (I want a Qpid t-shirt :-) ). Much as I agree that something like Qpid: Open Source AMQP Messaging succinctly describes the aims of the project, I don't think it draws in people to take a look. Furthermore it does nothing to help people remember the name Qpid. We *do* also need to make sure that in searches for AMQP and Enterprise Messaging, Qpid features highly. However I think there's a fair probability that if you've heard of AMQP you've probably heard of Qpid. So I would probably argue that we need (at least) two different slogans... And of the two I think that advertising and drawing people is is what we are currently more in need of. We need to get the name Qpid out there so that people remember it (even if they don't know what is does)... Now... time to think of some battle cries... -- Rob - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-1621) Flow control fails to release credit when unacknowledge message count exceeds the low water mark
Flow control fails to release credit when unacknowledge message count exceeds the low water mark Key: QPID-1621 URL: https://issues.apache.org/jira/browse/QPID-1621 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: M4, M3 Reporter: Marnie McCormack Assignee: Aidan Skinner Fix For: M5 Summary: If we receive more than 2500 msgs on a transacted session then we cannot recover that credit and will block at the prefetch limit of 5000. Acknowledging at msg 2501 demonstrates this issue (of being limited to 5000 mgs) but at 2500 then we are able to receive as many messages as are available, beyond 5000. This issue has been seen on Qpid M3, further extraction of a test case and testing on M4 is required. The test should also adjust the low water mark to identify if that is part of the issue. Workaround: To prevent client starvation ensure that clients never have more than the low water mark (2500 default) of unacked messages. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Qpid slogan?
If we're going down the popular culture/film-reference route: Qpid - Message Transformers! Qpid - Transforming Messaging! Qpid - Materializing Near You! Or (perhaps a bit obscure): Qpid: For all your Dark Nights... Marnie, how about: Qpid: Warp Factor AMQP! -- Mark On Thu, Jan 29, 2009 at 10:48 AM, Marnie McCormack marnie.mccorm...@googlemail.com wrote: Qpid: The force is with you Qpid: Warp Factor X (I'm not enough of a trekkie to have a better idea) On Thu, Jan 29, 2009 at 10:45 AM, Mark Atwell mark.atw...@gmail.com wrote: Sorry, tea-break made me think of a load more!: QPID: Queue This! (a la Matrix: Dodge This! - will appeal to techies) QPID: Quite Perfect Innate Design (or some variant) In a similar vein: QPID: Quite Possibly Iconic Design(or variant - Probably?) This one sounds like someone else's (so apologies in advance) QPID: Quick, Purposeful, Innate Design Ah... my tea's run out... -- Mark On Thu, Jan 29, 2009 at 10:21 AM, Mark Atwell mark.atw...@gmail.com wrote: If you're looking for a T-shirt-like/mug logo how about a play on 'The Classic': I'm with QPid! This also almost works with the arrow-like AMQP logo! BTW is the capitalisation of QPid settled on 'Qpid'? Or possibly: AMQP?: I'm with QPid! AMQP?: I love QPid!(opportunity to go with some Eros/cherub-type-stuff?) QPid loves AMQP BTW I'm not even going to go near the Kenny Everett Show character thing for fear of offence! -- Mark On Wed, Jan 28, 2009 at 1:59 PM, Robert Godfrey rob.j.godf...@gmail.com wrote: Sorry - been away for a couple of days and just caught up with this thread now. 2009/1/27 Jonathan Robie jonathan.ro...@redhat.com: It's OK to differ ;- But let me explain my reasoning: the whole point of a slogan is to establish identity so people know what it is. AMQP and messaging are fundamental to what Qpid is. I think it's interesting here to look at a quick definition (from http://www.thefreedictionary.com/slogan): 1. A phrase expressing the aims or nature of an enterprise, organization, or candidate; a motto. 2. A phrase used repeatedly, as in advertising or promotion: all the slogans and shibboleths coined out of the ideals of the peoples for the uses of imperialism Margaret Sanger. 3. A battle cry of a Scottish clan. What we seem to be arguing about here is whether we want a slogan that fulfils definition 1. or definition 2. (although perhaps the Glasgow contingent would like to make some suggestions fulfil definition 3.) Personally I think that right now we want to have a catchy advertising slogan to draw people in, along with logos etc that work well on marketing material (I want a Qpid t-shirt :-) ). Much as I agree that something like Qpid: Open Source AMQP Messaging succinctly describes the aims of the project, I don't think it draws in people to take a look. Furthermore it does nothing to help people remember the name Qpid. We *do* also need to make sure that in searches for AMQP and Enterprise Messaging, Qpid features highly. However I think there's a fair probability that if you've heard of AMQP you've probably heard of Qpid. So I would probably argue that we need (at least) two different slogans... And of the two I think that advertising and drawing people is is what we are currently more in need of. We need to get the name Qpid out there so that people remember it (even if they don't know what is does)... Now... time to think of some battle cries... -- Rob - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-1623) Setting JMSReplyTo field to NULL causes IllegalArgumentException to be thrown
Setting JMSReplyTo field to NULL causes IllegalArgumentException to be thrown
-
Key: QPID-1623
URL: https://issues.apache.org/jira/browse/QPID-1623
Project: Qpid
Issue Type: Improvement
Components: Java Client
Affects Versions: M4, M3, M2.1, M2, M1
Reporter: Marnie McCormack
Assignee: Aidan Skinner
Fix For: M5
Qpid versions 2.2.2.0
Platform: Windows
JDK: 16.0_11
I came across this problem while trying to write an example application for one
of our MAF clients that would take part in a JMS request-response message flow.
During testing of this I started hitting this IllegalArgumentException from
Qpid exception:
java.lang.IllegalArgumentException: Null destination not allowed
at
org.apache.qpid.client.message.AbstractJMSMessage.setJMSReplyTo(AbstractJMSMessage.java:200)
at
org.mule.providers.jms.JmsReplyToHandler.processReplyTo(JmsReplyToHandler.java:79)
at org.mule.impl.model.DefaultMuleProxy.onCall(DefaultMuleProxy.java:297)
at org.mule.impl.model.seda.SedaComponent.doSend(SedaComponent.java:406)
at
org.mule.impl.model.AbstractComponent.sendEvent(AbstractComponent.java:407)
at org.mule.impl.MuleSession.sendEvent(MuleSession.java:349)
at
org.mule.routing.inbound.InboundRouterCollection.send(InboundRouterCollection.java:197)
at
org.mule.routing.inbound.InboundRouterCollection.route(InboundRouterCollection.java:163)
at
org.mule.providers.AbstractMessageReceiver$DefaultInternalMessageListener.onMessage(AbstractMessageReceiver.java:585)
at
org.mule.providers.AbstractMessageReceiver.routeMessage(AbstractMessageReceiver.java:322)
at
org.mule.providers.AbstractReceiverWorker$1.doInTransaction(AbstractReceiverWorker.java:107)
at
org.mule.transaction.TransactionTemplate.execute(TransactionTemplate.java:98)
at
org.mule.providers.AbstractReceiverWorker.doRun(AbstractReceiverWorker.java:124)
at
org.mule.providers.AbstractReceiverWorker.run(AbstractReceiverWorker.java:60)
at org.mule.impl.work.WorkerContext.run(WorkerContext.java:310)
at org.mule.impl.work.SyncWorkExecutor.doExecute(SyncWorkExecutor.java:39)
at org.mule.impl.work.MuleWorkManager.executeWork(MuleWorkManager.java:277)
at org.mule.impl.work.MuleWorkManager.doWork(MuleWorkManager.java:169)
at
org.mule.providers.jms.MultiConsumerJmsMessageReceiver$SubReceiver.onMessage(MultiConsumerJmsMessageReceiver.java:281)
at
org.apache.qpid.client.BasicMessageConsumer.notifyMessage(BasicMessageConsumer.java:719)
at
org.apache.qpid.client.BasicMessageConsumer.notifyMessage(BasicMessageConsumer.java:656)
at
org.apache.qpid.client.AMQSession$Dispatcher.dispatchMessage(AMQSession.java:3043)
at org.apache.qpid.client.AMQSession$Dispatcher.run(AMQSession.java:2966)
After doing some digging through the Mule code I was able to track it down to
the following piece of code in Mule's JmsReplyToHandler where it tries to set
the JMSReplyTo field to be null.
final boolean topic =
connector.getTopicResolver().isTopic(replyToDestination);
session = connector.getSession(false, topic);
Message replyToMessage = JmsMessageUtils.toMessage(payload, session);
replyToMessage.setJMSReplyTo(null);
if (logger.isDebugEnabled())
{
logger.debug(Sending jms reply to: + replyToDestination + (
+ replyToDestination.getClass().getName() + ));
}
replyToProducer = connector.getJmsSupport().createProducer(session,
replyToDestination, topic);
The corresponding code in qpid (taken from the AbstractJMSMessage class) shows
that qpid throws the IllegalArgumentException whenever it receives a null
value:
public void setJMSReplyTo(Destination destination) throws JMSException
{
if (destination == null)
{
throw new IllegalArgumentException(Null destination not allowed);
}
if (!(destination instanceof AMQDestination))
{
throw new IllegalArgumentException(
ReplyTo destination may only be an AMQDestination - passed
argument was type + destination.getClass());
}
final AMQDestination amqd = (AMQDestination) destination;
final AMQShortString encodedDestination = amqd.getEncodedName();
_destinationCache.put(encodedDestination, destination);
getContentHeaderProperties().setReplyTo(encodedDestination);
}
The JMS Spec is a bit vague around whether or not you can actually set this
JMSReplyTo value to null or not but after talking with Martin about this he was
able to check both the Qpid and MQ code to see how they compared. While the
Qpid code disallows setting a null value on the JMSReplyTo field the MQ code is
more forgiving and allows Null values to be set. I've included the JMSReplyTo
section from the JMS
[jira] Updated: (QPID-1470) Reloading user data does not work
[ https://issues.apache.org/jira/browse/QPID-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marnie McCormack updated QPID-1470: --- Fix Version/s: Eclipse MC M5 Affects Version/s: (was: M4) Sscoping items for early 2009 release of Java Eclipse Mgt Console Reloading user data does not work - Key: QPID-1470 URL: https://issues.apache.org/jira/browse/QPID-1470 Project: Qpid Issue Type: Bug Components: Java Management : JMX Console Reporter: Martin Ritchie Assignee: Martin Ritchie Fix For: Eclipse MC M5 Summary: If the file is changed on disk and a reload requested then it reports Success however the data does not appear to have changed. Also if the file is corrupt (as by the defect in delete) then only an unsuccessful is reported. Where as in the case for delete where the file does not contain any user data this should be reported. -- 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-1482) Management Console cant complete PLAIN user authentication process
[ https://issues.apache.org/jira/browse/QPID-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marnie McCormack updated QPID-1482: --- Fix Version/s: Eclipse MC M5 Affects Version/s: (was: M4) Sscoping items for early 2009 release of Java Eclipse Mgt Console Management Console cant complete PLAIN user authentication process -- Key: QPID-1482 URL: https://issues.apache.org/jira/browse/QPID-1482 Project: Qpid Issue Type: Bug Components: Java Broker, Java Management : JMX Console Reporter: Robert Gemmell Assignee: Aidan Skinner Fix For: Eclipse MC M5 Attachments: QPID-1482_22nov2008.patch When the patches I supplied for QPID-1481 and QPID-794 are used, the management console is able to communicate with the broker across the JMXMPConnector link but is still unable to successfully complete the connection, however the failure now occurs during the PLAIN authentication process as opposed to before it like previously. Despite this, the management console reports that Qpid server is not running. Enabling debug console output for the management console yields the following exception listing: java.io.IOException: java.lang.NullPointerException at com.sun.jmx.remote.opt.security.AdminClient.throwExceptionOnError(AdminClient.java:379) at com.sun.jmx.remote.opt.security.AdminClient.connectionOpen(AdminClient.java:184) at com.sun.jmx.remote.generic.ClientSynchroMessageConnectionImpl.connect(ClientSynchroMessageConnectionImpl.java:112) at javax.management.remote.generic.GenericConnector.connect(GenericConnector.java:217) at javax.management.remote.jmxmp.JMXMPConnector.connect(JMXMPConnector.java:159) at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248) at org.apache.qpid.management.ui.jmx.JMXServerRegistry$ConnectorThread.run(JMXServerRegistry.java:204) at java.lang.Thread.run(Thread.java:619) java.io.IOException: java.lang.NullPointerException at com.sun.jmx.remote.opt.security.AdminClient.throwExceptionOnError(AdminClient.java:379) at com.sun.jmx.remote.opt.security.AdminClient.connectionOpen(AdminClient.java:184) at com.sun.jmx.remote.generic.ClientSynchroMessageConnectionImpl.connect(ClientSynchroMessageConnectionImpl.java:112) at javax.management.remote.generic.GenericConnector.connect(GenericConnector.java:217) at javax.management.remote.jmxmp.JMXMPConnector.connect(JMXMPConnector.java:159) at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248) at org.apache.qpid.management.ui.jmx.JMXServerRegistry$ConnectorThread.run(JMXServerRegistry.java:204) at java.lang.Thread.run(Thread.java:619) The broker was slightly more informative however, giving: GenericConnectorServer ClientCreation.run WARNING: Failed to open connection: java.lang.NullPointerException java.lang.NullPointerException at org.apache.qpid.server.security.auth.database.PlainPasswordFilePrincipalDatabase.compareCharArray(PlainPasswordFilePrincipalDatabase.java:182) at org.apache.qpid.server.security.auth.database.PlainPasswordFilePrincipalDatabase.verifyPassword(PlainPasswordFilePrincipalDatabase.java:130) at org.apache.qpid.server.management.JMXManagedObjectRegistry$UserCallbackHandler.handle(JMXManagedObjectRegistry.java:267) at org.apache.qpid.server.security.auth.sasl.plain.PlainSaslServer.evaluateResponse(PlainSaslServer.java:81) at com.sun.jmx.remote.opt.security.SASLServerHandler.consumeMessage(SASLServerHandler.java:164) at com.sun.jmx.remote.opt.security.AdminServer.connectionOpen(AdminServer.java:216) at com.sun.jmx.remote.generic.ServerSynchroMessageConnectionImpl.connect(ServerSynchroMessageConnectionImpl.java:98) at javax.management.remote.generic.GenericConnectorServer$ClientCreation.run(GenericConnectorServer.java:443) at com.sun.jmx.remote.opt.util.ThreadService$ThreadServiceJob.run(ThreadS -- 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-1013) Documentation on running Qpid Management Console within Eclipse is Required
[ https://issues.apache.org/jira/browse/QPID-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marnie McCormack updated QPID-1013: --- Fix Version/s: Eclipse MC M5 Sscoping items for early 2009 release of Java Eclipse Mgt Console Documentation on running Qpid Management Console within Eclipse is Required --- Key: QPID-1013 URL: https://issues.apache.org/jira/browse/QPID-1013 Project: Qpid Issue Type: Improvement Components: Java Management : JMX Console Reporter: Senaka Fernando Fix For: Eclipse MC M5 Documentation on running Qpid Management Console within Eclipse is Required -- 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-1491) Secure Management Console connections do not work
[ https://issues.apache.org/jira/browse/QPID-1491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marnie McCormack updated QPID-1491: --- Fix Version/s: (was: M4) Eclipse MC M5 Affects Version/s: (was: M3) Sscoping items for early 2009 release of Java Eclipse Mgt Console Secure Management Console connections do not work - Key: QPID-1491 URL: https://issues.apache.org/jira/browse/QPID-1491 Project: Qpid Issue Type: Bug Components: Java Management : JMX Console Reporter: Marnie McCormack Assignee: Martin Ritchie Fix For: Eclipse MC M5 Summary: The current build of the management console is unable to connect to the broker using the CRAM-MD5 JMX SASL. It is potentially a classpath problem with a newer JDK version than was originally tested as the console reports it cannot load a class from the JMXRemote jar. Current work around is to use the default PLAIN authentication Have to edit qpidmc.bat and remove -Dsecurity=CRAM-MD5 -- 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-1591) [JMX Console] server navigation view tree contains redundant 'Qpid Connections' root node
[ https://issues.apache.org/jira/browse/QPID-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marnie McCormack updated QPID-1591: --- Fix Version/s: Eclipse MC M5 Sscoping items for early 2009 release of Java Eclipse Mgt Console [JMX Console] server navigation view tree contains redundant 'Qpid Connections' root node - Key: QPID-1591 URL: https://issues.apache.org/jira/browse/QPID-1591 Project: Qpid Issue Type: Bug Components: Java Management : JMX Console Reporter: Robert Gemmell Assignee: Aidan Skinner Fix For: Eclipse MC M5 Attachments: QPID-1591_18jan2009.patch The server navigation tree in the management console has a 'Qpid Connections' root node. The navigation area is headed Qpid Connections so this node conveys no new information and its presence forces users to expand it before they can connect to a previously used server, which is usually the first task any recurring user will perform, every single time they start the console: this is clearly nuts. -- 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-1570) JMXConnectionFactory exception handling code is fragile
[ https://issues.apache.org/jira/browse/QPID-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marnie McCormack updated QPID-1570: --- Fix Version/s: Eclipse MC M5 Affects Version/s: (was: M4) Sscoping items for early 2009 release of Java Eclipse Mgt Console JMXConnectionFactory exception handling code is fragile --- Key: QPID-1570 URL: https://issues.apache.org/jira/browse/QPID-1570 Project: Qpid Issue Type: Bug Components: Java Management : CLI Tool, Java Management : JMX Console Reporter: Aidan Skinner Fix For: Eclipse MC M5 Split off from QPID-1522: Rob Godfrey: JMXConnectionFactory: The code which looks at the exception text seems remarkable fragile to me... At the very least I would expect some constants which could be shared with the code that throws the exception. Robbie Gemmell: Hi Rob, I wrote that bit originally. It is somewhat fragile, but unfortunately having looked at the code that generates the exceptions i didnt think there was much else i could do. The exception is generated by code within the optional JMXMP addon (jmxremote_optional.jar) and just directly throws an IOException like so: throw new IOException(The server supported profiles + serverProfilesList + do not + match the client required profiles + clientProfilesList + .); so there are no constants to match against (though granted i should possibly still have used constants for my own bit). I have a secure RMI based JMX setup ready to go, so we can remove the user-unfriendly/slightly-proprietary JMXMP stuff in future if desired (I know Aidan wants to :P), and if so then that section of code should only really ever be getting used for connecting to older brokers if they have used the JMXMP based solution, which it seems that at the moment many dont, given how guff the console was in that area. -- 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-1015) NPE Reported Incorrectly by Qpid Management Console
[ https://issues.apache.org/jira/browse/QPID-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marnie McCormack updated QPID-1015: --- Fix Version/s: (was: M4) Eclipse MC M5 Sscoping items for early 2009 release of Java Eclipse Mgt Console NPE Reported Incorrectly by Qpid Management Console --- Key: QPID-1015 URL: https://issues.apache.org/jira/browse/QPID-1015 Project: Qpid Issue Type: Bug Components: Java Management : JMX Console Reporter: Senaka Fernando Assignee: Aidan Skinner Priority: Minor Fix For: Eclipse MC M5 Attachments: npe_fix.patch.txt NPE Reported Incorrectly by Qpid Management Console -- 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-1240) NullPointerException when setting access level in UserManagement Panel
[
https://issues.apache.org/jira/browse/QPID-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marnie McCormack updated QPID-1240:
---
Fix Version/s: Eclipse MC M5
Affects Version/s: (was: M2.1)
(was: M3)
(was: M2)
Sscoping items for early 2009 release of Java Eclipse Mgt Console
NullPointerException when setting access level in UserManagement Panel
--
Key: QPID-1240
URL: https://issues.apache.org/jira/browse/QPID-1240
Project: Qpid
Issue Type: Bug
Components: Java Management : JMX Console
Reporter: Martin Ritchie
Fix For: Eclipse MC M5
Summary:
When using the Management Console to give a user (I used 'client') rights
('admin' in this case) to the console on executing the action a
NullPointerException window is shown rather than 'Operation Successful'
This is disconcerting for end users, howvever, the operation does indeed
complete successfully
--
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-1510) Splash Screen does not go away on Windows build
[ https://issues.apache.org/jira/browse/QPID-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marnie McCormack updated QPID-1510: --- Fix Version/s: Eclipse MC M5 Sscoping items for early 2009 release of Java Eclipse Mgt Console Splash Screen does not go away on Windows build --- Key: QPID-1510 URL: https://issues.apache.org/jira/browse/QPID-1510 Project: Qpid Issue Type: Bug Components: Java Management : JMX Console, Starter Reporter: Martin Ritchie Assignee: Aidan Skinner Priority: Minor Fix For: Eclipse MC M5 Summary: The new builds of the Windows console display the splash screen but do not remove it when the console has started. Perhaps the units of -splashScreen 600 have changed. The window is not set to be the front most window so other apps can be moved in front of it but if you had a small window right at the centre of your screen you would have to quite the console to find it again. -- 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-433) Queue depth to be shown in bytes or KBytes as appropriate in mangement console.
[ https://issues.apache.org/jira/browse/QPID-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marnie McCormack updated QPID-433: -- Fix Version/s: Eclipse MC M5 Sscoping items for early 2009 release of Java Eclipse Mgt Console Queue depth to be shown in bytes or KBytes as appropriate in mangement console. --- Key: QPID-433 URL: https://issues.apache.org/jira/browse/QPID-433 Project: Qpid Issue Type: Improvement Components: Java Management : JMX Console Reporter: Bhupendra Bhardwaj Assignee: Bhupendra Bhardwaj Fix For: Eclipse MC M5 Currently the Queue depth is shown as KB and if the value is less than 1024bytes, it is shown as 0. The feature of showing the queue depth in bytes, KB, MB should be in the management console and broker should send the actual value in bytes. -- 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-1481) jmxremote.sasl plugin doesnt export packages for other plugins to use
[ https://issues.apache.org/jira/browse/QPID-1481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marnie McCormack updated QPID-1481: --- Fix Version/s: Eclipse MC M5 Affects Version/s: (was: M4) Sscoping items for early 2009 release of Java Eclipse Mgt Console jmxremote.sasl plugin doesnt export packages for other plugins to use - Key: QPID-1481 URL: https://issues.apache.org/jira/browse/QPID-1481 Project: Qpid Issue Type: Bug Components: Java Management : JMX Console Reporter: Robert Gemmell Assignee: Aidan Skinner Fix For: Eclipse MC M5 Attachments: QPID-1481_22nov2008.patch The jmxremote.sasl plugin was created in order to allow the org.apache.qpid.management.ui plugin to import the jmxremote_optional.jar file for use in providing authenticated management console connections to the broke. As such is listed as a dependancy of the org.apache.qpid.management.ui plugin on which the management console is based. However, it does not export the packages for other plugins to use, and additionally is only required when there is a desire to use the authentication security. -- 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-1509) Buttons are often missing their text on Linux build.
[ https://issues.apache.org/jira/browse/QPID-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marnie McCormack updated QPID-1509: --- Fix Version/s: Eclipse MC M5 Sscoping items for early 2009 release of Java Eclipse Mgt Console Buttons are often missing their text on Linux build. Key: QPID-1509 URL: https://issues.apache.org/jira/browse/QPID-1509 Project: Qpid Issue Type: Bug Components: Java Management : JMX Console Reporter: Martin Ritchie Fix For: Eclipse MC M5 Summary: When running under RHEL4 the JMX Management console often loses the text on the buttons. This will make it difficult for new users to know which button is 'Connect' and which 'Cancel'. This is a transient issue and restarting will often bring the text back. But I see no pattern to what might cause the text to disappear. I see this as I have a local settings file. Start the JMX Console Select a connection from my list Click Reconnect Buttons often don't show 'Connect' / 'Cancel' but as they are ~ 12px high I can still click and tab to them. Unlike Mac OS X build that doesn't show the buttons at all (QPID-1507) -- 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-1615) [JMX Console] server navigation tree generates a runtime exception on first use
[ https://issues.apache.org/jira/browse/QPID-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marnie McCormack updated QPID-1615: --- Fix Version/s: (was: M5) Eclipse MC M5 Affects Version/s: (was: M4) (was: M2.1) (was: M3) Sscoping items for early 2009 release of Java Eclipse Mgt Console [JMX Console] server navigation tree generates a runtime exception on first use --- Key: QPID-1615 URL: https://issues.apache.org/jira/browse/QPID-1615 Project: Qpid Issue Type: Bug Components: Java Management : JMX Console Reporter: Robert Gemmell Fix For: Eclipse MC M5 The navigation tree generates the following runtime exception upon the first expansion made by a user after the first connection is made. In previous versions this would not have been noticed because the Eclipse RCP console log was disabled. The tree functions without noticable issue, and as noted the exception is raised once only. !ENTRY org.eclipse.jface 2 0 2009-01-26 17:20:50.884 !MESSAGE Ignored reentrant call while viewer is busy. This is only logged once per viewer instance, but similar calls will still be ignored. !STACK 0 java.lang.RuntimeException at org.eclipse.jface.viewers.ColumnViewer.checkBusy(ColumnViewer.java:763) at org.eclipse.jface.viewers.AbstractTreeViewer.setExpandedState(AbstractTreeViewer.java:2421) at org.apache.qpid.management.ui.views.NavigationView$2.treeExpanded(NavigationView.java:133) at org.eclipse.jface.viewers.AbstractTreeViewer$3.run(AbstractTreeViewer.java:1101) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:880) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.AbstractTreeViewer.fireTreeExpanded(AbstractTreeViewer.java:1099) at org.eclipse.jface.viewers.AbstractTreeViewer.handleTreeExpand(AbstractTreeViewer.java:1444) at org.eclipse.jface.viewers.TreeViewer.handleTreeExpand(TreeViewer.java:927) at org.eclipse.jface.viewers.AbstractTreeViewer$4.treeExpanded(AbstractTreeViewer.java:1453) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:126) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1182) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1167) at org.eclipse.swt.widgets.Tree.gtk_test_expand_row(Tree.java:2026) at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1572) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4105) at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method) at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:5792) at org.eclipse.swt.widgets.Display.eventProc(Display.java:1177) at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method) at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:1550) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3031) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.apache.qpid.management.ui.Application.run(Application.java:46) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:574) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:195) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at
[jira] Updated: (QPID-1511) JMX Interface does not require authentication
[ https://issues.apache.org/jira/browse/QPID-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marnie McCormack updated QPID-1511: --- Fix Version/s: Eclipse MC M5 Affects Version/s: (was: M4) (was: M2.1) (was: M3) (was: M2) (was: M1) Sscoping items for early 2009 release of Java Eclipse Mgt Console JMX Interface does not require authentication - Key: QPID-1511 URL: https://issues.apache.org/jira/browse/QPID-1511 Project: Qpid Issue Type: Improvement Components: Java Broker, Java Management : JMX Console Reporter: Martin Ritchie Fix For: Eclipse MC M5 Attachments: QPID-1511_wip_19dec2008.patch, QPID-1511_wip_8dec2008.patch Summary: JMX Interface uses the default RMI connector which has no authentication mechanism. We should not be shipping a JMX interface that doesn't have authentication. The interface has been disabled by default for M4 but this should be modified based on the outcome of the discussion on qpid-dev to authenticate all connections. -- 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-1241) qpidmc.bat script does not cope with spaces ( ) in the path.
[ https://issues.apache.org/jira/browse/QPID-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marnie McCormack updated QPID-1241: --- Fix Version/s: (was: M5) Eclipse MC M5 Affects Version/s: (was: M2.1) (was: M3) (was: M2) Sscoping items for early 2009 release of Java Eclipse Mgt Console qpidmc.bat script does not cope with spaces ( ) in the path. -- Key: QPID-1241 URL: https://issues.apache.org/jira/browse/QPID-1241 Project: Qpid Issue Type: Bug Components: Java Management : JMX Console Reporter: Martin Ritchie Assignee: Martin Ritchie Fix For: Eclipse MC M5 Attachments: QPID-1241_23nov2008.patch Summary: The management console cannot be installed in to Program Files as qpidmc.bat script does not correctly operate due to the space in the path. -- 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-1565) Improve repository layout of ancillary files for the jmx management console
[ https://issues.apache.org/jira/browse/QPID-1565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marnie McCormack updated QPID-1565: --- Fix Version/s: Eclipse MC M5 Sscoping items for early 2009 release of Java Eclipse Mgt Console Improve repository layout of ancillary files for the jmx management console --- Key: QPID-1565 URL: https://issues.apache.org/jira/browse/QPID-1565 Project: Qpid Issue Type: Task Components: Java Management : JMX Console Reporter: Robert Gemmell Priority: Trivial Fix For: Eclipse MC M5 Attachments: QPID-1565_9jan2009.zip The management console builds require ancillary files such as platform-dependant configuration + executable files, and additional manifests for sub component plugins. Some of these are currently in poorly named directories, making their purpose non-obvious. They should be arranged in a way that is more indicative of thier use and/or location within the console builds. -- 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-843) Management Console packaging doesn't work for unix
[ https://issues.apache.org/jira/browse/QPID-843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marnie McCormack updated QPID-843: -- Fix Version/s: (was: M4) Eclipse MC M5 Affects Version/s: (was: M2.1) Sscoping items for early 2009 release of Java Eclipse Mgt Console Management Console packaging doesn't work for unix -- Key: QPID-843 URL: https://issues.apache.org/jira/browse/QPID-843 Project: Qpid Issue Type: Bug Components: Java Management : JMX Console Reporter: Aidan Skinner Assignee: Aidan Skinner Fix For: Eclipse MC M5 The management console packaging in distribution doesn't work, you're left with a 748K tarfile as opposed to a 11M zip for windows, which then doesn't run as it's missing things like startup.jar -- 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-1472) Management Console Delete User corrupts password file and jmxremote.access
[ https://issues.apache.org/jira/browse/QPID-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marnie McCormack updated QPID-1472: --- Fix Version/s: Eclipse MC M5 Affects Version/s: (was: M4) Sscoping items for early 2009 release of Java Eclipse Mgt Console Management Console Delete User corrupts password file and jmxremote.access -- Key: QPID-1472 URL: https://issues.apache.org/jira/browse/QPID-1472 Project: Qpid Issue Type: Bug Components: Java Management : JMX Console Reporter: Martin Ritchie Assignee: Martin Ritchie Fix For: Eclipse MC M5 Summary: If a user is deleted using the JMX Management Console 'Delete User' then the password file is rewritten without line endings so the content is all comments. Also due to QPID-1769 (the inability to lookup the JMX Session username) the jmxremote.access file is left as jmxremote.access.old and the new jmxremote.access.tmp is left empty, preventing the broker from starting up. -- 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-1242) Ability to view Binary Messages was lost in the merge
[ https://issues.apache.org/jira/browse/QPID-1242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marnie McCormack updated QPID-1242: --- Fix Version/s: Eclipse MC M5 Affects Version/s: (was: M2.1) (was: M3) (was: M2) Sscoping items for early 2009 release of Java Eclipse Mgt Console Ability to view Binary Messages was lost in the merge - Key: QPID-1242 URL: https://issues.apache.org/jira/browse/QPID-1242 Project: Qpid Issue Type: Bug Components: Java Management : JMX Console Reporter: Martin Ritchie Fix For: Eclipse MC M5 Attachments: org.apache.commons.codec_1.3.0.v20080530-1600.jar, QPID-1242_22jan2009.patch Summary: The ability to view binary messages (ascii and hex views) were lost when the M2.x code base was merged to trunk. It was checked in at r571491 -- 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-1469) AMQUserManagementMBean.getCurrentJMXUser no longer returns a valid user
[ https://issues.apache.org/jira/browse/QPID-1469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marnie McCormack updated QPID-1469: --- Fix Version/s: (was: M4) Eclipse MC M5 Affects Version/s: (was: M4) Sscoping items for early 2009 release of Java Eclipse Mgt Console AMQUserManagementMBean.getCurrentJMXUser no longer returns a valid user --- Key: QPID-1469 URL: https://issues.apache.org/jira/browse/QPID-1469 Project: Qpid Issue Type: Bug Components: Java Management : JMX Console Reporter: Martin Ritchie Assignee: Martin Ritchie Fix For: Eclipse MC M5 Attachments: QPID-1469-NPE-AMQUMMBean.log, QPID-1469_8dec2008.patch, QPID-1469_test_9dec2008.patch, QPID-1469_test_style_fix_9dec2008.patch Summary: Currently when the password and jmxremote.access files are updated the current username is written in to the file as an audit trail. This used to work fine however we are now seeing a NullPointerException when performing any updates such as: Set Rights Delete User -- 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-1471) Argument Type Mismatch reported from Management Console
[ https://issues.apache.org/jira/browse/QPID-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marnie McCormack updated QPID-1471: --- Fix Version/s: Eclipse MC M5 Affects Version/s: (was: M4) Sscoping items for early 2009 release of Java Eclipse Mgt Console Argument Type Mismatch reported from Management Console --- Key: QPID-1471 URL: https://issues.apache.org/jira/browse/QPID-1471 Project: Qpid Issue Type: Bug Components: Java Management : JMX Console Reporter: Martin Ritchie Assignee: Aidan Skinner Fix For: Eclipse MC M5 Attachments: QPID-1471-ArgumentTypeMismatch.log Summary: When executing 'Set Password' from the JMX Management Console an error 'argument type mismatch' is reported. The same error occurs when calling 'Create User' , 'Set Password' Stack trace file attached. -- 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-1506) Auto Negotiate connections for JMX Management Console
[ https://issues.apache.org/jira/browse/QPID-1506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marnie McCormack updated QPID-1506: --- Fix Version/s: Eclipse MC M5 Affects Version/s: (was: M4) (was: M3) Sscoping items for early 2009 release of Java Eclipse Mgt Console Auto Negotiate connections for JMX Management Console - Key: QPID-1506 URL: https://issues.apache.org/jira/browse/QPID-1506 Project: Qpid Issue Type: Improvement Components: Java Management : JMX Console Reporter: Martin Ritchie Assignee: Aidan Skinner Fix For: Eclipse MC M5 Attachments: QPID-1506_11dec2008.patch Summary: Currently there are number of options that must be configured for the JMX Console to correctly connect, if these values are not set or correct then the connection will fail. However, the broker will provide the console with sufficient detail to auto-negotiate the connection. QPID-1504 highlights that if we connect using the RMI connector but the server is configured for JMXMP then we can tell. If we connect using JMXMP using SASL/CRAM-MD5 but the server wants SASL/PLAIN then we can tell as the exception is: java.io.IOException: The server supported profiles [SASL/PLAIN] do not match the client required profiles [SASL/CRAM-MD5]. We can use this information to swap Sasl mechanism in the console and try again. This would mean that the end user would not have to reconfigure or have multiple start scripts lying about so they could connect to a number of difference brokers using different mechanisms. Looking at the private class ConnectorThread in JMXServerRegistry along with the createSASLConnector and the constructor show that the security mechanism is hard coded but could using the above method be derived from the broker's response and handled appropriately if the ConnectorThread and createSASLConnector where better architected to take advantaged of the exceptions returned from the JMXConnectorFactory.connect method -- 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-1503) Base64MD5PasswordFile does not write end of line in header section
[ https://issues.apache.org/jira/browse/QPID-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marnie McCormack updated QPID-1503: --- Fix Version/s: Eclipse MC M5 Affects Version/s: (was: M2.1) (was: M3) (was: M2) Sscoping items for early 2009 release of Java Eclipse Mgt Console Base64MD5PasswordFile does not write end of line in header section -- Key: QPID-1503 URL: https://issues.apache.org/jira/browse/QPID-1503 Project: Qpid Issue Type: Bug Components: Java Management : JMX Console, Starter Reporter: Martin Ritchie Assignee: Aidan Skinner Fix For: Eclipse MC M5 Summary B64MD5 PasswordFile L: 400 is write() but is missing a println afterwards which causes the comment rows to merge with the next row. This will cause the first user to be disabled. -- 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-1011) Qpid Management Console Plugin has undefined behaviour in different Eclipse Perspectives
[ https://issues.apache.org/jira/browse/QPID-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marnie McCormack updated QPID-1011: --- Fix Version/s: (was: M4) Eclipse MC M5 Sscoping items for early 2009 release of Java Eclipse Mgt Console Qpid Management Console Plugin has undefined behaviour in different Eclipse Perspectives Key: QPID-1011 URL: https://issues.apache.org/jira/browse/QPID-1011 Project: Qpid Issue Type: Bug Components: Java Management : JMX Console Environment: Ubuntu 7.10 (Gusty Gibbon) Reporter: Senaka Fernando Assignee: Martin Ritchie Fix For: Eclipse MC M5 Attachments: invalid_perspective_fix.patch.txt Qpid Management Console Plugin has undefined behaviour in different Eclipse Perspectives. For example in the Java perspective, I can't create a connection and get a error Server Connection Failed. I believe that the error message must either be informative enough for the user to change the perspective, or, the toolbar and the menu item must rather be disabled in unsupported perspectives. Regards, Senaka N.B. this might not be an Ubuntu specific issue, and I'm not aware of the behaviour on other platforms. -- 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-1532) [JMX Console] MBeanUtility handleException prints exception stacktrace when users are denied due to access rights
[ https://issues.apache.org/jira/browse/QPID-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marnie McCormack updated QPID-1532: --- Fix Version/s: Eclipse MC M5 Affects Version/s: (was: M4) (was: M3) Sscoping items for early 2009 release of Java Eclipse Mgt Console [JMX Console] MBeanUtility handleException prints exception stacktrace when users are denied due to access rights - Key: QPID-1532 URL: https://issues.apache.org/jira/browse/QPID-1532 Project: Qpid Issue Type: Bug Components: Java Management : JMX Console Reporter: Robert Gemmell Assignee: Aidan Skinner Fix For: Eclipse MC M5 Attachments: QPID-1532_12dec2008.patch handleException (MBeanUtility:L:144) always prints the stackTrace as well as displaying an error dialog to the user when denied access to the UserManagement Mbean based on access rights in the jmxremote.access file. This behaviour is undesirable for a known SecurityException and the dialog box to the user is sufficient in this case. -- 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-1014) qpid.management.perspective should be replaced by a better phrase
[ https://issues.apache.org/jira/browse/QPID-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marnie McCormack updated QPID-1014: --- Fix Version/s: Eclipse MC M5 Sscoping items for early 2009 release of Java Eclipse Mgt Console qpid.management.perspective should be replaced by a better phrase - Key: QPID-1014 URL: https://issues.apache.org/jira/browse/QPID-1014 Project: Qpid Issue Type: Improvement Components: Java Management : JMX Console Reporter: Senaka Fernando Assignee: Aidan Skinner Priority: Minor Fix For: Eclipse MC M5 Attachments: plugin_xml.patch.txt qpid.management.perspective should be replaced by a better phrase. It looks a bit odd when compared to other Perspective names. Regards, Senaka -- 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-1504) Poor user feed back with protocol negotication mismatch on JMX Console
[ https://issues.apache.org/jira/browse/QPID-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marnie McCormack updated QPID-1504: --- Fix Version/s: Eclipse MC M5 Affects Version/s: (was: M3) Sscoping items for early 2009 release of Java Eclipse Mgt Console Poor user feed back with protocol negotication mismatch on JMX Console -- Key: QPID-1504 URL: https://issues.apache.org/jira/browse/QPID-1504 Project: Qpid Issue Type: Improvement Components: Java Management : JMX Console, Starter Reporter: Martin Ritchie Priority: Minor Fix For: Eclipse MC M5 Summary: If the broker has the jmxremote_optional.jar and securitytrue configured. When a JMX Console client connects using the standard RMI connector it tells the user that: 'User authentication has failed' Which is poor as the stack trace gives the reason as 'non-JRMP server at remote endpoint'. We should use this ConnectIOException and provide better feedback. -- 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-1530) [JMX Console] AbstractAction handleException always prints throwable stacktrace
[ https://issues.apache.org/jira/browse/QPID-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marnie McCormack updated QPID-1530: --- Fix Version/s: Eclipse MC M5 Affects Version/s: (was: M4) (was: M3) Sscoping items for early 2009 release of Java Eclipse Mgt Console [JMX Console] AbstractAction handleException always prints throwable stacktrace --- Key: QPID-1530 URL: https://issues.apache.org/jira/browse/QPID-1530 Project: Qpid Issue Type: Bug Components: Java Management : JMX Console Reporter: Martin Ritchie Assignee: Aidan Skinner Fix For: Eclipse MC M5 Attachments: QPID-1530_12dec2008.patch Summary: handleException (AbstractAction:L:77) always prints the stackTrace of the Throwable that it receives as well as displaying an error dialog to the user. This behaviour is undesirable for exceptions such as connection failures. The only stackTraces that should be printed are due to programming failures such as incorrect handingling of data from the broker. The IOException thrown from JMXServerRegistry due to a incorrect username/password, for example, does not need to printed out. The dialog box to the user is sufficient. -- 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-1539) Move common JMX code into shared library
[ https://issues.apache.org/jira/browse/QPID-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marnie McCormack updated QPID-1539: --- Fix Version/s: Eclipse MC M5 Affects Version/s: (was: M4) Sscoping items for early 2009 release of Java Eclipse Mgt Console Move common JMX code into shared library Key: QPID-1539 URL: https://issues.apache.org/jira/browse/QPID-1539 Project: Qpid Issue Type: Improvement Components: Java Management : CLI Tool, Java Management : JMX Console Reporter: Aidan Skinner Assignee: Aidan Skinner Fix For: Eclipse MC M5 Attachments: 0006-QPID-1539-add-management-common-module.-Move-SASL-a.patch Shared code such as the SASL negotiation, JMX login etc should be moved into a common library. -- 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-1531) JMX Console dialog boxes buttons do not accept default keyboard input
[ https://issues.apache.org/jira/browse/QPID-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marnie McCormack updated QPID-1531: --- Fix Version/s: Eclipse MC M5 Affects Version/s: (was: M4) (was: M3) Sscoping items for early 2009 release of Java Eclipse Mgt Console JMX Console dialog boxes buttons do not accept default keyboard input - Key: QPID-1531 URL: https://issues.apache.org/jira/browse/QPID-1531 Project: Qpid Issue Type: Bug Components: Java Management : JMX Console Reporter: Martin Ritchie Assignee: Aidan Skinner Priority: Minor Fix For: Eclipse MC M5 Summary: The JMX console boxes do not respond to what I would say are common keyboard inputs. Tab between fields is ok There is no default button for return to work on The cancel button does not respond to escape. This must just be a minor configuration issue on our part but would certainly improve usability. -- 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-1342) qpid-cli isn't properly integrated with the build system and the tests don't run correctly by default
[ https://issues.apache.org/jira/browse/QPID-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marnie McCormack updated QPID-1342: --- Component/s: (was: Java Management : JMX Console) Java Management : CLI Tool qpid-cli isn't properly integrated with the build system and the tests don't run correctly by default - Key: QPID-1342 URL: https://issues.apache.org/jira/browse/QPID-1342 Project: Qpid Issue Type: Bug Components: Java Management : CLI Tool Affects Versions: M4 Reporter: Rafael H. Schloming Assignee: Lahiru Gunathilake -- 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-1343) qpid/java/management/client has no build scripts!
[ https://issues.apache.org/jira/browse/QPID-1343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marnie McCormack updated QPID-1343: --- Component/s: (was: Java Management : JMX Console) Java Management : QMan qpid/java/management/client has no build scripts! - Key: QPID-1343 URL: https://issues.apache.org/jira/browse/QPID-1343 Project: Qpid Issue Type: Bug Components: Java Management : QMan Affects Versions: M4 Reporter: Rafael H. Schloming Assignee: Rafael H. Schloming -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Qpid slogan?
I have small children, who occasionally watch the same films over over so ... Qpid: To infinity and beyond (TM) This one for Robert Greig: Qpid: Mnah, Mnah Anyway, can you tell it's a big admin week this end ! This is my final frivolous posting, honest. Marnie On Thu, Jan 29, 2009 at 11:07 AM, Mark Atwell mark.atw...@gmail.com wrote: If we're going down the popular culture/film-reference route: Qpid - Message Transformers! Qpid - Transforming Messaging! Qpid - Materializing Near You! Or (perhaps a bit obscure): Qpid: For all your Dark Nights... Marnie, how about: Qpid: Warp Factor AMQP! -- Mark On Thu, Jan 29, 2009 at 10:48 AM, Marnie McCormack marnie.mccorm...@googlemail.com wrote: Qpid: The force is with you Qpid: Warp Factor X (I'm not enough of a trekkie to have a better idea) On Thu, Jan 29, 2009 at 10:45 AM, Mark Atwell mark.atw...@gmail.com wrote: Sorry, tea-break made me think of a load more!: QPID: Queue This! (a la Matrix: Dodge This! - will appeal to techies) QPID: Quite Perfect Innate Design (or some variant) In a similar vein: QPID: Quite Possibly Iconic Design(or variant - Probably?) This one sounds like someone else's (so apologies in advance) QPID: Quick, Purposeful, Innate Design Ah... my tea's run out... -- Mark On Thu, Jan 29, 2009 at 10:21 AM, Mark Atwell mark.atw...@gmail.com wrote: If you're looking for a T-shirt-like/mug logo how about a play on 'The Classic': I'm with QPid! This also almost works with the arrow-like AMQP logo! BTW is the capitalisation of QPid settled on 'Qpid'? Or possibly: AMQP?: I'm with QPid! AMQP?: I love QPid!(opportunity to go with some Eros/cherub-type-stuff?) QPid loves AMQP BTW I'm not even going to go near the Kenny Everett Show character thing for fear of offence! -- Mark On Wed, Jan 28, 2009 at 1:59 PM, Robert Godfrey rob.j.godf...@gmail.com wrote: Sorry - been away for a couple of days and just caught up with this thread now. 2009/1/27 Jonathan Robie jonathan.ro...@redhat.com: It's OK to differ ;- But let me explain my reasoning: the whole point of a slogan is to establish identity so people know what it is. AMQP and messaging are fundamental to what Qpid is. I think it's interesting here to look at a quick definition (from http://www.thefreedictionary.com/slogan): 1. A phrase expressing the aims or nature of an enterprise, organization, or candidate; a motto. 2. A phrase used repeatedly, as in advertising or promotion: all the slogans and shibboleths coined out of the ideals of the peoples for the uses of imperialism Margaret Sanger. 3. A battle cry of a Scottish clan. What we seem to be arguing about here is whether we want a slogan that fulfils definition 1. or definition 2. (although perhaps the Glasgow contingent would like to make some suggestions fulfil definition 3.) Personally I think that right now we want to have a catchy advertising slogan to draw people in, along with logos etc that work well on marketing material (I want a Qpid t-shirt :-) ). Much as I agree that something like Qpid: Open Source AMQP Messaging succinctly describes the aims of the project, I don't think it draws in people to take a look. Furthermore it does nothing to help people remember the name Qpid. We *do* also need to make sure that in searches for AMQP and Enterprise Messaging, Qpid features highly. However I think there's a fair probability that if you've heard of AMQP you've probably heard of Qpid. So I would probably argue that we need (at least) two different slogans... And of the two I think that advertising and drawing people is is what we are currently more in need of. We need to get the name Qpid out there so that people remember it (even if they don't know what is does)... Now... time to think of some battle cries... -- Rob - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-1618) unacked persistent messages don't get to messageStore of newbie cluster broker.
[ https://issues.apache.org/jira/browse/QPID-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] michael j. goulish updated QPID-1618: - Attachment: (was: unack_newbie.diff) unacked persistent messages don't get to messageStore of newbie cluster broker. --- Key: QPID-1618 URL: https://issues.apache.org/jira/browse/QPID-1618 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: M4 Reporter: michael j. goulish Priority: Critical When a new broker is added to a cluster, persistent messages that have not yet been ACKed do not get stored in the new brokers messageStore. How to reproduce: ( this is overview -- actual scripts follow ) 1. kill any MY_CLUSTER brokers from previous test 2. remove data dirs from previous test, and recreate 3. start node 1 as first member of MY_CLUSTER 4 declare the MY_CLUSTER queue -- durable 5. connect to it with receiver -- use ack frequency of 10; 6. connect with publish send only 5 persistent msgs, receiver will get them but not ack. 7. start second node 8. when the state transfer completes kill both nodes. (receiver should also perish) 9. start up the second node only, as new first member of MY_CLUSTER. ( I.e. use 2nd broker's data dir path. ) 10. start and attach a new receiver PREVIOUS RESULT -- nothing. messages were never stored in broker2's messageStore. RESULT -- new receiver now gets 5 messages. durable queue says that sender confirmed point moved to (5+0) == Scripts for reproducing problem. == ### #step 1 ## ### #! /bin/bash echo echo Step 1: Kill any brokers already running in the MY_CLUSTER cluster echo kill -9 `pgrep -f MY_STORE` echo There should be no remaining brokers. Here they are: ps -aef | grep qpidd | grep -v grep ### #step 2 ## ### #! /bin/bash echo echo Step 2: remove and rebuild the store data dirs. echo rm -rf ./data mkdir -p ./data/1 ./data/2 ### #step 3 ## ### #! /bin/bash echo echo Step 3: Start the first broker in a cluster, using Store in ./data/1 . echo rm broker_1.log $QPID_ROOT/cpp/src/qpidd --no-module-dir\ --load-module $QPID_ROOT/cpp/src/.libs/cluster.so \ --load-module $STORE_ROOT/cpp/lib/.libs/msgstore.so \ --cluster-name MY_CLUSTER -p 5813 \ --auth=no --mgmt-enable=no\ --log-enable debug --log-to-file ./broker_1.log \ --data-dir ./data/1 ### #step 4 ## ### #! /bin/bash echo Step 4: Declaring queue. $QPID_ROOT/cpp/examples/direct/declare_queues # !! NOTE !! # edit declare_queues.cpp to do port 5813 # in call to session.queueDeclare use arg::durable=true # and arg::queue=MY_QUEUE, # edit exchangeBind call to use: # arg::queue = MY_QUEUE, ### #step 5 ## ### #! /bin/bash echo Step 5: Starting receiver... $QPID_ROOT/cpp/src/tests/receiver \ -p 5813 \ --queue MY_QUEUE \ --messages 10 \ --ack-frequency 10 ### #step 6 ## ### #! /bin/bash echo Publish only 5 messages, so the receiver will not yet ack.
Re: Do we *need* the class hierarchy diagrams in the C++ doxygen?
I just committed a version without graphics. Shout if you hate me for it. Jonathan Steve Huston wrote: Jonathan Robie wrote: I don't like the class hierarchy diagrams in the C++ doxygen html. I think I can suppress them. This would reduce file size, and I think it might make it easier to read. Anyone want to tell me this would be a bad idea? I'm responsible for putting those in - they seemed cool at the time. They're probably not adding much value so if you think its more readable without, and given the huge size, I'd say go ahead and take them out. We can put them back if there's widespread uproar, I suspect there won't be. People who feel strongly can always generate their own customized doxygen. Right - for users, the only time they really add benefit is when the method you think you want is in an ancestor of the class you're reading and it's nice to have a map of where to look next. That's somewhat of an issue with qpid, but not such a big deal that the space is worth it, IMO. -Steve - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Qpid slogan?
Mark Atwell wrote: I'm with QPid! I like Carl. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Web site triage
A bunch of us have been working on the web pages - Carl, Gordon, and I have been among the contributors - with the immediate goal of making it easier to get a quick overview and get up and running with the distribution. How are we doing? I think the following pages are particularly important, and have been improved: http://qpid.apache.org/ http://qpid.apache.org/download.html http://qpid.apache.org/getting-started.html http://qpid.apache.org/documentation.html http://qpid.apache.org/docs/api/cpp/html/index.html http://qpid.apache.org/docs/api/python/html/index.html http://qpid.apache.org/faq.html These pages need work, and are probably the next priority: http://qpid.apache.org/building.html http://qpid.apache.org/developer-pages.html .NET materials (not yet available) These pages haven't changed much lately, but they look good to me as is: http://qpid.apache.org/mailing-lists.html http://issues.apache.org/jira/browse/qpid http://qpid.apache.org/source-repository.html Feedback is welcome! Jonathan - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Web site triage
Reading the FAQ, it needs more Java details and performance figures, which I'll add too. Marnie On Thu, Jan 29, 2009 at 4:51 PM, Marnie McCormack marnie.mccorm...@googlemail.com wrote: Hi Jonathan, Thanks for all this ! The C++ docs are looking good (so much more comprehensive). Overall the site has come on loads, and it's great to see it looking so much more rounded. I've updated a few of these pages to add details on the Java side, and separate some of the details out a little by broker (as per the conversations on Users). I have also pulled some of the important Java documentation up to the top as it has gotten a little buried in some of the re-orgs. I'd prefer not to be separating components from the same release out by AMQP version as I think it sends the wrong signal and is not how we actually make releases i.e. we released M4 not AMQP 0-10. Some of the information is becoming a little low level i.e on the download page we have pre-built Linux packlages with instructions but there's no info on what these actually are and some are rhm messaging instructions ? I think this stuff should probably be shipped onto the C++ pages or headlined more clearly. Regards, Marnie On Thu, Jan 29, 2009 at 4:24 PM, Jonathan Robie jonathan.ro...@redhat.com wrote: A bunch of us have been working on the web pages - Carl, Gordon, and I have been among the contributors - with the immediate goal of making it easier to get a quick overview and get up and running with the distribution. How are we doing? I think the following pages are particularly important, and have been improved: http://qpid.apache.org/ http://qpid.apache.org/download.html http://qpid.apache.org/getting-started.html http://qpid.apache.org/documentation.html http://qpid.apache.org/docs/api/cpp/html/index.html http://qpid.apache.org/docs/api/python/html/index.html http://qpid.apache.org/faq.html These pages need work, and are probably the next priority: http://qpid.apache.org/building.html http://qpid.apache.org/developer-pages.html .NET materials (not yet available) These pages haven't changed much lately, but they look good to me as is: http://qpid.apache.org/mailing-lists.html http://issues.apache.org/jira/browse/qpid http://qpid.apache.org/source-repository.html Feedback is welcome! Jonathan - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Web site triage
Marnie McCormack wrote: Hi Jonathan, Thanks for all this ! The C++ docs are looking good (so much more comprehensive). Overall the site has come on loads, and it's great to see it looking so much more rounded. Thanks! I've updated a few of these pages to add details on the Java side, and separate some of the details out a little by broker (as per the conversations on Users). I have also pulled some of the important Java documentation up to the top as it has gotten a little buried in some of the re-orgs. Excellent! I'd prefer not to be separating components from the same release out by AMQP version as I think it sends the wrong signal and is not how we actually make releases i.e. we released M4 not AMQP 0-10. Hmmm, I think I disagree. The two servers support different protocols, various parts of our M4 release are incompatible with each other, and that's a big surprise for the user if they don't know what to expect. In an ideal world, everything in one release is compatible with everything else. That's why I like being very clear about this. For instance, suppose a user just follows the instruction on the Getting Started page. They get a broker (pick one of 2), get a client, run the examples, and it doesn't work. Ooops. If we want to make it easier for the user to get started, we want to make sure they see this coming and know how to get compatible pieces. I'd rather just be able to tell our users that everything in a given release is compatible with everything else in the same release, but that's not realistic this time around. Some of the information is becoming a little low level i.e on the download page we have pre-built Linux packlages with instructions but there's no info on what these actually are and some are rhm messaging instructions ? I think this stuff should probably be shipped onto the C++ pages or headlined more clearly This section is for the binaries available for free on Fedora. How would you suggest headlining them more clearly? Jonathan - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Web site triage
I'd prefer not to be separating components from the same release out by AMQP version as I think it sends the wrong signal and is not how we actually make releases i.e. we released M4 not AMQP 0-10. that was me, to try make it really easy to know what works with what, based on some questions on the user list. Is it not clear that it is not all part of M4? ideas to make it better... Carl. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-1343) qpid/java/management/client has no build scripts!
[ https://issues.apache.org/jira/browse/QPID-1343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming resolved QPID-1343. --- Resolution: Fixed Fix Version/s: M4 qpid/java/management/client has no build scripts! - Key: QPID-1343 URL: https://issues.apache.org/jira/browse/QPID-1343 Project: Qpid Issue Type: Bug Components: Java Management : QMan Affects Versions: M4 Reporter: Rafael H. Schloming Assignee: Rafael H. Schloming Fix For: M4 -- 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-1343) qpid/java/management/client has no build scripts!
[ https://issues.apache.org/jira/browse/QPID-1343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming closed QPID-1343. - qpid/java/management/client has no build scripts! - Key: QPID-1343 URL: https://issues.apache.org/jira/browse/QPID-1343 Project: Qpid Issue Type: Bug Components: Java Management : QMan Affects Versions: M4 Reporter: Rafael H. Schloming Assignee: Rafael H. Schloming Fix For: M4 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Qpid slogan?
2009/1/29 Mark Atwell mark.atw...@gmail.com: If we're going down the popular culture/film-reference route: Well I realised that we could solve our logo and slogan issue in one go (apologies to non-British readers for whom this may be meaningless). We could use a box of chocolates as the logo and as the slogan: Qpid: Because the lady loves transactional messaging RG - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Qpid slogan?
The future's bright, the future's orang-utan? On Thu, Jan 29, 2009 at 7:45 PM, Robert Greig robert.j.gr...@gmail.comwrote: 2009/1/29 Mark Atwell mark.atw...@gmail.com: If we're going down the popular culture/film-reference route: Well I realised that we could solve our logo and slogan issue in one go (apologies to non-British readers for whom this may be meaningless). We could use a box of chocolates as the logo and as the slogan: Qpid: Because the lady loves transactional messaging RG - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Web site triage
Carl Trieloff wrote: I'd prefer not to be separating components from the same release out by AMQP version as I think it sends the wrong signal and is not how we actually make releases i.e. we released M4 not AMQP 0-10. that was me, to try make it really easy to know what works with what, based on some questions on the user list. Is it not clear that it is not all part of M4? ideas to make it better... I liked the way we had it, but I'm happy with any approach that makes it very clear which pieces are compatible. I really don't want people to download incompatible bits, shrug, and move on to some other implementation. Jonathan - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-1511) JMX Interface does not require authentication
[ https://issues.apache.org/jira/browse/QPID-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Gemmell updated QPID-1511: - Attachment: QPID-1511_29jan2009.patch create_example_ssl_certstores.sh I attach QPID-1511_29jan2009.patch to address this JIRA, and a script to produce an example keystore and truststore for users who dont have their own SSL certificate handy. I wasnt sure where to put that in the repository so its not in the patch. The JMXMP connector capabilities are left intact for now, but grouped for easy future removal (I think its a good idea to keep it all in for at least 1 revision before removing). 2 new files are added by the patch: qpid/java/broker/src/main/java/org/apache/qpid/server/security/auth/rmi/RMIPasswordAuthenticator.java qpid/java/broker/src/test/java/org/apache/qpid/server/security/auth/rmi/RMIPasswordAuthenticatorTest.java === Notes: === Adds authentication and SSL encryption to the JMX RMIConnectorServer, and updates the console and JMXConnectionFactory accordingly. Makes the RMI ConnectorServer use the custom MBeanServerForwarder invoker like the JMXMP connector has, thus enforcing the authorisation system. SSL is on by default in the config file but can be turned off in the config if desired, though the brokers config request defaults it to true so that need not be exposed if it isnt desired. The config.xml file is configured to use the test ssl certificate store in the java/test_resources/ssl directory created for the cpp.ssl test profile. The config file can be overidden by specifying the standard javax.net.ssl.* system properties normally available for this task. If the keystore or password are not set by one of these means, a configuration exception will be thrown and abort the broker startup. As a result of the above, to connect using the console/cli you will need to supply the relevant ssl trust store location and password if the certificates being used cant be verified by the default java trust stores. This can be done using the system properties javax.net.ssl.trustStore and javax.net.ssl.trustStorePassword, either at the command line when launching qpidmc(.exe), or by altering the qpidmc.ini file using the examples now provided within it. The broker will use the defined management port (default 8999) for the RMI registry as before, but now uses the OFFSET'th next port (+100 just now, thus 9099 normally) to export the actual JMX RMIConnectorServer, whereas previously this port was chosen at random by the JMX Factory methods, making it rather firewall unfriendly. A custom RMIServerSocketFactory is included to address the security issues surrounding RMI registries (namely that anyone on that machine is free to modify the registry and thus can intercept the JMX connections by replacing the JMX Connector Server stub in the registry with their own), by crippling the hostname detection and making it impossible to bind objects to the registry using RMI locally or remotely, instead requiring you to hold the object reference to it. The authenticator has a local MD5 hashing function to convert the password for comparison, but ideally this will be removed through modification of the Base64MD5 PD to do its own hashing, and the authenticator will then make use of the PD's verifyPassword method instead. Finally, the patch makes the JMXManagedObjectRegistry use the specific principal database listed in the configuration as the jmx management PD, as happens to AMQUserManagementMBean. The PD selection method used previously in JMXManagedObjectRegistry made it possible for the 2 areas to (unwittingly or otherwise) use different databases, which the AMQUMMBean implementation does not appear to be able to support properly if thats what was originally intended (see http://mail-archives.apache.org/mod_mbox/qpid-dev/200812.mbox/%3c00e101c953ff$1f33bca0$5d9b35...@gla.ac.uk%3e for way more info than you could ever want :P) JMX Interface does not require authentication - Key: QPID-1511 URL: https://issues.apache.org/jira/browse/QPID-1511 Project: Qpid Issue Type: Improvement Components: Java Broker, Java Management : JMX Console Reporter: Martin Ritchie Fix For: Eclipse MC M5 Attachments: create_example_ssl_certstores.sh, QPID-1511_29jan2009.patch Summary: JMX Interface uses the default RMI connector which has no authentication mechanism. We should not be shipping a JMX interface that doesn't have authentication. The interface has been disabled by default for M4 but this should be modified based on the outcome of the discussion on qpid-dev to authenticate all connections. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the
[java] QPID-1511 - JMX authentication
Just a quick prod for Martin so he doesn’t miss out on the fun due to email filters :) ..this one might take a touch longer to look at than some of the others still on your list hehe :) Robbie -Original Message- From: Robert Gemmell (JIRA) [mailto:qpid-...@incubator.apache.org] Sent: 30 January 2009 00:34 To: qpid-...@incubator.apache.org Subject: [jira] Updated: (QPID-1511) JMX Interface does not require authentication[MESSAGE NOT SCANNED] [ https://issues.apache.org/jira/browse/QPID-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Gemmell updated QPID-1511: - Attachment: QPID-1511_29jan2009.patch create_example_ssl_certstores.sh I attach QPID-1511_29jan2009.patch to address this JIRA, and a script to produce an example keystore and truststore for users who dont have their own SSL certificate handy. I wasnt sure where to put that in the repository so its not in the patch. The JMXMP connector capabilities are left intact for now, but grouped for easy future removal (I think its a good idea to keep it all in for at least 1 revision before removing). 2 new files are added by the patch: qpid/java/broker/src/main/java/org/apache/qpid/server/security/auth/rmi/RMIPasswordAuthenticator.java qpid/java/broker/src/test/java/org/apache/qpid/server/security/auth/rmi/RMIPasswordAuthenticatorTest.java === Notes: === Adds authentication and SSL encryption to the JMX RMIConnectorServer, and updates the console and JMXConnectionFactory accordingly. Makes the RMI ConnectorServer use the custom MBeanServerForwarder invoker like the JMXMP connector has, thus enforcing the authorisation system. SSL is on by default in the config file but can be turned off in the config if desired, though the brokers config request defaults it to true so that need not be exposed if it isnt desired. The config.xml file is configured to use the test ssl certificate store in the java/test_resources/ssl directory created for the cpp.ssl test profile. The config file can be overidden by specifying the standard javax.net.ssl.* system properties normally available for this task. If the keystore or password are not set by one of these means, a configuration exception will be thrown and abort the broker startup. As a result of the above, to connect using the console/cli you will need to supply the relevant ssl trust store location and password if the certificates being used cant be verified by the default java trust stores. This can be done using the system properties javax.net.ssl.trustStore and javax.net.ssl.trustStorePassword, either at the command line when launching qpidmc(.exe), or by altering the qpidmc.ini file using the examples now provided within it. The broker will use the defined management port (default 8999) for the RMI registry as before, but now uses the OFFSET'th next port (+100 just now, thus 9099 normally) to export the actual JMX RMIConnectorServer, whereas previously this port was chosen at random by the JMX Factory methods, making it rather firewall unfriendly. A custom RMIServerSocketFactory is included to address the security issues surrounding RMI registries (namely that anyone on that machine is free to modify the registry and thus can intercept the JMX connections by replacing the JMX Connector Server stub in the registry with their own), by crippling the hostname detection and making it impossible to bind objects to the registry using RMI locally or remotely, instead requiring you to hold the object reference to it. The authenticator has a local MD5 hashing function to convert the password for comparison, but ideally this will be removed through modification of the Base64MD5 PD to do its own hashing, and the authenticator will then make use of the PD's verifyPassword method instead. Finally, the patch makes the JMXManagedObjectRegistry use the specific principal database listed in the configuration as the jmx management PD, as happens to AMQUserManagementMBean. The PD selection method used previously in JMXManagedObjectRegistry made it possible for the 2 areas to (unwittingly or otherwise) use different databases, which the AMQUMMBean implementation does not appear to be able to support properly if thats what was originally intended (see http://mail-archives.apache.org/mod_mbox/qpid-dev/200812.mbox/%3c00e101c953ff$1f33bca0$5d9b35...@gla.ac.uk%3e for way more info than you could ever want :P) JMX Interface does not require authentication - Key: QPID-1511 URL: https://issues.apache.org/jira/browse/QPID-1511 Project: Qpid Issue Type: Improvement Components: Java Broker, Java Management : JMX Console Reporter: Martin Ritchie Fix For: Eclipse MC M5 Attachments: create_example_ssl_certstores.sh,
RE: IKVMing the Java client for .Net
Hi all, Just a quick intro for the list since I've been quiet to date. I work on messaging technologies in the Connected Systems Division at Microsoft. I've been tracking AMQP since early 2005 when John Davies first announced its existence at the Web Services on Wall Street Conference. In a previous life I architected HP's JMS implementation and chunks of transaction processing and messaging middleware for HP, Arjuna and Bluestone. Carl's right, we have been investigating the idea of layering a WCF channel implementation on top of the C++ client library. That is, the managed code channel implementation would pinvoke down to the native C++ code. This is the approach that we used for the MSMQ channel that ships in the .NET framework today and it works pretty well. We're drawn to this approach primarily because of the maturity of the C++ code base. The pure .NET approach clearly has merit too; one of the key advantages being that it offers the potential to factor the code in a way that's more in line with WCF best practice, i.e., as a set of layered channels rather than as a monolithic block. We're planning on putting in some effort in on this task but I think there are a few more pressing tasks on the Windows side of the house that we'll try to help out with first. Cliff has already commented on the build system issues; I think it'd be great if we could get the equivalent of the make/make check functionality that exists today on Linux up and running on Windows. As people have already mentioned, it would be a big improvement if we can get the builds running of the same input files so that we can avoid these sync issues that have been causing problems recently. Then there's the packaging work that folks have been discussing, adding DLL support and building some form of installer to make the end-user experience as slick as possible. Does this sound like a reasonable set of things? Anyway, it's great to be here and I look forward to working with you all. Cheers, Dave. -Original Message- From: Carl Trieloff [mailto:cctriel...@redhat.com] Sent: Wednesday, January 28, 2009 12:25 PM To: dev@qpid.apache.org Subject: Re: IKVMing the Java client for .Net Joshua Kramer wrote: I tend to agree that we'd need to build .NET stuff by hand on top since in a raw Java API there will be things that are not idiomatic in .NET - e.g. no use of events, or capitalisation of method names etc. Has anybody investigated the possibility of creating a .NET assembly from the C++ client, instead of trying to use IKVM and the Java client? When speaking to the Microsoft guys that had mentioned trying this approach with me. Cliff, any comments on the topic? Carl. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
