3 Replies Latest reply on Jan 4, 2013 8:25 PM by ffang

propagate credentials. Concurrency problems.

arcaballero Jan 2, 2013 3:38 PM

Hi,

I need an advice about my arquitecture. I have a binding component and a service engine, and, with a interceptor, I spread the consumer credentials using NormalizedMessage.

In addition, my service engine have many proxies (cxfse:proxy), which also need the credentials, and I set them as follow:

((BindingProvider)proxy).getRequestContext().put("credential", "true");

I think I have a problem if several consumers invoke my service simultaneously, because a consumer may use the credentials of another consumer.

¿What can I do? Do I have a problem really, or the client proxies are thread safe?

If no, I thought about creating a pool of proxies, is it a good idea?

Thanks!

Edited by: arcaballero on Jan 2, 2013 8:37 PM

1. Re: propagate credentials. Concurrency problems.

ffang Jan 4, 2013 12:41 AM (in response to arcaballero)

Hi,

This is a good question.

The client proxy isn't thread safe in your case, take a look at to get more details when the proxy isn't thread safe.
And yeah, client proxy pool is the way to go.

http://cxf.apache.org/faq.html#FAQ-AreJAXWSclientproxiesthreadsafe%3F

Freeman
Actions
2. Re: propagate credentials. Concurrency problems.

arcaballero Jan 4, 2013 4:01 AM (in response to ffang)

Hi,

I looked the link and I think if I set the follow property:

((BindingProvider)proxy).getRequestContext().put("thread.local.request.context", "true");

I have not any problems.

I also saw the servicemix-cxf-se-2011.02.1-fuse-08-15.jar and I could find that the property "thread.local.request.context" is set in the method createProxy.

Therefore, Do I have any troubles?

Regards.
Actions
3. Re: propagate credentials. Concurrency problems.

ffang Jan 4, 2013 8:25 PM (in response to arcaballero)

Hi,

Ah, right, cxfse:proxy is already thread safe, I made this change two years ago myself[1] but I didn't realize it when I answer you yesterday, sorry for it.

Anyway, cxfse:proxy is already thread safe and you needn't do anything else.

https://issues.apache.org/jira/browse/SMXCOMP-857

Freeman
Actions

Go to original post