[jira] [Reopened] (SYNCOPE-456) TaskTestITCase failures

["Hadrian Zbarcea (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SYNCOPE-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hadrian Zbarcea reopened SYNCOPE-456:
-------------------------------------


Sorry, I had a temporary brain freeze. In core/src/test/resources/content.xml, he hostname should be "not-existing.syncope.apache.org" not not-existing@s.a.o ('dot' instead of '@'). It does work but it's not quite a correct fqdn :). Doh...


> TaskTestITCase failures
> -----------------------
>
>                 Key: SYNCOPE-456
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-456
>             Project: Syncope
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.2.0
>            Reporter: Hadrian Zbarcea
>            Assignee: Hadrian Zbarcea
>         Attachments: syncope-456.patch
>
>
> Both issueSYNCOPE81 and issueSYNCOPE86 fail on my system. The symptom is that TaskController.execute hangs (the line below is the last in the log) and then there is a timeout on the client side.
> 22:46:09.087 DEBUG org.apache.syncope.core.rest.controller.ControllerHandler - Before TaskController.execute([101, false])
> I am not sure if anybody saw this, if so please add a comment. I reproduce the issue consistently on my Ubuntu laptop with both sun and openjdk 6. Others don't see it in an environment similar to mine. I also saw it on a CentOS server. I cannot reproduce it on osx though. It is quite likely related to the environment, but nevertheless syncope should be more robust and handle errors gracefully in a misconfigured environment.
> Since I have environments that both work and don't, I will try to dig deeper, compare the two and see what the culprit is.



--
This message was sent by Atlassian JIRA
(v6.1#6144)