Hi devs,

@Chetan: I set 'server.ready.timeout.seconds' and seems it works, but I'm
now getting a timeout. Please see below.

@Bertrand: Sorry about cross posting. Now I set
<keepJarRunning>true</keepJarRunning>

Now I get a 'server not ready after 60s' (timeout) message. It is the same
error I mentioned here [1]. Please help me find if I'm doing anything wrong.

Thanks in advance.

--Bhathiya

[1]
http://mail-archives.apache.org/mod_mbox/sling-dev/201208.mbox/%3ccapt+24tcfojnqsx046b+luo3ram33na7u-w9ys5fnq01kk4...@mail.gmail.com%3E




On Mon, Aug 6, 2012 at 6:54 PM, Bertrand Delacretaz
<[email protected]>wrote:

> Hi,
>
> (please don't cross-post such questions)
>
> On Sun, Aug 5, 2012 at 10:48 AM, Bhathiya Jayasekara
> <[email protected]> wrote:
> > ...When I run OsgiConsoleTest class as a junit test (in eclipse), I get
> > this[1] error. But when I add LINE_X in [2], it works fine. Is there any
> > known reason for this? I would like to know if there is any way to get
> this
> > work without having a Thread.sleep(..)....
>
> From your stack trace it looks like you're starting the Sling server
> every time you run that test from Eclipse, which is probably slow.
>
> You might want to start the Sling instance to test separately, and
> configure system properties so that tests run against it.
>
> The comments in the pom at [1] should help you find out how that works.
>
> -Bertrand
>
> [1]
> http://svn.apache.org/repos/asf/sling/trunk/testing/samples/integration-tests/pom.xml
>



-- 
-Bhathiya Jayasekara-
http://www.google.com/profiles/tobhathiyaj
http://www.facebook.com/#!/bhathiyaj1

Reply via email to