Re: problem getting test results
Hi Paulo, In article <[EMAIL PROTECTED]>, Wed, 1 Mar 2006 14:47:18 + (GMT), Paulo R C Siqueira <[EMAIL PROTECTED]> wrote: gangrelbr1> I tried to run the test with junit.textui.TestRunner. [snip] gangrelbr1> This is the error on the client side: gangrelbr1> gangrelbr1> org.apache.cactus.util.ChainedRuntimeException: Failed to get the test results at [http://127.0.0.1:8080/myapp/ServletRedirectorSecure] Could you try ServletRedirector instead of ServletRedirectorSecure? I'm not sure that the authentication could be a cause, though. Regards, Kazuhito SUGURI - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: problem getting test results
Hi, This is the exception at the server side: 14:08:40,918 ERROR [AbstractWebTestCaller] Error getting test result. This could happen for example if you're using a load-balancer. Please disable it before running Cactus tests. 14:08:40,919 ERROR [[ServletRedirectorSecure]] Servlet.service() for servlet ServletRedirectorSecure threw exception javax.servlet.ServletException: Error getting test result. This could happen for example if you're using a load-balancer. Please disable it before running Cactus tests. at org.apache.cactus.internal.server.AbstractWebTestCaller.doGetResults(AbstractWebTestCaller.java:176) at org.apache.cactus.internal.server.AbstractWebTestController.handleRequest_aroundBody0(AbstractWebTestController.java:98) at org.apache.cactus.internal.server.AbstractWebTestController.handleRequest_aroundBody1$advice(AbstractWebTestController.java:224) at org.apache.cactus.internal.server.AbstractWebTestController.handleRequest(AbstractWebTestController.java) at org.apache.cactus.server.ServletTestRedirector.doPost_aroundBody2(ServletTestRedirector.java:101) at org.apache.cactus.server.ServletTestRedirector.doPost_aroundBody3$advice(ServletTestRedirector.java:224) at org.apache.cactus.server.ServletTestRedirector.doPost(ServletTestRedirector.java) at org.apache.cactus.server.ServletTestRedirector.doGet_aroundBody0(ServletTestRedirector.java:72) at org.apache.cactus.server.ServletTestRedirector.doGet_aroundBody1$advice(ServletTestRedirector.java:224) at org.apache.cactus.server.ServletTestRedirector.doGet(ServletTestRedirector.java) at javax.servlet.http.HttpServlet.service(HttpServlet.java:697) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:159) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:482) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) at java.lang.Thread.run(Thread.java:595) thanks :) Kenney Westerhof <[EMAIL PROTECTED]> escreveu: On Wed, 1 Mar 2006, Paulo R C Siqueira wrote: Do you have the log for the server side? The internal server error there should give you more information about what went wrong on the server (a NullPointerException usually gives a status 500...) -- Kenney > Hi Kazuhito, > > Thanks again for the answer! :) > > I tried to run the test with junit.textui.TestRunner. The result was exactly > the same... That exception was raised on the server side and an "Internal > Server Error" on the client side. > > This is the error on the client side: > > org.apache.cactus.util.ChainedRuntimeException: Failed to get the test > results at [http://127.0.0.1:8080/myapp/ServletRedirectorSecure] > at > org.apache.cactus.internal.client.connector.http.DefaultHttpClient.doTest_aroundBody0(DefaultHttpClient.java:92) > at > org.apache.cactus.internal.client.connector.http.DefaultHttpClient.doTest_aroundBody1$advice(DefaultHttpClient.java:306) > at > org.apache.cactus.internal.client.connector.http.DefaultHttpClient.doTest(DefaultHttpClient.java) > at > org.apache.cactus.internal.client.connector.http.HttpProtocolHandler.runWebTest(HttpProtocolHandler.java:159) > at
Re: problem getting test results
On Wed, 1 Mar 2006, Paulo R C Siqueira wrote: Do you have the log for the server side? The internal server error there should give you more information about what went wrong on the server (a NullPointerException usually gives a status 500...) -- Kenney > Hi Kazuhito, > > Thanks again for the answer! :) > > I tried to run the test with junit.textui.TestRunner. The result was exactly > the same... That exception was raised on the server side and an "Internal > Server Error" on the client side. > > This is the error on the client side: > > org.apache.cactus.util.ChainedRuntimeException: Failed to get the test > results at [http://127.0.0.1:8080/myapp/ServletRedirectorSecure] > at > org.apache.cactus.internal.client.connector.http.DefaultHttpClient.doTest_aroundBody0(DefaultHttpClient.java:92) > at > org.apache.cactus.internal.client.connector.http.DefaultHttpClient.doTest_aroundBody1$advice(DefaultHttpClient.java:306) > at > org.apache.cactus.internal.client.connector.http.DefaultHttpClient.doTest(DefaultHttpClient.java) > at > org.apache.cactus.internal.client.connector.http.HttpProtocolHandler.runWebTest(HttpProtocolHandler.java:159) > at > org.apache.cactus.internal.client.connector.http.HttpProtocolHandler.runTest_aroundBody0(HttpProtocolHandler.java:80) > at > org.apache.cactus.internal.client.connector.http.HttpProtocolHandler.runTest_aroundBody1$advice(HttpProtocolHandler.java:306) > at > org.apache.cactus.internal.client.connector.http.HttpProtocolHandler.runTest(HttpProtocolHandler.java) > at > org.apache.cactus.internal.client.ClientTestCaseCaller.runTest(ClientTestCaseCaller.java:144) > at > org.apache.cactus.internal.AbstractCactusTestCase.runBareClient(AbstractCactusTestCase.java:215) > at > org.apache.cactus.internal.AbstractCactusTestCase.runBare(AbstractCactusTestCase.java:133) > org.apache.cactus.internal.client.ParsingException: Not a valid response [500 > Internal Server Error] > at > org.apache.cactus.internal.client.connector.http.DefaultHttpClient.callGetResult(DefaultHttpClient.java:211) > at > org.apache.cactus.internal.client.connector.http.DefaultHttpClient.doTest_aroundBody0(DefaultHttpClient.java:87) > at > org.apache.cactus.internal.client.connector.http.DefaultHttpClient.doTest_aroundBody1$advice(DefaultHttpClient.java:306) > at > org.apache.cactus.internal.client.connector.http.DefaultHttpClient.doTest(DefaultHttpClient.java) > at > org.apache.cactus.internal.client.connector.http.HttpProtocolHandler.runWebTest(HttpProtocolHandler.java:159) > at > org.apache.cactus.internal.client.connector.http.HttpProtocolHandler.runTest_aroundBody0(HttpProtocolHandler.java:80) > at > org.apache.cactus.internal.client.connector.http.HttpProtocolHandler.runTest_aroundBody1$advice(HttpProtocolHandler.java:306) > at > org.apache.cactus.internal.client.connector.http.HttpProtocolHandler.runTest(HttpProtocolHandler.java) > at > org.apache.cactus.internal.client.ClientTestCaseCaller.runTest(ClientTestCaseCaller.java:144) > at > org.apache.cactus.internal.AbstractCactusTestCase.runBareClient(AbstractCactusTestCase.java:215) > at > org.apache.cactus.internal.AbstractCactusTestCase.runBare(AbstractCactusTestCase.java:133) > > My Environment: > Linux kernel 2.4.26 > Sun jdk 1.5.0_05_b5 > JBoss-4.0.3 > Cactus-1.7.1 > > Any more ideas? :S > > Thanks again! > > You might try run test without NetBeans to know whether Cactus works > with your target container (JBoss-4.0.3). > I had tried following steps last weekend and it worked fine: > (1) create cactified-war with a simple test > (2) start JBoss > (3) deploy the cactified-war file to JBoss manually > (4) run test by using junit.textui.TestRunner: > java junit.textui.TestRunner > > My environment is as follows: > Linux kernel 2.6.8 > Sun jdk 1.5.0_06 > JBoss-4.0.3SP1 > Cactus-1.7.1 > > Once you found a working configuration, you can use that for other tests, > and can narrow the problem you have encountered. > > Regards, > > Kazuhito SUGURI > > > > _ > Paulo "gangrel-br" R C Siqueira > Sun Certified Programmer for the Java 2 Platform 1.4 > Mogi das Cruzes - SP - Brazil > Contact: (11) 8149-5046 > > - > Yahoo! Search > D� uma espiadinha e saiba tudo sobre o Big Brother Brasil. -- Kenney Westerhof http://www.neonics.com GPG public key: http://www.gods.nl/~forge/kenneyw.key - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: problem getting test results
Hi Kazuhito, Thanks again for the answer! :) I tried to run the test with junit.textui.TestRunner. The result was exactly the same... That exception was raised on the server side and an "Internal Server Error" on the client side. This is the error on the client side: org.apache.cactus.util.ChainedRuntimeException: Failed to get the test results at [http://127.0.0.1:8080/myapp/ServletRedirectorSecure] at org.apache.cactus.internal.client.connector.http.DefaultHttpClient.doTest_aroundBody0(DefaultHttpClient.java:92) at org.apache.cactus.internal.client.connector.http.DefaultHttpClient.doTest_aroundBody1$advice(DefaultHttpClient.java:306) at org.apache.cactus.internal.client.connector.http.DefaultHttpClient.doTest(DefaultHttpClient.java) at org.apache.cactus.internal.client.connector.http.HttpProtocolHandler.runWebTest(HttpProtocolHandler.java:159) at org.apache.cactus.internal.client.connector.http.HttpProtocolHandler.runTest_aroundBody0(HttpProtocolHandler.java:80) at org.apache.cactus.internal.client.connector.http.HttpProtocolHandler.runTest_aroundBody1$advice(HttpProtocolHandler.java:306) at org.apache.cactus.internal.client.connector.http.HttpProtocolHandler.runTest(HttpProtocolHandler.java) at org.apache.cactus.internal.client.ClientTestCaseCaller.runTest(ClientTestCaseCaller.java:144) at org.apache.cactus.internal.AbstractCactusTestCase.runBareClient(AbstractCactusTestCase.java:215) at org.apache.cactus.internal.AbstractCactusTestCase.runBare(AbstractCactusTestCase.java:133) org.apache.cactus.internal.client.ParsingException: Not a valid response [500 Internal Server Error] at org.apache.cactus.internal.client.connector.http.DefaultHttpClient.callGetResult(DefaultHttpClient.java:211) at org.apache.cactus.internal.client.connector.http.DefaultHttpClient.doTest_aroundBody0(DefaultHttpClient.java:87) at org.apache.cactus.internal.client.connector.http.DefaultHttpClient.doTest_aroundBody1$advice(DefaultHttpClient.java:306) at org.apache.cactus.internal.client.connector.http.DefaultHttpClient.doTest(DefaultHttpClient.java) at org.apache.cactus.internal.client.connector.http.HttpProtocolHandler.runWebTest(HttpProtocolHandler.java:159) at org.apache.cactus.internal.client.connector.http.HttpProtocolHandler.runTest_aroundBody0(HttpProtocolHandler.java:80) at org.apache.cactus.internal.client.connector.http.HttpProtocolHandler.runTest_aroundBody1$advice(HttpProtocolHandler.java:306) at org.apache.cactus.internal.client.connector.http.HttpProtocolHandler.runTest(HttpProtocolHandler.java) at org.apache.cactus.internal.client.ClientTestCaseCaller.runTest(ClientTestCaseCaller.java:144) at org.apache.cactus.internal.AbstractCactusTestCase.runBareClient(AbstractCactusTestCase.java:215) at org.apache.cactus.internal.AbstractCactusTestCase.runBare(AbstractCactusTestCase.java:133) My Environment: Linux kernel 2.4.26 Sun jdk 1.5.0_05_b5 JBoss-4.0.3 Cactus-1.7.1 Any more ideas? :S Thanks again! You might try run test without NetBeans to know whether Cactus works with your target container (JBoss-4.0.3). I had tried following steps last weekend and it worked fine: (1) create cactified-war with a simple test (2) start JBoss (3) deploy the cactified-war file to JBoss manually (4) run test by using junit.textui.TestRunner: java junit.textui.TestRunner My environment is as follows: Linux kernel 2.6.8 Sun jdk 1.5.0_06 JBoss-4.0.3SP1 Cactus-1.7.1 Once you found a working configuration, you can use that for other tests, and can narrow the problem you have encountered. Regards, Kazuhito SUGURI _ Paulo "gangrel-br" R C Siqueira Sun Certified Programmer for the Java 2 Platform 1.4 Mogi das Cruzes - SP - Brazil Contact: (11) 8149-5046 - Yahoo! Search Dê uma espiadinha e saiba tudo sobre o Big Brother Brasil.
Re: Is Cactus thread safe?
1. This shouldn't be a problem since I'm using Ant to run Cactus and with Ant I can thread the call. 2. This part I have working with my own stuff and would be taken care of on all remote machines before running the multi-threaded cactus calls. Thanks for the advice, Shay Kazuhito SUGURI wrote: Hi Shay, In article <[EMAIL PROTECTED]>, Tue, 28 Feb 2006 17:22:22 -0600, Shay Thompson <[EMAIL PROTECTED]> wrote: sthompso> I need to test multiple remote machines, from a single main machine, sthompso> using Cactus. I'm wondering if Cactus is thread safe for doing sthompso> something like this? I'd obviously have to have it run off of separate sthompso> ear files, 1 for each remote machine, but even then will it work? I think it's possible. Some possible constraints for the use-case I can imagine: 1. exclusive JVM is required for each cactified application under test since client-side of Cactus set the contextURL as a System property. So, you have to invoke multiple JVM processes each of which runs Cactus for one remote machine, if you need to test remote machines simultaneously. 2. Cactus does not have a capability of remote deployment, yet. So, you have to deploy cactified applications to remote machines before you run tests. Hope this helps, Kazuhito SUGURI - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- ... hey, it works on my machine. Shay Thompson - Lead Computer Scientist Adobe Systems, Inc. - Titan Core QE Voice: x34728 or 612.251.5415 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
