mod_jk or jk2??

Hello everyone, I see lots of posts saying that they are using or implementing jk2? For what I understand, that has been replaced by mod_jk... so which one is better or what is recommended?? I also have found better documentation related to jk2 so that adds to the puzzle. Regards, Luis

RE: mod_jk or jk2??

I thought the jk2 is newer... but I can be wrong... MC From: Luis Torres [EMAIL PROTECTED] Reply-To: Tomcat Users List tomcat-user@jakarta.apache.org To: Tomcat Users List tomcat-user@jakarta.apache.org Subject: mod_jk or jk2?? Date: Wed, 03 Aug 2005 13:47:42 -0500 Hello everyone, I see

Re: mod_jk or jk2??

You want to use mod_jk. JK2 has been deprecated and is no longer in active development. On 8/3/05, MC Moisei [EMAIL PROTECTED] wrote: I thought the jk2 is newer... but I can be wrong... MC From: Luis Torres [EMAIL PROTECTED] Reply-To: Tomcat Users List tomcat-user@jakarta.apache.org

Re: where to put request.registerRequests=false when using mod_jk (not jk2)

Thanks a lot bill!!! Bill Barker wrote: Emerson Cargnin [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] I'm running out of memory with the msg: ... WARNING: Error registering request May 25, 2004 5:36:44 PM org.apache.tomcat.util.threads.ThreadPool$ControlRunnable run SEVERE: Caught

Re: where to put request.registerRequests=false when using mod_jk (not jk2)

AFAIK, most os the attributes used in jk2.properties as related to mod_jk2. What other attributes can be used to configure later mod_jk? Thanks Bill Barker wrote: Emerson Cargnin [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] I'm running out of memory with the msg: ... WARNING: Error

where to put request.registerRequests=false when using mod_jk (not jk2)

I'm running out of memory with the msg: ... WARNING: Error registering request May 25, 2004 5:36:44 PM org.apache.tomcat.util.threads.ThreadPool$ControlRunnable run SEVERE: Caught exception (java.lang.OutOfMemoryError) executing [EMAIL PROTECTED], terminating thread May 25, 2004 5:37:05 PM

Re: where to put request.registerRequests=false when using mod_jk (not jk2)

Just to add, even when not getting out of memory, my catalina.log shows: ay 26, 2004 3:44:35 PM org.apache.jk.common.HandlerRequest invoke INFO: Unknown message 0 May 26, 2004 3:44:36 PM org.apache.jk.common.HandlerRequest invoke INFO: Unknown message 0 May 26, 2004 3:44:37 PM

Re: where to put request.registerRequests=false when using mod_jk (not jk2)

At this moment I have 5492 times the line WARNING: Error registering request at my catalina log maybe this could be the cause of the memory leak? In mod_jk, how do I solve this? in jk2 the solution is to add the request.registerRequests=false in jk2.properties I have an upgraded

Re: where to put request.registerRequests=false when using mod_jk (not jk2)

Does anyone could comment on that?? For what I saw the changelog of 5.0.25, there ins't any change in this field... At this moment I have 5492 times the line WARNING: Error registering request at my catalina log maybe this could be the cause of the memory leak? In mod_jk, how do I solve

Re: where to put request.registerRequests=false when using mod_jk (not jk2)

Emerson Cargnin [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] I'm running out of memory with the msg: ... WARNING: Error registering request May 25, 2004 5:36:44 PM org.apache.tomcat.util.threads.ThreadPool$ControlRunnable run SEVERE: Caught exception