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

Reply via email to