Cause of this problem is following code being executed in class -
org.apache.synapse.transport.nhttp.util.RESTUtil, method
prepareMessageContext
RequestURIBasedDispatcher requestDispatcher = new
RequestURIBasedDispatcher();
AxisService axisService = requestDispatcher.findService(msgContext);
Yes, this is wrong. Seems Dispatchers have been manually invoked, and these
dispatchers have set the axis2service and axis2operation in the message
context. So, ELB invokes those instead of passing to back-end service!
On Wed, Jul 31, 2013 at 12:02 PM, Geeth Munasinghe ge...@wso2.com wrote:
Let's introduce a System property called reverseProxyMode if that is
true, we don't do any dispatching internally. In an ELB component, let's
set this System property.
--
Afkham Azeez
Sent from my phone
On Jul 31, 2013 12:02 PM, Geeth Munasinghe ge...@wso2.com wrote:
Cause of this problem is
Kasun/Miyuru/Dushan,
Can you please fix this code correctly?
On Wed, Jul 31, 2013 at 12:02 PM, Geeth Munasinghe ge...@wso2.com wrote:
Cause of this problem is following code being executed in class -
org.apache.synapse.transport.nhttp.util.RESTUtil, method
prepareMessageContext
Another possible implementation is to say whether internal dispatching or
external dispatching needs to be given preference.
--
Afkham Azeez
Sent from my phone
On Jul 31, 2013 12:48 PM, Afkham Azeez az...@wso2.com wrote:
Let's introduce a System property called reverseProxyMode if that is
On Wed, Jul 31, 2013 at 12:48 PM, Afkham Azeez az...@wso2.com wrote:
Let's introduce a System property called reverseProxyMode if that is
true, we don't do any dispatching internally. In an ELB component, let's
set this System property.
+1
We have used a similar approach when handling MT
So, Azeez, this won't work in the case of a LB endpoint of ESB, right?
On Wed, Jul 31, 2013 at 12:48 PM, Afkham Azeez az...@wso2.com wrote:
Let's introduce a System property called reverseProxyMode if that is
true, we don't do any dispatching internally. In an ELB component, let's
set this
ELB packs org.wso2.carbon.core.services.jar, which has exposed
org.wso2.carbon.core.services.authentication.AuthenticationAdmin as a web
services. When IS is load balanced through ELB and a client tries to access
the AuthenticationAdmin of IS, ELB invoke it's own AuthenticationAdmin web
service
This is why all dispatchers were removed from the ELB. Has somebody added
those back?
--
Afkham Azeez
Sent from my phone
On Jul 29, 2013 7:40 PM, Geeth Munasinghe ge...@wso2.com wrote:
ELB packs org.wso2.carbon.core.services.jar, which has exposed
Hi Azeez,
There are no dispatchers in axis2 xml of ELB:
phase name=Dispatch class=org.apache.axis2.engine.DispatchPhase/
On Mon, Jul 29, 2013 at 9:22 PM, Afkham Azeez az...@wso2.com wrote:
This is why all dispatchers were removed from the ELB. Has somebody added
those back?
--
Afkham
10 matches
Mail list logo
