topic Strange (threading?) issue regarding rest services in Alfresco Archive

Strange (threading?) issue regarding rest services

atcevik — Mon, 22 Apr 2013 22:14:16 GMT

Hello,I am using angularjs to call activiti-rest interface. The scenario I am following is, 1. Listing all tasks of a user - OKRequest URL:http://localhost:8088/activiti-rest/service/tasks?assignee=kermit&start=0Request Method:GETStatus Code:200 OK‍‍‍‍‍2. Completing the task - OKRequest URL:http

Re: Strange (threading?) issue regarding rest services

frederikherema1 — Wed, 24 Apr 2013 07:34:23 GMT

Seems really strange that the "/tasks?assignee=XXX" call returns an error-message for the "/task/XXX" call. Is it possible that the framework you're using has some issues with sending a new HTTP-request from within the response-callback of the task-complete success?

Can you verify (using net-console or firebug or whatever) that the http-call done from the callback is indeed the "/tasks?assignee=XXX"? Because we're using rest let for URL-to-resource mapping and I really doubt there is a bug in restlet-routing. Also, since the error-message is "No task found for taskId '578'", it actually means that rest let received a call to tasks/578. Since restlet uses a new resource for each request, there is no way that it's a problem with server-side threading, as the container will NOT use the same request-context for multiple incoming requests. I suspect that the client-framework has a sticky URL somewhere…

Re: Strange (threading?) issue regarding rest services

atcevik — Mon, 06 May 2013 18:10:02 GMT

Dear Frederik,

Yes, I am sure that the call is done to that adress, as I stated, I repeat the call using the captured packet by the chrome dev tools and the fault does not occur on the repititive manual call. I do not change the log nor the adress, just resend it. Thus, the XHR call made from the browser is actually sent to the correct adress. My previous message includes log from the browser, not hand crafted. So the request url etc there are the actual adresses.

As I stated previously, the call is somehow an immediate call, maybe the update of the task mentioned in the log is not completed while listing the tasks of the same user, and I guess might be a problem regarding jpa/persistence at the activiti side.

Re: Strange (threading?) issue regarding rest services

frederikherema1 — Wed, 08 May 2013 07:42:19 GMT

The headers included do not say anything about the URL that is called. I'm pretty confident that this is something client-related, as we use Restlet for routing to the correct resource, which is a proven technology that won't just 'route" the request to the wrong resource just like that…