Hi Gurkan

I verified that I have all these properties already configured
correctly but if I don' have tomcat running, the test will time out
while attempting to connect to server over http, see below -

WARNING: Unable to connect to server after 240000ms, giving up!
Error Writing/Reading Streams.
Error Writing/Reading Streams.
Sep 3, 2010 2:40:58 PM
org.jboss.testharness.spi.helpers.AbstractContainerConnector cleanup
INFO: Shutting down server
Error Writing/Reading Streams.
Error Writing/Reading Streams.
[XmlMethodSelector]
CLASSNAME:org.jboss.testharness.impl.testng.DisableIntegrationTestsMethodSelector
[XmlMethodSelector] SETTING PRIORITY:0
[XmlMethodSelector]
CLASSNAME:org.jboss.testharness.impl.testng.ExcludeIncontainerUnderInvestigationMethodSelector
[XmlMethodSelector] SETTING PRIORITY:0
Tests run: 772, Failures: 1, Errors: 0, Skipped: 771, Time elapsed:
260.395 sec <<< FAILURE!

Results :

Failed tests:
  
beforeSuite(org.jboss.jsr299.tck.tests.implementation.simple.definition.dependentWithPublicField.DependentWithPublicFieldTest)

Tests run: 772, Failures: 1, Errors: 0, Skipped: 771

[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE

Lin

On Fri, Sep 3, 2010 at 2:39 AM, Gurkan Erdogdu <[email protected]> wrote:
> Hi Lin,
>
> For standalone tests, tweak the jboss-test-harness.properties as (under
> webbeans-tck)
>
> org.jboss.testharness.standalone=false
> org.jboss.testharness.runIntegrationTests=false
>
> Also tweak openwebbeans.properties(under webbeans-tck)
>
> org.apache.webbeans.spi.deployer.useEjbMetaDataDiscoveryService=true
> org.apache.webbeans.spi.JNDIService=org.apache.webbeans.corespi.se.DefaultJndiService
>
>
> Therefore,  Tomcat is not involved
>
>
> --Gurkan
>
>
> ________________________________
> From: Lin Sun <[email protected]>
> To: [email protected]
> Sent: Thu, September 2, 2010 8:24:03 PM
> Subject: Re: webbeans-tck in trunk
>
> Hi Gurkan
>
> Yes I saw that is what is documented in the readme, however, if tomcat
> is not running, no tests will be executed.  I believe Joe discovered
> the same thing per his email -
>
> http://mail-archives.apache.org/mod_mbox/openwebbeans-dev/201008.mbox/%[email protected]%3e
>
>
> Somehow at the beginning of the tests, it is trying to connect to the
> web server:
>
> Sep 2, 2010 1:19:14 PM
> org.jboss.testharness.spi.helpers.AbstractContainerConnector
> isServerUp
> INFO: Connected to server over http
>
>
> Lin
>
> On Thu, Sep 2, 2010 at 11:52 AM, Gurkan Erdogdu <[email protected]> 
> wrote:
>> Hi Lin,
>>
>> For standalone TCK, no need to use Tomcat. Tomcat is needed for executing Web
>> Profile TCK.
>>
>>
>> Thanks;
>>
>>
>> --Gurkan
>>
>>
>> ________________________________
>> From: Lin Sun <[email protected]>
>> To: [email protected]
>> Sent: Thu, September 2, 2010 6:05:36 PM
>> Subject: webbeans-tck in trunk
>>
>> Hi!
>>
>> I am new to the list and I did some searches on the titled topic and
>> was able to find the readme/TCK-RUNNING.txt.   I was able to follow
>> the instruction.
>>
>> I discovered that in order to run the tck standalone, I still need to
>> setup tomcat.home and have the tomcat server running.  Also, I have to
>> start tomcat server with -ea to enable assertions as some tests seems
>> to run as servlet and need the assertions to be enabled.
>>
>> My biggest prob right now is most of the tck in standalone failed for me.
>>
>>
>> Tests run: 574, Failures: 524, Errors: 0, Skipped: 0
>>
>> Does the total # of tests look right?  The good thing is test did run
>> instead of skipped but I am probably still missing something obvious
>> here.   I remember seeing a post that says that openwebbeans has
>> passed all jsr299 tcks.
>>
>> Thanks.
>>
>> Lin
>>
>>
>>
>
>
>

Reply via email to