trouble with stderr running tomcat5 as service via procrun

A

ajwerden

I've inherited a Tomcat application that makes explicit calls to
System.err.println to write to stderr, and has an external component
that looks for messages in stderr. Tomcat4 ran as a windows service.

The application was rehosted on Tomcat5 and runs as a windows service
via procrun / prunsvr (the executable Tomcat5.exe). Whilst the
application runs just fine, procrun is redirecting stderr to stdout.
Normally I wouldnt think this is a big deal, but the external
components that I do not control are explicitly looking in the stderr
file.

I'm running Tomcat 5.028. I downloaded the most recent Tomcat version
(5.59) and noticed that the procrun executable (tomcat5.exe) has
changed. I tried running Tomcat 5.028 under the procrun from 5.59;
service runs fine, but stderr still shows up in stdout.

Any suggestions?

/Andy
(e-mail address removed)
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
473,769
Messages
2,569,580
Members
45,054
Latest member
TrimKetoBoost

Latest Threads

Top