mod_jk integration, local_worker, session capping/bleeding....

2003-04-04 Thread Jules Gosnell
http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.0/doc/jk/workershowto.html

contains the following text:

'We need a graceful shut down of a node for maintenance. The balancer in 
front asks a special port on each node periodically. If we want to 
remove a node from the cluster, we switch off this port. The 
loadbalancer can't connect to it and marks the node as down. But we 
don't move the sessions to another node. In this environment it is an 
error if the balancer sends a request without a session to an 
apache+mod_jk+tomcat which port is switched off. And if the load 
balancer determines that a node is down no other node is allowed to send 
a request without a session to it. Only requests with old sessions on 
the switched off node would be routed to this node. After some time 
nobody uses the old sessions and the sessions will time out. Then nobody 
uses this node, because all session are gone and the node is unreachable 
without a session-id in the request. If someone uses a session which 
timed out, our servlet system sends a redirect response without a 
session id to the browser. This is necessary for me, because on a 
switched off node apache and tomcat can still be up and running, but 
they are in an old state and should only be asked for valid old 
sessions. After the last session timed out, I could update the node etc. 
without killing sessions or moving them to another node. Sometimes we 
have a lot of big objects in our sessions, so it would be really time 
consuming to move them.'

My reading of this is that I can dynamically tell TC to stop accepting 
new sessions. It will notify mod_jk and thenceforth only requests 
already bound to existing sessions hosted in this TC instance will be 
forwarded from mod_jk.

I have scoured the web, mailing list archives and src code, most likely 
with the wrong keywords, trying to find references explaining, how I can 
  tell TC that I want to bleed the existing sessions off it, using this 
functionality.

I understand and use the support for session affinity via jvmRoute and 
other worker properties. I would now like to extend what I have to 
support the graceful shutdown on TC nodes without the loss of session 
data. I do not want to persist or otherwise distribute these sessions.

Can anyone point me in the right direction ?

Thanks for your time,

Jules



--

This e-mail is intended for the named addressee only.  It may contain confidential and/or privileged information.  If you have received this message in error, please let us know and then delete this message from your system.  You should not copy the message, use it for any purpose or disclose its contents to anyone.


This e-mail has been scanned for all viruses by Star Internet. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk

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


Re: mod_jk integration

2003-02-19 Thread Bill Barker
For Apache 1.3.x, you need to move 'mod_rewrite' below 'mod_jk' in the
AddModule list.  Alternatively, the [PT] option may work (but I haven't
tried it).

