Hi Dinesh,
I hope the problem description in my previous mail was precise.
Kindly let me know if you need more details.Let me know how can i solve the
problem regarding SOAP fault.
Thanks in advance,
Navin Bhat
On Sun, Jun 1, 2008 at 10:41 PM, naveen bhat <[EMAIL PROTECTED]>
wrote:
> Hi Dinesh,
>
> To give to much clear picture about the problem.
> I did an investigation on mtom sample(service & client) in axis2c 1.4 and
> axis2c 1.3.
> I executed the mtom sample in both axis2c 1.4 and axis2c 1.3 for two
> scenarios.
>
>
> 1. First scenario for SOAP fault,where client sends only
> "mtomSample" node without the filename node and the associated
> attachment.SOAP fault was sent properly for axis2c 1.3 mtom service, where
> as for axis2c 1.4 mtom service it did not send SOAP fault,it sent only http
> headers as i explained before.
> 2. Second scenario for normal file transfer which succeds for both
> distributions.
>
>
> I have attached server log(axis2.log), tcp-monitor log (tcpmon_traffic.log)
> and mtom log(mtom.log) for axis2c-1.3 and axis2c-1.4 distribution in
> seperate zip file.Check these files to analyse the problem.
>
> I suspect the problem is with axis2c-1.4 distribution fault handling.
> I hope my explaination is clear to you.
> Eager to hear from you on this issue.
>
> Thanks in advance,
> Naveen.
>
>
>
> On Sat, May 31, 2008 at 10:51 PM, Dinesh Premalal <[EMAIL PROTECTED]>
> wrote:
>
>> Hi Naveen,
>>
>> "naveen bhat" <[EMAIL PROTECTED]> writes:
>>
>> > Hi Dinesh,
>> >
>> > Please find the server log file (axis2.log) attached.
>>
>> I looked through your log files seems there is nothing wrong with
>> Axis2/C engine. Does your service work for correct request ?
>>
>> thanks,
>> Dinesh
>>
>> --
>> http://nethu.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
