If a native library causes a segmentation fault, the complete vm will crash.
So with each native library that you are using you introduce possible stability degrations. The creation of segmentation faults is not the only risk. With each library (native or not) you use, you increase the risk to crash tomcat. The libraries might introduce application level errors that might stop tomcat from working, like memory leaks, file handle leaks, deadlocks, ...). If you can live with this risk depends on your requirements. In the end you always will have to test if your application is stable enough with this system. > -----Ursprüngliche Nachricht----- > Von: Sven Köhler [mailto:[EMAIL PROTECTED]] > Gesendet: Montag, 14. Oktober 2002 17:38 > An: [EMAIL PROTECTED] > Betreff: Tomcat and PHP-servlet? > > > hi, > > in the PHP-docs, a servlet is mentioned, that makes .php > pages runnable > again (somehow by loading PHP into the JavaVM). > > How stable can that be? > I worry aout the following: > PHP could internally produce a segmentation-fault. Does that also > crash the process(thread?) of the JavaVM? If yes, Tomcat would become > unstabe. > > Is anybody out there, that runs this "PHP-servlet" ??? > > > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