Alexander Czernay [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
 Hi Lajos,

 thanks for your help. I read through your pages and it sounds to me like
 I have to use the mod_rewrite technique to accomplish my goal. But I'm
 afraid I don't know the rewrite mechanism enough to get it going.

 It would be great, if you could help me again with that.

 This is kind of a special case, as I set up Cocoon to serve two sites
 from the same directory, using different XSLTs for the different design.

 The structure, defined in my sitemap, is mainly like this:
 /cocoon - just the usual one
 /cocoon/k8 - this is bundling the two sites
 /cocoon/k8/alexander - this is the first site to be mapped to one domain
 /cocoon/k8/moritz - this is the second site to be mapped to the other
domain


 Maybe this is completly wrong, so if I should have done it another way,
 please tell me.

 Thanks for any help,

 Alexander

 Lajos wrote:
  Hi Alexander -
 
  There are several ways you can do this - see my Cocoon notes at
  http://www.galatea.com/flashguides/cocoon-tips-2.xml (or my book ;) ).
  Probably the best is simply to make the cocoon webapp your default
  context in server.xml:
 
  Context path= docBase=cocoon debug=0/
 
  Regards,
 
  Lajos
 
 
  Alexander Czernay wrote:
 
  I'm trying to integrate my servlet (Apache Cocoon 2.0.4), running
  inside Tomcat 4.0.4 into my Apache 1.36. This works perfectly well,
  but I'd like to get rid of the /cocoon/ part in the URL, so I can map
  the whole Cocoon based app directly to my domain.
 
  I tried some Alias commands and some MountJk commands, but that
  doesn't work, as it seems to me like Apache doesn't pass the whole
  path to Tomcat, thus Tomcat doesn't search inside its /cocoon/ path,
  but rather in its root path - that obviously doesn't work.
 
  Any hints?
 
  Alexander
 
 
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 


 --
 _
 Alexander Czernay
 IT-Consulting  Media Development

 fon +49-40-41096742
 fax +49-40-41096743
 icq 4773650

 [EMAIL PROTECTED]
 www.czernay.com
 _




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




mod_jk integration

2003-02-18 Thread Alexander Czernay
I'm trying to integrate my servlet (Apache Cocoon 2.0.4), running inside 
Tomcat 4.0.4 into my Apache 1.36. This works perfectly well, but I'd 
like to get rid of the /cocoon/ part in the URL, so I can map the whole 
Cocoon based app directly to my domain.

I tried some Alias commands and some MountJk commands, but that doesn't 
work, as it seems to me like Apache doesn't pass the whole path to 
Tomcat, thus Tomcat doesn't search inside its /cocoon/ path, but rather 
in its root path - that obviously doesn't work.

Any hints?

Alexander



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



Re: mod_jk integration

2003-02-18 Thread Lajos
Hi Alexander -

There are several ways you can do this - see my Cocoon notes at 
http://www.galatea.com/flashguides/cocoon-tips-2.xml (or my book ;) ). 
Probably the best is simply to make the cocoon webapp your default 
context in server.xml:

Context path= docBase=cocoon debug=0/

Regards,

Lajos


Alexander Czernay wrote:
I'm trying to integrate my servlet (Apache Cocoon 2.0.4), running inside 
Tomcat 4.0.4 into my Apache 1.36. This works perfectly well, but I'd 
like to get rid of the /cocoon/ part in the URL, so I can map the whole 
Cocoon based app directly to my domain.

I tried some Alias commands and some MountJk commands, but that doesn't 
work, as it seems to me like Apache doesn't pass the whole path to 
Tomcat, thus Tomcat doesn't search inside its /cocoon/ path, but rather 
in its root path - that obviously doesn't work.

Any hints?

Alexander



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




--



   Lajos Moczar
  
Open Source Support, Consulting and Training
  
Cocoon Developer's Handbook
 (www.amazon.com/exec/obidos/tg/detail/-/0672322579)

   _  _
  / \ /
 /___\  /
/ \   /

 http://www.galatea.com -- powered by AzSSL


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




Re: mod_jk integration

2003-02-18 Thread Alexander Czernay
Hi Lajos,

thanks for your help. I read through your pages and it sounds to me like 
I have to use the mod_rewrite technique to accomplish my goal. But I'm 
afraid I don't know the rewrite mechanism enough to get it going.

It would be great, if you could help me again with that.

This is kind of a special case, as I set up Cocoon to serve two sites 
from the same directory, using different XSLTs for the different design.

The structure, defined in my sitemap, is mainly like this:
/cocoon	- just the usual one
/cocoon/k8 - this is bundling the two sites
/cocoon/k8/alexander - this is the first site to be mapped to one domain
/cocoon/k8/moritz - this is the second site to be mapped to the other domain


Maybe this is completly wrong, so if I should have done it another way, 
please tell me.

Thanks for any help,

Alexander

Lajos wrote:
Hi Alexander -

There are several ways you can do this - see my Cocoon notes at 
http://www.galatea.com/flashguides/cocoon-tips-2.xml (or my book ;) ). 
Probably the best is simply to make the cocoon webapp your default 
context in server.xml:

Context path= docBase=cocoon debug=0/

Regards,

Lajos


Alexander Czernay wrote:

I'm trying to integrate my servlet (Apache Cocoon 2.0.4), running 
inside Tomcat 4.0.4 into my Apache 1.36. This works perfectly well, 
but I'd like to get rid of the /cocoon/ part in the URL, so I can map 
the whole Cocoon based app directly to my domain.

I tried some Alias commands and some MountJk commands, but that 
doesn't work, as it seems to me like Apache doesn't pass the whole 
path to Tomcat, thus Tomcat doesn't search inside its /cocoon/ path, 
but rather in its root path - that obviously doesn't work.

Any hints?

Alexander



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







--
_
Alexander Czernay
IT-Consulting  Media Development

fon +49-40-41096742
fax +49-40-41096743
icq 4773650

[EMAIL PROTECTED]
www.czernay.com
_



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




Re: mod_jk integration

2003-02-18 Thread Lajos
Well, I do the same on my server. What I did was to have to 
VirtualHosts in Apache, each directing the appropriate Cocoon 
application to Tomcat. Then, in Tomcat, I point everything to the 
default context, which is Cocoon. In Cocoon's sitemap, I use the 
WildcardHostMatcher to direct the URLs for the appropriate host to the 
right sub-sitemaps.

I don't think you need mod_rewrite. Look at the WildcardHostMatcher.

If you have more questions, email me privately since we are straying 
off-topic here (and it'll spawn an endless thread of people admonishing 
the people talking about the people complaining about off-topic posts ;) )

