#254 #include.debug causes eval: 1: Found: not found

Jerry Mindek

Within wrapper.conf, if the following is uncommented:

--- wrapper.conf snippit ---
# Include file problems can be debugged by removing the first '#'
# from the following line:
--- end ---

Then when I execute
./tomcat start
./tomcat stop
./tomcat status

I do not get the expected confirmation messages from the scripts, but instead I get the following message:
eval: 1: Found: not found

If the line mentioned above is commented, then I get the correct output.

My system is:
Linux 2.6.31-22-server #61-Ubuntu SMP Wed Jul 28 02:58:50 UTC 2010 x86_64 GNU/Linux
Java Service Wrapper Professional Edition 64-bit 3.5.6

Please let me know if you need more information.


  • Jerry,
    I'm sorry for any inconveniences this might have caused you.

    The problem you are describing here, should have already been fixed in 3.5.7:
    - Fix a problem where include file problems could cause the shell script to have errors due to invalid translated output from the Wrapper.

    The cause of the problem is that the script uses some localization logic. For this purpose the script is doing a sub-call to the wrapper binary, passing over the string to be translated and reading the output. And in case the translated string contained a ($VAR)-like variable it had to expand the value of the variable back using eval. However, when the #include.debug was enabled, this actually prepends the debug output to the reply. Which caused the problem you were seeing when calling eval on that reply...

    Could you please give a try to this version and confirm the problem has been resolved for you.

    You can find 3.5.7 on our download page:


    • status: open --> closed-fixed
    • assigned_to: Christian Mueller
    • milestone: --> v3.5.9