Tomcat and URL rewriting

2003-09-09 Thread James Courtney
Does tomcat support ANY URL rewriting functionality similar to Apache's mod_rewrite 
but using stand alone Tomcat 4.1.24 without Apache?  Many thanks!

Jamey


RE: which jk2 to use

2003-07-15 Thread James Courtney
I've had problems with the 4.1.24 src release occasionally losing communication with 
the Tomcat.  I haven't fully debugged these yet but I'm suspicious of it.  I've also 
heard from others that the releases of mod_jk and mod_jk2 to use are those released 
with the connectors project, not with Tomcat.  Thus I'd suggest the 2.0.2 release of 
mod_jk2 though I'm in the process of testing it and can't tell you that it's 
definitely better.   Another option might be mod_jk 1.2.4 which I'm also trying out in 
hopes of solving my 4.1.24 mod_jk2 problems.  Best of luck.

Jamey

-Original Message-
From: Nicolas [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 15, 2003 5:37 PM
To: [EMAIL PROTECTED]
Subject: which jk2 to use


hi

there is a jk2 offered in the dir of tomcat-4.1.24
http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.24/src/jakarta-tomcat-connectors-4.1.24-src.tar.gz
but there is also a release of 2.0.2
http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/release/v2.0.2/src/jakarta-tomcat-connectors-jk2-2.0.2-src.tar.gz

in general which one is to use for produktion ?

regards nicolas


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



FW: Could you give some help for me (about mod_jk for solaris 9)

2003-07-10 Thread James Courtney
I figured this might be useful to this group...

Jamey


James Courtney
InPhonic, Inc.

-Original Message-
From: James Courtney 
Sent: Wednesday, July 09, 2003 11:33 PM
To: Tomcat Developers List
Cc: [EMAIL PROTECTED]
Subject: RE: Could you give some help for me (about mod_jk for solaris 9)


This worked for me on Solaris 8 this evening:

Make sure you have properly compiled and installed Apache 2.x and Tomcat 4.1.24.  
We'll call these installation directories apache2.home and tomcat4.home.

Also make sure you have recent versions of m4, automake, and autoconf installed from 
www.sunfreeware.com.

Set the environment variable M4 to the location of your GNU m4 executable.

For example in bash: export M4=/usr/local/bin/m4

Download jakarta-tomcat-connectors-jk-1.2.4-src.tar.gz from
http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.4/src/
and extract it to some directory, well call it jk.build.

cd ${jk.build}/jk/native

execute buildconf.sh

execute ./configure --with-apxs=${apache2.home}/bin/apxs

execute make

Locate mod_jk.so from the ${jk.build}/jk/native/apache-2.0 directory and copy it to 
your ${apache.home}/modules directory.  Just add the line
LoadModule jk_module ${apache.home}/modules/mod_jk.so
to your ${apache.home}/httpd.conf file and follow the configuration instructions for 
httpd.conf and workers.properties given at
http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.4/doc/.

Good luck!

Jamey


-Original Message-
From: David Choi [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 09, 2003 2:40 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Could you give some help for me (about mod_jk for solaris 9)


I have got your E-mai from some forum for tomcat
I am from south korea, and study about JSP and SUN OS.
First, Sorry for my poor english~

I am wondering where and how I can get the mod_jk.so (the
apache module) for connecting tomcat with apache
before, I found jakarta project FTP site but there was not
module(mod_jk.so) for solaris 9(some module for solaris 8 had some
error)

So many time I tried to make mod_jk.so from source file
(jakarta_tomcat_connector 4.1.24) but I couldn't 


Actually, I would like to connect tomcat 4.1.24 with apache 2.X on the
solaris 9 platform. 

Please help me now~

Thanks for your time and efforts~

From YH.Choi
South Korea 



Wishing you all the success in this business, we hope our transaction
makes much better world than before. 

We thank you for your time and efforts
Warm regards,

David Choi
Marketing Manager
SP KOREA Co.,LTD (Tel 82-53-588-0318, Cel 82-16-9775-3900, Fax
82-53-588-0319)
http://www.sp-korea.com http://www.sp-korea.com 
http://www.kacci.net






 http://www.korea.com
http://movie.korea.com/koreamovie/result.asp?genre=1m_id=5725

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



jk2.properties

2003-07-10 Thread James Courtney
Under what circumstances are the properties set in this file relevant?  At least for 
channelSocket they seem to at best be overridden by those in the server.xml for the 
corresponding CoyoteConnector.  I'm using Tomcat 4.1.24.

Jamey


shm and jk2?

2003-07-10 Thread James Courtney
What is the shm segment of the workers2.properties file for?  Is it actually used for 
a pure channel socket/lb configuration?

jk2 2.0.2
Tomcat 4.1.24
Apache 2.0.45

Thanks!

Jamey


RE: jk2.properties

2003-07-10 Thread James Courtney
Thanks Simon.  It's just odd that it's settings don't override what's in server.xml or 
that you can set the same thing both places.  I could see using jk2.properties for 
extended properties specific to each channel type but things like host and port that 
are specified in the server.xml are just confusing to repeat in jk2.properties.  Maybe 
the best approach is, as you say, to just comment the file but leave it there to avoid 
the warning.  Thanks!

Jamey


James Courtney
InPhonic, Inc.

-Original Message-
From: Simon Pabst [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 10, 2003 3:07 PM
To: Tomcat Users List
Subject: Re: jk2.properties


I think you can leave all entries commented when you're using channelSockets,
however when you use channelUnix (fast unix sockets) you need some entries 
in jk2.properties.
(see http://www.pubbitch.org/jboss/mod_jk2.html for details)

At 14:28 10.07.2003 -0700, you wrote:
Under what circumstances are the properties set in this file relevant?  At 
least for channelSocket they seem to at best be overridden by those in the 
server.xml for the corresponding CoyoteConnector.  I'm using Tomcat 4.1.24.

Jamey


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: shm and jk2?

2003-07-10 Thread James Courtney
Let me answer that myself and see if anyone corrects me.

Apache 2.0.45 is still a multiprocess application using the worker module.  Thus, 
presumably eash process has a copy of the mod_jk2 endpoint in memory, all of which 
must remain in sync for certain operations thus requiring the use of shared memory and 
the shm file.

Jamey



-Original Message-
From: James Courtney 
Sent: Thursday, July 10, 2003 3:08 PM
To: Tomcat Users List (E-mail)
Subject: shm and jk2?


What is the shm segment of the workers2.properties file for?  Is it actually used for 
a pure channel socket/lb configuration?

jk2 2.0.2
Tomcat 4.1.24
Apache 2.0.45

Thanks!

Jamey

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Tomcat-4.1.24

2003-07-10 Thread James Courtney
HAH, we just had that problem and fixed it about 5 minutes ago.  Maybe Tomcat should 
check for it's temp directory upon startup and error out in a more informative way if 
it doesn't exist.

Jamey



James Courtney
InPhonic, Inc.

-Original Message-
From: Ray Madigan [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 10, 2003 5:17 PM
To: Tomcat Users List
Subject: RE: Tomcat-4.1.24


Sorry - sometimes we do stupid things- lol

I forgot to create the temp directory in $CATALINA_BASE

Thanks

-Original Message-
From: Ray Madigan [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 10, 2003 1:02 PM
To: Tomcat-User
Subject: Tomcat-4.1.24


I am attempting to move my application over to tomcat 4.1.24 from tomcat
4.0.4 and I get the following error message:

lost of log messages

2003-07-10 12:40:58 WebappLoader[/Main]: Deploy JAR
/WEB-INF/lib/jakarta-oro.jar to
/usr/local/rtizon/webapps/Main/WEB-INF/lib/jakarta-oro.jar
2003-07-10 12:40:58 WebappLoader[/Main]: Deploy JAR
/WEB-INF/lib/jdbc7.1-1.2.jar to
/usr/local/rtizon/webapps/Main/WEB-INF/lib/jdbc7.1-1.2.jar
2003-07-10 12:40:58 WebappLoader[/Main]: Deploy JAR /WEB-INF/lib/jdom.jar to
/usr/local/rtizon/webapps/Main/WEB-INF/lib/jdom.jar
2003-07-10 12:40:58 WebappLoader[/Main]: Deploy JAR /WEB-INF/lib/jstl.jar to
/usr/local/rtizon/webapps/Main/WEB-INF/lib/jstl.jar
2003-07-10 12:40:58 WebappLoader[/Main]: Deploy JAR
/WEB-INF/lib/standard.jar to
/usr/local/rtizon/webapps/Main/WEB-INF/lib/standard.jar
2003-07-10 12:40:59 WebappLoader[/Main]: Deploy JAR /WEB-INF/lib/struts.jar
to /usr/local/rtizon/webapps/Main/WEB-INF/lib/struts.jar
2003-07-10 12:40:59 WebappLoader[/Main]: Deploy JAR
/WEB-INF/lib/xercesImpl.jar to
/usr/local/rtizon/webapps/Main/WEB-INF/lib/xercesImpl.jar
2003-07-10 12:40:59 ContextConfig[/Main] Exception processing JAR at
resource path /WEB-INF/lib/jakarta-oro.jar
javax.servlet.ServletException: Exception processing JAR at resource path
/WEB-INF/lib/jakarta-oro.jar
at
org.apache.catalina.startup.ContextConfig.tldScanJar(ContextConfig.java:930)
at
org.apache.catalina.startup.ContextConfig.tldScan(ContextConfig.java:868)
at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:647)

Has anyone seen this and know why?


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Tomcat-4.1.24

2003-07-10 Thread James Courtney
Also good.  Just something more informative.  Waiting for the class loader to fail 
because the java.io.tmpdir isn't available is not particularly elegant or transparent.

Jamey

-Original Message-
From: Jacob Kjome [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 10, 2003 5:25 PM
To: Tomcat Users List
Subject: RE: Tomcat-4.1.24


How about creating it if it doesn't exist?

Jake

At 05:22 PM 7/10/2003 -0700, you wrote:
HAH, we just had that problem and fixed it about 5 minutes ago.  Maybe 
Tomcat should check for it's temp directory upon startup and error out in 
a more informative way if it doesn't exist.

Jamey



James Courtney
InPhonic, Inc.

-Original Message-
From: Ray Madigan [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 10, 2003 5:17 PM
To: Tomcat Users List
Subject: RE: Tomcat-4.1.24


Sorry - sometimes we do stupid things- lol

I forgot to create the temp directory in $CATALINA_BASE

Thanks

-Original Message-
From: Ray Madigan [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 10, 2003 1:02 PM
To: Tomcat-User
Subject: Tomcat-4.1.24


I am attempting to move my application over to tomcat 4.1.24 from tomcat
4.0.4 and I get the following error message:

lost of log messages

2003-07-10 12:40:58 WebappLoader[/Main]: Deploy JAR
/WEB-INF/lib/jakarta-oro.jar to
/usr/local/rtizon/webapps/Main/WEB-INF/lib/jakarta-oro.jar
2003-07-10 12:40:58 WebappLoader[/Main]: Deploy JAR
/WEB-INF/lib/jdbc7.1-1.2.jar to
/usr/local/rtizon/webapps/Main/WEB-INF/lib/jdbc7.1-1.2.jar
2003-07-10 12:40:58 WebappLoader[/Main]: Deploy JAR /WEB-INF/lib/jdom.jar to
/usr/local/rtizon/webapps/Main/WEB-INF/lib/jdom.jar
2003-07-10 12:40:58 WebappLoader[/Main]: Deploy JAR /WEB-INF/lib/jstl.jar to
/usr/local/rtizon/webapps/Main/WEB-INF/lib/jstl.jar
2003-07-10 12:40:58 WebappLoader[/Main]: Deploy JAR
/WEB-INF/lib/standard.jar to
/usr/local/rtizon/webapps/Main/WEB-INF/lib/standard.jar
2003-07-10 12:40:59 WebappLoader[/Main]: Deploy JAR /WEB-INF/lib/struts.jar
to /usr/local/rtizon/webapps/Main/WEB-INF/lib/struts.jar
2003-07-10 12:40:59 WebappLoader[/Main]: Deploy JAR
/WEB-INF/lib/xercesImpl.jar to
/usr/local/rtizon/webapps/Main/WEB-INF/lib/xercesImpl.jar
2003-07-10 12:40:59 ContextConfig[/Main] Exception processing JAR at
resource path /WEB-INF/lib/jakarta-oro.jar
javax.servlet.ServletException: Exception processing JAR at resource path
/WEB-INF/lib/jakarta-oro.jar
 at
org.apache.catalina.startup.ContextConfig.tldScanJar(ContextConfig.java:930)
 at
org.apache.catalina.startup.ContextConfig.tldScan(ContextConfig.java:868)
 at 
 org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:647)

Has anyone seen this and know why?


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: concurrent users

2003-07-08 Thread James Courtney
Yes.  acceptCount is the number of connections to queue or block on in excess of those 
being handled by the pool of size maxProcessors.

Jamey

-Original Message-
From: Vijay Kandy [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 08, 2003 1:40 PM
To: 'Tomcat Users List'
Subject: concurrent users



Hello,

Is there a way to specify how many concurrent requests Tomcat can handle? Is
maxProcessors attribute in server.xml for this purpose? 

Thank you,
Vijay

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Apache Tomcat modjk2

2003-07-08 Thread James Courtney
Tom,
I don't believe you need anything else in your httpd.conf.  You should be able 
to configure mod_jk2 using workers2.properties (in your $APACHE_HOME/conf directory).  
See http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk2/configweb.html for more 
information.  Good luck!

Jamey


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 08, 2003 5:54 PM
To: [EMAIL PROTECTED]
Subject: Apache Tomcat modjk2


Hello-
I have successully compiled modjk2 with apache 2.0.4.6 and Tomcat 4.1.24.  
My question is now the configuration.  I have in the httpd.conf:

LoadModule jk2_module modules/mod_jk2.so

What else do I need?  Do I need to put:

JkWorkersFile /usr/local/tomcat4/conf/workers.properties
JkLogFile /usr/local/apache2/logs/mod_jk2.log
JkLogLevel info

JkMount /examples/*.jsp ajp13
JkMount /examples/servlet/* ajp13

or that is not necessary with mod_jk2?

Any help would be appreciated.

Tom


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: How do I determine sessions within Tomcat?

2003-07-08 Thread James Courtney
Mark,
Another option is to write a callback class that is registered with each 
session using the HttpSessionBindingListener interface.  Each time a session is 
destroyed, either explicitly by the user or implicitly by Tomcat (user just closed 
browser) then your widget should have its valueUnbound method called and you could 
update your DB.

I haven't worked with the SessionListener before but that sounds more tailor made for 
the purpose you intend than my solution above.

Jamey


-Original Message-
From: Mark W. Webb [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 08, 2003 1:36 PM
To: Tomcat Users List
Subject: Re: How do I determine sessions within Tomcat?


All you need is the following in your context's web.xml file :

listener
listener-classmy.own.SessionListener/listener-class
/listener

there should be an example in the examples context.  That is where I got 
mine from


Turansky, Mark wrote:

ok, I see th session listener interface in the javadocs as well as the session event 
class.  any advice regarding *how* I plug it into tomcat?  Is your method a standard 
J2EE solution or will this be Tomcat specific?

thanks for the quick reply,
mark


-Original Message-
From: Mark W. Webb [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 08, 2003 4:30 PM
To: Tomcat Users List
Subject: Re: How do I determine sessions within Tomcat?


you would probably want to write a SessionListener, and plug it into tomcat.

Turansky, Mark wrote:

  

I am required to track users and their sessions in my web application.  Is there a 
way to access all the sessions currently held in server memory?

My application is tracking users in a database table.  Upon login, I log the session 
id along with a timestamp and other pertinent information.  If the user specifically 
clicks the log out button, I can update my table with another timestamp, but I 
assume many will simply timeout.  How do I update my table with their logout 
timestamp in the event of timeout?  I was hoping to make a simple maintenance thread 
in the background that would check existing sessions against my database table for 
this purpose.

Thanks in advance,
Mark

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

 






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

  


-- 
Mark Webb
Software Engineer
Dolphin Technology
474 Phoenix Drive
Rome, NY  13441-4911

Phone : 315.838.7000 
  : 315.838.7024
Fax   : 315.838.7096
Email : [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



channel.socket or channel.apr

2003-07-07 Thread James Courtney
Which is preferable in the Tomcat 4.1.24 release (similar to connectors jk2 2.0.2 
release) of mod_jk2?

Thanks!

Jamey


RE: mod_jk and Coyote connector

2003-07-02 Thread James Courtney
Thanks John,
So you don't think that using the src distribution of the connectors provided 
with Tomcat 4.1.24 is advisable?  I'll see if I can get some log information 
representing my lack of functionality but honestly mod_jk seems even less verbose than 
mod_jk2 with logging errors even with the CoyoteConnector set to debug=10 and the 
JkLogLevel set to debug.  I'll see if I can formulate something more concrete for your 
guys then.  I'm only looking at mod_jk because we've had problems with our mod_jk2 
installation.  Do you have any thoughts on mod_jk2 and it's maturity?  Many thanks!

Jamey



-Original Message-
From: John Turner [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 02, 2003 5:23 AM
To: Tomcat Users List
Subject: Re: mod_jk and Coyote connector



Yes, CoyoteConnector fully supports JK.  Its what I use in production.  I 
would avoid Ajp13Connector, unless you need it.

I would use the actual source for the connectors:
http://jakarta.apache.org/builds/jakarta-tomcat-connectors/

If you want ot post your JK problems to the list, we can help.  Many, many 
people are using JK and are quite happy with it.  I know I am.

John

On Tue, 1 Jul 2003 14:57:18 -0700, James Courtney [EMAIL PROTECTED] 
wrote:

 Not that I've had any luck getting mod_jk to work with either the legacy 
 Ajp13Connector or the CoyoteConnector but which one should be used?  I 
 know that the CoyoteConnector is required for mod_jk2 and I've had that 
 working (mostly, occasional lapses in communication, see other messages 
 to user list) but is it compatible with mod_jk.  I'm using Apache 2.0.45 
 with Tomcat 4.1.24 and the mod_jk and mod_jk2 connectors were built from 
 the Tomcat 4.1.24 connectors release found at

 http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.24/src/

 Many thanks!

 Jamey




-- 
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: PLEASE HELP - Apache mod_jk2 loses communication with Tomcat

2003-07-02 Thread James Courtney
Eric,
Isn't the ajp13 specified in the workers2.properties simply a designation of 
protocol and not telling the client (Apache mod_jk2) which connector to use on the 
tomcat side.  It should only know host, port, protocol (ajp13 vs ajp12).

Again, although I see the sytax differences in our two workers2.properties 
configurations I don't see the logical differences.  The mod_jk2 assumes a lot from 
the naming convention of the workers and it is possible to create a configuration 
using a very minimal amount of text in a workers2.properties but I went with the more 
explicit approach which should be logically equivalent.  Can you site any specific 
instances where your configuration is logically different from mine?

Is using the 2.0.2 build of the connectors preferable to using the build 
distributed with Tomcat 4.1.24 which I used?  What kind of a user load does your 
mod_jk2 configuration handle on a daily basis?  How many concurrent sessions do you 
run per application server, etc?

Thanks again for your help!

Jamey


-Original Message-
From: Eric J. Pinnell [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 01, 2003 6:09 PM
To: Tomcat Users List
Subject: RE: PLEASE HELP - Apache mod_jk2 loses communication with
Tomcat


Hi,

On Tue, 1 Jul 2003, James Courtney wrote:

 Thanks Eric.
   I'm still puzzled though.  I don't really see any difference in
 what you're doing vs. what I'm doing.  I explicitly specify host and
 port for the channel sockets and I explicitly define the workers but
 that's shouldn't make any difference should it?  Is there anything in
 particular in my workers2.properties which is actually not correct?

I'd look closer.  There are quite a bit of differences.


   Please recall that my cluster works for a time and then
 communication falters between the servers.  This doesn't seem like a
 config problem as a config problem would probably preclude things
 working correctly in the first place.

I'm not so sure about that.  But I would start with the low hanging fruit
first.  My JK2 has worked fine for day.  In fact in another thread we
were talking about how mixing Ajp13 and Coyote causes unexpected errors
and general freaky-out-ness with no explanation what so ever.  I notice
you declare ajp13 in your workers2.properties file as part of the channel.


   Is the general opinion that mod_jk2 is ready for production use or
 is it likely still a little rough?  I'm having a lot of trouble getting
 mod_jk to work though as an alternative.  I'm using the release of
 mod_jk(2) from the Tomcat 4.1.24 release which can be found at:

I think so.  It's just a refactoring of mod_jk with some twists.  But it
will never get there if people don't try to use it! :)


 http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.24/src/

I use:
http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/release/v2.0.2/src/jakarta-tomcat-connectors-jk2-2.0.2-src.tar.gz

-e


 Thanks!

 Jamey


 -Original Message-
 From: Eric J. Pinnell [mailto:[EMAIL PROTECTED]
 Sent: Tuesday, July 01, 2003 2:34 PM
 To: Tomcat Users List
 Subject: Re: PLEASE HELP - Apache mod_jk2 loses communication with
 Tomcat


 Your workers2.properties looks a little off.  I don't know if this is the
 root of your problem but it should look more like:

 [shm]
 file=${serverRoot}/logs/shm.file
 size=1048576

 [lb:lb_01]
 info=Default load balancer.
 debug=0

 # Example socket channel, override port and host.
 [channel.socket:localhost:8109]
 info=Ajp13 forwarding over a TCP socket
 tomcatId=worker1:8109
 lb_factor=100
 group=lb_01

 # define the worker
 [channel.socket:localhost:8209]
 info=A second tomcat instance on a different port.
 tomcatId=worker2:8209
 lb_factor=100
 group=lb_01

 # Uri mapping
 [uri:/*]
 group=lb_01
 debug=0

 You have to adjust it to your own needs.  You can change 'localhost' to
 another IP or servername.

 -e

 On Tue, 1 Jul 2003, James Courtney wrote:

  I'm trying again as no one responded to my first email.  We REALLY need to resolve 
  this issue.  Thanks!
 
 
  We recently upgraded our production systems to Tomcat 4.1.24 and Apache 2.0.45 
  from 3.2.2 and 1.3.19 respectively and have noticed a VERY pleasing increase in 
  performance and over an 80% reduction in system load.  We also decided to deploy 
  with mod_jk2 and the whole system behaved itself quite well during QA and some 
  load testing (admittedly not overly thorough).  We pushed to production and things 
  ran fine for a couple of days but now, every day or two, our Apache partially 
  loses communication with one of the two Tomcats it's load balancing accross (not 
  always the same one).  The result is that requests block on Apache and the load 
  goes up as users click away trying to get their page(s) to load.  Restarting the 
  Tomcat seems to rectify the problem until the next time...
 
  Any thoughts on this problem and the overall maturity of mod_jk2 vs. mod_jk would

RE: mod_jk and Coyote connector

2003-07-02 Thread James Courtney
John,
I was simply making the assumption that the connector code released with 
Tomcat 4.1.24 had been tested and validated to be at a stable point for that release.  
I understand that there are two parts to the code and that the connectors are a 
separate project.  What I want to know is:

1)  Does anyone know why my mod_jk2 configuration posted below fails intermittently.  
I wouldn't be asking any of this if it were working reliably.
2)  Is mod_jk or mod_jk2 preferred for stable production use with moderate user 
loads (100-250 concurrent sessions per Tomcat, 2x Tomcat, 5-10 req/sec for the apache 
2.0.45).
3)  Which code release of mod_jk or mod_jk2 should I use if not the one released with 
4.1.24?  I know it's not the newest but the newest isn't always stable and I have to 
pick a stable point to test and release with.

Thanks!

Jamey


FROM AN EARLIER EMAIL:

We recently upgraded our production systems to Tomcat 4.1.24 and Apache 2.0.45 from 
3.2.2 and 1.3.19 respectively and have noticed a VERY pleasing increase in performance 
and over an 80% reduction in system load.  We also decided to deploy with mod_jk2 and 
the whole system behaved itself quite well during QA and some load testing (admittedly 
not overly thorough).  We pushed to production and things ran fine for a couple of 
days but now, every day or two, our Apache partially loses communication with one of 
the two Tomcats it's load balancing accross (not always the same one).  The result is 
that requests block on Apache and the load goes up as users click away trying to get 
their page(s) to load.  Restarting the Tomcat seems to rectify the problem until the 
next time...

Any thoughts on this problem and the overall maturity of mod_jk2 vs. mod_jk would be 
very helpful.  Many thanks to all!


Jamey


James Courtney
InPhonic, Inc.
Hayward, CA


***
** Apache Errors **
***
inunison.com:8081 145 Connection timed out [Wed Jun 25 15:08:10 2003] [error] 
ajp13.connect() failed ajp13:portal4.somedomain.com:8081 [Wed Jun 25 15:08:10 2003] 
[error] ajp13.service() failed to connect endpoint errno=145 Connection timed out [Wed 
Jun 25 15:08:10 2003] [error] ajp13.service() Error forwarding 
ajp13:portal4.somedomain.com:8081 1 1 [Wed Jun 25 15:08:10 2003] [error] lb.service() 
worker failed 12 for ajp13:portal4.somedomain.com:8081 [Wed Jun 25 15:08:13 2003] 
[error] channelSocket.open() connect failed portal4.somedomain.com:8081 145 Connection 
timed out [Wed Jun 25 15:08:13 2003] [error] ajp13.connect() failed 
ajp13:portal4.somedomain.com:8081 [Wed Jun 25 15:08:13 2003] [error] ajp13.service() 
failed to connect endpoint errno=145 Connection timed out [Wed Jun 25 15:08:13 2003] 
[error] ajp13.service() Error forwarding ajp13:portal4.somedomain.com:8081 1 1 [Wed 
Jun 25 15:08:13 2003] [error] lb.service() worker failed 12 for 
ajp13:portal4.somedomain.com:8081 [Wed Jun 25 15:08:22 2003] [error] 
channelSocket.open() connect failed portal4.somedomain.com:8081 145 Connection timed 
out [Wed Jun 25 15:08:22 2003] [error] ajp13.connect() failed 
ajp13:portal4.somedomain.com:8081 [Wed Jun 25 15:08:22 2003] [error] ajp13.service() 
failed to connect endpoint errno=145 Connection timed out [Wed Jun 25 15:08:22 2003] 
[error] ajp13.service() Error forwarding ajp13:portal4.somedomain.com:8081 1 1 [Wed 
Jun 25 15:08:22 2003] [error] lb.service() worker failed 12 for 
ajp13:portal4.somedomain.com:8081


** WORKERS2 CONFIGURATION **

# only at beginning. In production uncomment it out
[logger.apache2]
level=ERROR

[shm]
file=/tmp/workers2shmDONOTDELETE.file
size=1048576

# portal3 socket
[channel.socket:portal3.somedomain.com:8081]
host=portal3.somedomain.com
port=8081
tomcatId=portal3
group=lb:balanced
graceful=1

# portal3 worker
[ajp13:portal3.somedomain.com:8081]
channel=channel.socket:portal3.somedomain.com:8081
lb_factor=12

# portal4 socket
[channel.socket:portal4.somedomain.com:8081]
host=portal4.somedomain.com
port=8081
tomcatId=portal4
group=lb:balanced

# portal4 worker
[ajp13:portal4.somedomain.com:8081]
channel=channel.socket:portal4.somedomain.com:8081
lb_factor=12


# Load balanced worker
[lb:balanced]
worker=ajp13:portal3.somedomain.com:8081
worker=ajp13:portal4.somedomain.com:8081
# sticky is on by default but setting it adds a harmless error to the log
#stickySession=1


# Define a status worker
[status:status]


# URI mapping
[uri:/*]
group=lb:balanced


# Status URI mapping (should not be publicly accessible!!!)
[uri:/jkstatus]
group=status:status

-Original Message-
From: John Turner [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 02, 2003 9:31 AM
To: Tomcat Users List
Subject: Re: mod_jk and Coyote connector



Development on the connectors, especially the C side, happens separately 
from Tomcat development.  Keep in mind that there are two types of 
connectors.  There are Tomcat connectors, which are in server.xml (like

PLEASE HELP - Apache mod_jk2 loses communication with Tomcat

2003-07-01 Thread James Courtney
I'm trying again as no one responded to my first email.  We REALLY need to resolve 
this issue.  Thanks!


We recently upgraded our production systems to Tomcat 4.1.24 and Apache 2.0.45 from 
3.2.2 and 1.3.19 respectively and have noticed a VERY pleasing increase in performance 
and over an 80% reduction in system load.  We also decided to deploy with mod_jk2 and 
the whole system behaved itself quite well during QA and some load testing (admittedly 
not overly thorough).  We pushed to production and things ran fine for a couple of 
days but now, every day or two, our Apache partially loses communication with one of 
the two Tomcats it's load balancing accross (not always the same one).  The result is 
that requests block on Apache and the load goes up as users click away trying to get 
their page(s) to load.  Restarting the Tomcat seems to rectify the problem until the 
next time...

Any thoughts on this problem and the overall maturity of mod_jk2 vs. mod_jk would be 
very helpful.  Many thanks to all!


Jamey


James Courtney
InPhonic, Inc.
Hayward, CA


***
** Apache Errors **
***
inunison.com:8081 145 Connection timed out [Wed Jun 25 15:08:10 2003] [error] 
ajp13.connect() failed ajp13:portal4.somedomain.com:8081 [Wed Jun 25 15:08:10 2003] 
[error] ajp13.service() failed to connect endpoint errno=145 Connection timed out [Wed 
Jun 25 15:08:10 2003] [error] ajp13.service() Error forwarding 
ajp13:portal4.somedomain.com:8081 1 1 [Wed Jun 25 15:08:10 2003] [error] lb.service() 
worker failed 12 for ajp13:portal4.somedomain.com:8081 [Wed Jun 25 15:08:13 2003] 
[error] channelSocket.open() connect failed portal4.somedomain.com:8081 145 Connection 
timed out [Wed Jun 25 15:08:13 2003] [error] ajp13.connect() failed 
ajp13:portal4.somedomain.com:8081 [Wed Jun 25 15:08:13 2003] [error] ajp13.service() 
failed to connect endpoint errno=145 Connection timed out [Wed Jun 25 15:08:13 2003] 
[error] ajp13.service() Error forwarding ajp13:portal4.somedomain.com:8081 1 1 [Wed 
Jun 25 15:08:13 2003] [error] lb.service() worker failed 12 for 
ajp13:portal4.somedomain.com:8081 [Wed Jun 25 15:08:22 2003] [error] 
channelSocket.open() connect failed portal4.somedomain.com:8081 145 Connection timed 
out [Wed Jun 25 15:08:22 2003] [error] ajp13.connect() failed 
ajp13:portal4.somedomain.com:8081 [Wed Jun 25 15:08:22 2003] [error] ajp13.service() 
failed to connect endpoint errno=145 Connection timed out [Wed Jun 25 15:08:22 2003] 
[error] ajp13.service() Error forwarding ajp13:portal4.somedomain.com:8081 1 1 [Wed 
Jun 25 15:08:22 2003] [error] lb.service() worker failed 12 for 
ajp13:portal4.somedomain.com:8081


** WORKERS2 CONFIGURATION **

# only at beginning. In production uncomment it out
[logger.apache2]
level=ERROR

[shm]
file=/tmp/workers2shmDONOTDELETE.file
size=1048576

# portal3 socket
[channel.socket:portal3.somedomain.com:8081]
host=portal3.somedomain.com
port=8081
tomcatId=portal3
group=lb:balanced
graceful=1

# portal3 worker
[ajp13:portal3.somedomain.com:8081]
channel=channel.socket:portal3.somedomain.com:8081
lb_factor=12

# portal4 socket
[channel.socket:portal4.somedomain.com:8081]
host=portal4.somedomain.com
port=8081
tomcatId=portal4
group=lb:balanced

# portal4 worker
[ajp13:portal4.somedomain.com:8081]
channel=channel.socket:portal4.somedomain.com:8081
lb_factor=12


# Load balanced worker
[lb:balanced]
worker=ajp13:portal3.somedomain.com:8081
worker=ajp13:portal4.somedomain.com:8081
# sticky is on by default but setting it adds a harmless error to the log
#stickySession=1


# Define a status worker
[status:status]


# URI mapping
[uri:/*]
group=lb:balanced


# Status URI mapping (should not be publicly accessible!!!)
[uri:/jkstatus]
group=status:status
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: PLEASE HELP - Apache mod_jk2 loses communication with Tomcat

2003-07-01 Thread James Courtney
Thanks Eric.
I'm still puzzled though.  I don't really see any difference in what you're 
doing vs. what I'm doing.  I explicitly specify host and port for the channel sockets 
and I explicitly define the workers but that's shouldn't make any difference should 
it?  Is there anything in particular in my workers2.properties which is actually not 
correct?

Please recall that my cluster works for a time and then communication falters 
between the servers.  This doesn't seem like a config problem as a config problem 
would probably preclude things working correctly in the first place.

Is the general opinion that mod_jk2 is ready for production use or is it 
likely still a little rough?  I'm having a lot of trouble getting mod_jk to work 
though as an alternative.  I'm using the release of mod_jk(2) from the Tomcat 4.1.24 
release which can be found at:

http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.24/src/

Thanks!

Jamey


-Original Message-
From: Eric J. Pinnell [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 01, 2003 2:34 PM
To: Tomcat Users List
Subject: Re: PLEASE HELP - Apache mod_jk2 loses communication with
Tomcat


Your workers2.properties looks a little off.  I don't know if this is the
root of your problem but it should look more like:

[shm]
file=${serverRoot}/logs/shm.file
size=1048576

[lb:lb_01]
info=Default load balancer.
debug=0

# Example socket channel, override port and host.
[channel.socket:localhost:8109]
info=Ajp13 forwarding over a TCP socket
tomcatId=worker1:8109
lb_factor=100
group=lb_01

# define the worker
[channel.socket:localhost:8209]
info=A second tomcat instance on a different port.
tomcatId=worker2:8209
lb_factor=100
group=lb_01

# Uri mapping
[uri:/*]
group=lb_01
debug=0

You have to adjust it to your own needs.  You can change 'localhost' to
another IP or servername.

-e

On Tue, 1 Jul 2003, James Courtney wrote:

 I'm trying again as no one responded to my first email.  We REALLY need to resolve 
 this issue.  Thanks!


 We recently upgraded our production systems to Tomcat 4.1.24 and Apache 2.0.45 from 
 3.2.2 and 1.3.19 respectively and have noticed a VERY pleasing increase in 
 performance and over an 80% reduction in system load.  We also decided to deploy 
 with mod_jk2 and the whole system behaved itself quite well during QA and some load 
 testing (admittedly not overly thorough).  We pushed to production and things ran 
 fine for a couple of days but now, every day or two, our Apache partially loses 
 communication with one of the two Tomcats it's load balancing accross (not always 
 the same one).  The result is that requests block on Apache and the load goes up as 
 users click away trying to get their page(s) to load.  Restarting the Tomcat seems 
 to rectify the problem until the next time...

 Any thoughts on this problem and the overall maturity of mod_jk2 vs. mod_jk would be 
 very helpful.  Many thanks to all!


 Jamey


 James Courtney
 InPhonic, Inc.
 Hayward, CA


 ***
 ** Apache Errors **
 ***
 inunison.com:8081 145 Connection timed out [Wed Jun 25 15:08:10 2003] [error] 
 ajp13.connect() failed ajp13:portal4.somedomain.com:8081 [Wed Jun 25 15:08:10 2003] 
 [error] ajp13.service() failed to connect endpoint errno=145 Connection timed out 
 [Wed Jun 25 15:08:10 2003] [error] ajp13.service() Error forwarding 
 ajp13:portal4.somedomain.com:8081 1 1 [Wed Jun 25 15:08:10 2003] [error] 
 lb.service() worker failed 12 for ajp13:portal4.somedomain.com:8081 [Wed Jun 25 
 15:08:13 2003] [error] channelSocket.open() connect failed 
 portal4.somedomain.com:8081 145 Connection timed out [Wed Jun 25 15:08:13 2003] 
 [error] ajp13.connect() failed ajp13:portal4.somedomain.com:8081 [Wed Jun 25 
 15:08:13 2003] [error] ajp13.service() failed to connect endpoint errno=145 
 Connection timed out [Wed Jun 25 15:08:13 2003] [error] ajp13.service() Error 
 forwarding ajp13:portal4.somedomain.com:8081 1 1 [Wed Jun 25 15:08:13 2003] [error] 
 lb.service() worker failed 12 for ajp13:portal4.somedomain.com:8081 [Wed Jun 25 
 15:08:22 2003] [error] channelSocket.open() connect failed 
 portal4.somedomain.com:8081 145 Connection timed out [Wed Jun 25 15:08:22 2003] 
 [error] ajp13.connect() failed ajp13:portal4.somedomain.com:8081 [Wed Jun 25 
 15:08:22 2003] [error] ajp13.service() failed to connect endpoint errno=145 
 Connection timed out [Wed Jun 25 15:08:22 2003] [error] ajp13.service() Error 
 forwarding ajp13:portal4.somedomain.com:8081 1 1 [Wed Jun 25 15:08:22 2003] [error] 
 lb.service() worker failed 12 for ajp13:portal4.somedomain.com:8081

 
 ** WORKERS2 CONFIGURATION **
 
 # only at beginning. In production uncomment it out
 [logger.apache2]
 level=ERROR

 [shm]
 file=/tmp/workers2shmDONOTDELETE.file
 size=1048576

 # portal3 socket
 [channel.socket:portal3.somedomain.com:8081]
 host=portal3.somedomain.com
 port=8081

mod_jk and Coyote connector

2003-07-01 Thread James Courtney
Not that I've had any luck getting mod_jk to work with either the legacy 
Ajp13Connector or the CoyoteConnector but which one should be used?  I know that the 
CoyoteConnector is required for mod_jk2 and I've had that working (mostly, occasional 
lapses in communication, see other messages to user list) but is it compatible with 
mod_jk.  I'm using Apache 2.0.45 with Tomcat 4.1.24 and the mod_jk and mod_jk2 
connectors were built from the Tomcat 4.1.24 connectors release found at

http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.24/src/

Many thanks!

Jamey


RE: Running a class on startup - java newbie....

2003-07-01 Thread James Courtney
EJ,
You can create an initialization servlet that get's loaded at startup of your 
webapp.  This servlet could create a thread that does what Andre suggests below.  Use 
the web.xml to configure any parameters you need to pass to this servlet and to ensure 
it's loaded first.  Then just define an init method for that servlet that creates and 
executes your thread.  You can use the servlet's destroy method to shut down your 
thread.

Jamey


-Original Message-
From: Andre D Bonner [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 01, 2003 2:55 PM
To: Tomcat Users List
Subject: Re: Running a class on startup - java newbie


What I'd like to do is
 have something running that sleeps for 5 minutes at a time and then checks
 to see if 24 hours have passed since the row was inserted (and if so, delete
 it).  Is there a way to start up a class with my web app?
 


Looks like good old Thread based timer

It is a thread that sits and calls a method every 5 minutes?

while(true){
Thread.sleep(5 * 60 * 1000) // 5 minutes exactly

  // lookup my jdbc Datasource
 // do my jdbc checking?
  // releaseConnection
  // loop
}


-- 
Andre D Bonner
Sun Certified Programmer for the Java 2 Platform 1.4



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Running a class on startup - java newbie....

2003-07-01 Thread James Courtney
If that's the case then I'd run it as part of the user addition process to ensure that 
things are in the correct state for adding a user.  No additional threads required (no 
that they're bad when used correctly).

Jamey


-Original Message-
From: Ciramella, EJ [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 01, 2003 3:09 PM
To: Tomcat Users List
Subject: RE: Running a class on startup - java newbie


Ok, but like I said, all the developers 'round these parts are saying that
threads are a no-no.

Honestly, I'm not even sure that the DB cleanup I'm trying to perform needs
to happen every five minutes.  Honestly, it only needs to happen each time a
new user tries to register or gets added

hmm.

looks like I don't need to do this after all.

Unless someone has a better, cooler idea..

-Original Message-
From: James Courtney [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 01, 2003 6:07 PM
To: Ciramella, EJ
Cc: Tomcat Users List
Subject: RE: Running a class on startup - java newbie


EJ,
You can create an initialization servlet that get's loaded at
startup of your webapp.  This servlet could create a thread that does what
Andre suggests below.  Use the web.xml to configure any parameters you need
to pass to this servlet and to ensure it's loaded first.  Then just define
an init method for that servlet that creates and executes your thread.  You
can use the servlet's destroy method to shut down your thread.

Jamey


-Original Message-
From: Andre D Bonner [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 01, 2003 2:55 PM
To: Tomcat Users List
Subject: Re: Running a class on startup - java newbie


What I'd like to do is
 have something running that sleeps for 5 minutes at a time and then
checks
 to see if 24 hours have passed since the row was inserted (and if so,
delete
 it).  Is there a way to start up a class with my web app?
 


Looks like good old Thread based timer

It is a thread that sits and calls a method every 5 minutes?

while(true){
Thread.sleep(5 * 60 * 1000) // 5 minutes exactly

  // lookup my jdbc Datasource
 // do my jdbc checking?
  // releaseConnection
  // loop
}


-- 
Andre D Bonner
Sun Certified Programmer for the Java 2 Platform 1.4



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Apache mod_jk2 fizzles out

2003-06-25 Thread James Courtney
We recently upgraded our production systems to Tomcat 4.1.24 and Apache 2.0.45 from 
3.2.2 and 1.3.19 respectively and have noticed a VERY pleasing increase in performance 
and over an 80% reduction in system load.  We also decided to deploy with mod_jk2 and 
the whole system behaved itself quite well during QA and some load testing (admittedly 
not overly thorough).  We pushed to production and things ran fine for a couple of 
days but now, every day or two, our Apache partially loses communication with one of 
the two Tomcats it's load balancing accross (not always the same one).  The result is 
that requests block on Apache and the load goes up as users click away trying to get 
their page(s) to load.  Restarting the Tomcat seems to rectify the problem until the 
next time...

Any thoughts on this problem and the overall maturity of mod_jk2 vs. mod_jk would be 
very helpful.  Many thanks to all!


***
** Apache Errors **
***
inunison.com:8081 145 Connection timed out [Wed Jun 25 15:08:10 2003] [error] 
ajp13.connect() failed ajp13:portal4.somedomain.com:8081 [Wed Jun 25 15:08:10 2003] 
[error] ajp13.service() failed to connect endpoint errno=145 Connection timed out [Wed 
Jun 25 15:08:10 2003] [error] ajp13.service() Error forwarding 
ajp13:portal4.somedomain.com:8081 1 1 [Wed Jun 25 15:08:10 2003] [error] lb.service() 
worker failed 12 for ajp13:portal4.somedomain.com:8081 [Wed Jun 25 15:08:13 2003] 
[error] channelSocket.open() connect failed portal4.somedomain.com:8081 145 Connection 
timed out [Wed Jun 25 15:08:13 2003] [error] ajp13.connect() failed 
ajp13:portal4.somedomain.com:8081 [Wed Jun 25 15:08:13 2003] [error] ajp13.service() 
failed to connect endpoint errno=145 Connection timed out [Wed Jun 25 15:08:13 2003] 
[error] ajp13.service() Error forwarding ajp13:portal4.somedomain.com:8081 1 1 [Wed 
Jun 25 15:08:13 2003] [error] lb.service() worker failed 12 for 
ajp13:portal4.somedomain.com:8081 [Wed Jun 25 15:08:22 2003] [error] 
channelSocket.open() connect failed portal4.somedomain.com:8081 145 Connection timed 
out [Wed Jun 25 15:08:22 2003] [error] ajp13.connect() failed 
ajp13:portal4.somedomain.com:8081 [Wed Jun 25 15:08:22 2003] [error] ajp13.service() 
failed to connect endpoint errno=145 Connection timed out [Wed Jun 25 15:08:22 2003] 
[error] ajp13.service() Error forwarding ajp13:portal4.somedomain.com:8081 1 1 [Wed 
Jun 25 15:08:22 2003] [error] lb.service() worker failed 12 for 
ajp13:portal4.somedomain.com:8081


** WORKERS2 CONFIGURATION **

# only at beginning. In production uncomment it out
[logger.apache2]
level=ERROR

[shm]
file=/tmp/workers2shmDONOTDELETE.file
size=1048576

# portal3 socket
[channel.socket:portal3.somedomain.com:8081]
host=portal3.somedomain.com
port=8081
tomcatId=portal3
group=lb:balanced
graceful=1

# portal3 worker
[ajp13:portal3.somedomain.com:8081]
channel=channel.socket:portal3.somedomain.com:8081
lb_factor=12

# portal4 socket
[channel.socket:portal4.somedomain.com:8081]
host=portal4.somedomain.com
port=8081
tomcatId=portal4
group=lb:balanced

# portal4 worker
[ajp13:portal4.somedomain.com:8081]
channel=channel.socket:portal4.somedomain.com:8081
lb_factor=12


# Load balanced worker
[lb:balanced]
worker=ajp13:portal3.somedomain.com:8081
worker=ajp13:portal4.somedomain.com:8081
# sticky is on by default but setting it adds a harmless error to the log
#stickySession=1


# Define a status worker
[status:status]


# URI mapping
[uri:/*]
group=lb:balanced


# Status URI mapping (should not be publicly accessible!!!)
[uri:/jkstatus]
group=status:status
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Mod_rewrite and mod_jk2

2003-06-18 Thread James Courtney
Hey all,
We're using Apache 2.0.45 as a pure load-balancer for two Tomcat 4.1.24 
instances.  Apache serves no content and redirects /* to the Tomcats (using the uri 
element of the workers2.properties).  We have some rewrite rules that massage some 
URL's based on the domain name the user is accessing our site with.

For Example:

  RewriteCond %{HTTP_HOST} ^www.mysite.com
  RewriteRule ^$ /some/url/mysite [PT]
  RewriteCond %{HTTP_HOST} ^www.myothersite.com
  RewriteRule ^$ /some/url/myothersite [PT]

We're and ASP and basically have customer specific URLS for our product which should 
redirect the customer to the correct logon page for our app with their branding.  
mod_jk2 seems to intercept all requests prior to mod_rewrite getting a crack at it.  
Is there some way to let mod_rewrite get first shot at the URL before the urls are 
handed off to tomcat?

Thanks!

Jamey

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Mod_rewrite and mod_jk2

2003-06-18 Thread James Courtney
Apparently if you move the loading of mod_jk2 after the loading of mod_rewrite in 
httpd.conf this corrects the problem...

Jamey


-Original Message-
From: James Courtney 
Sent: Wednesday, June 18, 2003 11:47 AM
To: Tomcat Users List (E-mail)
Subject: Mod_rewrite and mod_jk2


Hey all,
We're using Apache 2.0.45 as a pure load-balancer for two Tomcat 4.1.24 
instances.  Apache serves no content and redirects /* to the Tomcats (using the uri 
element of the workers2.properties).  We have some rewrite rules that massage some 
URL's based on the domain name the user is accessing our site with.

For Example:

  RewriteCond %{HTTP_HOST} ^www.mysite.com
  RewriteRule ^$ /some/url/mysite [PT]
  RewriteCond %{HTTP_HOST} ^www.myothersite.com
  RewriteRule ^$ /some/url/myothersite [PT]

We're and ASP and basically have customer specific URLS for our product which should 
redirect the customer to the correct logon page for our app with their branding.  
mod_jk2 seems to intercept all requests prior to mod_rewrite getting a crack at it.  
Is there some way to let mod_rewrite get first shot at the URL before the urls are 
handed off to tomcat?

Thanks!

Jamey

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



mod_jk2 and shm

2003-06-06 Thread James Courtney
I keep getting errors like the following from my mod_jk2 installation.  Everything 
seems to work fine but my apache_error log has errors relating to the shm worker which 
I don't even configure in workers.properties since I don't see that it's in any way 
required for a simple channel.socket configuration.  My load balancing through Apache 
seems to work fine too so I'm pretty confused.  I've inlined the errors followed by OS 
and Apache information followed by my workers2.properties.  I'm using Tomcat 4.1.24.

Should I be configuring Apache to use an on-disk scoreboard file and should I be 
configuring the shm worker to point to that file?  I've tried this and the 
shm.init(): No file error goes away but that's it.

Thanks ahead of time for the help!

Jamey



**
** apache_error.log **
**

[Thu Jun 05 13:54:45 2003] [error] shm.init(): No file
[Thu Jun 05 13:54:45 2003] [notice] workerEnv.init() ok /home/jamey/cvs/inunison
/pt30/server/conf/workers2.properties
[Thu Jun 05 13:54:45 2003] [error] mod_jk child init 1 -2
[Thu Jun 05 13:54:46 2003] [error] jk2_init() Can't find child 11023 in scoreboa
rd


*
** OS Info **
*
SunOS viagra 5.8 Generic_108528-19 sun4u sparc SUNW,Ultra-60 Solaris


*
** Apache Info **
*
Server version: Apache/2.0.45
Server built:   May  8 2003 09:58:18
Server's Module Magic Number: 20020903:0
Architecture:   32-bit
Server compiled with
 -D APACHE_MPM_DIR=server/mpm/worker
 -D APR_HAS_MMAP
 -D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
 -D APR_USE_PROC_PTHREAD_SERIALIZE
 -D APR_USE_PTHREAD_SERIALIZE
 -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
 -D APR_HAS_OTHER_CHILD
 -D AP_HAVE_RELIABLE_PIPED_LOGS
 -D HTTPD_ROOT=/apps/apache/2.0.45
 -D SUEXEC_BIN=/apps/apache/2.0.45/bin/suexec
 -D DEFAULT_SCOREBOARD=logs/apache_runtime_status
 -D DEFAULT_ERRORLOG=logs/error_log
 -D AP_TYPES_CONFIG_FILE=conf/mime.types
 -D SERVER_CONFIG_FILE=conf/httpd.conf


*
** workers2.properties **
*
# only at beginning. In production comment it out
[logger.apache2]
level=DEBUG

# First socket channel, override port and host.
[channel.socket:localhost:6670]
host=localhost
port=6670
tomcatId=localhost
group=lb:balanced

# Define the first worker
[ajp13:localhost:6670]
channel=channel.socket:localhost:6670


# Define a status worker
[status:stat]


# URI mapping
[uri:/*]
group=ajp13:localhost:6670


# Status URI mapping (should not be publicly accessible!!!)
[uri:/jk2status]
group=status:stat

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: jk2_init() Can't find child xxxxx in scoreboard

2003-06-06 Thread James Courtney
Same here.  Please keep us informed.

Many thanks!

Jamey

-Original Message-
From: Faine, Mark [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 05, 2003 5:29 AM
To: '[EMAIL PROTECTED]'
Cc: '[EMAIL PROTECTED]'
Subject: Re: jk2_init() Can't find child x in scoreboard


I am currently having the exact problem you describe.  Did you ever figure
it out?

Thanks,
-Mark

Scott Ahten [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]...
I'm trying to setup Apache2 and mod_jk2 to pass Tomcat requests via 
JNI. After reading two or three HOWTOs and previously setting up a 
similar config  on Windows 2000 server, I've managed to make some 
progress on RedHat 7.3. Unfortunately, when I start Apache2, I get an 
jk2 error message about every 2-5 seconds.  Here is a example from a 
recent run.

[Tue Jun 03 21:51:35 2003] [warn] Init: Session Cache is not configured 
[hint: SSLSessionCache]
[Tue Jun 03 21:51:36 2003] [notice] Apache/2.0.46 (Unix) mod_ssl/2.0.46 
OpenSSL/0.9.6b mod_jk2/2.0.2 configured -- resuming normal operations [Tue
Jun 03 21:51:41 2003] [error] jk2_init() Can't find child 2545 in 
scoreboard
[Tue Jun 03 21:51:50 2003] [error] jk2_init() Can't find child 2560 in 
scoreboard
[Tue Jun 03 21:51:51 2003] [error] jk2_init() Can't find child 2568 in 
scoreboard
[Tue Jun 03 21:51:58 2003] [error] jk2_init() Can't find child 2575 in 
scoreboard
[Tue Jun 03 21:51:59 2003] [error] jk2_init() Can't find child 2583 in 
scoreboard

I've read somewhere that this might be related to the Jkstatus 
directive, so I removed it from my workers2.properties file. This 
seemed to have no effect.

Also, sending requests such as http://localhost/ stall without any 
additional errors any of Apache or Tomcat's log files. I'm guessing 
this has something to do with the scoreboard error, but may be because 
Tomcat isn't getting launched in-process with Apache. Removing the 
LoadModule directive for mod_jk2 allows the static Apache2 welcome page 
to load.

In brief, Apache2 was built from source using..

./configure --prefix=/usr/local/apache2 --enable-ssl --enable-module=so
--

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]