TED]>
A : "axis-dev" <[EMAIL PROTECTED]>
Copies :
Date : Wed, 10 Nov 2004 15:05:15 +0100
Sujet : Persistent connections
Hello
I'm using Axis 1-2 beta and commons-httpclient 2.0
to have persistent connections.
I have modified the client-config.wsdd as follow :
to
U
Hello
I'm using Axis 1-2 beta and commons-httpclient 2.0
to have persistent connections.
I have modified the client-config.wsdd as follow :
to
Unfortunatly, the connections (sockets) are not reused. In order to verify
this, i use the command 'netstat' in Solaris2.8.
Have
I'm using tomcat 4. I ended up defining the db in the server.xml using an
example I found(see my Thanks post).
Chris
-Original Message-
From: Ivan Aguirre [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 05, 2004 8:59 AM
To: [EMAIL PROTECTED]
Subject: Re: DB Connections with Axi
I use db pooling with Axis and It's working well.
I'll teel you how I use it, so I hope help you ;)
1. I don't define the Connections inside Context Elements on
server.xml. Instead I use a .xml located at
TOMCAT_HOME/conf/localhost, its's a recommendation:
"Please
axis and that made axis stop working.
Chris
-Original
Message-From: Larry Meadors
[mailto:[EMAIL PROTECTED]Sent: Wednesday, September 29,
2004 10:22 AMTo: [EMAIL PROTECTED]Subject: Re: DB
Connections with Axis
Why? If it is using JNDI, it should still be OK, no?
I'm not sure. Right now it defines a
connection per directory in the webapps dir.
Chris
-Original
Message-From: Larry Meadors
[mailto:[EMAIL PROTECTED]Sent: Wednesday, September 29,
2004 10:22 AMTo: [EMAIL PROTECTED]Subject: Re: DB
Connections with Axis
Why?
Why? If it is using JNDI, it should still be OK, no?
Larry>>> [EMAIL PROTECTED] 9/29/2004 8:09:42 AM >>>
I'm migrating a servlet over to Axis. The current servlet connects using dbpooling as configured in the server.xml file. How do I change this todeploy it to Axis?
I'm migrating a servlet over to Axis. The current servlet connects using db
pooling as configured in the server.xml file. How do I change this to
deploy it to Axis?
Chris
Thanks for the help guys, it seems likely that the problem is actually
coming from a proxy between the client and the web service container (a
server side proxy rather than a client side firewall, we have quite a
complex server setup here)
Cheers,
Tom
Davanum Srinivas wrote:
Here's one more -
h
Here's one more -
http://nagoya.apache.org/wiki/apachewiki.cgi?AxisProjectPages/AxisCommonsHTTP
-- dims
On Thu, 15 Jul 2004 12:49:07 +0100, Tom Oinn <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> We were at one point able to invoke calls on an axis server (from an
> axis client) with call durations in
See http://www.mail-archive.com/[EMAIL PROTECTED]/msg18632.html
-- dims
On Thu, 15 Jul 2004 12:49:07 +0100, Tom Oinn <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> We were at one point able to invoke calls on an axis server (from an
> axis client) with call durations in the order of an hour. Now we ha
Daniel Perry wrote:
I've recently been doing a bit of work involving another companies web
service, and thanks to their non-existent use of integer primary keys (or
for that matter any indexes) and the greatness that is MS's server products,
it takes it about half an hour to return some XML data.
S
mply doing:
call.setTimeout(new Integer(60*60*1000));
Set's axis's timeout to an hour, and solved our problems.
Daniel.
> -Original Message-
> From: Tom Oinn [mailto:[EMAIL PROTECTED]
> Sent: 15 July 2004 12:49
> To: [EMAIL PROTECTED]
> Subject: Long running connectio
Hi all,
We were at one point able to invoke calls on an axis server (from an
axis client) with call durations in the order of an hour. Now we have a
timeout (with a deeply unhelpful error message of '(0)null') after two
minutes. One of my colleagues has tracked this down to being related to
the
Hi,
I have a few question related to Axis and HTTP 1.1
Does Axis 1.1 support HTTP 1.1, more specifically
persistent connections and pipelines?
I can see from earlier posting to this group that you
are recommended to use the Commons HTTPClient library
to use the HTTP 1.1 connection control
I deployed a web service with axis 1.1 on tomcat 4.1
Now I'm experimenting https connections: I used keytool utility in this way:
keytool -genkey -alias tomcat -keyalg RSA
then I changed the URL of invocation of the ws, and it works.
The problem is that now my web service works both wit
y mind about this.
Anyway, I appreciated very much the help you all gave me.
Thank you.
Bye,
Matteo.
> -Messaggio originale-
> Da: Wang, Pengyu [IT] [mailto:[EMAIL PROTECTED]
> Inviato: mercoledì 5 novembre 2003 16.24
> A: [EMAIL PROTECTED]
> Oggetto: RE: Too many CLOSE_WAIT so
ocket connections
I got the solution!
The problem is not related to a timeout parameter. I think that each open
socket should be closed...
but, looking through the sources, I can't find where the axis client side
library closes the socket used to speak with the axis server.
If a process does
iginale-
> Da: Wang, Pengyu [IT] [mailto:[EMAIL PROTECTED]
> Inviato: lunedì 3 novembre 2003 15.54
> A: '[EMAIL PROTECTED]'
> Oggetto: RE: Too many CLOSE_WAIT socket connections
>
> By default java.net package of HttpURLConnection is using
> Http1.1 which is ke
eem to see the
obvious
effect if the above two have been set.
-Original Message-
From: Matteo Tamburini [mailto:[EMAIL PROTECTED]
Sent: Saturday, November 01, 2003 9:53 AM
To: [EMAIL PROTECTED]
Subject: R: Too many CLOSE_WAIT socket connections
Mike, thank You for your answer.
I'm u
ay, Monday I'll try to reduce significantly this parameter, then I'll
let you know.
Any more idea?
In the meantime, thank you Mike.
Bye,
Matteo.
> -Messaggio originale-
> Da: Mike Burati [mailto:[EMAIL PROTECTED]
> Inviato: venerdì 31 ottobre 2003 20.01
> A: &#x
--
From: Matteo Tamburini [mailto:[EMAIL PROTECTED]
Sent: Friday, October 31, 2003 1:56 PM
To: [EMAIL PROTECTED]
Subject: Too many CLOSE_WAIT socket connections
Hi.
I've got a thread (axis client) which calls an axis web service several
times (some thousands).
My client code creates the Service
norSyncClient.java:325)
at
it.matteo.SyncWorkers.DonorSyncClient.run(DonorSyncClient.java:201)
Using "netstat" I can see in the client lots (about one thousand) open
socket connections in CLOSE_WAIT state. It seems that terminating this ws
client process makes the OS allowed to correct
Subject: RE: Maximum Connections
I
think you need to look at the server side of your configuration (JBoss - the
web server component - Tomcat or Jetty?). Most likely it is refusing
connections once a certain number are being handled
concurrently.
Keith
Title: Message
I
think you need to look at the server side of your configuration (JBoss - the web
server component - Tomcat or Jetty?). Most likely it is refusing connections
once a certain number are being handled concurrently.
Keith
-Original Message-From: E.Narayanan
Title: Message
Hi,
I have an Axis Web service
hosted on Jboss. For performance testing I had made a
java client which creates threads and makes webservice
calls. The calls were using the proxies generated from wsdl2java.It worked
fine with 100 and 200 threads. When I tried with 300 thr
I will take a look at the latest release candidate and report my findings.
Thanks for the help.
Kevin
-Original Message-
From: Norris Merritt [mailto:[EMAIL PROTECTED]
Sent: Monday, March 17, 2003 4:36 PM
To: Davis, Kevin; '[EMAIL PROTECTED]'
Subject: RE: HTTP Connections Hang
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:
: Norris Merritt [mailto:[EMAIL PROTECTED]
Sent: Monday, March 17, 2003 4:15 PM
To: '[EMAIL PROTECTED]'
Cc: Davis, Kevin
Subject: RE: HTTP Connections Hanging
I believe that Axis client code relies on the remote web server to close the
connnection. The XML response from the SOAP server i
MAIL PROTECTED]
Sent: Monday, March 17, 2003 11:48 AM
To: '[EMAIL PROTECTED]'
Subject: RE: HTTP Connections Hanging
I took some time to look through the code and I can see the places where the
problems may be, but, like the comments state, is InputStream.close() being
called? Also, how do we
questions
answered.
Kevin
-Original Message-
From: Davis, Kevin
Sent: Monday, March 17, 2003 1:23 PM
To: '[EMAIL PROTECTED]'
Subject: RE: HTTP Connections Hanging
I'm surprised too, but trying to patch it is just not an option for me here.
So I guess someone with some more ti
this as a
major issue with anyone doing any real work with Axis.
I'll take a look at the code and see what I can come up with.
Kevin
-Original Message-
From: Brian Ewins [mailto:[EMAIL PROTECTED]
Sent: Monday, March 17, 2003 1:02 PM
To: [EMAIL PROTECTED]
Subject: Re: HTTP Connection
ch 14, 2003 1:19 PM
To: '[EMAIL PROTECTED]'
Subject: RE: HTTP Connections Hanging
I think much of the issue I'm having is around the bug pertaining to
Xerces/Axis still holding the connection open to ensure that all the bytes
have been recieved. But it does sound similar, but
Anyone else have any suggestions, workarounds for this?
Kevin
-Original Message-
From: Davis, Kevin
Sent: Friday, March 14, 2003 1:19 PM
To: '[EMAIL PROTECTED]'
Subject: RE: HTTP Connections Hanging
I think much of the issue I'm having is around the bug pertaining to
Xe
Davis, Kevin wrote:
I think much of the issue I'm having is around the bug pertaining to
Xerces/Axis still holding the connection open to ensure that all the bytes
have been recieved. But it does sound similar, but I'm letting Axis do all
the socket stuff.
I am not involved with troubleshooting
PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Friday, March 14, 2003 11:35 AM
To: [EMAIL PROTECTED]
Subject: Re: HTTP Connections Hanging
I ran into a similar problem using Weblogic while doing some low-level TCP
socket communications. It turns out that whenever a socket timeout occured
I was ha
ECTED]> cc: (bcc: Kevin Bedell/Systems/USHO/SunLife)
03/14/2003 10:53 AM Subject: HTTP Connections Hanging
I've been looking through the past messages and the Apache Axis bugzilla
database and it appears that the issue surrounding HTTP Connections
"hanging" is a known issue. What is the easiest way to get around this
issue?
I'm expieriencing some rather interesting problems
is essentially hard-coded for
HTTP/1.1.
Betsy
-Original Message-From: Norris Merritt
[mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 04,
2003 11:41 AMTo: '[EMAIL PROTECTED]'Subject: RE:
Keep-alive SOAP connections are disabled in Axis; Axis hangs if they
TP is handled by the
servlet engine, and HTTPSender.java isn't used at all.
-Original
Message-From: Betsy Frey
[mailto:[EMAIL PROTECTED]]Sent: Tuesday, February 04, 2003 10:02
AMTo: [EMAIL PROTECTED]Subject: RE: Keep-alive SOAP
connections are disabled in Axis; Axis hangs i
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 connections are disabled in Axis; Axis hangs if they are
Title: RE: Keep-alive SOAP connections are disabled in Axis; Axis hangs if they are enabled
Thanks. I think we are talking about two different things: 1) the concept
of SOAP sessions which permits SOAP clients and servers to remember variables
and do things like increment counters across
Title: RE: Keep-alive SOAP connections are disabled in Axis; Axis hangs if they are enabled
The original message describing how to get persistent sessions working was tucked inside a 2002-12-18 message.
1. modify servlet-config.wsdd (see below; a handler, requestFlow, responseFlow).
2
Title: RE: Keep-alive SOAP connections are disabled in Axis; Axis hangs if they are enabled
Hi
Betsy, I looked at the several messages posted by Sebastian on 12/17 but didn't
find the changes you referred to. I would appreciate it if you would forward
that message to me. Re Chen'
Title: RE: Keep-alive SOAP connections are disabled in Axis; Axis hangs if they are enabled
I think the problem of non-persistent connections only shows up if you're using HTTP/1.1.
I'm seeing persistent connections, with no hang (because I'm using an Axis server), without
ple, clearProperty has become removeProperty, etc). Here are the updated
> files. Forgive me for making the braces line up :-)
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, January 28, 2003 9:54 AM
> To: [EMAIL PROTECTED]
> Subject: Re: K
nuary 28, 2003 9:54 AM
To: [EMAIL PROTECTED]
Subject: Re: Keep-alive SOAP connections are disabled in Axis; Axis
hangs if they are enabled
Norris
Thanks much for your reply and great analysis. I also would have thought
that it is a much bigger issue than the responses seem to indicate.
Bill
[
ient:
1) org.apache.axis.transport.http.HTTPSender.java deliberately generates a
Connection:close header even if HTTP 1.1 is set, which prevents connections
from being maintained. A comment in the code implies this is deliberate,
perhaps to fix the hang I discovered (described below). Commenting out the
line 334 elimin
Implement your own SSLSocketFactory with a Socket Pool. I don't
know any other way around this.
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Gesendet: Donnerstag, 16. Januar 2003 19:16
An: [EMAIL PROTECTED]
Betreff: Keep-alive SSL Web Service connec
Yeapp, I implemented my own socketfactory. I'm caching the SSL sockets
myself. Other solution may be also possible.
> -Original Message-
> From: ext [mailto:[EMAIL PROTECTED]]
> Sent: 16. January 2003 19:16
> To: [EMAIL PROTECTED]
> Subject: Keep-alive SSL Web
I am designing a web service based application the will require a work
flow of web service calls. SSL will be used for transport security. I
am concerned about the SSL handshake overhead if each of the web
service calls use a new SSL connection. I would like reuse the SSL
socket across several
persistent connections and (re)-initiates it on demand.
I just wanted to make sure that no such solution exists,
or someone else is already working on it.
It might also be an interesting patch for the transport package
in general.
So long,
Heiko
On Friday 20 September 2002 16:45, Wayne Yan wrote
[mailto:[EMAIL PROTECTED]]
Sent: 20 September 2002 04:16
To: [EMAIL PROTECTED]
Subject: Re: persistent connections
Heiko--
I'm using Axis for the server and .NET for the client, and when I send
multiple requests from one .NET client to my service, they appear in tcpmon
as one HTTP conne
;hello,
>i am wondering if it is possible to have persistent
>http connections (as specified in http 1.1) with axis.
>
>i was looking through the docs and archives,
>but didnt find an answer.
>
>any suggestions appreciated.
>
>
>thanks in advance,
>heiko
>
>--
&g
hello,
i am wondering if it is possible to have persistent
http connections (as specified in http 1.1) with axis.
i was looking through the docs and archives,
but didnt find an answer.
any suggestions appreciated.
thanks in advance,
heiko
--
Heiko Braun - Entwicklung
Jamba! AG Pfuelstrasse
I read here and there about persistent connections. Is AXIS
using these by default or can I configure for it? Will it
improve performance?
]
www.hermes-softlab.com
--
> -Original Message-
> From: Ken Weiner [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, February 26, 2002 12:08 AM
> To: [EMAIL PROTECTED]
> Subject: Re: connections
>
>
> Gus,
>
> One thing you
February 25, 2002 1:17 PM
Subject: connections
> All the examples default to localhost:8080 how can I change that to a
> different port on the client examples. I know that you are supposed to
> user the Options class, but not quite sure if there is a value=pair
> parameter I need to m
All the examples default to localhost:8080 how can I change that to a
different port on the client examples. I know that you are supposed to
user the Options class, but not quite sure if there is a value=pair
parameter I need to map the url to a different one? any ideas, thanks in
advance.
-Gus
59 matches
Mail list logo
