Can you send me how you are accessing the website from within the firewall
and how you are accessing the same outside the firewall ?

Can you also send me the server.xml 


Regards
Guru 

Gurumoorthy Raghupathy
Web Support - Fidelity Investments International
* Tel: +44 1737 836798
* Internal: 8-724 6798
* Tel (R): +442086610646
* Tel (R): +447899033459
* Tel (S): +447736059647 
* Mail-Zone : XTW2A
* E-Mail: <<mailto:[EMAIL PROTECTED]>>

Important: Fidelity Investments International, Fidelity Investment Services
Limited, Fidelity Pensions Management and Financial Administration Services
Limited (a Fidelity Group company) are all authorised and regulated in the
UK by the Financial Services Authority and have their registered offices at
Oakhill House, 130 Tonbridge Road, Hildenborough, Tonbridge, Kent TN11 9DZ.
Tel 01732 361144. Fidelity only gives information on products and does not
give investment advice to private clients based on individual circumstances.
Any comments or statements made are not necessarily those of Fidelity. The
information transmitted is intended only for the person or entity to which
it is addressed and may contain confidential and/or privileged material. If
you received this in error, please contact the sender and delete the
material from any computer. All e-mails sent from or to Fidelity may be
subject to our monitoring procedures. 'Direct link to Fidelitys website.
<http://www.fidelity-international.com/world/index.html>

-----Original Message-----
From: Greg Allen [mailto:[EMAIL PROTECTED] 
Sent: 21 June 2006 12:37
To: Serlet Jean-Claude; users@tomcat.apache.org
Subject: RE: Mod_jk/firewall configuration problems


I didn't have socket_keepalive set.  But I added it and still have the same
problem.

 

>From my httpd.conf:

 

JkLogFile /var/log/httpd/mod_jk.log

JkLogLevel debug

 

# Just like workers.properties but exact line is prefixed

# with JkWorkerProperty

 

# Minimal jk configuration

JkWorkerProperty worker.list=ajp13w

JkWorkerProperty worker.ajp13w.type=ajp13

JkWorkerProperty worker.ajp13w.host=localhost

JkWorkerProperty worker.ajp13w.port=8009   

JkWorkerProperty worker.ajp13w.socket_keepalive=1   

 

# enter the full path to the tomcat webapps directory

JkAutoAlias /opt/tomcat/webapps

 

# Mount 'testapp' directory. It's physical location

# is assumed to be in the /opt/tomcat/webapps/testapp

# ajp13w is a worker defined in the workers.properties

JkMount /testapp/* ajp13w

 

# Unmount desired static content from testapp webapp.

# This content will be served by the httpd directly.

JkUnMount /testapp/images/*.gif ajp13w

JkUnMount /testapp/images/*.jpg ajp13w

 

-- Greg

 

 

 

 

  _____  

From: Serlet Jean-Claude [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, June 21, 2006 2:35 AM
To: Greg Allen; users@tomcat.apache.org
Subject: RE: Mod_jk/firewall configuration problems

 

Please give the configuration of your workers : the workers.properties.file

Have you set worker.yourworker.socket_keepalive=1 in it ?

 

Jean-Claude 

 

         

        
  _____  


        De : Greg Allen [mailto:[EMAIL PROTECTED] 
        Envoyé : mardi 20 juin 2006 16:42
        À : users@tomcat.apache.org
        Objet : Mod_jk/firewall configuration problems

        I am having a problem with mod_jk.so. I have apache set up as my web
server, forwarding my jsp
        traffic to a tomcat server running on the same machine.

         

        This setup works fine when the client is inside of my firewall.
However, when I try to access

        my site from outside the firewall, mod_jk does not forward the
traffic to tomcat and the page
        is not displayed.

         

        My firewall is set up to forward port 80 traffic from outside to my
web server machine. This
        is working, as I can get non-tomcat served pages to appear on
clients outside of the firewall.

         

        I have attached the debugging log from mod_jk. In it you can see two
requests - the first is 
        from outside (which fails), while the second is from inside and you
can see that it is served
        correctly.

         

        I'm sure this is some sort of configuration issue.  But I don't know
what.  

         

        Can anyone point out what is wrong?

         

        Thanks,

         

        -- Greg

         

Reply via email to