Return-Path: 
 <dev-return-12546-apmail-synapse-dev-archive=synapse.apache.org@synapse.apache.org>
Delivered-To: apmail-synapse-dev-archive@www.apache.org
Received: (qmail 60618 invoked from network); 13 Aug 2010 16:47:40 -0000
Received: from unknown (HELO mail.apache.org) (140.211.11.3)
  by 140.211.11.9 with SMTP; 13 Aug 2010 16:47:40 -0000
Received: (qmail 85723 invoked by uid 500); 13 Aug 2010 16:47:40 -0000
Delivered-To: apmail-synapse-dev-archive@synapse.apache.org
Received: (qmail 85652 invoked by uid 500); 13 Aug 2010 16:47:39 -0000
Mailing-List: contact dev-help@synapse.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@synapse.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@synapse.apache.org>
List-Post: <mailto:dev@synapse.apache.org>
List-Id: <dev.synapse.apache.org>
Reply-To: dev@synapse.apache.org
Delivered-To: mailing list dev@synapse.apache.org
Received: (qmail 85645 invoked by uid 99); 13 Aug 2010 16:47:38 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Aug 2010 16:47:38 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=10.0
	tests=ALL_TRUSTED,WEIRD_PORT
X-Spam-Check-By: apache.org
Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Aug 2010 16:47:37 +0000
Received: from thor (localhost [127.0.0.1])
	by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o7DGlHtT013911
	for <dev@synapse.apache.org>; Fri, 13 Aug 2010 16:47:17 GMT
Message-ID: <30846563.334301281718037064.JavaMail.jira@thor>
Date: Fri, 13 Aug 2010 12:47:17 -0400 (EDT)
From: "Hiranya Jayathilaka (JIRA)" <jira@apache.org>
To: dev@synapse.apache.org
Subject: [jira] Assigned: (SYNAPSE-675) 'InputStream cannot be NULL' when
 calling a web service via synapse proxy service
In-Reply-To: <1896779.299921281600978056.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


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

Hiranya Jayathilaka reassigned SYNAPSE-675:
-------------------------------------------

    Assignee: Hiranya Jayathilaka

> '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
>
> 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