raw http: how to retrieve the message body

Thanks for the advice. I have set logging to enable_all on Engine Log Configuration in the Properties tab for the thread. This hasn’t changed anything however. The message body does not appear in the logging or in the SMAT.

This is my basic config.

this is the raw handler

This is dumpMsg.tcl, does continue on the $mh:

proc dumpMsg { args } {
keylget args MODE mode ;# Fetch mode

set dispList {} ;# Nothing to return

switch -exact — $mode {
start {
# Perform special init functions
# N.B.: there may or may not be a MSGID key in args
}

run {
# ‘run’ mode always has a MSGID; fetch and process it
keylget args MSGID mh
keylget args CONTEXT context

puts “message id: $mh”
set INmsg [msgget $mh]
#set INmsg1 [httpget $mh]
puts “message body: $INmsg”
#puts “message body: $INmsg1”
echo \n\n$context Dump:
msgdump $mh
echo \n\n

lappend dispList “CONTINUE $mh”
}

time {
# Timer-based processing
# N.B.: there may or may not be a MSGID key in args
}

shutdown {
# Doing some clean-up work
}
}

return $dispList
}

bounceRaw, relevant lines:

#lappend dispList “KILL $mh” : in original code
lappend dispList “CONTINUE $mh”

I changed to continue from kill. The interesting thing is that I routed the outbound message to a file thread and every time I send a message through, the file thread gets a message. However, there is nothing in the message as nothing is written to the file, except a new blank line, which indicates to me that a “message” is passing through the system. Still not seeing anything in SMAT.

Thanks very much for your help, I’ve managed to get this working. There were I think 3 changes required.

First, was changing KILL to CONTINUE, as above, in the bounceRaw tcl.

Second, in my raw handler, I changed the context path, from “/rawJSON” to simply “/”

Third, and I think this is a peculiarity of SoupUI 5.1.2, which I was using as a test harness, I needed to change the media. I was using application/json, then tried text/html and the multipart options. I stumbled across another media type by accident, not available in the drop down, “x-www-form-urlencoded”.

I now get the message logged in SMAT, either xml or JSON, and the message writes out to my test file thread.

Addendum: I’ve created a new thread from scratch based upon my trials and tribulations above and again used SoapUI to test it. The media defaulted to application/json without my noticing and the message passed through successfully. So I think now that the media type/setting was a red herring.