Re: High availability of tomcat 6
Kindly provide the configurations in detail to have high availability of tomcat servers. On Tue, Jul 26, 2011 at 5:22 PM, Pid wrote: > On 26/07/2011 11:08, Sri Lalitha wrote: > > Hi > > I am using Tomcat 6. I would like to know if instances of tomcat > servers > > be made highly available? > > > > Yes. > > p > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
RE: Class loading order
Hello, Can I use virtualWebAppLoader class to meet my requirements..? Regards Krishna -Original Message- From: Anne, Radhakrishna (NSN - IN/Bangalore) Sent: Tuesday, July 26, 2011 2:24 PM To: Tomcat Users List Subject: RE: Class loading order Hello, My web applications is designed to plug-in 3 rd party modules. 3rd party jars and my jars would placed under WEB-INF/libs. In case of bugs, the third party developer may provide hot fixes , which would be placed under WEB-INF/classes usually. I do not want to place their hot fixes under WEB-INF/classes, as they may conflict with my hot fixes and this would create some problems during maintenance. So I was checking the possibility of defining a new location for 3rd party hot fixes. Is there any way to do this..? Regards, Krishna -Original Message- From: ext Pid [mailto:p...@pidster.com] Sent: Tuesday, July 26, 2011 2:15 PM To: Tomcat Users List Subject: Re: Class loading order On 26/07/2011 09:38, Anne, Radhakrishna (NSN - IN/Bangalore) wrote: > > Hello, > > I would like to changes the default order look up for class loading, as > I understood from the doc, the order of look up is > 1)WEB-INF/classes > 2)WEB_INF/lib. > > Now I wanted to change this order and have my own order look up as shown > below i.e. > 1)/opt/shared/classes > 2)WEB-INF/classes > 3)WEB_INF/lib. > > Can someone help me out..? I am using tomcat 6 version. No, the only way to do this is via a custom classloader of your own design. It is probably a bad idea to do this - a webapp's classloader is supposed to load its own classes first. Why can't you include the classes in the webapp? p - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Issue with accepting IP address connections
> From: Steve Allan [mailto:s_alla...@yahoo.com] > Subject: Fw: Issue with accepting IP address connections > However, I now need to set up the IP address for the server Why do you think you need to do that? By default, Tomcat will listen on all IP addresses configured for the OS, so all you will be doing is limiting which IP addresses can be used to access Tomcat. In particular, 127.0.0.1 won't be available... > The Connector element is: > connectionTimeout="2" > addres="192.xxx.xx.x" > redirectPort="8443" /> > What do I need to do to get Tomcat monitor a certain IP > address? Perhaps spell "address" correctly in the element? - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Fw: Issue with accepting IP address connections
Hello, I have set up Tomcat 6.0 on a Windows 2007 server. IIS was (and still is) installed. I have changed the port to 8081 for testing and can see the Tomcat start page at localhost:8081. However, I now need to set up the IP address for the server which I thought was done through the Connector element is the server.xml file but trying the IP address after setting it up and restarting Tomcat gets a 'page can not be displayed' error. The Connector element is: What do I need to do to get Tomcat monitor a certain IP address? Thanks in advance, Steve - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Problems after updating from Tomcat 3.3 to 4.1: http tunneling servlet not working anymore
2011/7/26 Volker : > - tomcat 4.1.36_2 One reason to abandon 4.1 is that there are known security issues that has been fixed in 5.5 and later but have never been evaluated against 4.1 Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Problems after updating from Tomcat 3.3 to 4.1: http tunneling servlet not working anymore
Hallo Felix, thanks for your hints, I will check them out today. Believe it or not: Obviously the configuration for tomcat 4.1 I posted here is running correctly. But I did not notice it - and this will be the problem for all my chat site visitors that need http tunneling - because it takes nearly 2 minutes with tomcat 4.1 until the chat applets request of http://test.Domain.com/servlet/*HttpTunnelingServletdc does show up in apache?s log file whereas tomcat 3.3 is requesting the tunneling servlet at once. Result: Chatters behind a firewall that blocks several ports except port 80 can enter the chat in a few seconds by help of the tunneling servlet and tomcat 3.3. With tomcat 4.1 they will think the chat does not work and leave the site. I only noticed that slow behaviour because I had a phone call after requesting the chat applet behind a firewall only permitting port 80. Maybe you can recommend any tuning settings for my problem concerning tomcat 4.1? Thanks a lot and best regards V o l k e r Am 26.07.2011 19:54, schrieb Felix Schumacher: Hi Volker, Am Dienstag, den 26.07.2011, 16:29 +0200 schrieb Volker: Hello, my current system configuration is like following: - FreeBSD 8.2 - apache-2.2.17_2 - mod_jk-ap2-1.2.31_1 Apache2 JK - tomcat 4.1.36_2 As you said elsewhere in this thread, that you are willing to upgrade to a newer tomcat as well, I will assume, that you will use tomcat 6 or even tomcat 7. - diablo-jdk1.6.0 In order to provide a http tunneling for a chat server I have been using*tomcat 3.3*, FreeBSD 5.4, Apache 1.3, mod_jk (ajp12 Connector) and diablo-jre1.5.0 in combination with a certain http tunneling servlet *without any problems* for several years. That http tunneling servlet is passed via a chat applet via " The configuration for that system above _*can be found below*_ *=> Configuration for tomcat 3.3 That looks like you are using the strongly discouraged dispatcher servlet. That is still available, but disabled by default. And you should leave it that way. ... Thanks a lot and best regards Volker * NOT WORKING Configuration for Tomcat 4.1.36 (FreeBSD 8.2, Apache 2.2.17, mod_jk-ap2-1.2.31, Diablo JDK 1.6) ** The servlet classes result in: */usr/local/apache-tomcat4.1/webapps/ROOT/WEB-INF/classes* */usr/local/apache-tomcat4.1/webapps/ROOT/WEB-INF/classes*/*com/* */usr/local/apache-tomcat4.1/webapps/ROOT/WEB-INF/classes/digi/... I read that as: There are some files and directories under WEB-INF/classes in your ROOT webapp and that /usr/local/apache-tomcat4.1 is your CATALINA_BASE and probably CATALINA_HOME too. ... * httpd.conf *JkWorkersFile "/usr/local/etc/apache22/workers.properties" JkLogFile "/usr/local/apache-tomcat4.1/logs/mod_jk.log" JkShmFile /var/log/jk-runtime-status JkLogLevel info Looks OK. * workers.properties *workers.java_home=/usr/local/diablo-jdk1.6.0 workers.tomcat_home=/usr/local/apache-tomcat4.1 Remove both deprecated config options java_home and tomcat_home. They are not needed anymore. worker.list=jsp-hostname worker.jsp-hostname.port=8009 worker.jsp-hostname.host=127.0.0.1 worker.jsp-hostname.type=ajp13 worker.jsp-hostname.lbfactor=1* **server.xml* Copy the server.xml from a fresh tomcat download and replace your port-numbers in there. ... Your context descriptions for ROOT and example would be placed in newly created files named ROOT.xml and example.xml under $CATALINA_BASE/conf/Catalina/localhost. But I seriously doubt, that you need example.xml and ROOT.xml is not needed, if all you want to achieve is logging. Look at http://tomcat.apache.org/tomcat-7.0-doc/logging.html for more info about simple logging. *web.xml* http://java.sun.com/dtd/web-app_2_3.dtd";> You could update your webapp to a newer version by replacing the above values, but they should do no harm. HttpTunnelingServletdc *com.diginet.digichat.util.tunnel3.HttpTunnelingServlet* Host localhost 1 invoker /servlet/* HttpTunnelingServletdc /HttpTunnelingServletdc Instead of mapping a not configured servlet named invoker to /servlet/* you should map your servlet named HttpTunnelingServletdc to /servlet/HttpTunnelingServletdc or alternatively change your applet configuration from top of your post. So remove invoker... and change url-pattern in the from /HttpTunnelingServletdc to /servlet/HttpTunnelingServletdc ... *description* _The server encountered an internal error () that prevented it from fulfilling this request._ *exception* javax.servlet.ServletException at com.diginet.digichat.util.tunnel3.HttpTunnelingServlet.doGet([DashoPro-V1.3BETA-091199]) at javax.servlet.http.HttpServlet.service(HttpServlet.java:697) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) ... at org.apache.jk.common.ChannelSocket$Socket
Re: Unable to generate pw hash on cmd line since 7.0.16
On 27.7.2011 0:11, Ognjen Blagojevic wrote: Add tomcat-coyote.jar to your classpath, and you should be fine. Ops... Didn't notice you already solved it. Thunderbird broke it into separate threads. -Ognjen - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Unable to generate pw hash on cmd line since 7.0.16
Hi Jeremy, On 26.7.2011 17:37, M. Jeremy Carter wrote: Since upgrading to Tomcat 7.0.16, the command line noted at http://tomcat.apache.org/tomcat-7.0-doc/realm-howto.html hasn't worked for me. I've been unable to find any answers from google, other than some references that seem to say I'm missing tomcat-util.jar on my classpath (which I'm not). I did narrow the problem down to catalina.jar. If I copy an old version into the lib directory, overwriting the new copy, it works again. Am I doing something wrong, or is this a bug? See below for examples of running the command with various versions. Classpath info on realm-howto is a bit outdated. Add tomcat-coyote.jar to your classpath, and you should be fine. -Ognjen - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 6 not working with JDBC driver for MySQL
- Original Message - > From: Rainer Frey > To: Tomcat Users List > Cc: > Sent: Tuesday, July 26, 2011 5:01 AM > Subject: Re: Tomcat 6 not working with JDBC driver for MySQL > > Please stop top posting. > > On 26.07.2011, at 12:02, A Df wrote: >>> On 25.07.2011, at 22:40, A Df wrote: >>> Dear All: I have read numerous posts and documentation and now I really need > help. I am using the following: Product Version: NetBeans IDE 7.0 (Build 20110408) I performed the steps below as follows: I have added the MySQL Connector/J JDBC Driver to the > $CATALINA_HOME/lib directory However, it gives the error: org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create JDBC > driver OR java.sql.SQLException: No suitable driver >>> >>> Are you launching Tomcat from within Netbeans? Then I'd suspect > that Netbeans sets it >>> up with its own configuration, and esp. with a project specific class > path. Most instructions >>> out there imply that you launch Tomcat with the supplied scripts or > service utilities, and not with >>> an IDE plugin. >>> >>> Try >>> * launching Tomcat manually, by shell/batch scripts OR >>> * add the JDBC driver also to your Netbeans project class path > >> Hi Rainer: >> >> I had already added the JDBC driver to my Netbeans project class path and > that worked for awhile then stopped. > > Well sorry, no idea, as I don't use Netbeans. Maybe ask on a Netbeans > list/forum. >> >> I will have to do some reading on launching Tomcat manually by shell/batch > scripts but I don't have much time as I have a deadline to meet which is my > major concern. > > Not much to read. See RUNNING.txt in a tomcat distribution. > $CATALINA_HOME/lib > is the correct place for the driver. > > Rainer NetBeans is pretty benign when it comes to changing the Tomcat environment. It changes the JRE (uses the $JDK_HOME/jre/bin/java instead of JRE_HOME), and captures catalina.out to display in the IDE. Other than that, it adds nothing to the CLASSPATH, nor does it add any additional defines to JAVA_OPTS. You can change JAVA_OPTS defines in the server properties dialog, but I normally just use $CATALINA_HOME/bin/setenv.sh for that. That way my environment is consistent both in and out of NetBeans. When you start the server in debugging or profile mode, NetBeans adds the appropriate properties, but does not alter those you have defined in $CATALINA_HOME/bin/setenv.sh. When you're building a project in NetBeans and have it assigned to a server, NetBeans will add the content of that server's library to your project's CLASSPATH. There is no need to add the JDBC driver to your project's CLASSPATH if it already exists in $CATALINA_HOME/lib. In fact, coupled with the default NetBeans server property of Enable JDBC driver deployment, this is almost certainly a bad thing. Also, adding the library or JAR file to your project and having NetBeans package that in the WAR file is a bad thing. Just add the JAR file to $CATALINA_HOME/lib, use the Tomcat supplied database pooling, and everything just works. Permission problems may be an issue. If you're on Linux and the copied MySQL JAR file cannot be read by the owner of the Tomcat process, that would create problems. If you're on Windows, I imagine there are similar access issues, especially with Windows Vista or Windows 7. It would be interesting to see the following: 1. Use NetBeans to just build the project right-mouse button on the project and select Build 2. Start the Tomcat server using startup.sh (or startup.bat if you're on Windows) a. Open a command line window b. Change directory to $CATALINA_HOME/bin (%CATALINA_HOME%\bin on Windows) c. ./startup.sh (startup.bat on Windows) 3. Open a browser to localhost:8080 4. Start up the Manager application (use the same userid / password defined in NetBeans) 5. Choose a file to deploy a. Navigate to /dist in the browser b. Select the war file c. Click on the Deploy button 6. Open the application in a new browser window or tab 7. Post the contents of the log files a. catalina.out b. catalina..log c. any logging your application does (you do catch and log exceptions, yes?) I use this combination on Linux and Windows/XP Professional all the time. . . . . just my two cents. /mde/ - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Problems after updating from Tomcat 3.3 to 4.1: http tunneling servlet not working anymore
Hi Volker, Am Dienstag, den 26.07.2011, 16:29 +0200 schrieb Volker: > Hello, > > my current system configuration is like following: > > - FreeBSD 8.2 > - apache-2.2.17_2 > - mod_jk-ap2-1.2.31_1 Apache2 JK > - tomcat 4.1.36_2 As you said elsewhere in this thread, that you are willing to upgrade to a newer tomcat as well, I will assume, that you will use tomcat 6 or even tomcat 7. > - diablo-jdk1.6.0 > > In order to provide a http tunneling for a chat server I have been > using*tomcat 3.3*, FreeBSD 5.4, Apache 1.3, mod_jk (ajp12 Connector) and > diablo-jre1.5.0 in combination with a certain http tunneling servlet > *without any problems* for several years. > That http tunneling servlet is passed via a chat applet via " NAME='HttpServlet' > VALUE='http://test.Domain.com/servlet/*HttpTunnelingServletdc*'> > The configuration for that system above _*can be found below*_ *=> > Configuration for tomcat 3.3 That looks like you are using the strongly discouraged dispatcher servlet. That is still available, but disabled by default. And you should leave it that way. > ... > > Thanks a lot and best regards > > Volker > * > > NOT WORKING > Configuration for Tomcat 4.1.36 (FreeBSD 8.2, Apache 2.2.17, > mod_jk-ap2-1.2.31, Diablo JDK 1.6) > ** > > The servlet classes result in: > */usr/local/apache-tomcat4.1/webapps/ROOT/WEB-INF/classes* > */usr/local/apache-tomcat4.1/webapps/ROOT/WEB-INF/classes*/*com/* > */usr/local/apache-tomcat4.1/webapps/ROOT/WEB-INF/classes/digi/... I read that as: There are some files and directories under WEB-INF/classes in your ROOT webapp and that /usr/local/apache-tomcat4.1 is your CATALINA_BASE and probably CATALINA_HOME too. > ... > * > httpd.conf > *JkWorkersFile "/usr/local/etc/apache22/workers.properties" > JkLogFile "/usr/local/apache-tomcat4.1/logs/mod_jk.log" > JkShmFile /var/log/jk-runtime-status > JkLogLevel info Looks OK. > * > workers.properties > *workers.java_home=/usr/local/diablo-jdk1.6.0 > workers.tomcat_home=/usr/local/apache-tomcat4.1 Remove both deprecated config options java_home and tomcat_home. They are not needed anymore. > worker.list=jsp-hostname > worker.jsp-hostname.port=8009 > worker.jsp-hostname.host=127.0.0.1 > worker.jsp-hostname.type=ajp13 > worker.jsp-hostname.lbfactor=1* > > **server.xml* Copy the server.xml from a fresh tomcat download and replace your port-numbers in there. > ... > > > crossContext="true"> > prefix="ROOT-http-tunneling_log." suffix=".txt" timestamp="true"/> > > > > crossContext="true"> > prefix="localhost_examples_log." suffix=".txt" timestamp="true"/> >home="com.wombat.empl.EmployeeRecordHome" > remote="com.wombat.empl.EmployeeRecord"/> Your context descriptions for ROOT and example would be placed in newly created files named ROOT.xml and example.xml under $CATALINA_BASE/conf/Catalina/localhost. But I seriously doubt, that you need example.xml and ROOT.xml is not needed, if all you want to achieve is logging. Look at http://tomcat.apache.org/tomcat-7.0-doc/logging.html for more info about simple logging. > > > *web.xml* > > PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" > "http://java.sun.com/dtd/web-app_2_3.dtd";> You could update your webapp to a newer version by replacing the above values, but they should do no harm. > > > > HttpTunnelingServletdc > > > *com.diginet.digichat.util.tunnel3.HttpTunnelingServlet* > > > Host > localhost > > 1 > > > invoker > /servlet/* > > > HttpTunnelingServletdc > /HttpTunnelingServletdc > Instead of mapping a not configured servlet named invoker to /servlet/* you should map your servlet named HttpTunnelingServletdc to /servlet/HttpTunnelingServletdc or alternatively change your applet configuration from top of your post. So remove invoker... and change url-pattern in the from /HttpTunnelingServletdc to /servlet/HttpTunnelingServletdc > > ... > *description* _The server encountered an internal error () that > prevented it from fulfilling this request._ > > *exception* > > javax.servlet.ServletException > at > com.diginet.digichat.util.tunnel3.HttpTunnelingServlet.doGet([DashoPro-V1.3BETA-091199]) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:697) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) ... > at > org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:895) > at > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685) > at java.lang.Thread.run(Thread.java:619) > > *root cause* > > java.lang.NullPointerException > at > com.diginet.digichat.util.tunnel3.HttpTunnelingServlet.doGet([DashoPro-V1.3BETA-091199]) Hopefully you have the source code for HttpTunnelingServlet since this line means, your servlet
Re: Unable to generate pw hash on cmd line since 7.0.16
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeremy, On 7/26/2011 12:09 PM, M. Jeremy Carter wrote: > Found a java guy here locally that helped me with this. It looks > like HexUtils was moved to tomcat-coyote.jar. Added that to my > classpath and it works now. The url I mentioned below should > probably be updated though. Please file a documentation bug in bugzilla. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk4u6ZoACgkQ9CaO5/Lv0PDkYgCdGONCU75ZKDtSO9sv0BDyXQC+ CPAAn05IkaFveBLq1VZLJeDOs7KYp2uh =TwkE -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: AJP-APR failures on Tomcat 7.0.16 with ISAPI Redirector 1.2.32
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Konstantin, On 7/14/2011 8:41 AM, eurotrans-Verlag wrote: > An alternative that I could imagine, would be to create a class > (that has a boolean flag) which extends OutputStream, and decorates > another OutputStream that is given to the class in the constructor > (that would be the OutputStream from the servlet's response). This > class would pass all calls to it to the other OutputStream (as long > as the flag is true), and as soon as close() or another special > method is called, it sets the flag to false, which causes all other > methods to do nothing (or throw an IOException). That way, Tomcat's > OutputStream would also be protected from future calls from the > ImageIO. You should also null-out the reference to Tomcat's output stream. This would allow you to "leak" your own decorator objects but not interfere with Tomcat's ability to do it's own object management. Such a class would definitely be useful to post on the Wiki. > However, it seems also a bit strange to me that Tomcat is recycling > OutputStreams, because in my understanding, once an OutputStream is > closed, it should be impossible to do any further write() calls to > it. True, but Tomcat tries to avoid as much memory churn as possible, and re-uses objects whenever possible. You can change this behavior with configuration if you want. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk4u6AQACgkQ9CaO5/Lv0PD6cACfW4BS55+FtwpK3ZonNjOuvfPV v+MAn3iCTpTSI+FOBkgdI9UOZD4YvsM6 =oazD -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: AJP-APR failures on Tomcat 7.0.16 with ISAPI Redirector 1.2.32
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Konstantin, On 7/13/2011 6:53 PM, eurotrans-Verlag wrote: > Thanks. In the meantime, I also came to that conclusion and replaced > all instances of > > ImageIO.write(img, "PNG", response.getOutputStream()) > > in my servlets/webapps with something like > > ByteArrayOutputStream bout = new ByteArrayOutputStream(); > ImageIO.write(img, "PNG", bout); > bout.writeTo(response.getOutputStream()); > > so that the ImageIO never sees the real OutputStream, and it seems to > work fine (no more IllegalStateExceptions or "wrong message format" > errors in the isapi log when using AJP-APR). Wow, I'm surprised that had an effect. Or, rather, I'm surprised that ImageIO doesn't have decent object reference management. > Is that a good practice (using ByteArrayOutputStream, then copy it to > the response) to dynamically generate Images and serve them to the > clients? There is a downside: you need a bunch of temporary memory available to perform these image manipulations. ImageIO uses a lots of memory already, and now you are going to have to buffer the entire output image before the first byte is written back to the client. That means no streaming whatsoever, which might strain your resources. You might want to look at your heap size, average image size, and estimated user load to determine if you want to do something like put a hard limit on the number of image transformations that can be performed simultaneously. Otherwise, you risk OOME. > Also, is there any hint to this on the Tomcat documentation/wiki? > Because I don't think it would be unusual to dynamically generate > images and serve them to clients using the ImageIO, and I think it > could be a bit frustrating to find the actual problem if one doesn't > know this. Tomcat obviously can't document all foreign API problems out there, but it might be worth mentioning this one on the Wiki somewhere. Feel free to create a wiki account and create a new page for these kinds of things. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk4u5yMACgkQ9CaO5/Lv0PDMGQCfSLZ1BpdK7GVqd5wh+ZjYzFTA H50AoIzjIoX6r72h4k1/VMLLqBjNPSI8 =V6o8 -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Unable to generate pw hash on cmd line since 7.0.16
Found a java guy here locally that helped me with this. It looks like HexUtils was moved to tomcat-coyote.jar. Added that to my classpath and it works now. The url I mentioned below should probably be updated though.
Unable to generate pw hash on cmd line since 7.0.16
Since upgrading to Tomcat 7.0.16, the command line noted at http://tomcat.apache.org/tomcat-7.0-doc/realm-howto.html hasn't worked for me. I've been unable to find any answers from google, other than some references that seem to say I'm missing tomcat-util.jar on my classpath (which I'm not). I did narrow the problem down to catalina.jar. If I copy an old version into the lib directory, overwriting the new copy, it works again. Am I doing something wrong, or is this a bug? See below for examples of running the command with various versions. OS: Windows XP and Windows Server 2003 Thanks, Jeremy C. C:\Code\tomcattest>java -version java version "1.6.0_26" Java(TM) SE Runtime Environment (build 1.6.0_26-b03) Java HotSpot(TM) Client VM (build 20.1-b02, mixed mode, sharing) C:\Code\tomcattest>dir /ad /b apache-tomcat-7.0.11 apache-tomcat-7.0.12 apache-tomcat-7.0.14 apache-tomcat-7.0.16 apache-tomcat-7.0.19 C:\Code\tomcattest>set classpath classpath=c:\code\tomcattest\apache-tomcat\bin\tomcat-juli.jar;c:\code\tomcattest\apache-tomcat\lib\catalina.jar;c:\code\tomcattest\apache-tomcat\lib\tomcat-util.jar C:\Code\tomcattest>xcopy /e /q /i apache-tomcat-7.0.11 apache-tomcat 543 File(s) copied C:\Code\tomcattest>java org.apache.catalina.realm.RealmBase -a SHA mypass mypass:e727d1464ae12436e899a726da5b2f11d8381b26 C:\Code\tomcattest>rd /q /s apache-tomcat C:\Code\tomcattest>xcopy /e /q /i apache-tomcat-7.0.12 apache-tomcat 544 File(s) copied C:\Code\tomcattest>java org.apache.catalina.realm.RealmBase -a SHA mypass mypass:e727d1464ae12436e899a726da5b2f11d8381b26 C:\Code\tomcattest>rd /q /s apache-tomcat C:\Code\tomcattest>xcopy /e /q /i apache-tomcat-7.0.14 apache-tomcat 544 File(s) copied C:\Code\tomcattest>java org.apache.catalina.realm.RealmBase -a SHA mypass mypass:e727d1464ae12436e899a726da5b2f11d8381b26 C:\Code\tomcattest>rd /q /s apache-tomcat C:\Code\tomcattest>xcopy /e /q /i apache-tomcat-7.0.16 apache-tomcat 544 File(s) copied C:\Code\tomcattest>java org.apache.catalina.realm.RealmBase -a SHA mypass mypass:Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/tomcat/util/buf/HexUtils at org.apache.catalina.realm.RealmBase.Digest(RealmBase.java:1293) at org.apache.catalina.realm.RealmBase.main(RealmBase.java:1320) Caused by: java.lang.ClassNotFoundException: org.apache.tomcat.util.buf.HexUtils at java.net.URLClassLoader$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) ... 2 more C:\Code\tomcattest>rd /q /s apache-tomcat C:\Code\tomcattest>xcopy /e /q /i apache-tomcat-7.0.19 apache-tomcat 547 File(s) copied C:\Code\tomcattest>java org.apache.catalina.realm.RealmBase -a SHA mypass mypass:Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/tomcat/util/buf/HexUtils at org.apache.catalina.realm.RealmBase.Digest(RealmBase.java:1291) at org.apache.catalina.realm.RealmBase.main(RealmBase.java:1318) Caused by: java.lang.ClassNotFoundException: org.apache.tomcat.util.buf.HexUtils at java.net.URLClassLoader$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) ... 2 more C:\Code\tomcattest>copy apache-tomcat-7.0.11\lib\catalina.jar apache-tomcat\lib Overwrite apache-tomcat\lib\catalina.jar? (Yes/No/All): y 1 file(s) copied. C:\Code\tomcattest>java org.apache.catalina.realm.RealmBase -a SHA mypass mypass:e727d1464ae12436e899a726da5b2f11d8381b26 C:\Code\tomcattest>
there is mistake in the LocalString file
hi all: my configure: tomcat 7.0.12/19 windows xp sp3 in the file "org/apache/catalina/connectorLocalStrings.properties" line 54&55 coyoteRequest.getInputStream.ise=getReader() has already been called for this request coyoteRequest.getReader.ise=getInputStream() has already been called for this request i think that should be: coyoteRequest.getInputStream.ise=getInputStream() has already been called for this request coyoteRequest.getReader.ise=getReader() has already been called for this request it's OK?
Re: Problems after updating from Tomcat 3.3 to 4.1: http tunneling servlet not working anymore
Am 26.07.2011 16:43, schrieb David kerber: On 7/26/2011 10:29 AM, Volker wrote: Hello, my current system configuration is like following: - FreeBSD 8.2 - apache-2.2.17_2 - mod_jk-ap2-1.2.31_1 Apache2 JK - tomcat 4.1.36_2 - diablo-jdk1.6.0 Since you have to upgrade any way, why not upgrade to a current version of TC, such as 6.0.x, or 7.x? You're not likely to find many people here who remember (or even ever used) tc 4.x. D Hi, I chose tomcat 4.1 because I thought that the differences in configuration of tomcat 4.1 compared with 3.3 are less than compared with 7.x. If you could have a look on my working config of 3.3 and tell me how to transfer them in a config for 7.x I even would install 7.x ;-) I really "only" use it for that littel http tunneling script! Best regards Volker - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Problems after updating from Tomcat 3.3 to 4.1: http tunneling servlet not working anymore
I forget to mention that in httpd.conf the connectors are integrated like following: JkMount /servlet jsp-hostname JkMount /servlet/* jsp-hostname Best regards Volker Am 26.07.2011 16:29, schrieb Volker: Hello, my current system configuration is like following: - FreeBSD 8.2 - apache-2.2.17_2 - mod_jk-ap2-1.2.31_1 Apache2 JK - tomcat 4.1.36_2 - diablo-jdk1.6.0 In order to provide a http tunneling for a chat server I have been using*tomcat 3.3*, FreeBSD 5.4, Apache 1.3, mod_jk (ajp12 Connector) and diablo-jre1.5.0 in combination with a certain http tunneling servlet *without any problems* for several years. That http tunneling servlet is passed via a chat applet via " The configuration for that system above _*can be found below*_ *=> Configuration for tomcat 3.3 *After upgrading to FreeBSD 8.2 I had to upgrade from tomcat 3.3 to 4.1 because I did not find any port for tomcat version 3.3. I do not manage to make the httpd tunneling applet running correctly with ajp1.3 but I think it does not depend on the connector but a misconfigured mapping. I guess that following warning in mod_jk.log shows up the reason for my problem when requesting http://test.Domain.com/servlet/*HttpTunnelingServletdc*' *[Tue Jul 26 13:00:56.615 2011] [36163:34382823872] [warn] map_uri_to_worker_ext::jk_uri_worker_map.c (962): Uri * is invalid. Uri must start with /* However the tomcat 4.1 start page is accessible via http://domain:8180 and working correctly! Below you find the configuration of my current system under FreeBSD mentioned above with tomcat 4.1.36 and apache 2.2.17 which does not run correctly _and the configuration for tomcat 3.3 which is running correctly_.* *Since I am not familiar with tomcat I would be glad if someone could give me a hint to solve my problem. Or maybe someone can give me some hints for how to compile tomcat 3.3 sources for FreeBSD ;-) Thanks a lot and best regards Volker * NOT WORKING Configuration for Tomcat 4.1.36 (FreeBSD 8.2, Apache 2.2.17, mod_jk-ap2-1.2.31, Diablo JDK 1.6) ** The servlet classes result in: */usr/local/apache-tomcat4.1/webapps/ROOT/WEB-INF/classes* */usr/local/apache-tomcat4.1/webapps/ROOT/WEB-INF/classes*/*com/* */usr/local/apache-tomcat4.1/webapps/ROOT/WEB-INF/classes/digi/... ... * httpd.conf *JkWorkersFile "/usr/local/etc/apache22/workers.properties" JkLogFile "/usr/local/apache-tomcat4.1/logs/mod_jk.log" JkShmFile /var/log/jk-runtime-status JkLogLevel info * workers.properties *workers.java_home=/usr/local/diablo-jdk1.6.0 workers.tomcat_home=/usr/local/apache-tomcat4.1 worker.list=jsp-hostname worker.jsp-hostname.port=8009 worker.jsp-hostname.host=127.0.0.1 worker.jsp-hostname.type=ajp13 worker.jsp-hostname.lbfactor=1* **server.xml* *web.xml* http://java.sun.com/dtd/web-app_2_3.dtd";> HttpTunnelingServletdc *com.diginet.digichat.util.tunnel3.HttpTunnelingServlet* Host localhost 1 invoker /servlet/* HttpTunnelingServletdc /HttpTunnelingServletdc *catalina.out* StandardEngine[null]: setJvmRoute=jsp-hostname Jul 26, 2011 11:25:19 AM org.apache.coyote.http11.Http11BaseProtocol init INFO: Initializing Coyote HTTP/1.1 on http-8180 Starting service Tomcat-Standalone Apache Tomcat/4.1.36 HTTP Tunnel connected to the digichat server localhost HTTP Tunnel connected to the digichat server localhost Jul 26, 2011 11:25:20 AM org.apache.coyote.http11.Http11BaseProtocol start INFO: Starting Coyote HTTP/1.1 on http-8180 Jul 26, 2011 11:25:20 AM org.apache.jk.common.ChannelSocket init INFO: JK: ajp13 listening on /0.0.0.0:8009 Jul 26, 2011 11:25:20 AM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=0/17 config=null *mod_jk.log* [Tue Jul 26 11:25:13.007 2011] [35031:34382823872] [info] init_jk::mod_jk.c (3198): mod_jk/1.2.31 (1026297) initialized [Tue Jul 26 11:29:37.458 2011] [35103:34382823872] [warn] map_uri_to_worker_ext::jk_uri_worker_map.c (962): Uri * is invalid. Uri must start with / [Tue Jul 26 11:30:15.672 2011] [35034:34382823872] [warn] map_uri_to_worker_ext::jk_uri_worker_map.c (962): Uri * is invalid. Uri must start with / *ROOT-http-tunneling_log.2011-07-26.txt* 2011-07-26 11:25:19 WebappLoader[/ROOT]: Deploying class repositories to work directory /usr/local/apache-tomcat4.1/work/Standalone/localhost/ROOT 2011-07-26 11:25:19 WebappLoader[/ROOT]: Deploy class files /WEB-INF/classes to /usr/local/apache-tomcat4.1/webapps/ROOT/WEB-INF/classes 2011-07-26 11:25:19 WebappLoader[/ROOT]: Reloading checks are enabled for this Context 2011-07-26 11:25:19 StandardManager[/ROOT]: Seeding random number generator class java.security.SecureRandom 2011-07-26 11:25:19 StandardManager[/ROOT]: Seeding of random number generator has been completed 2011-07-26 11:25:19 StandardWrapper[/ROOT:default]: Loading container servlet default 2011-07-26 11:25:19
Re: Problems after updating from Tomcat 3.3 to 4.1: http tunneling servlet not working anymore
On 7/26/2011 10:29 AM, Volker wrote: Hello, my current system configuration is like following: - FreeBSD 8.2 - apache-2.2.17_2 - mod_jk-ap2-1.2.31_1 Apache2 JK - tomcat 4.1.36_2 - diablo-jdk1.6.0 Since you have to upgrade any way, why not upgrade to a current version of TC, such as 6.0.x, or 7.x? You're not likely to find many people here who remember (or even ever used) tc 4.x. D - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Problems after updating from Tomcat 3.3 to 4.1: http tunneling servlet not working anymore
Hello, my current system configuration is like following: - FreeBSD 8.2 - apache-2.2.17_2 - mod_jk-ap2-1.2.31_1 Apache2 JK - tomcat 4.1.36_2 - diablo-jdk1.6.0 In order to provide a http tunneling for a chat server I have been using*tomcat 3.3*, FreeBSD 5.4, Apache 1.3, mod_jk (ajp12 Connector) and diablo-jre1.5.0 in combination with a certain http tunneling servlet *without any problems* for several years. That http tunneling servlet is passed via a chat applet via "NAME='HttpServlet' VALUE='http://test.Domain.com/servlet/*HttpTunnelingServletdc*'> The configuration for that system above _*can be found below*_ *=> Configuration for tomcat 3.3 *After upgrading to FreeBSD 8.2 I had to upgrade from tomcat 3.3 to 4.1 because I did not find any port for tomcat version 3.3. I do not manage to make the httpd tunneling applet running correctly with ajp1.3 but I think it does not depend on the connector but a misconfigured mapping. I guess that following warning in mod_jk.log shows up the reason for my problem when requesting http://test.Domain.com/servlet/*HttpTunnelingServletdc*' *[Tue Jul 26 13:00:56.615 2011] [36163:34382823872] [warn] map_uri_to_worker_ext::jk_uri_worker_map.c (962): Uri * is invalid. Uri must start with /* However the tomcat 4.1 start page is accessible via http://domain:8180 and working correctly! Below you find the configuration of my current system under FreeBSD mentioned above with tomcat 4.1.36 and apache 2.2.17 which does not run correctly _and the configuration for tomcat 3.3 which is running correctly_.* *Since I am not familiar with tomcat I would be glad if someone could give me a hint to solve my problem. Or maybe someone can give me some hints for how to compile tomcat 3.3 sources for FreeBSD ;-) Thanks a lot and best regards Volker * NOT WORKING Configuration for Tomcat 4.1.36 (FreeBSD 8.2, Apache 2.2.17, mod_jk-ap2-1.2.31, Diablo JDK 1.6) ** The servlet classes result in: */usr/local/apache-tomcat4.1/webapps/ROOT/WEB-INF/classes* */usr/local/apache-tomcat4.1/webapps/ROOT/WEB-INF/classes*/*com/* */usr/local/apache-tomcat4.1/webapps/ROOT/WEB-INF/classes/digi/... ... * httpd.conf *JkWorkersFile "/usr/local/etc/apache22/workers.properties" JkLogFile "/usr/local/apache-tomcat4.1/logs/mod_jk.log" JkShmFile /var/log/jk-runtime-status JkLogLevel info * workers.properties *workers.java_home=/usr/local/diablo-jdk1.6.0 workers.tomcat_home=/usr/local/apache-tomcat4.1 worker.list=jsp-hostname worker.jsp-hostname.port=8009 worker.jsp-hostname.host=127.0.0.1 worker.jsp-hostname.type=ajp13 worker.jsp-hostname.lbfactor=1* **server.xml* protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler" /> jvmRoute="jsp-hostname"> crossContext="true"> prefix="ROOT-http-tunneling_log." suffix=".txt" timestamp="true"/> crossContext="true"> prefix="localhost_examples_log." suffix=".txt" timestamp="true"/> *web.xml* http://java.sun.com/dtd/web-app_2_3.dtd";> HttpTunnelingServletdc *com.diginet.digichat.util.tunnel3.HttpTunnelingServlet* Host localhost 1 invoker /servlet/* HttpTunnelingServletdc /HttpTunnelingServletdc *catalina.out* StandardEngine[null]: setJvmRoute=jsp-hostname Jul 26, 2011 11:25:19 AM org.apache.coyote.http11.Http11BaseProtocol init INFO: Initializing Coyote HTTP/1.1 on http-8180 Starting service Tomcat-Standalone Apache Tomcat/4.1.36 HTTP Tunnel connected to the digichat server localhost HTTP Tunnel connected to the digichat server localhost Jul 26, 2011 11:25:20 AM org.apache.coyote.http11.Http11BaseProtocol start INFO: Starting Coyote HTTP/1.1 on http-8180 Jul 26, 2011 11:25:20 AM org.apache.jk.common.ChannelSocket init INFO: JK: ajp13 listening on /0.0.0.0:8009 Jul 26, 2011 11:25:20 AM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=0/17 config=null *mod_jk.log* [Tue Jul 26 11:25:13.007 2011] [35031:34382823872] [info] init_jk::mod_jk.c (3198): mod_jk/1.2.31 (1026297) initialized [Tue Jul 26 11:29:37.458 2011] [35103:34382823872] [warn] map_uri_to_worker_ext::jk_uri_worker_map.c (962): Uri * is invalid. Uri must start with / [Tue Jul 26 11:30:15.672 2011] [35034:34382823872] [warn] map_uri_to_worker_ext::jk_uri_worker_map.c (962): Uri * is invalid. Uri must start with / *ROOT-http-tunneling_log.2011-07-26.txt* 2011-07-26 11:25:19 WebappLoader[/ROOT]: Deploying class repositories to work directory /usr/local/apache-tomcat4.1/work/Standalone/localhost/ROOT 2011-07-26 11:25:19 WebappLoader[/ROOT]: Deploy class files /WEB-INF/classes to /usr/local/apache-tomcat4.1/webapps/ROOT/WEB-INF/classes 2011-07-26 11:25:19 WebappLoader[/ROOT]: Reloading checks are enabled for this Context 2011-07-26 11:25:19 StandardManager[/ROOT]: Seeding random number generator class java.security.SecureRandom 2011-07-26 11:25:19 St
Re: Tomcat 6 not working with JDBC driver for MySQL
Please stop top posting. On 26.07.2011, at 12:02, A Df wrote: >> On 25.07.2011, at 22:40, A Df wrote: >> >>> Dear All: >>> >>> I have read numerous posts and documentation and now I really need help. >>> >>> >>> I am using the following: >>> >>> Product Version: NetBeans IDE 7.0 (Build 20110408) >>> >>> I performed the steps below as follows: >>> >>> I have added the MySQL Connector/J JDBC Driver to the $CATALINA_HOME/lib >>> directory >>> However, it gives the error: >>> org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create JDBC driver >>> OR >>> java.sql.SQLException: No suitable driver >> >> Are you launching Tomcat from within Netbeans? Then I'd suspect that >> Netbeans sets it >> up with its own configuration, and esp. with a project specific class path. >> Most instructions >> out there imply that you launch Tomcat with the supplied scripts or service >> utilities, and not with >> an IDE plugin. >> >> Try >> * launching Tomcat manually, by shell/batch scripts OR >> * add the JDBC driver also to your Netbeans project class path > Hi Rainer: > > I had already added the JDBC driver to my Netbeans project class path and > that worked for awhile then stopped. Well sorry, no idea, as I don't use Netbeans. Maybe ask on a Netbeans list/forum. > > I will have to do some reading on launching Tomcat manually by shell/batch > scripts but I don't have much time as I have a deadline to meet which is my > major concern. Not much to read. See RUNNING.txt in a tomcat distribution. $CATALINA_HOME/lib is the correct place for the driver. Rainer - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: High availability of tomcat 6
On 26/07/2011 11:08, Sri Lalitha wrote: > Hi > I am using Tomcat 6. I would like to know if instances of tomcat servers > be made highly available? > Yes. p - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
High availability of tomcat 6
Hi I am using Tomcat 6. I would like to know if instances of tomcat servers be made highly available?
Re: Tomcat 6 not working with JDBC driver for MySQL
Hi Rainer: I had already added the JDBC driver to my Netbeans project class path and that worked for awhile then stopped. The previous problem is that it works occasionally then stopped. Now it works and inserts one row then stops even if restart Tomcat. I will have to do some reading on launching Tomcat manually by shell/batch scripts but I don't have much time as I have a deadline to meet which is my major concern. I don't really know much about Tomcat so do you have any suggestions on: * should i start the web application from netbeans or from Tomcat? * how would i test the web application from Tomcat alone? * do you know how to prevent netbeans from launching Tomcat? * which locations do I need to have the jar file in? Sorry for asking so many questions but as I mentioned I don't really know much about Tomcat and this is my first time using netbeans to create a web application usually I do windows/desktop apps in Eclipse. Cheers, A Df > >From: Rainer Frey >To: Tomcat Users List >Sent: Tuesday, 26 July 2011, 7:04 >Subject: Re: Tomcat 6 not working with JDBC driver for MySQL > > >On 25.07.2011, at 22:40, A Df wrote: > >> Dear All: >> >> I have read numerous posts and documentation and now I really need help. >> >> >> I am using the following: >> >> Product Version: NetBeans IDE 7.0 (Build 20110408) >> >> I performed the steps below as follows: >> >> I have added the MySQL Connector/J JDBC Driver to the $CATALINA_HOME/lib >> directory >> However, it gives the error: >> org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create JDBC driver >> OR >> java.sql.SQLException: No suitable driver > >Are you launching Tomcat from within Netbeans? Then I'd suspect that Netbeans >sets it >up with its own configuration, and esp. with a project specific class path. >Most instructions >out there imply that you launch Tomcat with the supplied scripts or service >utilities, and not with >an IDE plugin. > >Try >* launching Tomcat manually, by shell/batch scripts OR >* add the JDBC driver also to your Netbeans project class path > >Rainer >- >To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >For additional commands, e-mail: users-h...@tomcat.apache.org > > > >
Re: Upgrading from Tomcat 7.0.8 to 7.0.10 and higher causes Old Generation memory problems
On 26/07/2011 10:43, Ian Marsh wrote: > Unfortunately the conf changes to fork the compilation of JSPs and the > increased 'modificationTestInterval' value made no real improvement so > I am continuing to work towards replacing the language text request > scope variables with property files references. > > However, if this is a problem, this has made me concerned that all > request scope variables aren't being released, not just the ones we > use for language text! Again, use a profiler and follow the gc roots. Until you provide some evidence that Tomcat is doing something wrong, the assumption is going to be that the problem is with the application. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Upgrading from Tomcat 7.0.8 to 7.0.10 and higher causes Old Generation memory problems
Unfortunately the conf changes to fork the compilation of JSPs and the increased 'modificationTestInterval' value made no real improvement so I am continuing to work towards replacing the language text request scope variables with property files references. However, if this is a problem, this has made me concerned that all request scope variables aren't being released, not just the ones we use for language text! Ian On 25 July 2011 10:45, Ian Marsh wrote: > Good morning and thanks for the replies! > > Unfortunately, as far as I am aware, our bank determines who we must > use as the PCI Auditor so our hands are tied with that one, but it > does seem like they're just covering their backs by choosing the > latest available version rather than actually determining a reason as > to why its needed. > > However, thanks for looking into my problem... the first thing that > rang a bell was the mention that it could be to do with the JSPs. I > have checked for development mode settings and neither have it > enabled. The bell it rang though was that, for some slightly silly > reasons that I am planning on finally clearing up today to see if they > are the cause, we have, in certain pages of the site, roughly 1000 > tags of text for different languages set in request scope. I > know these should be implemented through properties files instead but > the excuses are for me to deal with not you guys! > > Could this be link to the cause though? Could it somehow be that the > text variables are being held or referenced for longer than the > request scope period and so quickly eating up memory? > > I also remembered some changes we made to the tomcat settings in > web.xml to fork the compilation of JSPs to a separate JVM and we had > set the 'modificationTestInterval' to 40 seconds. These may have had > an impact as well so I'll change these in the later versions of Tomcat > to see if they have any effect. > > Thanks again, > > Ian > > > > > On 22 July 2011 22:42, Pid wrote: >> On 22/07/2011 20:17, Mark Thomas wrote: >>> On 22/07/2011 17:26, Ian Marsh wrote: Hi, I am in charge of running a Apache-2, Tomcat-7, Ubuntu-10.04 set up for which we have to be PCI Compliant. We recently upgraded to Apache-2.2.17 and Tomcat-7.0.8 (from Apache-2.0.x and Tomcat 5.0.28) in order to comply with the requirements of the PCI Compliance checks and ironed out any issues to get us back to a satisfactory running state. >>> >>> Hmm. I think you need some better PCI auditors. If your app was running >>> on Tomcat 5.0.x and you trust the app (which seems reasonable given it >>> is doing something that requires PCI compliance) then an upgrade to >>> 7.0.12 should be sufficient if you using the HTTP BIO connector. >> >> Indeed. >> >> In my experience, I'd expect a QSA/PCI Auditor to be far, far more >> conservative than to promote Tomcat 7.0.x as a 'safe' version compared >> to 6.0.recent. >> >> >> p >> >> >>> Since Tomcat appears to behind httpd then there is a strong chance you >>> are using AJP (BIO or APR), in which case 7.0.2 should be sufficient. >>> >>> It appears your current auditors are blindly (and wrongly) assuming any >>> vulnerability in Tomcat will impact your installation. Expect a demand >>> to upgrade to 7.0.19 when they get around to reading the Tomcat security >>> pages again. >>> >>> >>> It seems that the character arrays [C, java.lang.String and javax.servlet.jsp.tagext.TagAttributeInfo entries are considerably higher in Tomcat-7.0.10 than in Tomcat-7.0.8 and I am wondering if this could lead to an explanation for the difference. >>> >>> Maybe. What you really want to look at is the GC roots for those >>> objects. That will tell you what is holding on to the references. Based >>> on that data I'd start looking at the arrays of TagAttributeInfo but >>> that might be completely the wrong place to look. >>> >>> I've just triggered a heap dump on the ASF Jira instance (running >>> 7.0.19) to see what that looks like. I'll report back what I find (once >>> the 4GB heap has finished downloading - it may be some time). >>> Would anyone know of any changes between the two versions, possibly linked to those memory entries, that could lead to such behaviour? >>> >>> Nothing jumped out at me from the changelog. >>> Any help or suggestions is greatly appreciated! I'm sorry for a long post, but hopefully its got the information needed to help diagnosis. >>> >>> To be honest, there isn't enough info hear to diagnose the root cause >>> but there is enough to demonstrate that there is probably a problem and >>> maybe where to start looking. That might not seem like much but it is a >>> heck of a lot better than most of the reports we get here. Thanks for >>> providing such a useful problem report. >>> >>> Mark >>> >>> >>> >>> - >>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.o
RE: Class loading order
Hello, My web applications is designed to plug-in 3 rd party modules. 3rd party jars and my jars would placed under WEB-INF/libs. In case of bugs, the third party developer may provide hot fixes , which would be placed under WEB-INF/classes usually. I do not want to place their hot fixes under WEB-INF/classes, as they may conflict with my hot fixes and this would create some problems during maintenance. So I was checking the possibility of defining a new location for 3rd party hot fixes. Is there any way to do this..? Regards, Krishna -Original Message- From: ext Pid [mailto:p...@pidster.com] Sent: Tuesday, July 26, 2011 2:15 PM To: Tomcat Users List Subject: Re: Class loading order On 26/07/2011 09:38, Anne, Radhakrishna (NSN - IN/Bangalore) wrote: > > Hello, > > I would like to changes the default order look up for class loading, as > I understood from the doc, the order of look up is > 1)WEB-INF/classes > 2)WEB_INF/lib. > > Now I wanted to change this order and have my own order look up as shown > below i.e. > 1)/opt/shared/classes > 2)WEB-INF/classes > 3)WEB_INF/lib. > > Can someone help me out..? I am using tomcat 6 version. No, the only way to do this is via a custom classloader of your own design. It is probably a bad idea to do this - a webapp's classloader is supposed to load its own classes first. Why can't you include the classes in the webapp? p - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Class loading order
On 26/07/2011 09:38, Anne, Radhakrishna (NSN - IN/Bangalore) wrote: > > Hello, > > I would like to changes the default order look up for class loading, as > I understood from the doc, the order of look up is > 1)WEB-INF/classes > 2)WEB_INF/lib. > > Now I wanted to change this order and have my own order look up as shown > below i.e. > 1)/opt/shared/classes > 2)WEB-INF/classes > 3)WEB_INF/lib. > > Can someone help me out..? I am using tomcat 6 version. No, the only way to do this is via a custom classloader of your own design. It is probably a bad idea to do this - a webapp's classloader is supposed to load its own classes first. Why can't you include the classes in the webapp? p - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Class loading order
Hello, I would like to changes the default order look up for class loading, as I understood from the doc, the order of look up is 1) WEB-INF/classes 2) WEB_INF/lib. Now I wanted to change this order and have my own order look up as shown below i.e. 1) /opt/shared/classes 2) WEB-INF/classes 3) WEB_INF/lib. Can someone help me out..? I am using tomcat 6 version. Regards,Mailcode: tL3PbjBL Krishna
Chuck
I'm really sorry to post birthday-congrats into this list, however: One of the dinosaurs and most helpful souls of this list is enjoying his birthday today, if I'm not mistaken. Therefore, Chuck, all the best and have a great day! Besides, thanks again for all the help you've provided to this list so far. Cheers! Gregor -- just because you're paranoid, don't mean they're not after you... gpgp-fp: 79A84FA526807026795E4209D3B3FE028B3170B2 gpgp-key available @ http://pgpkeys.pca.dfn.de:11371 @ http://pgp.mit.edu:11371/ skype:rc46fi gplus.to/gregor twitter.com/#/2smart4u - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
