I didn't mention that I am running redhat 7.3 with java version 1.4.2_03. Now you know.
My findings do not jive with Zoran's findings. I can run both of the execs mentioned before in the tcl interpreter. The tcl interpreter is the one that compiles with aolserver and it is verrsion 8.4. Since I can't run [exec /bin/bash -c "/opt/myscript"] when nsjk2 is active and I can when nsjk2 is inactive I am lead to believe this problem is nsjk2 related. 1. [exec /bin/bash -c "ls -al"] 2. [exec /bin/bash -c "/opt/myscript"] Number 1 works even when nsjk2 is active. Number 2 only works when nsjk2 is inactive. I'm not sure what is going on behind the scenes here. Number one runs /bin/ls and 2 is a shell script. -Nate > I didn't mention that I was running on solaris 2.8 - based on Zoran's > findings, that could be the discriminator. What specific OS version are > you using and what JDK version? > > -Elizabeth > > Nathaniel H wrote on 6/8/04, 7:02 PM: > > > Commenting out nsjk2 in the config turns off nsjk2. I can exec after > > that. Looks like the jvm (or something else?) is catching SIGCHLD > > > > I've got > > Tomcat 4.1.29 > > AOLserver 4.0.1 > > nsjk2 1.3 > > > > I'll have to try 4.0.3 next. > > > > -Nate > > > > > > > I'm not sure its explained by just by virtue of the jvm running. I > have > > > an out-of-the-box 4.0.3 running nsjk2 v1.3 with Tomcat 4.1.27 and am > > > able to successfully exec both commands below (I ran them from the > > > control port) When I get a chance I will try and run a test with > 4.0.1 > > > and see if it behaves differently. > > > > > > -Elizabeth > > > > > > > > > Barry Books wrote on 6/8/04, 3:10 PM: > > > > > > > I have not tracked it specifically to the Oracle libs but that's > my > > > > best guess. I'm not running the nsjk2 module. Currently I got > around > > > > the problem by building the TCL Posix signal routines and > > reseting the > > > > signal. I think I've other discussion about the jvm catching > > SIGCHLD. > > > > > > > > > > > > On Tuesday, June 08, 2004, at 12:14PM, Dossy <[EMAIL PROTECTED]> > > > wrote: > > > > > > > > >On 2004.06.08, Nathaniel H <[EMAIL PROTECTED]> wrote: > > > > >> AOlserver 4.0.0 to AOlserver 4.0.1 introduces an exec > > problem. On > > > > 4.0.0 I > > > > >> can run both: > > > > >> > > > > >> 1. [exec /bin/bash -c "ls -al"] > > > > >> 2. [exec /bin/bash -c "/opt/myscript"] > > > > >> > > > > >> But on AOLserver 4.0.1 (with nsjk2) number 2. fails with this > > error. > > > > >> > > > > >> error waiting for process to exit: child process lost (is > SIGCHLD > > > > ignored > > > > >> or trapped?) > > > > >> while executing > > > > >> > > > > >> You should also know that, thanks to Elizabeth nsjk2, I am > > running > > > > nsjk2 > > > > >> on the problem 4.0.1 version. > > > > > > > > > >This sounds exactly like the problem that Barry Books reported > > earlier > > > > >on this list about nsora and exec. The newer Oracle client > library > > > > >apparently either installs its own SIGCHLD signal handler, or > > throws > > > > >SIGCHLD itself. This interferes with Tcl's SIGCHLD handler, > > therefore > > > > >when Tcl's [exec] executes something, it wants to be able to > > catch the > > > > >SIGCHLD of the child process when it dies. Unfortunately, the > > signal > > > > >gets handled elsewhere, so Tcl doesn't see it, and thus [exec] > > > complains > > > > >about it. > > > > > > > > > >I'm guessing that nsjk2 or the JVM, too, installs a SIGCHLD > handler > > > > >replacing Tcl's handler. > > > > > > > > > >I don't know enough about nsjk2 or the various JVMs to know the > > answer > > > > >to this. > > > > > > > > > >-- Dossy > > > > > > > > > >-- > > > > >Dossy Shiobara mail: [EMAIL PROTECTED] > > > > >Panoptic Computer Network web: > http://www.panoptic.com/ > > > > > "He realized the fastest way to change is to laugh at your own > > > > > folly -- then you can let go and quickly move on." (p. 70) > > > > > > > > > > > > > > >-- > > > > >AOLserver - http://www.aolserver.com/ > > > > > > > > > >To Remove yourself from this list, simply send an email to > > > > <[EMAIL PROTECTED]> with the > > > > >body of "SIGNOFF AOLSERVER" in the email message. You can leave > the > > > > Subject: field of your email blank. > > > > > > > > > > > > > > > > > > > > > > -- > > > > AOLserver - http://www.aolserver.com/ > > > > > > > > To Remove yourself from this list, simply send an email to > > > > <[EMAIL PROTECTED]> with the > > > > body of "SIGNOFF AOLSERVER" in the email message. You can leave > the > > > > Subject: field of your email blank. > > > > > > > > > -- > > > AOLserver - http://www.aolserver.com/ > > > > > > To Remove yourself from this list, simply send an email to > > > <[EMAIL PROTECTED]> with the > > > body of "SIGNOFF AOLSERVER" in the email message. You can leave the > > > Subject: field of your email blank. > > > > > > > > > -- > > AOLserver - http://www.aolserver.com/ > > > > To Remove yourself from this list, simply send an email to > > <[EMAIL PROTECTED]> with the > > body of "SIGNOFF AOLSERVER" in the email message. You can leave the > > Subject: field of your email blank. > > > -- > AOLserver - http://www.aolserver.com/ > > To Remove yourself from this list, simply send an email to > <[EMAIL PROTECTED]> with the > body of "SIGNOFF AOLSERVER" in the email message. You can leave the > Subject: field of your email blank. > -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