Regards,

Lajos


Alexander Czernay wrote:
Hi Lajos,

thanks for your help. I read through your pages and it sounds to me like 
I have to use the mod_rewrite technique to accomplish my goal. But I'm 
afraid I don't know the rewrite mechanism enough to get it going.

It would be great, if you could help me again with that.

This is kind of a special case, as I set up Cocoon to serve two sites 
from the same directory, using different XSLTs for the different design.

The structure, defined in my sitemap, is mainly like this:
/cocoon- just the usual one
/cocoon/k8 - this is bundling the two sites
/cocoon/k8/alexander - this is the first site to be mapped to one domain
/cocoon/k8/moritz - this is the second site to be mapped to the other 
domain


Maybe this is completly wrong, so if I should have done it another way, 
please tell me.

Thanks for any help,

Alexander

Lajos wrote:

Hi Alexander -

There are several ways you can do this - see my Cocoon notes at 
http://www.galatea.com/flashguides/cocoon-tips-2.xml (or my book ;) ). 
Probably the best is simply to make the cocoon webapp your default 
context in server.xml:

Context path= docBase=cocoon debug=0/

Regards,

Lajos


Alexander Czernay wrote:

I'm trying to integrate my servlet (Apache Cocoon 2.0.4), running 
inside Tomcat 4.0.4 into my Apache 1.36. This works perfectly well, 
but I'd like to get rid of the /cocoon/ part in the URL, so I can map 
the whole Cocoon based app directly to my domain.

I tried some Alias commands and some MountJk commands, but that 
doesn't work, as it seems to me like Apache doesn't pass the whole 
path to Tomcat, thus Tomcat doesn't search inside its /cocoon/ path, 
but rather in its root path - that obviously doesn't work.

Any hints?

Alexander



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










--



   Lajos Moczar
  
Open Source Support, Consulting and Training
  
Cocoon Developer's Handbook
 (www.amazon.com/exec/obidos/tg/detail/-/0672322579)

   _  _
  / \ /
 /___\  /
/ \   /

 http://www.galatea.com -- powered by AzSSL


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




RE: tomcat 4.1.12 with apache1.3.26 and mod_jk integration error.

2002-11-04 Thread Lambert, Stephen : CO IR
The hosts file is now correct.

I'm now able to load the /examples directory the following ways:
http://w121c20.legacyhs:8080/examples
http://w121c20.legacyhs/examples

but not with http://localhost:8080/examples or http://localhost/examples

