Please set the following to false in the configuration file if you run an
external selenium server.

runInternally = false

On Fri, Sep 3, 2010 at 9:24 AM, Jian Fang <[email protected]> wrote:

> Seems the embedded selenium server was down after the test suites and could
> not be started for
> your new test case. Could you try to use external selenium server to see if
> you have the same problem?
>
> To run the external selenium, simply run
>
> java -jar selenium-server.jar
>
> We will look into the problem of the embedded selenium server and 0.8.0
> core will be changed soon to support multiple threads/parallel processing.
> But hopefully this would not affect user's current test code.
>
> Thanks,
>
> Jian
>
>
> On Fri, Sep 3, 2010 at 4:28 AM, Viktor Korling <[email protected]> wrote:
>
>> Thanks for the quick reply,
>>
>> the first test in the suite runs as expected saying:
>>
>> Configure Embedded Selenium Server using configuration
>> Warning: No user-extensions.js
>> log4j:WARN No appenders could be found for logger
>> (org.openqa.selenium.server.SeleniumServer).
>> log4j:WARN Please initialize the log4j system properly.
>> Configure Selenium Client using configuration
>>
>> and starts the browser and runs the test, but after it has run the next
>> test will error.
>>
>>
>> This is the section from the TelluriumConfig.groovy file I'm using
>>
>> tellurium{
>>     //embedded selenium server configuration
>>
>>     embeddedserver {
>>         //port number
>>         port = "4444"
>>         //whether to use multiple windows
>>         useMultiWindows = false
>>         //whether to trust all SSL certs, i.e., option
>> "-trustAllSSLCertificates"
>>         trustAllSSLCertificates = true
>>         //whether to run the embedded selenium server. If false, you need
>> to manually set up a selenium server
>>         runInternally = true
>>
>> These are the changes I do in the pom file:
>>
>> from:
>>
>>  <dependency>
>>             <groupId>org.telluriumsource</groupId>
>>             <artifactId>tellurium-core</artifactId>
>>            * <version>0.7.0</version>*
>>             <scope>compile</scope>
>>         </dependency>
>>
>> to:
>>
>>  <dependency>
>>             <groupId>org.telluriumsource</groupId>
>>             <artifactId>tellurium-core</artifactId>
>>             *<version>0.8.0-SNAPSHOT</version>*
>>             <scope>compile</scope>
>>         </dependency>
>>
>> and from:
>>
>> <properties>
>>         <java-version>1.6</java-version>
>>         <groovy-version>1.7.0</groovy-version>
>>         <gmaven-version>1.2</gmaven-version>
>>         <selenium-version>1.0.1-te4-SNAPSHOT</selenium-version>
>>         *<tellurium-version>0.7.0</tellurium-version>*
>>         <javac-debug>true</javac-debug>
>>     </properties>
>>
>> to:
>>
>> <properties>
>>         <java-version>1.6</java-version>
>>         <groovy-version>1.7.0</groovy-version>
>>         <gmaven-version>1.2</gmaven-version>
>>         <selenium-version>1.0.1-te4-SNAPSHOT</selenium-version>
>>         *<tellurium-version>0.8.0-SNAPSHOT</tellurium-version>*
>>         <javac-debug>true</javac-debug>
>>     </properties>
>>
>> Running* telnet localhost 4444 *
>>
>> after the suites have run will give the same result:
>>
>> Trying ::1...
>> Trying 127.0.0.1...
>> telnet: Unable to connect to remote host: Connection refused
>>
>> Running *mvn clean install test*
>> with the 0.7.0 settings runs through the whole test suite,
>> but with the 0.8.0-SNAPSHOT settings run through the first test and then
>> give the connection refused error.
>>
>> thanks
>> Viktor
>>
>>
>>
>>
>> On Wed, Sep 1, 2010 at 5:12 PM, Jian Fang <[email protected]>wrote:
>>
>>> Seems your selenium server is not running. Are you using the embedded
>>> selenium server or an external server?
>>>
>>> Please check the following portion of the TelluriumConfig.groovy file
>>>
>>>     embeddedserver {
>>>         //port number
>>>         port = "4444"
>>>         //whether to use multiple windows
>>>         useMultiWindows = false
>>>         //whether to trust all SSL certs, i.e., option
>>> "-trustAllSSLCertificates"
>>>         trustAllSSLCertificates = true
>>>         //whether to run the embedded selenium server. If false, you need
>>> to manually set up a selenium server
>>>         runInternally = true
>>>
>>> Also, run the following command
>>>
>>> telnet localhost 4444
>>>
>>> to see if the server is listening on the port 4444.
>>>
>>> Thanks,
>>>
>>> Jian
>>>
>>>
>>> On Wed, Sep 1, 2010 at 11:04 AM, Viktor Korling <[email protected]>wrote:
>>>
>>>> Hi,
>>>>
>>>> I'm successfully running a test suite on linux(Ubuntu) using maven,
>>>> with tellurium-core-0.7.0 and the embedded selenium-server-1.0.1-te4-
>>>> SNAPSHOT and the *chrome browser setting.
>>>>
>>>> However if I change to using the tellurium-core-0.8.0-SNAPSHOT in the
>>>> maven  pom file, keeping the other settings, the first test in the
>>>> suite will run as expected but the remaining tests will all end in
>>>> error showing the following error in the test reports:
>>>>
>>>> org.telluriumsource.exception.TelluriumException: Cannot start
>>>> selenium: Could not contact Selenium Server; have you started it on
>>>> 'localhost:4444' ?
>>>> Read more at
>>>> http://seleniumhq.org/projects/remote-control/not-started.html
>>>> Connection refused
>>>>        at
>>>> sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>>>>        at
>>>>
>>>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:
>>>> 39)
>>>>        at
>>>>
>>>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:
>>>> 27)
>>>>        at java.lang.reflect.Constructor.newInstance(Constructor.java:
>>>> 513)
>>>>        at
>>>>
>>>> org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:
>>>> 77)
>>>>        at org.codehaus.groovy.runtime.callsite.ConstructorSite
>>>> $ConstructorSiteNoUnwrapNoCoerce.callConstructor(ConstructorSite.java:
>>>> 107)
>>>>        at
>>>>
>>>> org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallConstructor(CallSiteArray.java:
>>>> 52)
>>>>        at
>>>>
>>>> org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:
>>>> 192)
>>>>        at
>>>>
>>>> org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:
>>>> 200)
>>>>        at
>>>>
>>>> org.telluriumsource.component.connector.CustomSelenium.startSeleniumSession(CustomSelenium.groovy:
>>>> 66)
>>>>        at org.telluriumsource.component.connector.CustomSelenium
>>>> $startSeleniumSession.call(Unknown Source)
>>>>        at
>>>>
>>>> org.telluriumsource.component.connector.SeleniumConnector.connectSeleniumServer(SeleniumConnector.groovy:
>>>> 95)
>>>>
>>>> thanks
>>>> Viktor
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "tellurium-users" group.
>>>> To post to this group, send email to [email protected].
>>>> To unsubscribe from this group, send email to
>>>> [email protected]<tellurium-users%[email protected]>
>>>> .
>>>> For more options, visit this group at
>>>> http://groups.google.com/group/tellurium-users?hl=en.
>>>>
>>>>
>>>  --
>>> You received this message because you are subscribed to the Google Groups
>>> "tellurium-users" group.
>>> To post to this group, send email to [email protected].
>>> To unsubscribe from this group, send email to
>>> [email protected]<tellurium-users%[email protected]>
>>> .
>>> For more options, visit this group at
>>> http://groups.google.com/group/tellurium-users?hl=en.
>>>
>>
>>  --
>> You received this message because you are subscribed to the Google Groups
>> "tellurium-users" group.
>> To post to this group, send email to [email protected].
>> To unsubscribe from this group, send email to
>> [email protected]<tellurium-users%[email protected]>
>> .
>> For more options, visit this group at
>> http://groups.google.com/group/tellurium-users?hl=en.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"tellurium-users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/tellurium-users?hl=en.

Reply via email to