ing Unknown error
> processing message
> ---
>
> Key: AXIS2-5844
> URL: https://issues.apache.org/jira/browse/AXIS2-5844
> Project: Axis2
>
lems here.
> AXIS2 1.7.1 is forcing a replyDestination or else throwing Unknown error
> processing message
> ---
>
> Key: AXIS2-5844
> URL: https://issues.a
e in 1.7.9?
> AXIS2 1.7.1 is forcing a replyDestination or else throwing Unknown error
> processing message
> ---
>
> Key: AXIS2-5844
> URL: https://issues.
was not being sent anywhere as we did not specify a replyDestination.
I have upgraded to 1.7.1 from 1.6.0 and the upgrade is causing an unknown error
message from JMS Sender. The only way it works is adding a
transport.jms.ReplyDestination. This is supposed to be optional as mentioned in
the
Anil Kotla created AXIS2-5844:
-
Summary: AXIS2 1.7.1 is forcing a replyDestination or else
throwing Unknown error processing message
Key: AXIS2-5844
URL: https://issues.apache.org/jira/browse/AXIS2-5844
need to have your own Message receiver and
construct the SOAP fault as you wish.
> Unknown soap fault
> --
>
> Key: AXIS2-5699
> URL: https://issues.apache.org/jira/browse/AXIS2-5699
> Project: Axis2
>
[
https://issues.apache.org/jira/browse/AXIS2-5699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-5699.
--
Resolution: Won't Fix
Current version of Axis2 can handle this.
> Unknown so
[
https://issues.apache.org/jira/browse/AXIS2-5699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lulseged Zerfu updated AXIS2-5699:
--
Priority: Critical (was: Major)
> Unknown soap fa
Lulseged Zerfu created AXIS2-5699:
-
Summary: Unknown soap fault
Key: AXIS2-5699
URL: https://issues.apache.org/jira/browse/AXIS2-5699
Project: Axis2
Issue Type: Bug
Components
Thanks,
> Swapna Soni.
>
> -Original Message-
> From: Denise Wu [mailto:[email protected]]
> Sent: Monday, June 06, 2011 2:16 PM
> To: [email protected]
> Cc: [email protected]
> Subject: Re: unknown
>
> Hi Swapna,
>
> The call is not reaching
[email protected]]
Sent: Monday, June 06, 2011 2:16 PM
To: [email protected]
Cc: [email protected]
Subject: Re: unknown
Hi Swapna,
The call is not reaching the webservice at all as I put some logging
information in the method before doing any processing and nothing is
displayed. Is there another
t;
> Thanks,
> Swapna Soni.
>
> -Original Message-
> From: Denise Wu [mailto:[email protected]]
> Sent: Friday, June 03, 2011 4:26 PM
> To: [email protected]; [email protected]
> Subject: unknown
>
> Hi,
>
> I am trying to call my webservice and getting
Soni.
-Original Message-
From: Denise Wu [mailto:[email protected]]
Sent: Friday, June 03, 2011 4:26 PM
To: [email protected]; [email protected]
Subject: unknown
Hi,
I am trying to call my webservice and getting the following error at
the client side.
Tomcat log doesn&#
tailed log file?
Thanks for your help
org.apache.axis2.AxisFault: unknown
at
org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:451)
at
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:371)
at
org.ap
with soapsession services, and we do not see this error anymore.
> ServiceGroupContextID re-created by second client calling in
> scope=soapsession making first client session fail with exception unknown
> ServiceGroup
org.apache.axis2.client.Stub. Most probably
you try to compile a code generanted with older axis2 version.
Resolve this issue since it is not a problem with the current axis2 trunk.
> Unknown method addAnonymousOperations() called in the generated code of the
> clien
16 matches
Mail list logo
