fix which I believe has been accepted and may be in the current
release candidate, not sure. See bug 16522 for details.
-Original Message-
From: Davis, Kevin [mailto:[EMAIL PROTECTED]
Sent: Monday, March 17, 2003 1:20 PM
To: 'Norris Merritt'; '[EMAIL PROTECTED]'
Subject:
I believe that Axis client code relies on the remote web server to close the
connnection. The XML response from the SOAP server is not read into memory
and then parsed, it is parsed as it is read from the network. Unless the
remote server closes the connection, Xerces will cause a hang trying to re
If https is an unknown protocol, perhaps you don't have JSSE installed /
configured? If you are running jdk 1.3.x you should download the latest JSSE
from Sun. If you have jdk 1.4, I think it comes with it.
-Original Message-
From: Slaybaugh Laura J IHMD [mailto:[EMAIL PROTECTED]
Sent: Fr
This is fixed in the nightly builds
-Original Message-
From: Cory Wilkerson [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 21, 2003 10:11 AM
To: [EMAIL PROTECTED]
Subject: HTTPS -- Working with .Net, Not Axis -- Call to Arms ;)
When my service is published at http://myservice.com/serv
I just updated that patch, by the way. Version 2 has a serious flaw, but the
one I just posted works well. I went back to using Chen's HTTPInputStream,
because I realized that a "content-length aware" input stream was really an
essential part of the solution. The latest version of the patch keeps
Hi Maurizio, do
call.setProperty(call.ATTACHMENT_ENCAPSULATION_FORMAT,
call.ATTACHMENT_ENCAPSULATION_FORMAT_DIME);
before the call.invoke()
-Original Message-
From: Maurizio Sciglio [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 10, 2003 8:00 AM
To: [EMAIL PROTECTED]
Subject: DIME & Ax
req.getSession(true); // creates a new HttpSession if one
doesn't yet exist
Betsy
-Original Message-From: Norris Merritt
[mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 04,
2003 10:20 AMTo: '[EMAIL PROTECTED]'Subject:
RE: Keep-alive SOAP co
stantiating your service, set the
MaintainSession to true > before your instantiate
your calls from this service. > > I think if you follow this, you should see in the SOAP-message
(e.g. > with > tcpmon)
that the session ID is transferred in the sopaenv-header in the
> resp
the simple
changes described in Sebastian Beyer's 17 Dec 2002 mail, and they worked
fine.
The problem described in #1 below should say "HTTPSender.java
deliberately generates a Connection:close header IF HTTP 1.0 is NOT
set".
Betsy
-Original Message- From:
ginal Message -
From: "Norris Merritt" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, January 28, 2003 13:07
Subject: RE: Interoperative attachments
> If you have an binary type of attachment such as image/jpeg, then it has
to
> be Base-64 encoded if MIME is u
> -Original Message-
> From: Norris Merritt [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, January 28, 2003 2:09 PM
> To: '[EMAIL PROTECTED]'
> Subject: RE: Interoperative attachments
>
>
> I've had success with the Axis 1.1 beta DIME support demonstrated in t
I've had success with the Axis 1.1 beta DIME support demonstrated in the
echoAttachments sample (which also has a mode in which it uses MIME). Axis
1.1 beta DIME support interoperates both with gSOAP and .NET. For my money
DIME is the way to go, especially with attachments that would otherwise nee
I just tried them, and Chen's HTTPSender and HTTPInputStream work great, for
both http and https. The only issues I encountered were that when you
download the attachments from the mailing list, they have funky MIME
characters in them like =0A= and =3D that have to be converted. Also, Axis
has chan
There was a major internet worm incident over the weekend affecting lots of
servers, maybe it got hit?
-Original Message-
From: Reynardine [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 27, 2003 1:34 PM
To: [EMAIL PROTECTED]
Subject: www.webservicex.net has gone ?
I had an axis web ser
Anyone care to comment on this, or the code submission from Shih-Chang Chen
of 4/9/2002 to fix it:
http://marc.theaimsgroup.com/?l=axis-dev&m=101837980122603&w=2
Here is what I have found so far in looking into this, from the perspective
of using Axis as a client:
1) org.apache.axis.transport.htt
another program that
works correctly using the JSSE library, but does not use Axis, I failure
the cause may be in the Axis code. But you are absolutely right that it
should throw more meaningful exception.
Thanks.
At 12:13 PM 1/23/2003 -0800, Norris Merritt wrote:
>Hi Juzer, Use the source, L
n.
Thanks.
At 12:13 PM 1/23/2003 -0800, Norris Merritt wrote:
>Hi Juzer, Use the source, Luke! :-) The stack trace shows that getSocket is
>blowing up on a null pointer exception. Looking at source code for
>HttpSender.getSocket, it has to be because the
>SocketFactoryFactory.getFact
Hi Juzer, Use the source, Luke! :-) The stack trace shows that getSocket is
blowing up on a null pointer exception. Looking at source code for
HttpSender.getSocket, it has to be because the
SocketFactoryFactory.getFactory returned null, and getSocket fails to check
for null and blithely calls facto
line 334: httpConnection = HTTPConstants.HEADER_CONNECTION_CLOSE; //Force
close for now.
em to want.
-Original Message-
From: Zhaohua Meng [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 16, 2003 7:33 AM
To: Norris Merritt; [EMAIL PROTECTED]
Subject: Re: tcp and SOAP monitor
Norris,
Thank you very much. I followed your instruction on tcpmon and it
worked!. But I'm gre
You can consume a document style service with an RPC-style client. For
example, if you download the wsdl for the "Shakespeare" service (which is a
fun little document-style service on xmethods) and feed it to the Axis
wsdl2java tool, it will generate Java objects which can be used to
communicate R
Your
symptom looks a lot like what I get if I run my web service under the debugger
and abruptly terminate it without permitting it to send a response to the
client. It may be that Axis behaves this way when the server side closes
the socket connection without sending anything, which is rea
22 matches
Mail list logo