Also, when I test a jsp example as standalone, it works fine
(http://w121c20.legacyhs:8080/examples/jsp/num/numguess.jsp) 

but not when I remove the port 8080 from the URL:
http://w121c20.legacyhs/examples/jsp/num/numguess.jsp


The only strange config problem was that jk directory under
CATALINA_HOME/conf didn't exist prior to me creating the workers.properties
file!
I'm not sure if this meaningful.

Suggestions anyone?


-Original Message-
From: Josh G [mailto:josh;gfunk007.com]
Sent: Wednesday, October 30, 2002 5:37 PM
To: Tomcat Users List
Subject: Re: tomcat 4.1.12 with apache1.3.26 and mod_jk integration
error.


You don't have localhost in your HOSTS file, add this entry and it'll all be
good :)

-Josh

Who can it be knocking at my door?
Go away, don't come round here no more.
Can't you see that it's late at night?
I'm very tired, and I'm not feeling right.
- Original Message -
From: Lambert, Stephen : CO IR [EMAIL PROTECTED]
To: 'Tomcat Users List' [EMAIL PROTECTED]
Sent: Thursday, October 31, 2002 11:20 AM
Subject: RE: tomcat 4.1.12 with apache1.3.26 and mod_jk integration error.


 John, I still can't get this to work?!
 I started over from scratch with your docs and was able correct the
 duplicate mod_jk.conf problem.
 However, when I try the following URL's, localhost still doesn't work.

 http://localhost result= Netscape starts searching the internet

 http://localhost:8080 result= Netscape starts searching the internet

 http://w121c20.legacyhs:8080 result= works fine!

 http://w121c20.legacyhs result= works fine!

 Is this a Netscape issue?


 -Original Message-
 From: Turner, John [mailto:JTurner;AAS.com]
 Sent: Tuesday, October 08, 2002 5:34 AM
 To: 'Tomcat Users List'
 Subject: RE: tomcat 4.1.12 with apache1.3.26 and mod_jk integration
 error .



 Take a look at the docs for the ApacheConfig Listener...there are
parameters
 there to stop things like appending to mod_jk.conf, which might be what is
 happening.  In other words, shut everything down, wait a bit, delete
 mod_jk.conf, then start up Tomcat and see if the mod_jk.conf file is
correct
 (make sure permissions on mod_jk.conf file are correct, too...the user
 Tomcat is running as should have write/delete access to that file).  It's
 possible that you just keep using the same mod_jk.conf file, a new one may
 not be getting written everytime Tomcat starts.

 For the 8080 message, make sure you have a HTTP connector on 8080 enabled
in
 server.xml.  Take a second and go back through my HOWTO (not the connector
 build steps).  There are only 4 or 5 specific changes to make to
httpd.conf
 and server.xml to get Apache working with Tomcat...and none of those
changes
 are major.

 John


  -Original Message-



--
To unsubscribe, e-mail:   mailto:tomcat-user-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org




RE: tomcat 4.1.12 with apache1.3.26 and mod_jk integration error.

2002-10-30 Thread Lambert, Stephen : CO IR
John, I still can't get this to work?!
I started over from scratch with your docs and was able correct the
duplicate mod_jk.conf problem.
However, when I try the following URL's, localhost still doesn't work.

http://localhost result= Netscape starts searching the internet

http://localhost:8080 result= Netscape starts searching the internet

http://w121c20.legacyhs:8080 result= works fine!

http://w121c20.legacyhs result= works fine!

Is this a Netscape issue?


-Original Message-
From: Turner, John [mailto:JTurner;AAS.com]
Sent: Tuesday, October 08, 2002 5:34 AM
To: 'Tomcat Users List'
Subject: RE: tomcat 4.1.12 with apache1.3.26 and mod_jk integration
error .



Take a look at the docs for the ApacheConfig Listener...there are parameters
there to stop things like appending to mod_jk.conf, which might be what is
happening.  In other words, shut everything down, wait a bit, delete
mod_jk.conf, then start up Tomcat and see if the mod_jk.conf file is correct
(make sure permissions on mod_jk.conf file are correct, too...the user
Tomcat is running as should have write/delete access to that file).  It's
possible that you just keep using the same mod_jk.conf file, a new one may
not be getting written everytime Tomcat starts.

