Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Received-SPF: pass (athena.apache.org: domain of asankha.apache@gmail.com
 designates 72.14.246.248 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=sender:message-id:date:from:user-agent:mime-version:to:subject
         :references:in-reply-to:content-type;
        b=hlTX96bsXh6teBtNsDlATDrlNdw4EKnOQPpoEN2Je35iVgSPSsXWkICFWeZhvBJ+4E
         e5IMPzVDFvwYLru0YIh7rFkDrQIli0ZlYVg/bys2dazvNQ0SDP+Z99WDd2kbxgm1eGIT
         oFaOMs4l5GAG+UsXjHaMDYbe0BlMN+3Cxd2NA=
Sender: Asankha Perera <asankha.apache@gmail.com>
Message-ID: <499471D8.70000@apache.org>
Date: Fri, 13 Feb 2009 00:30:40 +0530
From: "Asankha C. Perera" <asankha@apache.org>
User-Agent: Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: axis-dev@ws.apache.org
Subject: Re: Axis2 doesn't play nice with PFP (payflow, paypal)
References: <9BCCB7054FD99E499020515FAC2D4C810165ABDD@mail-41ps.atlarge.net>
 <9BCCB7054FD99E499020515FAC2D4C81017275AF@mail-41ps.atlarge.net>
 <49927BD7.8020001@apache.org>
 <9BCCB7054FD99E499020515FAC2D4C8101727C05@mail-41ps.atlarge.net>
In-Reply-To: <9BCCB7054FD99E499020515FAC2D4C8101727C05@mail-41ps.atlarge.net>
Content-Type: multipart/alternative;
 boundary="------------030904020205040605050305"

This is a multi-part message in MIME format.
--------------030904020205040605050305
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi Grover
> Before answering your questions, I will add a new development: 
> yesterday we switched our soap communication method to use Axis 1.4 
> (Axis 1) instead of Axis2 1.4.1.  Making this change did resolve the 
> issue and PFP does not break Axis 1 communication.  At this point we 
> are satisfied with this solution and have decided to move forward with 
> Axis 1.
Thats good to hear!
>
> One other thing I should mention is that the soap server we are using 
> Axis to communicate with requires basic authentication to connect, so 
> simple telnet commands do get connection refused.
>
Hmm.. that should not happen, since a basic auth failure (which has a 
HTTP response) is different from a connection refused - which means that 
the remote host did not accept the message over the selected port.
>
> However, ngrep does show packets going to and from xyz.com when 
> attempting the telnet connection, even when we are in the broken 
> communication state.
>
I am not much familiar with ngrep.. but if communication takes place, 
that means you have network level connectivity. What would be 
interesting to see is the output of tcpdump for the manual telnet vs the 
Axis2 connection attempt.. anyway, leave that to the next time you want 
to revisit Axis2

cheers
asankha

-- 
Asankha C. Perera
http://adroitlogic.org

http://esbmagic.blogspot.com


--------------030904020205040605050305
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Grover
<blockquote
 cite="mid:9BCCB7054FD99E499020515FAC2D4C8101727C05@mail-41ps.atlarge.net"
 type="cite">
  <meta http-equiv="Content-Type" content="text/html; ">
  <meta name="Generator" content="Microsoft Word 12 (filtered medium)">
  <style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
  </style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext="edit">
  <o:idmap v:ext="edit" data="1" />
 </o:shapelayout></xml><![endif]-->
  <div class="Section1"><span style="color: rgb(31, 73, 125);">Before
answering your questions,
I will add a new development: yesterday we switched our soap
communication
method to use Axis 1.4 (Axis 1) instead of Axis2 1.4.1.&nbsp; Making this
change did resolve the issue and PFP does not break Axis 1
communication.&nbsp;
At this point we are satisfied with this solution and have decided to
move
forward with Axis 1.</span></div>
</blockquote>
Thats good to hear!<o:p></o:p>
<blockquote
 cite="mid:9BCCB7054FD99E499020515FAC2D4C8101727C05@mail-41ps.atlarge.net"
 type="cite">
  <div class="Section1"><span style="color: rgb(31, 73, 125);"></span>
  <p class="MsoNormal"><span style="color: rgb(31, 73, 125);">One other
thing I should mention is
that the soap server we are using Axis to communicate with requires
basic authentication
to connect, so simple telnet commands do get connection refused.</span></p>
  </div>
</blockquote>
Hmm.. that should not happen, since a basic auth failure (which has a
HTTP response) is different from a connection refused - which means
that the remote host did not accept the message over the selected port.<br>
<blockquote
 cite="mid:9BCCB7054FD99E499020515FAC2D4C8101727C05@mail-41ps.atlarge.net"
 type="cite">
  <div class="Section1">
  <p class="MsoNormal"><span style="color: rgb(31, 73, 125);"> However,
ngrep
does show packets going to and from xyz.com when attempting the telnet
connection, even when we are in the broken communication state.</span></p>
  </div>
</blockquote>
I am not much familiar with ngrep.. but if communication takes place,
that means you have network level connectivity. What would be
interesting to see is the output of tcpdump for the manual telnet vs
the Axis2 connection attempt.. anyway, leave that to the next time you
want to revisit Axis2<br>
<br>
cheers<br>
asankha<br>
<br>
<pre class="moz-signature" cols="72">-- 
Asankha C. Perera
<a class="moz-txt-link-freetext" href="http://adroitlogic.org">http://adroitlogic.org</a>

<a class="moz-txt-link-freetext" href="http://esbmagic.blogspot.com">http://esbmagic.blogspot.com</a>
</pre>
</body>
</html>

--------------030904020205040605050305--