synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Herwig David (JIRA)" <j...@apache.org>
Subject [jira] Updated: (SYNAPSE-675) 'InputStream cannot be NULL' when calling a web service via synapse proxy service
Date Mon, 16 Aug 2010 09:23:17 GMT

     [ https://issues.apache.org/jira/browse/SYNAPSE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Herwig David updated SYNAPSE-675:
---------------------------------

    Attachment: trace.log
                service.log
                synapse.log

> 'InputStream cannot be NULL' when calling a web service via synapse proxy service
> ---------------------------------------------------------------------------------
>
>                 Key: SYNAPSE-675
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-675
>             Project: Synapse
>          Issue Type: Bug
>          Components: Proxy Services
>    Affects Versions: 1.2
>         Environment: standalone synapse 1.2 (synapse-1.2-bin.zip) installation on windows
xp SP2 and Tomcat 5.5 with axis2-1.5.1 
>            Reporter: Herwig David
>            Assignee: Hiranya Jayathilaka
>         Attachments: service.log, synapse.log, trace.log, wrapper.log
>
>
> Hi,
> When calling one of my web services via synapse proxy service I get an AxisFault 'InputStream
cannot be NULL'.
> When calling the web service directly on the tomcat I get the response without problems.
> Both are https requests.
> Searching the internet I have found two solutions to increase the timeout:
> 1st: setting the client options:
> "
>             ServiceClient client = stub._getServiceClient();
> 			
>             client.engageModule("addressing"); 
>             client.engageModule("rampart"); 
>             // get option object 
>             Options options = client.getOptions();
>             // set username / password
>             options.setProperty("user", TestClient.userAlias.toString());
> 	    options.setProperty("encryptionUser", TestClient.serverAlias);
> 	    options.setTimeOutInMilliSeconds(1200000);
>             
>             //setting created option into service      
>             client.setOptions(options); 
> "
> 2nd: Increasing the timeout in synapse.xml
> "
>     <sequence name="_ProxyOut">
>         <send/>
>     </sequence>
>     <!-- Delivery Service -->
>     <sequence name="WS7X4Delivery_ProxyIn" trace="disable">
>         <send>
>             <endpoint>
>                 <address uri="https://app02-kohlpharma.com:8443/axis2/services/WS7X4Delivery"/>

>             </endpoint>
>         </send>
>     </sequence>
>     <proxy name="WS7X4Delivery" transports="https">
>         <publishWSDL key="WS7X4Delivery_ProxyWsdl"/> 
>         <target inSequence="WS7X4Delivery_ProxyIn" outSequence="_ProxyOut"/>
>     </proxy>
> "
> Unfortunately this doesn't help.
> I assume that the connection issue is on synapse side.
> Is there another way to increase the timeout in synapse when using as proxy service?
  
> Thanks and regards,
> Herwig
> ---------------------
> Herwig David
> EDV-Entwicklung
> kohlpharma GmbH
> Im Holzhau 8, 66663 Merzig, Germany
> eMail: HDavid@kohlpharma.com

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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


Mime
View raw message