Theo Schlossnagle wrote:
I haven't had the time lately, but you (all) are welcome to dissect the
mod_backhand (Apache 1.3) module and pull the resource collection and
decision making framework out and put in into mod_proxy for Apache 2.
I have been watching the commits to proxy, but haven't yet
Pier Fumagalli wrote:
What's wrong with:
ProxyPassReverse / http://localhost:/
ProxyPreserveHost On
RewriteMap hosts rnd:/opt/apache/conf/tables/hosts.map
RewriteRule "^/(.*)" "${hosts:live}/$1" [P,L]
It isn't very elegant though. Someone who is well versed in mod_rewrite
and regular expressio
William A. Rowe, Jr. wrote:
Since it will take some time to assess that the changes and new features
are stable, v.s. dev quality, I believe it's sorta pointless to put extra energy
into the 2.0 backport. We won't compromise mod_proxy again in 2.0 after
its very slow crawl to some measure of stab
Remy Maucherat wrote:
Q: is there session stickiness in HTTP ?
As I understood from the commits, stickiness is part of balancer, and
balancer is protocol independant, which would make the answer yes.
Am I understanding correctly?
Regards,
Graham
--
smime.p7s
Description: S/MIME Cryptographic Si
William A. Rowe, Jr. wrote:
That's something of a shame, because we lose the development
history importing the finished effort, and it was further disappointing
that you didn't bring across the earlier cvs history so this branch
could be brought back into httpd/modules/proxy with a complete
history
[EMAIL PROTECTED] wrote:
Bounding to client connection is not needed(?).
Since AJP can serve multiple request trough the same
backend connection, no need to create separate conn_rec.
For now comment out all the set/get module config.
Is there still a reason why in proxy_http the backend con
Mladen Turk wrote:
I've finished the connection pool for mod_proxy.
The proxy_http now uses the connection pool (cca 10% speedup for HTTP1.0,
the 1.1 should be even higher, but the ab doesn't support 1.1).
If someone is willing to test and chase the bugs, he's more then welcome :).
Cool bananas! Po
Mladen Turk wrote:
IMO we could perhaps use exiting Proxy:
BalancerMember ajp://host1:port [balancer params]
etc...
Or..
BalancerMember http://host1:port [balancer params]
etc ...
I just looked at the manual for - it defines config that is
common to a particular part of the URL sp
Mladen Turk wrote:
The removed proxyhost and port are from new hook 'pre_request' that is used
to obtain a valid worker and/or balancer for a scheme.
It has nothing to do with the way the connection is going to be made.
Cool, this makes sense.
The load balancer if present will decide to which route
[EMAIL PROTECTED] wrote:
Log:
Remove proxyhost and proxyport from pre_request hook.
They are not needed for finding apropriate worker.
Reading this again, I see better what is happening.
The proxyhost and proxyport are used when a downstream proxy is used,
would the balancer ever want to bal
[EMAIL PROTECTED] wrote:
Log:
Remove proxyhost and proxyport from pre_request hook.
They are not needed for finding apropriate worker.
They are needed for the use of mod_proxy as a forward proxy.
The correct way of handling these in the AJP case is to DECLINE the
request if proxyhost and pro
Mladen Turk wrote:
Here is what I meant:
ProxyPass /url balancer:number//[stickysessionname | none]/[nofailover]
ProxyRemote balancer:number ://host-1(lbfactor)
ProxyRemote balancer:number ://host-2(lbfactor) ...
ProxyRemote balancer:number ://host-n(lbfactor)
And (eventually) ...
ProxyPassReverse
[EMAIL PROTECTED] wrote:
Allow parsing lbfactor for ProxyPassReverse in the form
ProxyPassReverse scheme://uri/path(lbfactor).
The lbfactor is number 1...100 inside braces.
Just a quick note - ProxyPassReverse is for dealing with the conversion
of Location headers from the backend to the fro
Costin Manolache wrote:
Hard == replicating the configuration data to all the nodes, instead of
having it in a central place ( file or a config server ). Not
impossible, but it's a different problem, and not very commonly used
Ldap, nis, ldap and most other "config servers" are using the later.
T
[EMAIL PROTECTED] wrote:
First try to get proxy using ajp (Note that is for httpd-2.1).
Couple of comments (realising this is first try code):
/*
* Canonicalise http-like URLs.
* scheme is the scheme for the URL
* urlis the URL starting with the first '/'
* def_port is the de
Costin Manolache wrote:
So if someone breaks in one node, he has the entire pool :-)
If someone breaks into one node, then they very likely have access to
any backend databases anyway. Being able to manipulate the pool is the
least of your worries. But it's a valid concern nonetheless.
I don't k
Costin Manolache wrote:
I just hope you agree that having cluster info in httpd.conf is the
worst possible solution - you have all the control access problems, you
need to gracefully restart often, it is very hard to automate and use
tools to manage it, etc.
I 100% agree with this statement, yes
Henri Gomez wrote:
Well using an URL could be a good idea, since it could be :
- a static file, edited by admin, on the web-server or
another web-server/tomcat
- a dynamically generated file, PHP/JSP/Servlet/PERL, whatever.
An URL is a logical solution, which leaves us with two choices:
- A speci
Costin Manolache wrote:
Httpd already has some support for that - .htaccess for example
The trouble with .htaccess is that it only applies for data on the local
filesystem. Url space created by other content handlers (such as proxy
or ajp) is not covered.
You're assuming that the tomcat admin ha
Costin Manolache wrote:
Well, you may keep the discussion separated, but the code will
eventually be mixed.
Eventually, but keeping each thing logically separate makes it easy to
see where one feature might impact another. The devil with this is in
the details, and I don't want to see important
Filip Hanik (lists) wrote:
why are we so focused on dynamic this dynamic that,
This thread is focused on the dynamic features, and was split out from
the thread on the new work on ajp. Whether we do the dynamic features
now or later isn't important, what is important is that any discussion
happe
Costin Manolache wrote:
1.
- add a new worker to a pool ( for example - expect big load, you buy
more hardware, etc ).
- gracefully remove a worker ( for upgrade for example ) - the
implication is that sticky sessions will still go, no new sessions.
- change parameters of a worker ( like balanc
Mladen Turk wrote:
If I make a design flaw, and the entire project gets unusable, it will make
it just something like mod_java, mod_warp, mod_jk and mod_jk2 are... Dead.
Nobody will get hanged for that.
Some code is always better than no code - at best, the code will be good
enough to fit the need
Hi all,
I am starting a new thread for this, as it seems to be an important
killer-app feature for any httpd v2.0 integration.
People have said the config should be dynamically configurable - which
part of the config should be dynamically configurable?
In other words, would any of these senario
Henri Gomez wrote:
Peace on ASF :)
Indeed :)
well mod_ajp will probably goes a bit farther than mod_proxy + proxy_ajp
since mod_proxy will allways relay static configuration, ie map some
knowns URL to knowns Tomcat.
Why would mod_proxy always rely on a static configuration?
Don't forget that a lo
Remy Maucherat wrote:
I think very few people are actually using mod_proxy instead of mod_jk.
You've got to back your assertion with some kind of numbers, otherwise
it's FUD.
As do you. The assertion was based on comments on this mailing list, but
we've already established that there is a need f
Remy Maucherat wrote:
The framework itself could be designed in a way which would end up
hurting performance. It did happen in Tomcat in the past, and I don't
know about mod_proxy since I haven't looked at it, but it could happen.
All the framework does is determine that a proxy handler is respon
Remy Maucherat wrote:
Until I'm shown a mod_proxy (with HTTP) with performance close to
mod_jk, my opinion is that we can't use it.
As I've pointed out already, mod_proxy is a framework. The performance
numbers quoted tested mod_proxy_http, not mod_proxy, which doesn't do
anything on it's own.
Mladen Turk wrote:
Yes, that's the general idea.
We focus on v2.0 and TCP/IP protocol (for now).
Cool.
Well, the development will not be over in 2 days, and the plan is to use
mod_ajp as a base for testing new protocol extensions, and to be always a
little bit faster and better then mod_proxy with
Mladen Turk wrote:
Some rationale:
I spoke with Henri and we decided that although mod_proxy with proxy_ajp is a
good idea (in the long term... very long term), we need something that will
fill in the gaps.
As there is an existing codebase, getting a module together that
supports Apache v2.0 nativ
Mladen Turk wrote:
If you turn the loglevel to debug then there is no error messages (although
everything is by the order of magnitude slower), so the closing algorithm is
correct.
The problem is IMHO that you are using a socket (presuming it is free) still
served by the bucket brigade, but I may b
Fernando R. Torrijos wrote:
Please help me to unsubscribe me from the tomcat and
relatives forum. I already send a lot of mails to the
mayordomo with the words unsubscribe but im still
receiving mail. Please help me.
Please follow the instructions at the bottom of the emails you have
received, whi
Mladen Turk wrote:
OS error 10048 means:
Typically, only one usage of each socket address (protocol/IP address/port) is
permitted. This error occurs if an application attempts to bind a socket to an
IP address/port that has already been used for an existing socket, or a socket
that was not closed p
Mladen Turk wrote:
We had a same problen in jk for over two years now. The problem is that you
will need at least:
Line 1037 in proxy_util.c:
/* make the connection out of the socket */
do {
rv = apr_socket_connect(*newsock, backend_addr);
} while (APR_STATUS_IS_
jean-frederic clere wrote:
Not for each request but each time http makes a new connection to Tomcat.
We have to cache the result of apr_sockaddr_info_get().
Added to bugzilla as a request for enhancement (so this doesn't fall
through the cracks).
Regards,
Graham
--
smime.p7s
Description: S/MIME
Mladen Turk wrote:
/* make the connection out of the socket */
do {
rv = apr_socket_connect(*newsock, backend_addr);
} while (APR_STATUS_IS_EINTR(rv));
One further question (I am not 100% clued up on the workings of apr's
socket handling) - would a situation ev
Mladen Turk wrote:
All are exactly the same:
[error] (OS 10048)Only one usage of each socket address (protocol/network
address/port) is normally permitted. : proxy: HTTP: attempt to connect to
127.0.0.1:8080 (localhost) failed
Ok.
We had a same problen in jk for over two years now. The problem is
Remy Maucherat wrote:
> DNS lookup failure for: pgtr0327.mch.fsc.net returned by
^^
It's not normal there's a DNS lookup on each request. Why does it happen ?
In the config it was set to connect to a DNS name, which has to be
resolved - but httpd doesn't do any caching of this (
jean-frederic clere wrote:
I also I have some (40) errors with concurrency 300 but Tomcat and
Apache are in 2 different machines:
+++
[Thu Jul 22 11:39:39 2004] [error] [client 172.25.182.35] proxy:
> DNS lookup failure for: pgtr0327.mch.fsc.net returned by
^^
/examples/servlet/H
Mladen Turk wrote:
BTW, the errors reported comes from mod_proxy.
What are the errors though, and do they come from mod_proxy or
mod_proxy_http?
It would be a huge help to the people using proxy (ie for non tomcat
related stuff) if we could find and fix these error conditions under load.
Regard
Henri Gomez wrote:
- I'm using ab (ApacheBench) and wonder if the -k (keep alive)
if HTTP keep-alive is really used ?
- Did mod_proxy keep a connection cache ?
Proxy's HTTP module will reuse the same connection from previous
connections if keepalives are being used, it doesn't keep a connection
Remy Maucherat wrote:
It's cool to have one less thing to configure, but it seems to me
jvmRoute is the most reliable and efficient way of doing stickiness
Can you describe the jvmRoute method to me?
(the
cookie way is intrusive, and the IP way is highly inaccurate).
I agree on the IP way being i
Tim Funk wrote:
I'm not sure of the status so far, but I'd like to summarize a strawman.
I have no idea how to code this at this time or if it can be done.
No problem, we drill down into the details as we go along :)
*Config* [Feel free to change the names]
ProxyClient http://server1/config.xml
Pr
Filip Hanik - Dev wrote:
I suppose in this case the load balancer would run HOOK_MIDDLE, and
sticky would run HOOK_LAST.
cool, and then have the server just try them in that order? ie, if the sticky server
went down, it just takes the next one from the
list (and that list should be ordered well s
Mladen Turk wrote:
Yes, but why would you wish to separate those?
Because they are two separate behaviours that could quite easily be used
independantly of each other.
I would probably use the stickiness long before I started messing around
with load balancing.
I'm not that familiar with mod_pr
Mladen Turk wrote:
Ok, just wanted to clear if we are going to make another compromise :),
since sticky sessions are tightly coupled with the load balancer itself and
the way it decides the client route.
In theory sticky sessions shouldn't be tightly coupled like this - it
should be a case of "pla
Costin Manolache wrote:
But I still think we should start with using mod_proxy with http
protocol, and add the missing load balancing and extra info - if we are
not happy with the performance and we need a small boost, we could also
add ajp.
I think this is a good idea.
Solve the general load ba
Costin Manolache wrote:
One thing missing - the proposal to actually just use mod_proxy, with
enhancements for load balancing, and with http as protocol ( i.e. drop
Ajp ).
That would be a real simplification on both sides !
I also find HTTP to be more than adequate in most cases, but if there is
Mladen Turk wrote:
AjpBalancer could be applied to a theoretical proxy_balancer module (all
modules can define their own config parameters, even the helper modules,
the only guideline is that the config directives are named to give some
indication of the scope they're valid for, so instead of a
Mladen Turk wrote:
I think that we forked from jk/jk2 to be able to write from the scratch the
module that will do exactly _one_ and _only_one_ thing; and that is
effectively communicate with TC server using ajp13+ protocol.
So, my question is. Why do we need again some container to accomplish that
jean-frederic clere wrote:
I see in ap_proxy_http_handler() that DECLINED allows to try another. Is
there somewhere an example of a configuration using it?
ap_proxy_http_handler() is found in mod_proxy_http, which is the helper
module that handles the HTTP protocol in the proxy framework. You wil
Mladen Turk wrote:
I think it's very necessary - sharing those common concepts
ultimately makes for doing things in a consistent way. It
makes a big difference to the usability of httpd.
I'm sure that the 'normalization' would lead to nowhere.
I don't follow - what does "normalisation would lead
Henri Gomez wrote:
BTW, could we expect to be able to use in proxy_ajp URL like
ajp://VIRTUALNAME, where VIRTUALNAME could be the name of an
AJP cluster backend ?
That would be up to proxy_ajp to decide, so yes.
What happens is that when the config says
ProxyPass /myApp ajp://VIRTUALNAME
and the us
Mladen Turk wrote:
I don't think that it is necessary for a mod_ajp to be included inside the
mod_proxy, although they are sharing some common concepts.
I think it's very necessary - sharing those common concepts ultimately
makes for doing things in a consistent way. It makes a big difference to
Colm MacCarthaigh wrote:
Using OPTIONS has the advantage of being backwards compatible, if you
send OPTIONS to a plain-old HTTP receiver, the standard ACK can be
taken to mean "yep, I'm here". Intelligent backends (read: modify
tomcat and co slightly) can have an X-header or whatever to go
"I'm acc
Henri Gomez wrote:
- mod_proxy + proxy_ajp could be one solution.
Now what about the mod_proxy load-balancing add-on ?
Would be a completely separate module.
The way proxy works, is that it:
- obtains the IP address to connect to (currently via DNS round robin,
but a module proxy_loadbalancer migh
Henri Gomez wrote:
Well let see my suggestion :
ProxyPass /myWebapp/*.jsp ajp://myajpworker/
myajpworker is not a machine but a virtual resource which could be :
- a physical Tomcat using its AJP/1.3 connector
- a cluster of physical Tomcats using their AJP/1.3 connector
And via AJP/1.4 we could ma
Remy Maucherat wrote:
I think AJP has advantages, but if the HTTPd folks only accept a simple
solution based on mod_proxy, then so be it, it'll be our entry level
connector.
We'll certainly be interested in features like load balancing, sticky
sessions, stuff like that - but the general design p
Henri Gomez wrote:
It's now time to refactor and redesign it with Apache 2.x (APR/AP) in
mind to follow Apache 2.x admins habbits and try to make something
simpler.
We came on httpd-dev for advice from experts, and may be an
extended mod_proxy could be the solution. But we also want to keep
the AJP
Henri Gomez wrote:
jk was designed a long time ago so may be mod_proxy allready support
persistant connections.
Persistence will happen on the backend on the condition there was
persistence on the frontend. Generally the networks between backend and
frontend are fast enough that connection setup
Henri Gomez wrote:
And what about using AJP/1.3 instead of HTTP for connection to tomcat ?)
In all my deployments of tomcat I have never seen the point of a custom
protocol that did exactly what HTTP does, so all my tomcat deployments
are all HTTP, with a simple mod_proxy frontend.
Even the "get
Martin Gainty wrote:
What is this?
Some virus writer's idea of harvesting private information from the
gullible.
Your e-mail account will be disabled because of improper using in next
three days, if you are still wishing to use it, please, resign your
account information.
Regards,
Graham
--
Hi all,
I have been trying to run my HttpUnit test against my webapp running
inside tomcat v4.1.29, and have run into hassles with the webapp
freezing after a certain number of requests.
After a certain number of requests have been received, tomcat refuses to
serve any more URLs from within th
Hi all,
I have a web application that is password protected against a postgres
database, defined like so:
For normal users logging in, this works fine.
If however, a user in the postgres database has their password field set
to "null", and an attempt is made to log in as this user using any
Hi all,
I have been using tomcat v4.1.27 for a while, hosting some web
applications without any notable reliability hassles.
Along comes a new application - this app uses the database pool feature
of tomcat. While this application is deployed, tomcat refuses to stay
operational for more than a
Hi all,
I have been following the JNDI Datasource HOW-TO published at
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples-howto.html,
to try and create a postgresql database pool, and a basic authentication
realm associated with it.
The docs say the config is untested - an
Hi all,
I got no response from the user list, so I'm reposting this here.
After upgrading my system (but not my Blackdown JDK v1.3.0 nor my Tomcat
v4.0.1) Tomcat suddenly refuses to start. The following exception is
thrown on startup in catalina.out:
ERROR reading /var/tomcat4/conf/server.xml
67 matches
Mail list logo
