[ANN] Apache Tomcat 7.0.50 released
The Apache Tomcat team announces the immediate availability of Apache Tomcat 7.0.50. Apache Tomcat is an open source software implementation of the Java Servlet, JavaServer Pages and Java Expression Language technologies. This release contains a number of bug fixes and improvements compared to version 7.0.47. Please refer to the change log for the complete list of changes: http://tomcat.apache.org/tomcat-7.0-doc/changelog.html Note: This version has 4 zip binaries: a generic one and three bundled with Tomcat native binaries for Windows operating systems running on different CPU architectures. Note: Use of the JSR-356 Java WebSocket 1.0 implementation requires Java 7. Note: If you use the APR/native AJP or HTTP connector you *must* upgrade to version 1.1.29 or later of the APR/native library. Downloads: http://tomcat.apache.org/download-70.cgi Migration guides from Apache Tomcat 5.5.x and 6.0.x: http://tomcat.apache.org/migration.html
Re: [ANN] Apache Tomcat 7.0.50 released
Thanks for that. :-) You might like to correct this Typo under Tomcat 7.0.50 / Catalina: Streamline handling of WebSocket messages whe... to when or where for example. All the best, DaveLaw On 12/01/2014 11:15, Violeta Georgieva wrote: The Apache Tomcat team announces the immediate availability of Apache Tomcat 7.0.50. Apache Tomcat is an open source software implementation of the Java Servlet, JavaServer Pages and Java Expression Language technologies. This release contains a number of bug fixes and improvements compared to version 7.0.47. Please refer to the change log for the complete list of changes: http://tomcat.apache.org/tomcat-7.0-doc/changelog.html Note: This version has 4 zip binaries: a generic one and three bundled with Tomcat native binaries for Windows operating systems running on different CPU architectures. Note: Use of the JSR-356 Java WebSocket 1.0 implementation requires Java 7. Note: If you use the APR/native AJP or HTTP connector you *must* upgrade to version 1.1.29 or later of the APR/native library. Downloads: http://tomcat.apache.org/download-70.cgi Migration guides from Apache Tomcat 5.5.x and 6.0.x: http://tomcat.apache.org/migration.html - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
serialization and newest tomcat
erialization causes some problems in apache-tomcat-7.0.35 I have several applications and run on fedora linux. I have used many releases of fedora and tomcat. My applications are characterized by a) all use a DB (firebird) b) all use both jsp and java servlets c) all use transient java beans for a round of interaction (user request - user response) d) all have 1 or more session java beans for each user (login - logout) e) all have 1 or more application beans (initialized at startup, can refresh, passed around) f) all have an application specific jar and share a common code jar Long ago I added serialization to almost all of the java beans to stop tomcat whining in the catalina.out file. This worked just fine until the most recent tomcat release. On my development machine, java changes build new jars and apache/tomcat must be restarted to work right. Starting with the new release, problems with connections happened. After research, I discovered that the applications were going nuts with connection requests and xinetd was shutting down the connection factory service. It took a 30 minute wait (or reboot) to fix this problem. My guess is that the application wide beans were not only being made fresh as always happens (they use one connection each to initialize), but that the serialized versions were coming back up and trying to refresh causing lots of strange connections to be created (if one is not passed, one is made and there are many routines each needing a connection). To solve this problem, I stopped serialization. This solved the problem. From the notes I got from others (thanks Mark and ...): serialization can be stopped by putting this in many places - here is one: appname/META-INF/context.xml Manager pathname= /
Re: Mod_jk error
Hi, Alex What is your mod_jk.conf file that used for mod_jk configuration. You can config it as blow: LoadModule jk_module modules/mod_jk.so JkWorkersFile conf/workers.properties JkLogFile logs/mod_jk.log JkLogLevel error JkLogStampFormat [%a %b %d %H:%M:%S %Y] JkOptions +ForwardKeySize +ForwardURICompat -ForwardDirectories JkMount /test_status mystatus JkMount /hello*loadbalancer1 or Just as your configuration now, but add the JkMount to http.conf. The JkMount /hello* loadbalancer1 will send all request start with hello to loadbalancer1 Hope to help you. 2014/1/11 Mark Eggers its_toas...@yahoo.com On 1/10/2014 2:53 PM, Alex Lucard wrote: . On Jan 10, 2014 5:00 PM, Alex Lucard priest.luc...@gmail.com wrote: I am running CentOS 6.5 and tomcat 7 I cannot get the mod_jk to work I have a JSP page on this server and if you go to localhost:8080/Hello it will work but if I just go to localhost/Hello The requested URL /Hello was not found on this server. I have apache2 and tomcat 7 install both work. Here is the part I added to the httpd.conf file # Load the mod_jk module. LoadModule jk_module /usr/lib64/httpd/modules/mod_jk.so JkWorkersFile /etc/httpd/conf/workers.properties jkLogFile /var/log/mod_jk.log JkLogLevellevel JkLogStampFormat [%a %b %d %H:%M:%S %Y] My workers.properties file at /etc/httpd/conf/workers.properties worker.list=worker1 worker.worker1.type=ajp13 worker.worker1.port=8009 worker.worker1.host=localhost #worker.worker1.lbfactor=1 My error log file /var/log/mod_jk.log [Fri Jan 10 15:19:22 2014] [1854:140509786134496] [info] init_jk::mod_jk.c (3365): mod_jk/1.2.37 initialized [Fri Jan 10 15:19:23 2014] [1855:140509786134496] [error] ajp_validate::jk_ajp_common.c (2696): worker worker1 can't resolve tomcat address localhost [Fri Jan 10 15:19:23 2014] [1855:140509786134496] [info] init_jk::mod_jk.c (3365): mod_jk/1.2.37 initialized What happens when you type the following from the command line: dig localhost As a workaround, replace localhost with 127.0.0.1. . . . . 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: Packet misses in Tomcat
-Original Message- From: Stefan Mayr [mailto:ste...@mayr-stefan.de] Sent: 10 January 2014 23:26 To: users@tomcat.apache.org Subject: Re: Packet misses in Tomcat Hi Am 09.01.2014 14:21, schrieb Divyaprakash Y: -Original Message- From: Divyaprakash Y Sent: 08 January 2014 14:35 To: Tomcat Users List Subject: RE: Packet misses in Tomcat ... Strange that this is happening only to me. Looks like something similar was reported on the dev list when voting for Tomcat 7.0.50 .. Thanks. I tried same setup today with the BIO connector, everything worked flawlessly. Will there be any issue with the APR connector(earlier setup) or are there any extra configurations which I missed in my server.xml? This might be the issue seen in https://issues.apache.org/bugzilla/show_bug.cgi?id=55976 . Looks like Mark fixed it today for 7.0.51 (not released yet) - Stefan Thanks Stefan for the information. Should that(Fix on NIO Connector) fix the possible issue in APR Connector as well? - DISCLAIMER: This electronic message and any attachments to this electronic message is intended for the exclusive use of the addressee(s) named herein and may contain legally privileged and confidential information. It is the property of Celstream Systems Private Limited. If you are not the intended recipient, you are hereby strictly notified not to copy, forward, distribute or use this message or any attachments thereto. If you have received this message in error, please delete it and all copies thereof, from your system and notify the sender at Celstream Systems or administrat...@celstream.com immediately. -
