How to view Tomcat log in Psi Probe

1,122 views
Skip to first unread message

Lyle Frost

unread,
Jan 13, 2017, 6:39:03 PM1/13/17
to psi-probe-discuss
I am using Psi Probe (latest from master) with Tomcat 8.0.  I need to expose the Tomcat log file catalina.out in Psi Probe as described in https://github.com/psi-probe/psi-probe/wiki/Adding-Additional-Loggers, but spring-probe-resources.xml no longer exists in Psi Probe.

What is the current procedure to expose catalina.out in Psi Probe?

Thanks.

Jeremy Landis

unread,
Jan 13, 2017, 7:30:51 PM1/13/17
to psi-probe-discuss
Assuming you build off master, in the core module package 'psiprobe' go into ProbeConfig class and find the standard out bean which replaced the xml and simply add what you need. Then build and you will be good to go. Extra points if you address the TODO there and submit back to the community.

Smithfield W

unread,
Aug 7, 2017, 12:25:52 AM8/7/17
to psi-probe-discuss
Hi, similar issue on my side, I'm trying to force tomcat version but can't locate 'spring-probe-resources.xml' (https://github.com/psi-probe/psi-probe/wiki/Troubleshooting#error-on-first-request) I can explode probe.war (something like 
jar xvf probe.war WEB-INF/spring-probe-resources.xml) but past that point I'm clueless. Where and when should I look for a 'psiprobe' package, if still the correct approach. 
Any help appreciated. (Tomcat 8.5, hidden version in ServerInfo.properties), psi probe fails after login without any stacktrace, can't read anything relevant (to paste here) in probe.log)

Jeremy Landis

unread,
Aug 14, 2017, 10:06:42 PM8/14/17
to psi-probe-discuss

The entire project is now spring annotation based.  As a result, without extending spring out further to allow for property based configuration on some of the pieces such as logging and forcing tomcat version, it would require you to go into the source code and make a change.  Everything you need is under the main source package (psi-probe\core\src\main\java\psiprobe).  There you have access to ProbeConfig, ProbeInitializer, ProbeSecurityConfig, and ProbeServlet.  These entirely replaced the xml configuration.  Extending this out to allow proper overriding like you have pointed out is the primary reason releases stopped at the moment.  By all means, I'm open for pull request help on getting this done.  I have a few starts locally on the code needed for logging but haven't tried to fully advance anything else.  Any help is much appreciated!
Reply all
Reply to author
Forward
0 new messages