For the 8080 message, make sure you have a HTTP connector on 8080 enabled in
server.xml.  Take a second and go back through my HOWTO (not the connector
build steps).  There are only 4 or 5 specific changes to make to httpd.conf
and server.xml to get Apache working with Tomcat...and none of those changes
are major.

John


 -Original Message-
 From: Lambert, Stephen : CO IR [mailto:SLambert;LHS.ORG]
 Sent: Monday, October 07, 2002 7:31 PM
 To: 'Tomcat Users List'
 Subject: RE: tomcat 4.1.12 with apache1.3.26 and mod_jk integration
 error .
 
 
 Changes below completed.
 Apache now starts with no warning!
 However, result of http://localhost:8080/examples is unable 
 to locate server
 localhost:8080
 
 And result of http://localhost/examples finds the jsp 
 examples with a URL of
 http://w121c20.legacyhs/examples/
 
 
 What's bizarre is that the mod_jk.conf file is once again 
 populated with a
 second VirtualHost directive after starting Tomcat.
 
 So if I stop/start Tomcat/Apache the VirtualHost warning 
 message re-appears.
 
 Stephen.
 
 -Original Message-
 From: Turner, John [mailto:JTurner;AAS.com]
 Sent: Monday, October 07, 2002 3:08 PM
 To: 'Tomcat Users List'
 Subject: RE: tomcat 4.1.12 with apache1.3.26 and mod_jk intergration
 error .
 
 
 
 In your server.xml, change the defaultHost parameter of your 
 Engine element
 to localhost.
 
 You're getting that Apache error because you have two VirtualHost
 definitions for w121c20.legacyhs in mod_jk.conf.  There 
 should only be one.
 
 Also, change ServerName in httpd.conf to w121c20.legacyhs.
 
 Give that a try, and see what happens.
 
 John
 
 
 


--
To unsubscribe, e-mail:   mailto:tomcat-user-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org




Re: tomcat 4.1.12 with apache1.3.26 and mod_jk integration error.

2002-10-30 Thread Josh G
You don't have localhost in your HOSTS file, add this entry and it'll all be
good :)

-Josh

Who can it be knocking at my door?
Go away, don't come round here no more.
Can't you see that it's late at night?
I'm very tired, and I'm not feeling right.
- Original Message -
From: Lambert, Stephen : CO IR [EMAIL PROTECTED]
To: 'Tomcat Users List' [EMAIL PROTECTED]
Sent: Thursday, October 31, 2002 11:20 AM
Subject: RE: tomcat 4.1.12 with apache1.3.26 and mod_jk integration error.


 John, I still can't get this to work?!
 I started over from scratch with your docs and was able correct the
 duplicate mod_jk.conf problem.
 However, when I try the following URL's, localhost still doesn't work.

 http://localhost result= Netscape starts searching the internet

 http://localhost:8080 result= Netscape starts searching the internet

 http://w121c20.legacyhs:8080 result= works fine!

 http://w121c20.legacyhs result= works fine!

 Is this a Netscape issue?


 -Original Message-
 From: Turner, John [mailto:JTurner;AAS.com]
 Sent: Tuesday, October 08, 2002 5:34 AM
 To: 'Tomcat Users List'
 Subject: RE: tomcat 4.1.12 with apache1.3.26 and mod_jk integration
 error .



 Take a look at the docs for the ApacheConfig Listener...there are
parameters
 there to stop things like appending to mod_jk.conf, which might be what is
 happening.  In other words, shut everything down, wait a bit, delete
 mod_jk.conf, then start up Tomcat and see if the mod_jk.conf file is
correct
 (make sure permissions on mod_jk.conf file are correct, too...the user
 Tomcat is running as should have write/delete access to that file).  It's
 possible that you just keep using the same mod_jk.conf file, a new one may
 not be getting written everytime Tomcat starts.

 For the 8080 message, make sure you have a HTTP connector on 8080 enabled
