Hi, It was a misunderstanding, I thought that Apache caught the www.roamware.com:8080 and redirected it through the connector to Tomcat. Now I realise it is just Tomcat not working full stop. A pity they don't do a rpm for 4.1.12! I will delete the whole thing and start again.
By the way I altered the http script file in /etc/rc.d/init.d to call /use/local/apache2/apachectl. I did find that the tomcat4 script in /etc/rc.d/init.d points to one I didn't even know about in /user/bin/dtomcat4. I had changed the user in the tomcat.conf file that launches tomcat4 to root already based on your earlier suggestion. Thanks David -----Original Message----- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: 27 September 2002 19:34 To: 'Tomcat Users List' Subject: RE: New Release JK 1.2.0 not installing OK. I'm not sure I can comment any more, because I am fairly confused. I don't understand what you want to do...in your last message you mentioned accessing your app on port 8080, yet we are jumping through hoops trying to help you get a connector configured. If you access your app on port 8080, a connector to Apache is irrelevant. Can you not worry about Apache + Tomcat for a couple of hours, and just focus on getting your app working with Tomcat alone on port 8080 as mentioned in your last message? Just to try and clear things up...we are all over the board now and the best thing is to keep things as simple as possible. Regarding the socket connection error, at this point I can only assume it is an issue with Mandrake. I don't see anyone else posting about it from other operating systems, and I have never seen it on RedHat. John > -----Original Message----- > From: David Wynter [mailto:[EMAIL PROTECTED]] > Sent: Friday, September 27, 2002 2:31 PM > To: Tomcat Users List > Subject: RE: New Release JK 1.2.0 not installing > > > Hi John, > > I get identical results using startup.sh as root followed by > shutdown.sh as > root as I do with service tomcat4 start etc.. Same socket error. > > David > > -----Original Message----- > From: Turner, John [mailto:[EMAIL PROTECTED]] > Sent: 27 September 2002 19:10 > To: 'Tomcat Users List' > Subject: RE: New Release JK 1.2.0 not installing > > > > I think your socket problem has to do with 2 things: running > tomcat as user > "tomcat4", and using "service tomcat stop". > > Can you please try to start tomcat and stop tomcat just by executing > startup.sh and shutdown.sh in CATALINA_HOME/bin as root? > > John > > > > -----Original Message----- > > From: David Wynter [mailto:[EMAIL PROTECTED]] > > Sent: Friday, September 27, 2002 2:00 PM > > To: Tomcat Users List > > Subject: RE: New Release JK 1.2.0 not installing > > > > > > OK, > > > > I made the changes you and John suggested. I had put in a > > connector for port > > 8007 because I had it before with Apache 1.3.23, but now > > realise it was > > associated with ajp12 and is not needed. And yes the rest was > > the standard > > workers.properties. > > > > I have very simple requirements. I need Apache so I can run > Webmin to > > administer my Linux services easily. I have no static content > > on my website > > it is all served up by my Turbine servlet application. I need > > Tomcat on port > > 8080 so I can run my web site which is a Servlet application. > > > > After making the changes I am in exactly the same position. > > The same errors > > appear in the mod_jk.log. and I ge tthe same results when > > hitting the site. > > So there must be something more fundemental wrong. I > > discovered that I get > > an exception when I service tomcat4 stop here it is: > > > > Stopping tomcat4: Using CATALINA_BASE: /var/tomcat4 > > Using CATALINA_HOME: /var/tomcat4 > > Using CATALINA_TMPDIR: /var/tomcat4/temp > > Using JAVA_HOME: /usr/java/j2sdk1.4.1 > > Catalina.stop: java.net.ConnectException: Connection refused > > java.net.ConnectException: Connection refused > > at java.net.PlainSocketImpl.socketConnect(Native Method) > > at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305) > > at > > java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171) > > at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158) > > at java.net.Socket.connect(Socket.java:426) > > at java.net.Socket.connect(Socket.java:376) > > at java.net.Socket.<init>(Socket.java:291) > > at java.net.Socket.<init>(Socket.java:119) > > at org.apache.catalina.startup.Catalina.stop(Catalina.java:579) > > at > > org.apache.catalina.startup.Catalina.execute(Catalina.java:402) > > at > > org.apache.catalina.startup.Catalina.process(Catalina.java:180) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > at > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess > > orImpl.java:39 > > ) > > at > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth > > odAccessorImpl > > .java:25) > > at java.lang.reflect.Method.invoke(Method.java:324) > > at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203 > > > > It seems to start without error so not sure what this is? > > > > workers.properties is now reduced to this: > > > > workers.tomcat_home=/var/tomcat4 > > workers.java_home=/usr/java/j2sdk1.4.1 > > ps=/woker.list=ajp13 > > worker.list=ajp13 > > worker.ajp13.port=8009 > > worker.ajp13.host=www.roamware.com > > worker.ajp13.type=ajp13 > > > > I removed the 8007 connector from server.xml and changed the > > host name to > > www.roamware.com from localhost. Ditto for httpd.conf for ServerName > > > > I assume the "Jkmount /rwsite/servlet/* ajp13" in httpd.conf > > should cause > > any Gets with that in the URL to route via the connector? > > > > Should I re install Tomcat or do you think the socket problem > > has somethign > > to do with the connector? > > > > David > > > > -----Original Message----- > > From: Michael Schulz [mailto:[EMAIL PROTECTED]] > > Sent: 27 September 2002 18:34 > > To: Tomcat Users List > > Subject: RE: New Release JK 1.2.0 not installing > > > > > > David, > > > > You are all over the place...do you have a specific idea of > > what you are > > trying to do? > > > > Are you trying to integrate apache and tomcat? Do you want to > > send http > > requests directly to tomcat? > > > > Why are you using both ajp12 and ajp13, and load balancing? > > And your tomcat > > subsystem is configured to run in-process with apache? Is > > this really how > > you want it to run? > > > > I don't believe this is a default configuration, at least, > > not one that I > > have seen. > > > > You need to simplify...simplify...simplify. > > > > Let's assume that you want a (relatively) simple apache-tomcat > > configuration. > > > > That means http requests will ONLY arrive on port 80 - forget > > about port > > 8080, that is for running tomcat without apache. > > > > Get rid of the loadbalancing and ajp12 references in your > > workers.properties > > file. > > > > Since tomcat will only be listening for ajp13 requests from > > apache, you > > should remove *ALL* connectors from your tomcat server.xml > > file except the > > ajp13 connector listening on port 8009. > > > > Once you have made all those changes, perhaps we can have > > some sanity in > > terms of trying to figure out what is going wrong. Please > > post only your > > workers.properties and server.xml files. > > > > -Mike > > > > > > > > -----Original Message----- > > From: David Wynter [mailto:[EMAIL PROTECTED]] > > Sent: Friday, September 27, 2002 12:06 PM > > To: Tomcat Users List > > Subject: RE: New Release JK 1.2.0 not installing > > > > > > OK, they are all reproduced here, I have not tried to change > > them because I > > am stumped. Based on what I have read the config file s'look' right. > > > > I have Apache running on port 80 but when I try to use > www.roamware.com:8080 > I get connection refused now. > > I successfully built the connectors, followed the tutorial at > yolinux but > still cannot get Apache to redirect gets to port 8080 to Tomcat. > > Here are the contents of my logs and key config files, I've > cut the comments > out to reduce the bulk. Can you see what is > wrong, 'cause I cannot. > > > > -- > 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]> > > -- > 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]> -- 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]>
