D
dbeavon
Guest
Thanks for the tip Irfan, I tried some of the "current-request-info" properties like so: LOG-MANAGER:WRITE-MESSAGE(string(session:current-request-info:AdapterType)). LOG-MANAGER:WRITE-MESSAGE(session:current-request-info:ClientContextId). LOG-MANAGER:WRITE-MESSAGE(string(session:current-request-info:SessionId)). LOG-MANAGER:WRITE-MESSAGE(string(session:current-request-info:ThreadId)). LOG-MANAGER:WRITE-MESSAGE(string(session:current-request-info:AgentId)). LOG-MANAGER:WRITE-MESSAGE(session:current-request-info
rocedureName). LOG-MANAGER:WRITE-MESSAGE(session:current-request-info:RequestId). The results are promising for many properties: APSV MWphYQb9c0Gp+XP07QVT+Q 8 4 31800 app/Production/Maintenance/AppServer/BurdenAltDescMaintenance.p&BrowseFirstPage ? ... However the session:current-request-info:RequestId is always being displayed as "?". We only use the APSV transport. Perhaps that "RequestId" doesn't work for APSV? Is there another way to retrieve the current WebApp name (and, ultimately, the HTTP session ID that would be recognized by the tomcat-manager-REST-interface)?
Continue reading...
rocedureName). LOG-MANAGER:WRITE-MESSAGE(session:current-request-info:RequestId). The results are promising for many properties: APSV MWphYQb9c0Gp+XP07QVT+Q 8 4 31800 app/Production/Maintenance/AppServer/BurdenAltDescMaintenance.p&BrowseFirstPage ? ... However the session:current-request-info:RequestId is always being displayed as "?". We only use the APSV transport. Perhaps that "RequestId" doesn't work for APSV? Is there another way to retrieve the current WebApp name (and, ultimately, the HTTP session ID that would be recognized by the tomcat-manager-REST-interface)?Continue reading...