You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cactus-user@jakarta.apache.org by Chris Huisman <ch...@taylor.com> on 2004/08/05 00:32:49 UTC
cactus.properties
Hello,
I'm attempting to use the Junit in action book example to do ejb
integration testing via cactus . Using the sample build-cactus.xml file
(modified of course) I get the following error:
[cactus] Missing Cactus property [cactus.contextURL]
[cactus] org.apache.cactus.util.ChainedRuntimeException: Missing
Cactus property [cactus.contextURL]
were am I supposed to specify cactus properties, and what is the
cactus.contextURL?
Thank you,
Chris.
Re: cactus.properties
Posted by Chris Huisman <ch...@taylor.com>.
Thanks,
I refactored my ant build script and it's working now.
c.
Vincent Massol wrote:
>Chris,
>
>I can see 2 ways of helping you:
>
>1/ You try with the exact sample from JUnit in Action. It should work OOB.
>Then you modify slowly to reach the state you wish.
>
>Or
>
>2/ You show us your build script and your test.
>
>What you're saying is true. If you're using the Ant integration you don't
>need to set the cactus.contextURL property (it is set automatically by the
><cactus> Ant task).
>
>-Vincent
>
>
>
>>-----Original Message-----
>>From: Chris Huisman [mailto:chuisman@taylor.com]
>>Sent: jeudi 5 août 2004 00:43
>>To: Cactus Users List
>>Subject: Re: cactus.properties
>>
>>So I did some more digging and found a similar set of posts here:
>>http://www.mail-archive.com/cactus-user@jakarta.apache.org/msg04457.html
>>
>>It sasy that if you are using ant integration you don't have to set this
>>property. I'm using ant, and still getting this error.
>>c.
>>
>>Chris Huisman wrote:
>>
>>
>>
>>>Hello,
>>>
>>>I'm attempting to use the Junit in action book example to do ejb
>>>integration testing via cactus . Using the sample build-cactus.xml
>>>file (modified of course) I get the following error:
>>>
>>>[cactus] Missing Cactus property [cactus.contextURL]
>>> [cactus] org.apache.cactus.util.ChainedRuntimeException: Missing
>>>Cactus property [cactus.contextURL]
>>>
>>>were am I supposed to specify cactus properties, and what is the
>>>cactus.contextURL?
>>>
>>>Thank you,
>>>
>>>Chris.
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org
>>>For additional commands, e-mail: cactus-user-help@jakarta.apache.org
>>>
>>>
>>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: cactus-user-help@jakarta.apache.org
>>
>>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: cactus-user-help@jakarta.apache.org
>
>
>
RE: RE: cactus task and container contextUrl
Posted by Vincent Massol <vm...@pivolis.com>.
> -----Original Message-----
> From: Maxim V. Gordienko [mailto:maxim@dgap.mipt.ru]
> Sent: lundi 9 août 2004 12:00
> To: Cactus Users List
> Subject: Re: RE: cactus task and container contextUrl
>
> Vincent Massol цитата:
>
> > You mean the JNDI port? It is also configurable using the "jndiPort"
> > attribute.
>
> Yes, and Jndi port too. But I think to support all possible configuration
> parameters for all supported containers is not a Cactus project task.
> After
> all <generic> container helps when some container specific configuration
> is
> required.
True... Maybe it's a CCI (http://tinyurl.com/423jk) project task... :-)
>
> > From what I gather, your need is simply to pass the host name instead of
> it
> > being hardcoded to localhost.
> >
> > Could you please add a JIRA issue to add support for adding a host name
> > attribute to the <cactus> task?
>
> Yes! That would be great! Jira issue is submited.
>
> Thanks a lot, for replies!
Thanks
-Vincent
Re: RE: cactus task and container contextUrl
Posted by "Maxim V. Gordienko" <ma...@dgap.mipt.ru>.
Vincent Massol цитата:
> You mean the JNDI port? It is also configurable using the "jndiPort"
> attribute.
Yes, and Jndi port too. But I think to support all possible configuration
parameters for all supported containers is not a Cactus project task. After
all <generic> container helps when some container specific configuration is
required.
> From what I gather, your need is simply to pass the host name instead of it
> being hardcoded to localhost.
>
> Could you please add a JIRA issue to add support for adding a host name
> attribute to the <cactus> task?
Yes! That would be great! Jira issue is submited.
Thanks a lot, for replies!
RE: cactus task and container contextUrl
Posted by Vincent Massol <vm...@pivolis.com>.
> -----Original Message-----
> From: Maxim V. Gordienko [mailto:maxim@dgap.mipt.ru]
> Sent: lundi 9 août 2004 09:19
> To: Cactus Users List
> Subject: Re: cactus task and container contextUrl
>
> Hello, Vincent !
>
> Thanks for reply!
>
> By "fine-grained startup configuration" I mean passing all(or maybe only
> "major") configuration parameters to container. In case of JBoss it would
> be
> nice to see
> all parameters that available for `run.bat --help`... it just for
> convinience, but who knows... it might be useful
> Yes it's true, port and servlet context (and more in 1.7 version) are
> configurable via <jboss3x> element, but what about host binding address?
You mean the JNDI port? It is also configurable using the "jndiPort"
attribute.
>
> In my case all quite simple, I have multi interface host, and want to run
> several JBosses at the time (test host, with several developers testing
> something).
> The simpliest solution is too up number of dummy interfaces (luck linux
> allows that)
> and run each container on individual interface. I can start container from
> cactus tast to run that way, BUT cactus task queries 'localhost' to run
> tests, not custom address container listens. and, as result, tests are not
> run.
>
> Hope i clarified why custom contextUrl is necessary.
Re: cactus task and container contextUrl
Posted by "Maxim V. Gordienko" <ma...@dgap.mipt.ru>.
Hello, Vincent !
Thanks for reply!
By "fine-grained startup configuration" I mean passing all(or maybe only
"major") configuration parameters to container. In case of JBoss it would be
nice to see
all parameters that available for `run.bat --help`... it just for
convinience, but who knows... it might be useful
Yes it's true, port and servlet context (and more in 1.7 version) are
configurable via <jboss3x> element, but what about host binding address?
In my case all quite simple, I have multi interface host, and want to run
several JBosses at the time (test host, with several developers testing
something).
The simpliest solution is too up number of dummy interfaces (luck linux
allows that)
and run each container on individual interface. I can start container from
cactus tast to run that way, BUT cactus task queries 'localhost' to run
tests, not custom address container listens. and, as result, tests are not
run.
Hope i clarified why custom contextUrl is necessary.
RE: org.apache.commons.httpclient.HttpRecoverableException: java.net.SocketException: Connection reset
Posted by Vincent Massol <vm...@pivolis.com>.
Hi Ming,
> -----Original Message-----
> From: ffffc3fffff9ffffb7ffffef ffffb5ffffd4
> [mailto:sevenseeds2004@yahoo.com.cn]
> Sent: lundi 9 août 2004 03:41
> To: Cactus Users List
> Subject: org.apache.commons.httpclient.HttpRecoverableException:
> java.net.SocketException: Connection reset
>
>
> Hi all,
> I have deploy a webapp (meetingcenter) on weblogic which run in a
> server(whose ip is 192.168.5.4).The application has been configured SSL
> namely "https://..." and I have a cactus struts test in me local host.
> Because the cactus does not support https so I put "cactus.contextURL =
> http://192.168.5.4:8002/meetingcenter" in cactus.properties. when I
> ran the test the background of weblogic reported :
Is the application configured to work without SSL?
As for the error below, I have no idea. My suggestion would be to enable Cactus logging on the client side so that you can check what's going on and why HttpClient throws a "Connection reset".
See http://jakarta.apache.org/cactus/integration/manual/howto_config.html for help on enabling logging.
-Vincent
>
> "<Security> <BEA-090475> <Plaintext data for protocol HTTP was received
> from peer 172.16.192.180 - 172.16.192.180 instead of an SSL handshake.>"
> here "172.16.192.180" is my local host's ip address.
>
> And the exeptional trace in the eclipse reported :
> org.apache.commons.httpclient.HttpRecoverableException:
> java.net.SocketException: Connection reset
> at
> org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.j
> ava:1952)
> at
> org.apache.commons.httpclient.HttpMethodBase.processRequest(HttpMethodBase
> .java:2631)
> at
> org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1
> 085)
> at
> org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:674
> )
> at
> org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:558
> )
> at
> org.apache.cactus.internal.client.connector.http.HttpClientConnectionHelpe
> r.connect_aroundBody0(HttpClientConnectionHelper.java:142)
> at
> org.apache.cactus.internal.client.connector.http.HttpClientConnectionHelpe
> r.connect_aroundBody1$advice(HttpClientConnectionHelper.java:188)
> at
> org.apache.cactus.internal.client.connector.http.HttpClientConnectionHelpe
> r.connect(HttpClientConnectionHelper.java)
> at
> org.apache.cactus.internal.client.connector.http.DefaultHttpClient.callRun
> Test(DefaultHttpClient.java:162)
> at
> org.apache.cactus.internal.client.connector.http.DefaultHttpClient.doTest_
> aroundBody0(DefaultHttpClient.java:80)
> at
> org.apache.cactus.internal.client.connector.http.DefaultHttpClient.doTest_
> aroundBody1$advice(DefaultHttpClient.java:188)
> at
> org.apache.cactus.internal.client.connector.http.DefaultHttpClient.doTest(
> DefaultHttpClient.java)
> at
> org.apache.cactus.internal.client.connector.http.HttpProtocolHandler.runWe
> bTest(HttpProtocolHandler.java:159)
> at
> org.apache.cactus.internal.client.connector.http.HttpProtocolHandler.runTe
> st_aroundBody0(HttpProtocolHandler.java:80)
> at
> org.apache.cactus.internal.client.connector.http.HttpProtocolHandler.runTe
> st_aroundBody1$advice(HttpProtocolHandler.java:188)
> at
> org.apache.cactus.internal.client.connector.http.HttpProtocolHandler.runTe
> st(HttpProtocolHandler.java)
> at
> org.apache.cactus.internal.client.ClientTestCaseCaller.runTest(ClientTestC
> aseCaller.java:144)
> at
> org.apache.cactus.internal.AbstractCactusTestCase.runBareClient(AbstractCa
> ctusTestCase.java:215)
> at
> org.apache.cactus.internal.AbstractCactusTestCase.runBare(AbstractCactusTe
> stCase.java:133)
> at junit.framework.TestResult$1.protect(TestResult.java:106)
> at junit.framework.TestResult.runProtected(TestResult.java:124)
> at junit.framework.TestResult.run(TestResult.java:109)
> at junit.framework.TestCase.run(TestCase.java:118)
> at junit.framework.TestSuite.runTest(TestSuite.java:208)
> at junit.framework.TestSuite.run(TestSuite.java:203)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTest
> Runner.java:392)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunne
> r.java:276)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunn
> er.java:167)
>
>
>
> can anyone who know the reason tell me the solution?
> Thanks very much
> -Ming
>
>
>
>
> ---------------------------------
> Do You Yahoo!?
> 150万曲MP3疯狂搜，带您闯入音乐殿堂
> 美女明星应有尽有，搜遍美图、艳图和酷图
> 1G就是1000兆，雅虎电邮自助扩容！
org.apache.commons.httpclient.HttpRecoverableException: java.net.SocketException: Connection reset
Posted by ffffc3fffff9ffffb7ffffef ffffb5ffffd4 <se...@yahoo.com.cn>.
Hi all,
I have deploy a webapp (meetingcenter) on weblogic which run in a
server(whose ip is 192.168.5.4).The application has been configured SSL namely "https://..." and I have a cactus struts test in me local host.
Because the cactus does not support https so I put "cactus.contextURL = http://192.168.5.4:8002/meetingcenter" in cactus.properties. when I
ran the test the background of weblogic reported :
"<Security> <BEA-090475> <Plaintext data for protocol HTTP was received from peer 172.16.192.180 - 172.16.192.180 instead of an SSL handshake.>" here "172.16.192.180" is my local host's ip address.
And the exeptional trace in the eclipse reported :
org.apache.commons.httpclient.HttpRecoverableException:
java.net.SocketException: Connection reset
at
org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.java:1952)
at
org.apache.commons.httpclient.HttpMethodBase.processRequest(HttpMethodBase.java:2631)
at
org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1085)
at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:674)
at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:558)
at
org.apache.cactus.internal.client.connector.http.HttpClientConnectionHelper.connect_aroundBody0(HttpClientConnectionHelper.java:142)
at
org.apache.cactus.internal.client.connector.http.HttpClientConnectionHelper.connect_aroundBody1$advice(HttpClientConnectionHelper.java:188)
at
org.apache.cactus.internal.client.connector.http.HttpClientConnectionHelper.connect(HttpClientConnectionHelper.java)
at
org.apache.cactus.internal.client.connector.http.DefaultHttpClient.callRunTest(DefaultHttpClient.java:162)
at
org.apache.cactus.internal.client.connector.http.DefaultHttpClient.doTest_aroundBody0(DefaultHttpClient.java:80)
at
org.apache.cactus.internal.client.connector.http.DefaultHttpClient.doTest_aroundBody1$advice(DefaultHttpClient.java:188)
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:188)
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)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:392)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:276)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:167)
can anyone who know the reason tell me the solution?
Thanks very much
-Ming
---------------------------------
Do You Yahoo!?
150万曲MP3疯狂搜，带您闯入音乐殿堂
美女明星应有尽有，搜遍美图、艳图和酷图
1G就是1000兆，雅虎电邮自助扩容！
RE: cactus.properties
Posted by Vincent Massol <vm...@pivolis.com>.
Chris,
I can see 2 ways of helping you:
1/ You try with the exact sample from JUnit in Action. It should work OOB.
Then you modify slowly to reach the state you wish.
Or
2/ You show us your build script and your test.
What you're saying is true. If you're using the Ant integration you don't
need to set the cactus.contextURL property (it is set automatically by the
<cactus> Ant task).
-Vincent
> -----Original Message-----
> From: Chris Huisman [mailto:chuisman@taylor.com]
> Sent: jeudi 5 août 2004 00:43
> To: Cactus Users List
> Subject: Re: cactus.properties
>
> So I did some more digging and found a similar set of posts here:
> http://www.mail-archive.com/cactus-user@jakarta.apache.org/msg04457.html
>
> It sasy that if you are using ant integration you don't have to set this
> property. I'm using ant, and still getting this error.
> c.
>
> Chris Huisman wrote:
>
> > Hello,
> >
> > I'm attempting to use the Junit in action book example to do ejb
> > integration testing via cactus . Using the sample build-cactus.xml
> > file (modified of course) I get the following error:
> >
> > [cactus] Missing Cactus property [cactus.contextURL]
> > [cactus] org.apache.cactus.util.ChainedRuntimeException: Missing
> > Cactus property [cactus.contextURL]
> >
> > were am I supposed to specify cactus properties, and what is the
> > cactus.contextURL?
> >
> > Thank you,
> >
> > Chris.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: cactus-user-help@jakarta.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: cactus-user-help@jakarta.apache.org
Re: cactus.properties
Posted by Chris Huisman <ch...@taylor.com>.
So I did some more digging and found a similar set of posts here:
http://www.mail-archive.com/cactus-user@jakarta.apache.org/msg04457.html
It sasy that if you are using ant integration you don't have to set this
property. I'm using ant, and still getting this error.
c.
Chris Huisman wrote:
> Hello,
>
> I'm attempting to use the Junit in action book example to do ejb
> integration testing via cactus . Using the sample build-cactus.xml
> file (modified of course) I get the following error:
>
> [cactus] Missing Cactus property [cactus.contextURL]
> [cactus] org.apache.cactus.util.ChainedRuntimeException: Missing
> Cactus property [cactus.contextURL]
>
> were am I supposed to specify cactus properties, and what is the
> cactus.contextURL?
>
> Thank you,
>
> Chris.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: cactus-user-help@jakarta.apache.org
>