You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Mladen Turk (JIRA)" <ji...@apache.org> on 2010/02/11 18:30:31 UTC

[jira] Resolved: (DAEMON-16) [daemon] When changing UID in jsvc on fedora core 4, warning occurs: find_vma failed

     [ https://issues.apache.org/jira/browse/DAEMON-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mladen Turk resolved DAEMON-16.
-------------------------------

    Resolution: Won't Fix

There is workaround for that issue as explained with the case

> [daemon] When changing UID in jsvc on fedora core 4, warning occurs: find_vma failed
> ------------------------------------------------------------------------------------
>
>                 Key: DAEMON-16
>                 URL: https://issues.apache.org/jira/browse/DAEMON-16
>             Project: Commons Daemon
>          Issue Type: Bug
>         Environment: Operating System: Linux
> Platform: PC
>            Reporter: Brian Peter Thorsbro
>
> Greetings List.
> I have searched a lot for information about this Warning I am getting when I
> start up tomcat by using jsvc on my Fedora Core 4 platform, but I have not been
> able to find anything that helped me solve my problem. So now I am reporting it
> here.
> I am using the Tomcat5.sh script supplied in the native folder.
> I have tried 2 different scenarios:
> 1. running jsvc with "-user tomcat"
> 2. ommitting the -user option entirely (running it as root)
> In scenario 1 I get the warning:
> "Java HotSpot(TM) Server VM warning: Can't detect initial thread stack location
> - find_vma failed"   (same message if I use the Client VM).
> I do not get this warning in scenario 2.
> If I use the script "catalina.sh" as the user tomcat I can start up the
> webserver fine without warnings (though not on port 80 naturally).
> System is Fedora Cora 4
> Tomcat is the the apache-tomcat-5.5.15.tar.gz
> JDK/JRE is Suns jdk 1.5.0_06 for linux (rpm distribution)
> (note I dont have any other java distributions installed, so fedora RPM name
> clashes is not an issue)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.