in
 server.xml.  Take a second and go back through my HOWTO (not the connector
 build steps).  There are only 4 or 5 specific changes to make to
httpd.conf
 and server.xml to get Apache working with Tomcat...and none of those
changes
 are major.

 John


  -Original Message-
  From: Lambert, Stephen : CO IR [mailto:SLambert;LHS.ORG]
  Sent: Monday, October 07, 2002 7:31 PM
  To: 'Tomcat Users List'
  Subject: RE: tomcat 4.1.12 with apache1.3.26 and mod_jk integration
  error .
 
 
  Changes below completed.
  Apache now starts with no warning!
  However, result of http://localhost:8080/examples is unable
  to locate server
  localhost:8080
 
  And result of http://localhost/examples finds the jsp
  examples with a URL of
  http://w121c20.legacyhs/examples/
 
 
  What's bizarre is that the mod_jk.conf file is once again
  populated with a
  second VirtualHost directive after starting Tomcat.
 
  So if I stop/start Tomcat/Apache the VirtualHost warning
  message re-appears.
 
  Stephen.
 
  -Original Message-
  From: Turner, John [mailto:JTurner;AAS.com]
  Sent: Monday, October 07, 2002 3:08 PM
  To: 'Tomcat Users List'
  Subject: RE: tomcat 4.1.12 with apache1.3.26 and mod_jk intergration
  error .
 
 
 
  In your server.xml, change the defaultHost parameter of your
  Engine element
  to localhost.
 
  You're getting that Apache error because you have two VirtualHost
  definitions for w121c20.legacyhs in mod_jk.conf.  There
  should only be one.
 
  Also, change ServerName in httpd.conf to w121c20.legacyhs.
 
  Give that a try, and see what happens.
 
  John
 
 
 


 --
 To unsubscribe, e-mail:
mailto:tomcat-user-unsubscribe;jakarta.apache.org
 For additional commands, e-mail:
mailto:tomcat-user-help;jakarta.apache.org



--
To unsubscribe, e-mail:   mailto:tomcat-user-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org




RE: tomcat 4.1.12 with apache1.3.26 and mod_jk integration error .

2002-10-08 Thread Turner, John


Take a look at the docs for the ApacheConfig Listener...there are parameters
there to stop things like appending to mod_jk.conf, which might be what is
happening.  In other words, shut everything down, wait a bit, delete
mod_jk.conf, then start up Tomcat and see if the mod_jk.conf file is correct
(make sure permissions on mod_jk.conf file are correct, too...the user
Tomcat is running as should have write/delete access to that file).  It's
possible that you just keep using the same mod_jk.conf file, a new one may
not be getting written everytime Tomcat starts.

For the 8080 message, make sure you have a HTTP connector on 8080 enabled in
server.xml.  Take a second and go back through my HOWTO (not the connector
build steps).  There are only 4 or 5 specific changes to make to httpd.conf
and server.xml to get Apache working with Tomcat...and none of those changes
are major.

