Hi
I also have got a similar problem .But TCPMon is showing
HTTP/1.1 202 Accepted
Server: Apache-Coyote/1.1
X-Powered-By: Servlet 2.4; JBoss-4.0.2 (build: CVSTag=JBoss_4_0_2
date=200505022023)/Tomcat-5.5
Content-Type: text/xml;charset=UTF-8
Transfer-Encoding: chunked
Date: Fri, 25 May 2007 11:38:56 GMT
0
But is it possible to infer anything from this?
Exception Trace is
Exception in thread "main" org.apache.axis2.AxisFault: A header
representing a Message Addressing Property is not valid and the message
cannot be processed
at
org.apache.axis2.addressing.AddressingFaultsHelper.triggerAddressingFaul
t(AddressingFaultsHelper.java:150)
at
org.apache.axis2.addressing.AddressingFaultsHelper.triggerActionMismatch
Fault(AddressingFaultsHelper.java:81)
at
org.apache.axis2.handlers.addressing.AddressingInHandler.extractActionIn
formation(AddressingInHandler.java:276)
at
org.apache.axis2.handlers.addressing.AddressingInHandler.extractAddressi
ngInformation(AddressingInHandler.java:159)
at
org.apache.axis2.handlers.addressing.AddressingInHandler.invoke(Addressi
ngInHandler.java:95)
at org.apache.axis2.engine.Phase.invoke(Phase.java:383)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:203)
at
org.apache.axis2.engine.AxisEngine.receiveFault(AxisEngine.java:354)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper
ation.java:370)
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisO
peration.java:294)
at
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:520
)
at
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:500
)
at
org.apache.savan.eventing.client.EventingClient.subscribe(EventingClient
.java:73)
at publisher.client.Client.doSubscribe(Client.java:101)
at publisher.client.Client.run(Client.java:52)
at publisher.client.Client.main(Client.java:40)
________________________________
From: Brian De Pradine [mailto:[EMAIL PROTECTED]
Sent: Friday, May 25, 2007 7:11 PM
To: [email protected]
Subject: Re: AXIS2 : FAULT_ADDRESSING_HEADER_REQUIRED_REASON
Hello Zakaria,
To identify the immediate problem you can use TCPMon to look at the
fault message that is being returned to the client. This will allow you
to identify the header that the server is complaining about and to take
corrective action in your application.
As far as the missing resource bundle is concerned please raise a JIRA
issue at [1] so that it can be fixed.
[1] http://issues.apache.org/jira/browse/AXIS2
Cheers
Brian DePradine
Web Services Development
IBM Hursley
External +44 (0) 1962 816319 Internal 246319
If you can't find the time to do it right the first time, where will you
find the time to do it again?
zakaria ghandour <[EMAIL PROTECTED]> wrote on 25/05/2007 12:53:57:
>
> i use Axis 1.2
> do you have any solution ?
> thanks
> --
> View this message in context: http://www.nabble.com/AXIS2-%3A-
> FAULT_ADDRESSING_HEADER_REQUIRED_REASON-tf3815153.html#a10801531
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
________________________________
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU
The information contained in this electronic message and any attachments to
this message are intended for the exclusive use of the addressee(s) and may
contain proprietary, confidential or privileged information. If you are not the
intended recipient, you should not disseminate, distribute or copy this e-mail.
Please notify the sender immediately and destroy all copies of this message and
any attachments.
WARNING: Computer viruses can be transmitted via email. The recipient should
check this email and any attachments for the presence of viruses. The company
accepts no liability for any damage caused by any virus transmitted by this
email.
www.wipro.com
