syncope-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colm O hEigeartaigh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SYNCOPE-931) Error in Camel route causes subsequent failures
Date Tue, 06 Sep 2016 16:14:20 GMT

    [ https://issues.apache.org/jira/browse/SYNCOPE-931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15467789#comment-15467789
] 

Colm O hEigeartaigh commented on SYNCOPE-931:
---------------------------------------------

I committed a partial fix for this problem. When a Camel Route is updated, it starts the Camel
Context if it is stopped, which would be the case if it was originally started with a route
containing a incorrect propagateType as mentioned in the JIRA description. This fixes one
of the errors I found in investigating this task, but not others.

If you start Syncope + edit the UpdateUser route to add in "update123" instead of "update",
save it, and then try to create a User it (the console) will hang (as expected). However,
if you subsequently edit the UpdateUser route back to "update", and try to create a new user,
it will still hang, even though the context has been restarted as per the first commit for
this issue. More investigation required....

> Error in Camel route causes subsequent failures
> -----------------------------------------------
>
>                 Key: SYNCOPE-931
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-931
>             Project: Syncope
>          Issue Type: Bug
>    Affects Versions: 2.0.0.M5
>            Reporter: Colm O hEigeartaigh
>            Assignee: Colm O hEigeartaigh
>             Fix For: 2.0.0
>
>
> Start Syncope with a clean slate + create a new user, and then edit the Camel updateUser
script so that it calls the "update123" propagate type instead of "update". Now edit the user
+ change some attribute. As expected, the update fails.
> Go back into the UI and change the route back to "update" + save. The route appears to
have saved normally. However, if you now go back into the user + update some attribute again,
it gives the same error message as before.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message