John


 -Original Message-
 From: Lambert, Stephen : CO IR [mailto:[EMAIL PROTECTED]]
 Sent: Monday, October 07, 2002 7:31 PM
 To: 'Tomcat Users List'
 Subject: RE: tomcat 4.1.12 with apache1.3.26 and mod_jk integration
 error .
 
 
 Changes below completed.
 Apache now starts with no warning!
 However, result of http://localhost:8080/examples is unable 
 to locate server
 localhost:8080
 
 And result of http://localhost/examples finds the jsp 
 examples with a URL of
 http://w121c20.legacyhs/examples/
 
 
 What's bizarre is that the mod_jk.conf file is once again 
 populated with a
 second VirtualHost directive after starting Tomcat.
 
 So if I stop/start Tomcat/Apache the VirtualHost warning 
 message re-appears.
 
 Stephen.
 
 -Original Message-
 From: Turner, John [mailto:[EMAIL PROTECTED]]
 Sent: Monday, October 07, 2002 3:08 PM
 To: 'Tomcat Users List'
 Subject: RE: tomcat 4.1.12 with apache1.3.26 and mod_jk intergration
 error .
 
 
 
 In your server.xml, change the defaultHost parameter of your 
 Engine element
 to localhost.
 
 You're getting that Apache error because you have two VirtualHost
 definitions for w121c20.legacyhs in mod_jk.conf.  There 
 should only be one.
 
 Also, change ServerName in httpd.conf to w121c20.legacyhs.
 
 Give that a try, and see what happens.
 
 John
 
 
 
  -Original Message-
  From: Lambert, Stephen : CO IR [mailto:[EMAIL PROTECTED]]
  Sent: Monday, October 07, 2002 5:58 PM
  To: 'Tomcat Users List'
  Subject: RE: tomcat 4.1.12 with apache1.3.26 and mod_jk intergration
  error .
  
  
  
  
  -Original Message-
  From: Turner, John [mailto:[EMAIL PROTECTED]]
  Sent: Monday, October 07, 2002 2:50 PM
  To: 'Tomcat Users List'
  Subject: RE: tomcat 4.1.12 with apache1.3.26 and mod_jk intergration
  error .
  
  
  
  Post your httpd.conf, and mod_jk.conf if your JK commands are not in
  httpd.conf.
  
  John
  
  
 
 
 --
 To unsubscribe, e-mail:   
mailto:[EMAIL PROTECTED]
For additional commands, e-mail:
mailto:[EMAIL PROTECTED]

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




RE: tomcat 4.1.12 with apache1.3.26 and mod_jk integration error .

2002-10-07 Thread Lambert, Stephen : CO IR

Changes below completed.
Apache now starts with no warning!
However, result of http://localhost:8080/examples is unable to locate server
localhost:8080

And result of http://localhost/examples finds the jsp examples with a URL of
http://w121c20.legacyhs/examples/


What's bizarre is that the mod_jk.conf file is once again populated with a
second VirtualHost directive after starting Tomcat.

So if I stop/start Tomcat/Apache the VirtualHost warning message re-appears.

Stephen.

-Original Message-
From: Turner, John [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 07, 2002 3:08 PM
To: 'Tomcat Users List'
Subject: RE: tomcat 4.1.12 with apache1.3.26 and mod_jk intergration
error .



In your server.xml, change the defaultHost parameter of your Engine element
to localhost.

You're getting that Apache error because you have two VirtualHost
definitions for w121c20.legacyhs in mod_jk.conf.  There should only be one.

Also, change ServerName in httpd.conf to w121c20.legacyhs.

Give that a try, and see what happens.

John



 -Original Message-
 From: Lambert, Stephen : CO IR [mailto:[EMAIL PROTECTED]]
 Sent: Monday, October 07, 2002 5:58 PM
 To: 'Tomcat Users List'
 Subject: RE: tomcat 4.1.12 with apache1.3.26 and mod_jk intergration
 error .
 
 
 
 
 -Original Message-
 From: Turner, John [mailto:[EMAIL PROTECTED]]
 Sent: Monday, October 07, 2002 2:50 PM
 To: 'Tomcat Users List'
 Subject: RE: tomcat 4.1.12 with apache1.3.26 and mod_jk intergration
 error .
 
 
 
 Post your httpd.conf, and mod_jk.conf if your JK commands are not in
 httpd.conf.
 
 John
 
 


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




Apache-Tomcat-mod_jk integration

2001-07-05 Thread kun yan

I am new to tomcat. When I tried to build mod_jk from tomcat souce code, I
got the following error:
apxs:Break: Command failed with rc=16777215
after all the *.c compiled.

Anyone know why and how could I get mod_jk.so?

Thanks in advance!

Regards,

Kun