Mark, The app deploys, I can hit it from a browser.
http://beach-breaker:7001/testconsole/ServletRedirector?Cactus_Service=RUN_T EST I don't see any output, just a blank web page. http://beach-breaker:7001/testconsole Brings up the application just fine. -----Original Message----- From: Mark Lybarger [mailto:[EMAIL PROTECTED] Sent: Friday, June 25, 2004 11:58 AM To: Cactus Users List Subject: RE: Cactus + weblogic 81 Bret, Have you tried taking this step by stem? First does the server startup command, start the server successfully with the cactus components deployed? > -----Original Message----- > From: Bret Kumler [mailto:[EMAIL PROTECTED] > Sent: Friday, June 25, 2004 2:44 PM > To: 'Cactus Users List' > Subject: RE: Cactus + weblogic 81 > > > According to > http://jakarta.apache.org/cactus/integration/ant/task_cactus.html > > If you put > > <!-- Configure the cactus task for logging --> > <cactusproperty server="false" > propertiesFile="${target.dir}/logging_client.properties"/> > <cactusproperty server="true" > propertiesFile="${target.dir}/logging_server.properties"/> > > this will enabled logging. I tried it, but it didn't work. > Is there a way > I can see if it loaded these files? sorry, i've never enabled logging for cactus. can't help on that one. > > " is localhost defined for you? does weblogic answer request > on localhost? > i think cactus is hardwired to use localhost for the url it > tries to hit, > but maybe i'm mistaken." > > I set in the config.xml the Server ListenAddress="machine-name", so > localhost doesn't respond. > > I thought cactus.properties is suppose to set the URL cactus > would use to > make a request. again, i've not used a cactus.properties file and have always used localhost. worked out ok for me. Looking into the CactusTask.java source code, it does seem that localhost is hardcoded: if(containers[i].isEnabled()) { containers[i].init(); log("-----------------------------------------------------------------", 2); log("Running tests against " + containers[i].getName(), 2); log("-----------------------------------------------------------------", 2); contextUrl.setValue("http://localhost:"; + containers[i].getPort() + "/" + thisDeployable.getTestContext()); executeInContainer(containers[i], thisDeployable); } and even in the provate executeInContainer method it's using localhost: URL url = new URL("http", "localhost", theContainer.getPort(), "/" + theFile.getTestContext() + theFile.getServletRedirectorMapping() + "?Cactus_Service=RUN_TEST"); > > -----Original Message----- > From: Mark Lybarger [mailto:[EMAIL PROTECTED] > Sent: Friday, June 25, 2004 10:55 AM > To: Cactus Users List > Subject: RE: Cactus + weblogic 81 > > Bret, > > If you're still seeing the log4j errors, you might try adding: > <sysproperty > key="org.apache.commons.logging.LogFactory" > value="org.apache.commons.logging.impl.LogFactoryImpl"/> > to your server startup command. I believe Weblogic provides > a "feature" > that overrides the log4j config you might have. i had lots of > log4j issues > with weblogic 8.1 getting to run cactus tests. i had to also > put an empty > commons-logging.properties file in my classpath that helped > to override > weblogic's settings. > > is localhost defined for you? does weblogic answer request > on localhost? i > think cactus is hardwired to use localhost for the url it > tries to hit, but > maybe i'm mistaken. > > good luck! > > > > -----Original Message----- > > From: Bret Kumler [mailto:[EMAIL PROTECTED] > > Sent: Friday, June 25, 2004 12:18 PM > > To: 'Cactus Users List' > > Subject: RE: Cactus + weblogic 81 > > > > > > Vincent, > > > > I noticed when I ran ant -debug test > > When the server was starting it was trying to connect to the > > correct url, > > but as soon as it went to the target to execute the tests, > > the url changed. > > > > The only difference is machine-name was beach-breaker, now > > its localhost. > > > > For some reason it cannot connect to localhost.. > > > > -----Original Message----- > > From: Vincent Massol [mailto:[EMAIL PROTECTED] > > Sent: Friday, June 25, 2004 12:53 AM > > To: 'Cactus Users List' > > Subject: RE: Cactus + weblogic 81 > > > > Hi Bret, > > > > > -----Original Message----- > > > From: Bret Kumler [mailto:[EMAIL PROTECTED] > > > Sent: 25 June 2004 01:51 > > > To: 'Cactus Users List' > > > Subject: Cactus + weblogic 81 > > > > > > I'm having a problem with the tests not executing. > > > > [snip] > > > > > BUILD FAILED > > > file:C:/misc/builds/cactus/build.xml:604: Failed to start the > > container > > > after mo > > > re than [180000] ms. Trying to connect to the > > > [http://localhost:7001/prismconsol > > > e/ServletRedirector?Cactus_Service=RUN_TEST] test URL > yielded a [-1] > > error > > > code. > > > Please run in debug mode for more details about the error. > > > > Can you please turn on Cactus logging and check the server > > log file? If > > you look hard you'll see the exact error returned by the > > container. That > > will give you the reason of the error. You may also want to > check the > > weblogic log file itself (located in your target dir). > > > > [snip] > > > > Thanks > > -Vincent > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
