Mailing-List: contact axis-c-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache AXIS C User List" <axis-c-user@ws.apache.org>
Received-SPF: pass (athena.apache.org: domain of premalal@gmail.com designates
 64.233.166.177 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:subject:references:from:x-url:to:date:in-reply-to:message-id:user-agent:mime-version:content-type:sender;
        b=eI8cctIOmo06jUv6Xk6J2l5Yjx3mWT/IIzwVkFF5goa1V/NY4OryN5r9QrVxZSsKts6u65lZATB60VHzkISs50NSoym8Ozagf3arxSV29nWdJ+q7TBD1S3H6czncIjBljsIrv0BuiWfAewRim7R3KVl8nnbvkln8r933DiMhMGs=
Subject: Re: AW: echo.exe client has "infer transport" error
References: 
 <55369AF6DCB7F84E82B389410504C3F104AFF89E@WIC-CHMN-02.chres1.doleni.net>
From: Dinesh Premalal <xydinesh@gmail.com>
To: axis-c-user@ws.apache.org
Date: Wed, 21 Nov 2007 09:55:40 +0530
In-Reply-To: 
 <55369AF6DCB7F84E82B389410504C3F104AFF89E@WIC-CHMN-02.chres1.doleni.net>
 (Stadelmann Josef's message of "Tue\, 20 Nov 2007 18\:57\:17 +0100")
Message-ID: <871wakrzqz.fsf@etch.wso2.com>
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.95 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: Dinesh Premalal <premalal@gmail.com>

Hi Josef,
   Please find my comments inline.

"Stadelmann Josef" <josef.stadelmann@axa-winterthur.ch> writes:

> Now my simple http server is up and running on OpenVMS, in fact it is waiting within it's first accept() for the client to initiate a conversation.
>
> Now, the echo_blocking client fails with the following
> echo_blocking.log

Can you see the deployed services through the browser ?

>
>
> [Tue Nov 20 15:36:31 2007] [debug] DSA5:[webservices.axis2.trunk.c.src.core.clientapi]op_client.c;3(813) Start:axis2_op_client_infer_transport
> [Tue Nov 20 15:36:31 2007] [error] DSA5:[webservices.axis2.trunk.c.src.core.clientapi]op_client.c;3(863) [axis2c] Cannot infer transport
> [Tue Nov 20 15:36:31 2007] [debug]
> DSA5:[webservices.axis2.trunk.c.src.core.clientapi]op_client.c;3(868)
> End:axis2_op_client_infer_transport

This error usually happens when op_client unable to locate the
transport in/out descriptors (as you mentioned in the later in this
mail). According to my knowledge That happens due to several reasons.

1. axis2.xml has wrong transport sender/receiver information

2. Axis2/C engine unable to locate libaxis2_http_sender.so or
libaxis2_http_receiver.so.

3.When there is unloadable (corrupted) library.

BTW, what axis2/c version are you using? as per log messages it should
be prior to the Axis2/C 1.1.0.

> *********************
> Tell me ! if the client code finds all the services and the addr
> module and the logging module why should axis2c_home be the problem
> with this client run?

> *********************
AFAIK, AXIS2C_HOME is not important , but repo_path is
essential. (AXIS2C_HOME use to make the repo_path). Repo path is use
to find axis2.xml. Details in axis2.xml use to build axis2
configuration. 

HTH

thanks,
Dinesh

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