https://bz.apache.org/bugzilla/show_bug.cgi?id=64831
--- Comment #5 from Michael Osipov <[email protected]> --- (In reply to Felix Schumacher from comment #4) > The debug sampler has currently no knowledge of the keystore and is > therefore not my preferred sampler to extend :) but ... we could store the > information that is currently logged into a variable, which then would be > reported by the debug sampler. What do you think? OK, let's leave the debug sampler stupid. Hmm, while storing into a variable seems reasonable, it still requires to invoke a real sampler to have this kind of information. Sometimes I do invoke debug sampler to see JMeter internal information w/o any other sampler involved. Do you see a way to store this kind of information when the keystore is first loaded by JMeter? This would of course require the keystore to be static, means JMeter won't notice changes until re-reads it or restarts, but that's would be acceptable. > The information about the SAN can (and should) be enhanced. Thanks for the > OIDs. > > Could you explain, what you mean by comment 1)? I guess you mean this one: > log.debug("{}: {}", i++, alias); It will merly print a number and an alias. More context means: log.debug("certitifate at index {} with alias {}", i++, alias); Subsequent log messages could be indented to establish visual context. -- You are receiving this mail because: You are the assignee for the bug.
