Navjeet,
I don't understand why it does not work and it looks like it might be an
IPlanet bug ...
What happens is that Cactus saves each test result as an attribute in the
servlet context just after the test finished executing and then later on
queries it. What happens is that the call to save it in the context scope is
done (proven by the "Result holder semaphore is in place" log) and when the
doGetResults() method is called it doesn't find the object place in the
context scope ... this is weird.
I have no IPlanet on my machine to debug it further. The only thing I can
tell you is
1/ check if there is no know bug on the servlet context in IPlanet
2/ debug the cactus code
Is there anyone else using IPlanet 6 with Cactus on this mailing list ?
Thanks
-Vincent
----- Original Message -----
From: "Chabbewal, Navjeet" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, August 14, 2001 2:35 PM
Subject: RE: cactus and Iplanet App Server 6.0
> Here are the contents of the cactus_server.log file.
>
> 0 [Thread-43] DEBUG server.ServletTestRedirector - >doPost(...)
> 60 [Thread-43] DEBUG server.ServletTestRedirector - Default buffer size
> = 0
> 60 [Thread-43] DEBUG server.ServletTestRedirector - Service called =
> CALL_TEST
> 220 [Thread-43] DEBUG server.ServletTestRedirector - >doTest(...)
> 260 [Thread-43] DEBUG server.ServletTestRedirector - Result holder
> semaphore is in place
> 260 [Thread-43] DEBUG server.ServletTestRedirector - Class to call =
> org.apache.commons.cactus.sample.TestSampleServlet
> 260 [Thread-43] DEBUG server.ServletTestRedirector - Method to call =
> testPositiveNumber
> 260 [Thread-43] DEBUG server.ServletTestRedirector -
> >callTestMethod(...)
> 921 [Thread-43] DEBUG server.ServletTestRedirector - Result holder
> semaphore inactive (result set in holder)
> 921 [Thread-43] DEBUG server.ServletTestRedirector - <doTest
> 921 [Thread-43] DEBUG server.ServletTestRedirector - Sending magic
> keyword ...
> 921 [Thread-43] DEBUG server.ServletTestRedirector - <doPost
> 1092 [Thread-43] DEBUG server.ServletTestRedirector - >doPost(...)
> 1092 [Thread-43] DEBUG server.ServletTestRedirector - Default buffer
> size = 0
> 1092 [Thread-43] DEBUG server.ServletTestRedirector - Service called =
> GET_RESULTS
> 1092 [Thread-43] DEBUG server.ServletTestRedirector -
> >doGetResults(...)
> 1092 [Thread-43] DEBUG server.ServletTestRedirector - Try to read
> results from Holder ...
>
>
> --Navjeet
>
> -----Original Message-----
> From: Vincent Massol
> Sent: Wed 8/8/2001 10:58 AM
> To: [EMAIL PROTECTED]
> Cc:
> Subject: Re: cactus and Iplanet App Server 6.0
>
>
>
> Hi Navjeet,
>
> No it doesn't look like a classpath issue at all ... The null
> pointer
> exception at line 236 means that the result of the test could
> not be
> retrieved from a variable stored in the servlet context. The
> question is :
> why wasn't it put there ? It should have been.
>
> What version of Cactus are you using ?
> Could you send the server log file (file cactus_server.log) that
> is
> generated if you have the log4j jar in your server classpath
> (put the log4j
> jar in WEB-INF/lib). You can find the log4j jar in
> <cactusroot>/lib, it is
> delivered in the distribution.
>
> Thanks
> -Vincent
>
> ----- Original Message -----
> From: "Chabbewal, Navjeet" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>;
> <[EMAIL PROTECTED]>
> Sent: Tuesday, August 07, 2001 4:30 PM
> Subject: RE: cactus and Iplanet App Server 6.0
>
>
> > I checked again and these classes are there on clinet and
> server side.
> > If it helps here is the output in the java engine of the app
> server:
> >
> > [07/Aug/2001 10:57:33:9] error: SERVLET-put_nonserial: Putting
> > non-serializable
> > object when using NAS session
> > [07/Aug/2001 10:57:33:9] info:
> --------------------------------------
> > [07/Aug/2001 10:57:33:9] info: ServletTestRedirector: init
> > [07/Aug/2001 10:57:33:9] info:
> --------------------------------------
> > [07/Aug/2001 10:57:34:0] error: Exception:
> SERVLET-execution_failed:
> > Error in ex
> > ecuting servlet ServletTestRedirector:
> java.lang.NullPointerException
> > Exception Stack Trace:
> > java.lang.NullPointerException
> > at
> >
> org.apache.commons.cactus.server.ServletTestCaller.doGetResults(Servl
> > etTestCaller.java:236)
> > at
> >
> org.apache.commons.cactus.server.ServletTestRedirector.doPost(Servlet
> > TestRedirector.java:191)
> > at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:772)
> > at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
> > at
> >
> com.netscape.server.servlet.servletrunner.ServletInfo.service(Unknown
> > Source)
> > at
> >
> com.netscape.server.servlet.servletrunner.ServletRunner.execute(Unkno
> > wn Source)
> > at com.kivasoft.applogic.AppLogic.execute(Unknown
> Source)
> > at com.kivasoft.applogic.AppLogic.execute(Unknown
> Source)
> > at com.kivasoft.thread.ThreadBasic.run(Native Method)
> > at java.lang.Thread.run(Thread.java:479)
> >
> > Seems like the request does invoke proxy redirector on the
> server side.
> > Do you think it is a classpath issue ? Seems like it is
> related to
> > Iplanet does things ( not sure..)
> >
> >
> >
> > --Navjeet
> >
> >
> > -----Original Message-----
> > From: Vincent Massol
> > Sent: Tue 8/7/2001 9:28 AM
> > To: [EMAIL PROTECTED]
> > Cc:
> > Subject: Re: cactus and Iplanet App Server 6.0
> >
> >
> >
> > Navjeet,
> >
> > Can you verify that you have the following files in your web
> app
> > classpath
> > (i.e. either in WEB-INF/classes or in WEB-INF/lib) :
> > - junit classes
> > - cactus classes
> > - test classes
> > - classes under test
> >
> > And on the client side (the junit test runner JVM) :
> > - junit classes
> > - cactus classes
> > - test classes
> > - servlet API jar (not sure if it is needed actually ...)
> >
> > You can check
> > http://jakarta.apache.org/commons/cactus/installation.html
> > for details.
> >
> > Thanks
> > -Vincent
> >
> > ----- Original Message -----
> > From: "Chabbewal, Navjeet" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Tuesday, August 07, 2001 1:50 PM
> > Subject: RE: cactus and Iplanet App Server 6.0
> >
> >
> > > Vincent,
> > >
> > >
> > > I am still having problems as mentioned below. Any help will
> > be
> > > appreciated.
> > >
> > >
> > > I presumed that TestRunner is the servlet which can be used
> > > to run tests
> > > by providing classname parameter with appropriate test
> class
> > name.
> > > Anyhow I am getting the exact same results when I run the
> > test through
> > > junit.awtui.TestRunner.
> > >
> > > I do not have junit.jar in WEB-INF/lib but I do have the
> > > expanded junit
> > > classes under WEB-INF/classes ( i.e. junit/framework,
> > junit/extensions
> > > etc.. ) That should be ok.
> > >
> > >
> > > --Navjeet
> > >
> > >
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: Vincent Massol [ mailto:[EMAIL PROTECTED]]
> > > > > Sent: Friday, August 03, 2001 2:08 PM
> > > > > To: [EMAIL PROTECTED]
> > > > > Subject: Re: cactus and Iplanet App Server 6.0
> > > > >
> > > > >
> > > > > Hi,
> > > > >
> > > > > * What is TestRunner ? I usually run the tests by either
> > > > > starting the JUnit
> > > > > text runner or the awt/swing runner ones.
> > > > > * Can you verify that you have junit.jar in your
> > WEB-INF/lib
> > > > > directory ?
> > > > >
> > > > > Thanks
> > > > > -Vincent
> > > > >
> > > > >
> > >
> >
> >
>
>
