Hi
options.setTo(new EndpointReference("http://localhost:"; +
synapsePort)) is the one by default there (as only need to talk to
synapse by default) and if you look at further in the code, you can
see if 'addurl' is presented, it is used as 'to' EPR to be called and
if 'trpurl' presents it set as TRASPORT_URL. So, for me, no need for
change in client code.
Try with –Daddurl or –Dtrpurl (same as for other client – stockquote,etc)
BTW, in the DynamicLoadbalanceEndpoint code, it seems 'path'
information of 'to 'address of incoming message is used to create new
target ApplicationMember's address. So, in case where client directly
call to synapse, this 'path' is empty and it may cause your issue.
BTW, I only just look at code ...didn't go into deep
Thanks
Indika
On Thu, Nov 13, 2008 at 5:11 PM, Hiranya Jayathilaka
<[EMAIL PROTECTED]> wrote:
> Hi Folks,
>
> I may have found one of the issues. In LoadBalanceFailoverClient the 'To'
> value is not properly set. Currently it is being set as follows.
>
> options.setTo(new EndpointReference("http://localhost:"; + synapsePort));
>
> But I think it should be set as follows.
>
> options.setTo(new EndpointReference("http://localhost:"; + synapsePort +
> "/services/LBService1"));
>
> Looking at the SVN history this is how it used to be. It has been changed
> recently though. Thoughts?
>
> Thanks
>
> Best Regards,
> Hiranya
>
>
> On Thu, Nov 13, 2008 at 4:46 PM, Hiranya Jayathilaka <[EMAIL PROTECTED]>
> wrote:
>>
>> Hi Asanka,
>>
>> Things seem to work when invoking the service directly from the client. I
>> used the trpurl switch to specify the URI and then I get this.
>>
>> [EMAIL PROTECTED]:~/synapse-SNAPSHOT/samples/axis2Client$ ant
>> loadbalancefailover -Di=1
>> -Dtrpurl=http://10.8.108.114:9001/services/LBService1?sampleOperation
>> Buildfile: build.xml
>>
>> init:
>>
>> compile:
>>
>> loadbalancefailover:
>> [java] timeout=10000000
>> [java] Request: 1 ==> Response from server: Node1
>>
>> I'll continue to look into this problem.
>>
>> Thanks
>>
>> Best Regards,
>> Hiranya
>>
>> On Thu, Nov 13, 2008 at 4:12 PM, Asankha C. Perera <[EMAIL PROTECTED]>
>> wrote:
>>>
>>> Hiranya
>>>>
>>>> org.apache.axis2.AxisFault: The service cannot be found for the endpoint
>>>> reference (EPR) http://10.8.108.114:9001
>>>> ...
>>>> 2008-11-13 15:35:17,242 [-] [HttpServerWorker-1] ERROR ServerWorker
>>>> Error processing POST request
>>>> org.apache.axis2.AxisFault: The service cannot be found for the endpoint
>>>> reference (EPR) http://10.8.108.114:9001
>>>>
>>>> I ran a few debug sessions and found that the DynamicLoadbalanceEndpoint
>>>> actually performs the URL rewrite accurately and forwards the message to
>>>> one
>>>> of the Axis2 node instances in the cluster. But the node instance cannot
>>>> deal with the incoming request.
>>>
>>> So what you mean is that the remote service does not properly reply to
>>> this request? If so can you post a TCPMon trace of the conversation?
>>>>
>>>> The LoadBalanceFailOver service is properly deployed on the Axis2
>>>> instance too.
>>>
>>> What if you invoke it through the same client bypassing Synapse?
>>>
>>> asankha
>>>
>>> --
>>> Asankha C. Perera
>>> http://adroitlogic.org
>>>
>>> http://esbmagic.blogspot.com
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
