Re: qpid-route can't link two broker
pclovec wrote: i have try to tested link two broker in one mahcine. 1. first using c++ declare_queue create two queue names message_queue and two exchange amp.direct for each broker. sample: #./declare_queue 127.0.0.1:10003 and #./declare_queue 127.0.0.1:10004 2. the queue and exchange has created . i running command to link them #qpid-route link add 127.0.0.1:10003 127.0.0.1:10004 #qpid-route link add 127.0.0.1:10004 127.0.0.1:10003 check qpid-route link list 127.0.0.1 1003 check qpid-route link list 127.0.0.1 1004 3. running qpid-route to map them # qpid-route route add 127.0.0.1:10003 127.0.0.1:10004 amp.direct routing-key # qpid-route route add 127.0.0.1:10004 127.0.0.1:10003 amp.direct routing-key check #qpid-route route list 127.0.0.1:10003 #qpid-route route list 127.0.0.1:10004 i can saw the link map created. broker. exchange key...are seems works now i guess this two brokers and two exchange has map success. then i running #./direct_producer 127.0.0.1 10003 to send the message .it show me success. and i running #./listener 127.0.0.1 1004 to get message .show me the error. i don't know what i miss? thanks It looks like you mis-typed the routing key in your qpid-route route add commands. The direct example uses routing_key (with an underscore). You typed routing-key (with a hyphen). -Ted - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Assigned: (QPID-1650) in src/tests, separate the code for ClusterFixture
[ https://issues.apache.org/jira/browse/QPID-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway reassigned QPID-1650: - Assignee: Alan Conway in src/tests, separate the code for ClusterFixture --- Key: QPID-1650 URL: https://issues.apache.org/jira/browse/QPID-1650 Project: Qpid Issue Type: Improvement Components: C++ Broker Reporter: michael j. goulish Assignee: Alan Conway Priority: Minor Attachments: separate_ClusterFixture.diff Separating out the code for ClusterFixture into its own files so it can be re-used. -- 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-1650) in src/tests, separate the code for ClusterFixture
[ https://issues.apache.org/jira/browse/QPID-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway closed QPID-1650. - Resolution: Fixed Comitted r741568 in src/tests, separate the code for ClusterFixture --- Key: QPID-1650 URL: https://issues.apache.org/jira/browse/QPID-1650 Project: Qpid Issue Type: Improvement Components: C++ Broker Reporter: michael j. goulish Priority: Minor Attachments: separate_ClusterFixture.diff Separating out the code for ClusterFixture into its own files so it can be re-used. -- 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
for qpid-route problem ,some body can help me .thanks
i have try to tested link two broker in one mahcine. 1. first using c++ declare_queue create two queue names message_queue and two exchange amp.direct for each broker. sample: #./declare_queue 127.0.0.1:10003 and #./declare_queue 127.0.0.1:10004 2. the queue and exchange has created . i running command to link them #qpid-route link add 127.0.0.1:10003 127.0.0.1:10004 #qpid-route link add 127.0.0.1:10004 127.0.0.1:10003 check qpid-route link list 127.0.0.1 1003 check qpid-route link list 127.0.0.1 1004 3. running qpid-route to map them # qpid-route route add 127.0.0.1:10003 127.0.0.1:10004 amp.direct routing-key # qpid-route route add 127.0.0.1:10004 127.0.0.1:10003 amp.direct routing-key check #qpid-route route list 127.0.0.1:10003 #qpid-route route list 127.0.0.1:10004 i can saw the link map created. broker. exchange key...are seems works now i guess this two brokers and two exchange has map success. then i running #./direct_producer 127.0.0.1 10003 to send the message .it show me success. and i running #./listener 127.0.0.1 1004 to get message .show me the error. i don't know what i miss? thanks - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-1128) NPE displayed when adding queue to navigation
[ https://issues.apache.org/jira/browse/QPID-1128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Ritchie resolved QPID-1128. -- Resolution: Fixed Assignee: Martin Ritchie (was: Aidan Skinner) Work committed and reviewed by Martin NPE displayed when adding queue to navigation - Key: QPID-1128 URL: https://issues.apache.org/jira/browse/QPID-1128 Project: Qpid Issue Type: Bug Components: Java Management : JMX Console Reporter: Martin Ritchie Assignee: Martin Ritchie Fix For: Eclipse MC M5 Attachments: QPID-1128_23nov2008.patch Summary: If you sort the queues on a Virtualhost by 'Consumer count' and then proceed to '- Add to Navigation' then it will fail and a box stating 'Manged Object is null : NPE' will be displayed. Workaround: Ensure that 'Consumer count' is not the chosen 'Sort by' value. -- 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-1651) add editable broker argv to src/tests/ClusterFixture
[ https://issues.apache.org/jira/browse/QPID-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] michael j. goulish updated QPID-1651: - Attachment: ClusterFixtureArgv.diff add editable broker argv to src/tests/ClusterFixture Key: QPID-1651 URL: https://issues.apache.org/jira/browse/QPID-1651 Project: Qpid Issue Type: Improvement Components: C++ Broker Reporter: michael j. goulish Priority: Minor Attachments: ClusterFixtureArgv.diff make the argv that is used for the broker creation editable -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-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 ] Martin Ritchie resolved QPID-1530. -- Resolution: Fixed Work reviewed and committed by Martin [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] Created: (QPID-1652) Create concrete MessagePublishInfo class and test
Create concrete MessagePublishInfo class and test - Key: QPID-1652 URL: https://issues.apache.org/jira/browse/QPID-1652 Project: Qpid Issue Type: Improvement Components: Java Broker Affects Versions: M4 Reporter: Martin Ritchie Assignee: Martin Ritchie Priority: Minor Fix For: M5 Summary: We currently have a large number of anonymous classes that all do the same or similar things, but none are tested. Replace anonymous classes and test new class. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-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 ] Martin Ritchie resolved QPID-1532. -- Resolution: Fixed Assignee: Martin Ritchie (was: Aidan Skinner) Work reviewed and committed by Martin [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: Martin Ritchie 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] Resolved: (QPID-1533) PrincipalDatabase interface has no reload()
[ https://issues.apache.org/jira/browse/QPID-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Ritchie resolved QPID-1533. -- Resolution: Fixed Fix Version/s: M5 Assignee: Martin Ritchie (was: Aidan Skinner) Work reviewed and committed by Martin PrincipalDatabase interface has no reload() --- Key: QPID-1533 URL: https://issues.apache.org/jira/browse/QPID-1533 Project: Qpid Issue Type: Bug Components: Java Broker, Java Management : JMX Console, Starter Reporter: Martin Ritchie Assignee: Martin Ritchie Fix For: M5, Eclipse MC M5 Attachments: QPID-1533_16dec2008.patch Summary: The management console has a reload function which is described as 'Reloading all user data' Currently it only reloads the JMX Rights file 'jmxremote.access'. This reload method should be updated to reload the user credentials stored in the PrincipalDatabase if they are loaded and cached at startup. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-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 ] Martin Ritchie resolved QPID-1591. -- Resolution: Fixed Assignee: Martin Ritchie (was: Aidan Skinner) Work reviewed and committed by Martin [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: Martin Ritchie 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] Resolved: (QPID-1592) [JMX Console] Update the management console to use recent rcp plugins and standardise launcher types
[ https://issues.apache.org/jira/browse/QPID-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Ritchie resolved QPID-1592. -- Resolution: Fixed Work reviewed and committed by Martin [JMX Console] Update the management console to use recent rcp plugins and standardise launcher types Key: QPID-1592 URL: https://issues.apache.org/jira/browse/QPID-1592 Project: Qpid Issue Type: Improvement Components: Java Management : JMX Console Reporter: Robert Gemmell Assignee: Aidan Skinner Fix For: Eclipse MC M5 Attachments: QPID-1592_1.zip, QPID-1592_19jan2008.patch, QPID-1592_19jan2008.sh, QPID-1592_2.zip The console is currently using a mixture of newer and older rcp plugins, and a mixture of different launchers depending on platform. It should be updated to uniformly use recent plugins, and the launchers for all platforms standardised on the new equinox launchers. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Assigned: (QPID-1592) [JMX Console] Update the management console to use recent rcp plugins and standardise launcher types
[ https://issues.apache.org/jira/browse/QPID-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Ritchie reassigned QPID-1592: Assignee: Martin Ritchie (was: Aidan Skinner) [JMX Console] Update the management console to use recent rcp plugins and standardise launcher types Key: QPID-1592 URL: https://issues.apache.org/jira/browse/QPID-1592 Project: Qpid Issue Type: Improvement Components: Java Management : JMX Console Reporter: Robert Gemmell Assignee: Martin Ritchie Fix For: Eclipse MC M5 Attachments: QPID-1592_1.zip, QPID-1592_19jan2008.patch, QPID-1592_19jan2008.sh, QPID-1592_2.zip The console is currently using a mixture of newer and older rcp plugins, and a mixture of different launchers depending on platform. It should be updated to uniformly use recent plugins, and the launchers for all platforms standardised on the new equinox launchers. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-1653) add ability to dump queue/message content to a file via JMX
add ability to dump queue/message content to a file via JMX --- Key: QPID-1653 URL: https://issues.apache.org/jira/browse/QPID-1653 Project: Qpid Issue Type: New Feature Components: Java Broker, Java Management : JMX Console Reporter: Robert Gemmell Priority: Minor Fix For: Eclipse MC M5 It would be useful to be able to dump queue/message content to a file using the mangement console. Some initial discussion on the topic from partychat: (4:41:20 PM) Robbie: just considering the message/queue dump to file feature (4:41:53 PM) Robbie: i was wondering...any thoughts on the best approach for tackling binary content ? (4:42:30 PM) Robbie: since it may or may not be mixed in with plain text messages (4:43:22 PM) Robbie: i think thinking maybe go with hex output..? (4:43:32 PM) Robbie: *was thinking (4:43:40 PM) partych...@gmail.com: [Martin] binary file? (4:44:05 PM) Robbie: what about the text messages then ?:) (4:44:06 PM) partych...@gmail.com: [Martin] The Messae/queue dump feature was it to be readable? (4:44:23 PM) Robbie: hmm, good point...i just asumed so snip (4:45:45 PM) partych...@gmail.com: [Martin] Is it couple with a message/queue load? (4:45:52 PM) partych...@gmail.com: [Martin] s/couple/coupled/ (4:45:52 PM) partych...@gmail.com: Martin meant Is it coupled with a message/queue load? (4:46:02 PM) Robbie: nope (4:46:20 PM) partych...@gmail.com: [aidan] i would say leave the contents alone and dump the bit stream. I might have a zip or something i want to get out of the message that I don't want to de-hexify (4:46:24 PM) Robbie: i dot eall have any mroe background on it than what i just said above hehe (4:46:44 PM) Robbie: *dont really (4:47:06 PM) partych...@gmail.com: [Martin] I'd say dump like the MC viewer : | ASCII | HEX | (4:47:42 PM) Robbie: my original thoughts were to be putting out some of the header info, then the contents.lather, rinse and repeat (4:47:58 PM) partych...@gmail.com: [aidan] the viewer is a somewhat different use case IMO (4:48:13 PM) partych...@gmail.com: [Martin] Take a look at the MessasgeStore Tool ... it does some thing similar.. but only dumps to the screen (4:48:37 PM) Robbie: k (4:48:59 PM) partych...@gmail.com: [aidan] yeah, see, in the case of the message store tool I think the intention is to get something human-readable (4:49:08 PM) partych...@gmail.com: [aidan] same as with view-message in the console (4:49:26 PM) partych...@gmail.com: [aidan] but with dump to disk you might want to do a number of things with the message (4:49:36 PM) partych...@gmail.com: [aidan] that require the origional message contents (4:49:49 PM) partych...@gmail.com: [Martin] but without a load it seems a bit odd (4:50:03 PM) partych...@gmail.com: [Martin] I'd expect dump , fix issue, load (4:50:09 PM) Robbie: i think maybe we need a marnie:ping to decide futher :) (4:50:24 PM) Robbie: well, load isnt out of the question, it was jsut never mentioned is all :) (4:50:24 PM) partych...@gmail.com: [aidan] file a jira and attach this conversation to it? (4:50:36 PM) partych...@gmail.com: [rob] i'd not worry about load just yet (4:50:40 PM) Robbie: k (4:50:48 PM) partych...@gmail.com: [aidan] load gets rather more messy (4:50:52 PM) partych...@gmail.com: [rob] indeed snip (4:51:01 PM) partych...@gmail.com: [rob] it breaks lots of important properties of the model as well snip (4:51:30 PM) partych...@gmail.com: [aidan] but I can see a use case of something like i need this humongous archive out of my queue so I can put it on an ftp server snip (4:51:43 PM) partych...@gmail.com: [aidan] and having to de-MIME it first would irritate me (4:52:00 PM) Robbie: ;) (4:52:09 PM) partych...@gmail.com: [rob] The most likely thing is going to be this message keeps breaking my application what's in the message I don't know - whenever I try to get it it breaks my application snip (4:52:52 PM) partych...@gmail.com: [aidan] rob: indeed, and if the message is a bitstream it should probably stay a bitstream snip (4:53:03 PM) partych...@gmail.com: [rob] yes - you want to have the option (4:53:22 PM) partych...@gmail.com: [rob] ideally we'd like to have a way to deserialize the different java message types (4:53:32 PM) partych...@gmail.com: [rob] you also want to get the headers - separate from the file content (4:55:07 PM) Robbie: k -- 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
WsDmAdapterTest Failure
Hi all, been meaning to say for a while now. All the tests in WsDmAdapterTest fail like this for me: I'm running JDK 1.6.0_10 on a RHEL 4 box. Anyone any thoughts? Testcase: testGeResourcePropertiesOK took 0.14 sec Caused an ERROR Connection refused org.apache.muse.ws.addressing.soap.SoapFault: Connection refused at org.apache.muse.core.AbstractResourceClient.invoke(AbstractResourceClient.java:298) at org.apache.muse.core.AbstractResourceClient.invoke(AbstractResourceClient.java:254) at org.apache.muse.ws.resource.remote.WsResourceClient.getResourceProperty(WsResourceClient.java:138) at org.apache.muse.ws.resource.sg.remote.ServiceGroupClient.getMembers(ServiceGroupClient.java:110) at org.apache.qpid.management.wsdm.WsDmAdapterTest.setUp(WsDmAdapterTest.java:160) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.extensions.TestSetup.run(TestSetup.java:23) -- Martin Ritchie - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Binary compatibility and 1.1.2
A thread on d...@qpid reminds me that we still don't have a binary compatibility story. I'm not sure where customer expectations are set but right now there is an excellent chance that a simple yum update will cause qpid-based apps to explode. If this seems like something we want to do I can write up a Bugzilla. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-1648) Enable live reconfiguration of Log4J settings for the Java broker via JMX
[ https://issues.apache.org/jira/browse/QPID-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Gemmell updated QPID-1648: - Attachment: log4j_config_changes.patch QPID-1648_6feb2009.patch I attach QPID-1648_6feb2009.patch - this should be applied after the patch for QPID-1511 The patch adds a new MBean to cater for logging management. It allows changing the levels of any active log4j logger at runtime, and viewing the effective (taking the logger heirarchy into consideration) logging levels of the active loggers. It also allows viewing and updating of the existing level assigned to a logger within the log4j xml configuration file (it doesnt add new loggers/level elements, just manipulates existing ones.) It has similar capabilities for the RootLogger, although in this case the viewing of the level is done via an attribute. Finally it has an attribute for the log4j logwatch period to allow viewing whether logwatch is enabled or not. The MBeanInvocationHandler is updated to restrict access to the MBean to 'admin' level users. A test is included in the patch. I also attach a second patch which need not be applied, but shows some changes versus the current file which occur when the new configuration file is output. This happens because the XML parser adds in any defaulted attributes present in the DTD. (It also insists on writing the doctype line out on the same line as the end of the apache licence, I couldnt get it to stop that) Enable live reconfiguration of Log4J settings for the Java broker via JMX - Key: QPID-1648 URL: https://issues.apache.org/jira/browse/QPID-1648 Project: Qpid Issue Type: New Feature Components: Java Broker, Java Management : JMX Console Reporter: Robert Gemmell Fix For: Eclipse MC M5 Attachments: log4j_config_changes.patch, QPID-1648_6feb2009.patch It would be useful to be able to update the Log4J settings for a running Java broker via JMX, incase it was desirable to adjust logging to investigate an issue which became apparent after startup. Whilst Log4J supports monitoring its own configuration file for updates, the broker must be started with this enabled for it to be of any use, and updating the settings by manually modifying the xml file runs the risk of accidentally rendering the file invalid, which could lead to serious issues when the update is detected and applied by Log4j. In order to address these issues, adding the ability to to update the settings via JMX would allow users to be able to adjust the Log4J settings in 2 ways: by modifying the xml file programatically rather than by hand, or by modifying the Log4J runtime settings directly, allowing (temporary) updates even where Log4J has not been instructed to monitor its configuration file for change. -- 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
