[jira] Updated: (QPID-1918) Patches/files for Windows QMF plug-in support
[ https://issues.apache.org/jira/browse/QPID-1918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete MacKinnon updated QPID-1918: - Attachment: (was: qpid-1918.zip) > Patches/files for Windows QMF plug-in support > - > > Key: QPID-1918 > URL: https://issues.apache.org/jira/browse/QPID-1918 > Project: Qpid > Issue Type: New Feature > Components: Qpid Managment Framework > Environment: Windows XP SP3, VC++ 9.0 >Reporter: Pete MacKinnon >Assignee: Steve Huston > Attachments: qpid-1918.cmake.tar > > > Various files for the Windows QMF plug-in support in cpp, based off revision: > 785848 > Need Static builds (release and debug) for correct runtime integration with > Condor: > src/broker.vcproj > src/client.vcproj > src/common.vcproj > src/qmfagent.vcproj > src/qmfconsole.vcproj > src/qpid.sln > src/qpidbroker.vcproj > - Changed to provide compile flags required for header file integration of > Posix types declared by both Qpid and Condor: > src/qpid/sys/windows/IntegerTypes.h > src/qpid/sys/windows/uuid.cpp > src/qpid/sys/windows/uuid.h > - Modified signature of PipeHandle ctor and fixed a Windows race condition in > the processing loop: > src/qpid/agent/ManagementAgentImpl.cpp > - Refactored the pipe code so that Condor can get a true socket fd it can > select on in daemon_core: > src/qpid/sys/Pipehandle.h > src/qpid/sys/posix/PipeHandle.cpp > src/qpid/sys/windows/PipeHandle.cpp > - Removed explicit dependency on Debug libs since we now have even more > targets. Added Apache license: > examples/qmf_agent.vcproj > - Added Apache license: > src/protocol_gen.mak > examples/qmf-agent/example_gen.mak > - Updated QMF Agent example README: > examples/README -- 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-1918) Patches/files for Windows QMF plug-in support
[ https://issues.apache.org/jira/browse/QPID-1918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete MacKinnon updated QPID-1918: - Attachment: qpid-1918.cmake.tar Hi Steve, OK Round 2. The attached tar file has the requested Cmake changes and the other patches are fixes needed for Condor/Grid integration. The CMake changes are for a static build (release and debug) on Windows and are optional. They are turned off by default and should be non-intrusive to a standard Qpid Windows build. I also need the qmf-agent file name example.cpp moved to sample.cpp since the very name "example" messes up in the Cmake build. Please contact me by email if you have any questions. PATCH: qpid/cpp/src/CMakeLists.txt qpid/cpp/src/tests/CMakeLists.txt qpid/cpp/examples/CMakeLists.txt qpid/cpp/examples/qmf-agent/Makefile qpid/cpp/examples/README.txt qpid/cpp/src/qpid/agent/ManagementAgentImpl.cpp qpid/cpp/include/qpid/sys/windows/IntegerTypes.h qpid/cpp/include/qpid/sys/windows/uuid.h qpid/cpp/src/qpid/sys/windows/uuid.cpp qpid/cpp/src/qpid/sys/windows/PipeHandle.cpp ADD: qpid/cpp/examples/qmf-agent/CMakeLists.txt MOVE: qpid/cpp/examples/qmf-agent/example_gen.mak -> qpid/cpp/examples/qmf-agent/sample_gen.mak qpid/cpp/examples/qmf-agent/example.cpp -> qpid/cpp/examples/qmf-agent/sample.cpp > Patches/files for Windows QMF plug-in support > - > > Key: QPID-1918 > URL: https://issues.apache.org/jira/browse/QPID-1918 > Project: Qpid > Issue Type: New Feature > Components: Qpid Managment Framework > Environment: Windows XP SP3, VC++ 9.0 >Reporter: Pete MacKinnon >Assignee: Steve Huston > Attachments: qpid-1918.cmake.tar > > > Various files for the Windows QMF plug-in support in cpp, based off revision: > 785848 > Need Static builds (release and debug) for correct runtime integration with > Condor: > src/broker.vcproj > src/client.vcproj > src/common.vcproj > src/qmfagent.vcproj > src/qmfconsole.vcproj > src/qpid.sln > src/qpidbroker.vcproj > - Changed to provide compile flags required for header file integration of > Posix types declared by both Qpid and Condor: > src/qpid/sys/windows/IntegerTypes.h > src/qpid/sys/windows/uuid.cpp > src/qpid/sys/windows/uuid.h > - Modified signature of PipeHandle ctor and fixed a Windows race condition in > the processing loop: > src/qpid/agent/ManagementAgentImpl.cpp > - Refactored the pipe code so that Condor can get a true socket fd it can > select on in daemon_core: > src/qpid/sys/Pipehandle.h > src/qpid/sys/posix/PipeHandle.cpp > src/qpid/sys/windows/PipeHandle.cpp > - Removed explicit dependency on Debug libs since we now have even more > targets. Added Apache license: > examples/qmf_agent.vcproj > - Added Apache license: > src/protocol_gen.mak > examples/qmf-agent/example_gen.mak > - Updated QMF Agent example README: > examples/README -- 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-2013) Previous/Next N Message button in queue browser should take current size as step size
[ https://issues.apache.org/jira/browse/QPID-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-2013: - Status: Ready To Review (was: In Progress) > Previous/Next N Message button in queue browser should take current size as > step size > - > > Key: QPID-2013 > URL: https://issues.apache.org/jira/browse/QPID-2013 > Project: Qpid > Issue Type: Improvement > Components: Java Management : JMX Console >Affects Versions: 0.6 >Reporter: Aidan Skinner >Assignee: Robbie Gemmell > Fix For: 0.6 > > > It would be clearer to calculate the size of the currently displayed range of > messages and use that for the size of messages the next/previous buttons step > through. So if you displayed messages 20-30 you'd have "previous 10" and > "next 10" buttons. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Assigned: (QPID-2013) Previous/Next N Message button in queue browser should take current size as step size
[ https://issues.apache.org/jira/browse/QPID-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reassigned QPID-2013: Assignee: Aidan Skinner (was: Robbie Gemmell) Hi Aidan, can you review this change please, thanks. > Previous/Next N Message button in queue browser should take current size as > step size > - > > Key: QPID-2013 > URL: https://issues.apache.org/jira/browse/QPID-2013 > Project: Qpid > Issue Type: Improvement > Components: Java Management : JMX Console >Affects Versions: 0.6 >Reporter: Aidan Skinner >Assignee: Aidan Skinner > Fix For: 0.6 > > > It would be clearer to calculate the size of the currently displayed range of > messages and use that for the size of messages the next/previous buttons step > through. So if you displayed messages 20-30 you'd have "previous 10" and > "next 10" buttons. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2014) Clear notifications should prompt when clearing all of them
[ https://issues.apache.org/jira/browse/QPID-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-2014: - Status: Ready To Review (was: In Progress) > Clear notifications should prompt when clearing all of them > --- > > Key: QPID-2014 > URL: https://issues.apache.org/jira/browse/QPID-2014 > Project: Qpid > Issue Type: Improvement > Components: Java Management : JMX Console >Affects Versions: 0.6 >Reporter: Aidan Skinner >Assignee: Robbie Gemmell > Fix For: 0.6 > > > The clear notifications button removes all the notifications if none are > selected. This is a good choice of behaviour, but could be made safer with a > "are you sure? yes/no" prompt in case of user error. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Assigned: (QPID-2014) Clear notifications should prompt when clearing all of them
[ https://issues.apache.org/jira/browse/QPID-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reassigned QPID-2014: Assignee: Aidan Skinner (was: Robbie Gemmell) Hi Aidan, can you review this change please, thanks. > Clear notifications should prompt when clearing all of them > --- > > Key: QPID-2014 > URL: https://issues.apache.org/jira/browse/QPID-2014 > Project: Qpid > Issue Type: Improvement > Components: Java Management : JMX Console >Affects Versions: 0.6 >Reporter: Aidan Skinner >Assignee: Aidan Skinner > Fix For: 0.6 > > > The clear notifications button removes all the notifications if none are > selected. This is a good choice of behaviour, but could be made safer with a > "are you sure? yes/no" prompt in case of user error. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
August board report
As a TLP I need to report for Qpid to the Apache board every few months. In the past I have collected a list of items from the PMC. Based on suggestion from an Apache Member, I will start to also collect items to report on from the dev list. Please mail me or the dev list if you would like me to add/comment something on the next Qpid board report in the next 24 hours or so. kind regards Carl. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Assigned: (QPID-2007) new UI dialogs open in the upper left corner of the screen on Windows
[ https://issues.apache.org/jira/browse/QPID-2007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reassigned QPID-2007: Assignee: Aidan Skinner (was: Robbie Gemmell) Hi Aidan, can you review this change please, thanks. > new UI dialogs open in the upper left corner of the screen on Windows > - > > Key: QPID-2007 > URL: https://issues.apache.org/jira/browse/QPID-2007 > Project: Qpid > Issue Type: Bug > Components: Java Management : JMX Console >Affects Versions: 0.6 >Reporter: Robbie Gemmell >Assignee: Aidan Skinner >Priority: Minor > Fix For: 0.6 > > > Several parts of the new UI include custom dialogs for taking user input. On > Linux these new shells open in the centre of the parent however, in WIndows > they instead open at or near the upper left corner of the screen the > application is running. They should instead be centred on the application or > the monitor. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2021) provide new icons to distinguish the various 'manager' mbeans
[ https://issues.apache.org/jira/browse/QPID-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-2021: - Status: Ready To Review (was: In Progress) > provide new icons to distinguish the various 'manager' mbeans > - > > Key: QPID-2021 > URL: https://issues.apache.org/jira/browse/QPID-2021 > Project: Qpid > Issue Type: Improvement > Components: Java Management : JMX Console >Affects Versions: M2.1, M3, M4 >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Trivial > Fix For: 0.6 > > > The console currently uses the same icon for all the mbean objects in the > navigation tree. It would be helpful if the various 'manager' mbeans were > visually identifiable. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Assigned: (QPID-2021) provide new icons to distinguish the various 'manager' mbeans
[ https://issues.apache.org/jira/browse/QPID-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reassigned QPID-2021: Assignee: Aidan Skinner (was: Robbie Gemmell) Hi Aidan, can you review this change please, thanks. > provide new icons to distinguish the various 'manager' mbeans > - > > Key: QPID-2021 > URL: https://issues.apache.org/jira/browse/QPID-2021 > Project: Qpid > Issue Type: Improvement > Components: Java Management : JMX Console >Affects Versions: M2.1, M3, M4 >Reporter: Robbie Gemmell >Assignee: Aidan Skinner >Priority: Trivial > Fix For: 0.6 > > > The console currently uses the same icon for all the mbean objects in the > navigation tree. It would be helpful if the various 'manager' mbeans were > visually identifiable. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2008) queue names are not sorted when presented for user selection in some new UI dialogs
[ https://issues.apache.org/jira/browse/QPID-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-2008: - Status: Ready To Review (was: In Progress) > queue names are not sorted when presented for user selection in some new UI > dialogs > --- > > Key: QPID-2008 > URL: https://issues.apache.org/jira/browse/QPID-2008 > Project: Qpid > Issue Type: Bug > Components: Java Management : JMX Console >Affects Versions: 0.6 >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Minor > Fix For: 0.6 > > > queue names are not sorted when presented for user selection in some new UI > dialogs -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Assigned: (QPID-2008) queue names are not sorted when presented for user selection in some new UI dialogs
[ https://issues.apache.org/jira/browse/QPID-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reassigned QPID-2008: Assignee: Aidan Skinner (was: Robbie Gemmell) Hi Aidan, can you review this change please, thanks. > queue names are not sorted when presented for user selection in some new UI > dialogs > --- > > Key: QPID-2008 > URL: https://issues.apache.org/jira/browse/QPID-2008 > Project: Qpid > Issue Type: Bug > Components: Java Management : JMX Console >Affects Versions: 0.6 >Reporter: Robbie Gemmell >Assignee: Aidan Skinner >Priority: Minor > Fix For: 0.6 > > > queue names are not sorted when presented for user selection in some new UI > dialogs -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2007) new UI dialogs open in the upper left corner of the screen on Windows
[ https://issues.apache.org/jira/browse/QPID-2007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-2007: - Status: Ready To Review (was: In Progress) > new UI dialogs open in the upper left corner of the screen on Windows > - > > Key: QPID-2007 > URL: https://issues.apache.org/jira/browse/QPID-2007 > Project: Qpid > Issue Type: Bug > Components: Java Management : JMX Console >Affects Versions: 0.6 >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Minor > Fix For: 0.6 > > > Several parts of the new UI include custom dialogs for taking user input. On > Linux these new shells open in the centre of the parent however, in WIndows > they instead open at or near the upper left corner of the screen the > application is running. They should instead be centred on the application or > the monitor. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Assigned: (QPID-2009) password fields are not masked in the new UserManagement UI
[ https://issues.apache.org/jira/browse/QPID-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reassigned QPID-2009: Assignee: Aidan Skinner (was: Robbie Gemmell) Hi Aidan, can you review this change please, thanks. > password fields are not masked in the new UserManagement UI > --- > > Key: QPID-2009 > URL: https://issues.apache.org/jira/browse/QPID-2009 > Project: Qpid > Issue Type: Bug > Components: Java Management : JMX Console >Affects Versions: 0.6 >Reporter: Robbie Gemmell >Assignee: Aidan Skinner >Priority: Minor > Fix For: 0.6 > > > password fields are not masked in the new UserManagement UI -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2009) password fields are not masked in the new UserManagement UI
[ https://issues.apache.org/jira/browse/QPID-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-2009: - Status: Ready To Review (was: In Progress) > password fields are not masked in the new UserManagement UI > --- > > Key: QPID-2009 > URL: https://issues.apache.org/jira/browse/QPID-2009 > Project: Qpid > Issue Type: Bug > Components: Java Management : JMX Console >Affects Versions: 0.6 >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Minor > Fix For: 0.6 > > > password fields are not masked in the new UserManagement UI -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2021) provide new icons to distinguish the various 'manager' mbeans
[ https://issues.apache.org/jira/browse/QPID-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-2021: - Affects Version/s: (was: 0.5) (was: M2) (was: M1) M3 M4 > provide new icons to distinguish the various 'manager' mbeans > - > > Key: QPID-2021 > URL: https://issues.apache.org/jira/browse/QPID-2021 > Project: Qpid > Issue Type: Improvement > Components: Java Management : JMX Console >Affects Versions: M2.1, M3, M4 >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Trivial > Fix For: 0.6 > > > The console currently uses the same icon for all the mbean objects in the > navigation tree. It would be helpful if the various 'manager' mbeans were > visually identifiable. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-2021) provide new icons to distinguish the various 'manager' mbeans
provide new icons to distinguish the various 'manager' mbeans - Key: QPID-2021 URL: https://issues.apache.org/jira/browse/QPID-2021 Project: Qpid Issue Type: Improvement Components: Java Management : JMX Console Affects Versions: M2.1, M2, M1, 0.5 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Priority: Trivial Fix For: 0.6 The console currently uses the same icon for all the mbean objects in the navigation tree. It would be helpful if the various 'manager' mbeans were visually identifiable. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-2020) AMQConnection.create[Durable]ConnectionConsumer should do something better than just return null
AMQConnection.create[Durable]ConnectionConsumer should do something better than just return null Key: QPID-2020 URL: https://issues.apache.org/jira/browse/QPID-2020 Project: Qpid Issue Type: Bug Components: Java Client Reporter: Rafael H. Schloming In some cases these methods are expected to throw IllegalStateExceptions. At a minimum we should do this even if we aren't going to implement them for real. -- 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
Qrsh: a qpid-based remote execution utility.
I just checked in the code and test scripts for "Qrsh" to cpp/src/tests -- since the original motivation was to help with some cluster-testing tasks. I know that the original justification for doing this was .. a little slim. But it seems to me that Qpid and remote execution go together like .. chocolate and peanut butter. Like wine and cheese. Like fire and gasoline. So I wanted to do a remote-execution utility using Qpid. I wonder if it could grow up into a utility that might be handy to lots of people, to do things that aren't easy with just ssh. Here is the qrsh_doc.txt file, which is also checked in ( to a new directory, src/tests/qrsh_utils. ## qrsh: a Qpid-based remote shell utility Last updated: 3 Aug 09Mick Goulish ## = Overview = You're writing a multi-box test, and you want to write a shell script in which you start processes on other boxes and kill them (or send arbitrary signals to them). But ssh doesn't let you signal them, and bash isn't the greatest language in the world for creating data structures (like you need to associate the PIDs with box names and executable names.) Qsh is a utility implemented on Qpid that you can use from within your bash script, or any other scripting language. With it, you can: 1. run any executable on any box in your cluster. 2. don't worry about PIDs and box-names. You associate your own abstract names with the executable instances, and then use those names in the rest of your script. I.e. "broker_1" "sender_3" etc. 3. Launch the executable and wait until it returns, and get its exit code. 4. Launch your executable and do other stuff, then come back later and see if it has exited. 5. Get whatever it sent to stdout or stderr. 6. Get the contents of any other file. 7. send a command to all your boxes at once 8. send a command to a randomly selected box. 9. define groups of boxes, and send a command simultaneously to all boxes in a given group. = Using It = 1. You need to run a Qpid broker. 2. You start a Qpid client ( which is called a qrsh_server ) on all the boxes you care about. And you give them all names like "mrg13", "mrg14" etc. The names can be anything you want, but I've always used one qrsh_server per box, and given it the box name. ( However, you can run two on one box, they won't collide. ) 3. After you start all servers, send a "start" command to any one of them: 4. The qrsh_servers use the fanout exchange to talk to each other. 5. In your script, you run an executable called "qrsh". It knows how to talk to the servers, do what you want, and retrieve the data you want. example start script: (this does 4 servers on the same box) - echo "Starting server mrg22 ..." ./qrsh_server mrg22 ./qrsh_run 127.0.0.1 5813 & echo "Starting server mrg23 ..." ./qrsh_server mrg23 ./qrsh_run 127.0.0.1 5813 & echo "Starting server mrg24 ..." ./qrsh_server mrg24 ./qrsh_run 127.0.0.1 5813 & echo "Starting server mrg25 ..." ./qrsh_server mrg25 ./qrsh_run 127.0.0.1 5813 & echo "Issuing start command..." sleep 2 ./qrsh 127.0.0.1 5813 mrg22 start sleep 1 echo "Ready." # end of script. = Qrsh Syntax = qrsh host port server_name command_name arg* "host" and "port" specify the Qpid server to connect to. "server_name" can be anything you want. I always use the name of the box that the server is running on. "command_name" is the name that you choose to assign to the process you are running. Each process that you decide to name must have a unique name within this script. Or it could be a reserved command name, that Qsh interprets in a special way. Reserved command names are: exec exec_wait exited get "exec" means "interpret the rest of the command line as a command to be executed by the designated server. "exec_wait" means same as "exec", but wait for the command to terminate, and return its exit code. "exited" -- you provide 1 arg, which is an abstract process name. qrsh returns 1 if that process has exited, else 0. "get" -- you provide one arg which is a path. qrsh returns (by printing to stdout) the contents of that file. "arg*" is zero or more arguments. They are interpreted
Re: Building the ruby client on Mac OS X
On Mon, 2009-08-03 at 06:13 -0700, Rob Gabbard wrote: > FYI... I wanted to use the Ruby client library on Mac OS X (10.4) but had an > issue building the sasl Ruby extension included. The issue was the lack of > malloc.h in the stndard include paths on Mac OS X. But since malloc is > included in stdlib, an easy warkaround was to change the malloc.h include in > ext/sasl/sasl.c to... > > #if !defined(__APPLE__) > #include > #endif > > After doing so, the sasl library built and installed correctly and the Ruby > sample and tests ran fine, taking to a remote broker. I think this is a small bug in the original code: The POSIX/C location for malloc is stdlib.h, not malloc.h (which seems to be a GNU/BSD? location) so if there is already an #include then #include should not be needed on usual Unix platforms. Andrew > > -- > Rob Gabbard > Senior Computer Scientist > Adobe Systems Incorporated > - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-2019) Exclude lists are unable to exclude packages
Exclude lists are unable to exclude packages Key: QPID-2019 URL: https://issues.apache.org/jira/browse/QPID-2019 Project: Qpid Issue Type: Improvement Components: Build Tools Reporter: Martin Ritchie Fix For: 0.6 Summary: Currently there is no bulk exclude for a whole java package of tests. Normally this would not be required but the new logging tests for the Java broker cannot be run against the CPP broker. So the entire 'org.apache.qpid.server.logging' tests need excluded. For now simply using the full Class package will allow us to disable the logging tests like this: _exclusionList.contains(getClass().getPackage().getName() + ".*") However, we may wish to add more sophisticated glob matching in the future so the above pattern can exclude all sub packages. -- 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-2018) Clear queue doesn't clear acquired messages which is a little confusing if that's all there is.
Clear queue doesn't clear acquired messages which is a little confusing if that's all there is. --- Key: QPID-2018 URL: https://issues.apache.org/jira/browse/QPID-2018 Project: Qpid Issue Type: Bug Components: Java Management : JMX Console Affects Versions: 0.6 Reporter: Aidan Skinner Assignee: Robbie Gemmell Priority: Minor Fix For: 0.6 The clear queue button prompts but doesn't actually clear the queue. I suspect because all the messages have been acquired by consumers. This should probably display a better error message if there are acquired messages which can't be cleared. An int return of uncleared ones maybe? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: [jira] Created: (QPID-2017) Files for Async Store interface layer (NOTE, read carefully - license issues)
On Sat, 2009-08-01 at 08:05 +0100, James Mansion wrote: > Kim van der Riet (JIRA) wrote: > > They are encumbered with BDB, which is used to save the broker state. For > > this reason, these files are LGPL > Why are they encumbered with BDB? You aren't redistributing BDB are you? No. > And even if you deem that referencing symbols in BDB is somehow > 'redistribution' of > (part of) BDB, why does that make it LGPL? > > Surely it just requires: > > 'Redistributions in any form must be accompanied by information on > how to obtain complete source code for the DB software and any > accompanying software that uses the DB software.' > > (And that 's more like GPL, than LGPL) IANAL, you may be correct. However, this decision was made about 2 years ago out of an abundance of caution regarding non-apache-compatible licenses. The reason LGPL was selected was that it is suited for use with libraries (which this is - msgstore.so) which can be run against the apache-licensed qpidd. > I'm not sure how referencing BDB symbols can be redistributing BDB, > but I guess Sleepycat and Oracle have no interest in clarity on that. > > The symbols are discussed in books and documentation and used from code > that could be considered as the source of snippets used. APR has code that > can use BDB doesn't it? > > James Whatever the reasons, the bottom line is that this interface code is currently LGPL, and the process outlined in this JIRA is the one suggested by Apache legal to get it into the current Qpid source tree. Kim - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Building the ruby client on Mac OS X
FYI... I wanted to use the Ruby client library on Mac OS X (10.4) but had an issue building the sasl Ruby extension included. The issue was the lack of malloc.h in the stndard include paths on Mac OS X. But since malloc is included in stdlib, an easy warkaround was to change the malloc.h include in ext/sasl/sasl.c to... #if !defined(__APPLE__) #include #endif After doing so, the sasl library built and installed correctly and the Ruby sample and tests ran fine, taking to a remote broker. -- Rob Gabbard Senior Computer Scientist Adobe Systems Incorporated
