https://bz.apache.org/bugzilla/show_bug.cgi?id=63063
Bug ID: 63063
Summary: 8.5.37 does not longer start because of error in
catalina.sh start section with new redirect to
$catalina_out_command eval code code block
Product: Tomcat 8
Version: 8.5.x-trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: major
Priority: P2
Component: Catalina
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ----
In relation to ticket https://bz.apache.org/bugzilla/show_bug.cgi?id=53930
since tomcat 8.5.36 the catalina.sh start section was changed to handle the
stdout & stderr redirect into $CATALINA_OUT in another way.
But with 8.5.37 release I was not longer able to start the tomcat by using
systemd. On the other hand I was able to start it manually by calling
bin/startup.sh. This was strange....
At the end I hopyfully found the simple fault in catalina.sh start section.
During the rebuild of the eval .... code blocks in lines 470 ++ and 482 ++
there is a typo.
Line 479 and 489 contains both that code:
2\>\&1 \& echo \$! \>\"$catalina_pid_file\" \; \} $catalina_out_command "&"
but since the redirect "2\>\&1" finishes the command call, the next "\&" has to
be a:
1. "\;" to delimiter the follow up command "echo \$!"
2. or I belive it should be a double ampersand "\&\&" to combine both shell
commands
After I changed both lines into:
for case 1: 2\>\&1 \; echo \$! \>\"$catalina_pid_file\" \; \}
$catalina_out_command "&"
for case 2: 2\>\&1 \&\& echo \$! \>\"$catalina_pid_file\" \; \}
$catalina_out_command "&"
it works again for me with both variants.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
