You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Ali Sadik Kumlali (JIRA)" <ji...@apache.org> on 2006/08/01 22:51:14 UTC

[jira] Commented: (AXIS2-955) ServiceClient.sendRobust() throws AxisFault: Incoming message input stream is null

    [ http://issues.apache.org/jira/browse/AXIS2-955?page=comments#action_12425007 ] 
            
Ali Sadik Kumlali commented on AXIS2-955:
-----------------------------------------

AFAIK, this is rather a feature. When you use sendRobust(), client will wait for a *soap* message from the service. But when you use RawXMLINOnlyMessageReceiver at the server side, there will be no *soap* message from the server. Yes, the server sends back a *HTTP* response, but it doesn't have a soap message in it. 

Consequently, you should either use fireAndForget () or use RawXMLINOutMessageReceiver.

Please note that, what I say is how sendRobust () and RawXMLINOnlyMessageReceiver interaction behaves currently. I cannot claim that it must be in this way.

> ServiceClient.sendRobust() throws AxisFault: Incoming message input stream is null
> ----------------------------------------------------------------------------------
>
>                 Key: AXIS2-955
>                 URL: http://issues.apache.org/jira/browse/AXIS2-955
>             Project: Apache Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: client-api
>    Affects Versions: 1.0
>         Environment: Weblogic 8.1.2, Solaris 8 (dont ask!)
>            Reporter: Jeff Peterson
>            Priority: Minor
>
> The setup:
> Client -------> Service
> The service is using the RawXMLINOnlyMessageReceiver and the interface looks like the following (pseudo-code):
> interface Service {
>   void doWork(OMElement elem);
> }
> When the client invokes the target service using ServiceClient.sendRobust(), the following exception is generated on the client-side:
> org.apache.axis2.AxisFault: Incoming message input stream is null
>         at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:64)
>         at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:349)
>         at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:279)
>         at org.apache.axis2.client.ServiceClient.sendRobust(ServiceClient.java:359)
>         at org.apache.axis2.client.ServiceClient.sendRobust(ServiceClient.java:339)
>         ...
> This does not limit functionality, the full message is received and processed by the service.  It does, however, force the client to handle (ignore) the exception.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org