Re: (resend) RE: mod_ssl

2007-12-14 Thread Mads Toftum
On Thu, Dec 13, 2007 at 09:50:46PM -0500, Hammer, Tim wrote: I am attempting to upgrade httpd from 1.3.x to 2.2.x for our web application. I have managed to get everything building and working, ... As you can see, the call from mod_ssl.so into the buckets/ code is passing a null pointer.

Re: Connection Pool Module

2007-12-14 Thread Nick Kew
On Fri, 14 Dec 2007 08:35:12 -0500 Mike O'Leary [EMAIL PROTECTED] wrote: I am looking to write an Apache module that maintains a pool of socket connections to a back-end server. mod_proxy does that. Alternatively, you could look at mod_dbd, which maintains a pool of database connections. --

Re: Specifying a different target directory for APXS

2007-12-14 Thread Subra A Narayanan
Hello folks, Has anyone come across a similar situation before? Can a target folder be specified or is that not possible? Any help is greatly appreciated. Subra On Dec 13, 2007 12:05 PM, Subra A Narayanan [EMAIL PROTECTED] wrote: Hello folks, I use the following command to compile my

RE: (resend) RE: mod_ssl

2007-12-14 Thread Hammer, Tim
On Thu, Dec 13, 2007 at 09:50:46PM -0500, Hammer, Tim wrote: I am attempting to upgrade httpd from 1.3.x to 2.2.x for our web application. I have managed to get everything building and working, ... As you can see, the call from mod_ssl.so into the buckets/ code is passing a null

Re: (resend) RE: mod_ssl

2007-12-14 Thread Mads Toftum
On Fri, Dec 14, 2007 at 11:01:09AM -0500, Hammer, Tim wrote: No, I am trying to use the new (2.2.x) mod_ssl with our modules that have been ported from 1.3.x to 2.2.x. However, the port did not convert our modules to use buckets and I am wondering if the new mod_ssl is requiring the content

Re: Specifying a different target directory for APXS

2007-12-14 Thread Subra A Narayanan
Joe, Thanks for ur reply. Let me clarify somethingWhen I said I didnt get any helpful responses, I meant I didn't get any answers as to what is wrong with gcc and why the module was behaving the way it was. Anywayspoint taken.will use apxs for compiling the module. Subra On Dec

Re: Specifying a different target directory for APXS

2007-12-14 Thread Ralf Mattes
On Fri, 2007-12-14 at 08:07 -0500, Subra A Narayanan wrote: Hello folks, Hello folk, your problem has nothing to do with apxs. The .libs directory is created by libtool. You might want to contact the helpful dwellers on the libtool mailing list. Has anyone come across a similar situation

Re: Specifying a different target directory for APXS

2007-12-14 Thread Ralf Mattes
On Fri, 2007-12-14 at 11:05 -0500, Subra A Narayanan wrote: Joe, Thanks for ur response. The reason I wanted to change the target directory was because my apache module is being compiled as one of the components of a much larger makefile. All the other shared libraries generated by this

Re: Specifying a different target directory for APXS

2007-12-14 Thread Subra A Narayanan
Ralf/Joe, Now I am trying to (just) compile my module using apxs and I see this warning *$ /usr/sbin/apxs -c -L /myprj/deps/axis2c/lib -L /myprj/lib/ -l axutil -l axis2_engine -l dl -l pthread -l client -l operations -c /myprj/obj/webservices/mod_my.o /myprj/obj/webservices/dispatcher.o

Re: Specifying a different target directory for APXS

2007-12-14 Thread Nick Kew
On Fri, 14 Dec 2007 16:57:28 -0500 Subra A Narayanan [EMAIL PROTECTED] wrote: PLEASE LEARN TO POST! In particular, don't append someone else's post to yours. Now I am trying to (just) compile my module using apxs and I see this warning *$ /usr/sbin/apxs -c -L /myprj/deps/axis2c/lib -L

Re: Memory issue in apache modules

2007-12-14 Thread Eric Covener
On Dec 14, 2007 6:05 PM, John Zhang [EMAIL PROTECTED] wrote: When my module processes requests, I see a consistent memory increase. It is like the memories were never released. I am using the apr_* functions to allocate memory (most of the time from the request-pool). My understanding is

Re: Memory issue in apache modules

2007-12-14 Thread John Zhang
--- Eric Covener [EMAIL PROTECTED] wrote: It should level out as each thread in the process has had a chance to run and allocate some memory for a range of requests. MaxMemFree can be used to return the heap memory that would otherwise be used by subsequent requests on that thread.

Re: Memory issue in apache modules

2007-12-14 Thread Ray Morris
I am using the apr_* functions to allocate memory (most of the time from the request-pool). If there are few places where you allocate from othr than the reqquest pool, I'd look at those first. -- Ray B. Morris [EMAIL PROTECTED] Strongbox - The next generation in site security: