Hi Stefan
This Exception is just because the initialization failed and the
JarExecuter waits only for 60sec.
The interesting loggings - describing what went wrong - are in the
"/sling/log/error.log" within the "integration-tests" directory.
It would be nice if you could provide those.
best
Rupert
On Mon, Mar 21, 2011 at 11:27 AM, Stefane Fermigier <s...@nuxeo.com> wrote:
> On my own box (slow, eeepc w/ Intel(R) Atom(TM) CPU 330 @ 1.60GHz), I have
> the following errors:
>
> -------------------------------------------------------------------------------
> Test set: org.apache.stanbol.enhancer.it.OsgiConsoleTest
> -------------------------------------------------------------------------------
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 69.074 sec
> <<< FAILURE!
> testDefaultConsolePaths(org.apache.stanbol.enhancer.it.OsgiConsoleTest) Time
> elapsed: 67.759 sec <<< ERROR!
> java.lang.Exception: Server not ready after 60 seconds
> at
> org.apache.stanbol.commons.testing.stanbol.StanbolTestBase.waitForServerReady(StanbolTestBase.java:168)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
>
> -------------------------------------------------------------------------------
> Test set: org.apache.stanbol.enhancer.it.StatelessEngineTest
> -------------------------------------------------------------------------------
> Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 110.555 sec
> <<< FAILURE!
> testSimpleEnhancement(org.apache.stanbol.enhancer.it.StatelessEngineTest)
> Time elapsed: 64.246 sec <<< ERROR!
> java.lang.Exception: Server not ready after 60 seconds
> at
> org.apache.stanbol.commons.testing.stanbol.StanbolTestBase.waitForServerReady(StanbolTestBase.java:168)
> ...
>
> S.
>
> On Mar 20, 2011, at 1:44 PM, Rupert Westenthaler wrote:
>
>> Hi again
>>
>> After the same problem appeared again this weekend I have done some
>> more testing but still do not have any idea why the problem appears
>> because locally everything works as expected (even with the exact same
>> jar used on the server).
>>
>> However I think I have found a solution for:
>> On Fri, Mar 18, 2011 at 6:23 AM, Rupert Westenthaler <rwes...@apache.org>
>> wrote:
>>> Is it possible to make the loggings of the sling launcher used for the
>>> integration tests available? I was not able to find it on the web
>>> interface. This would be the only possibility to understand what
>>> happened in that specific case.
>>
>> by adding to the CommandLine used by the JarExectutor the arguments
>> //add "-f -" argument to redirect logging to the command
>> cl.addArgument("-f");
>> cl.addArgument("-");
>> the loggings should be available in the console log accessible via the
>> hudson server.
>>
>> If nobody objects I will commit this change to redirect the loggings
>> of the executed jar the the console on monday.
>>
>> best
>> Rupert
>>
>>
>> --
>> | Rupert Westenthaler rupert.westentha...@gmail.com
>> | Bodenlehenstraße 11 ++43-699-11108907
>> | A-5500 Bischofshofen
>
> --
> Stefane Fermigier, Founder and Chairman, Nuxeo
> Open Source, Java EE based, Enterprise Content Management (ECM)
> http://www.nuxeo.com/ - +33 1 40 33 79 87 - http://twitter.com/sfermigier
> Join the Nuxeo Group on LinkedIn: http://linkedin.com/groups?gid=43314
> New Nuxeo release: http://nuxeo.com/dm54
> "There's no such thing as can't. You always have a choice."
>
>
--
| Rupert Westenthaler rupert.westentha...@gmail.com
| Bodenlehenstraße 11 ++43-699-11108907
| A-5500 Bischofshofen
