Re: Stream closed- IOException exception
On Sat, Mar 1, 2014 at 1:33 AM, Christopher Schultz < ch...@christopherschultz.net> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Prashant, > > On 2/28/14, 7:54 AM, Prashant Kadam wrote: > > thanks Mark and Konstantin for your reply > > > > If you create the simplest possible JSP that demonstrates the > > issue (start with the one you have and remove as much as you can) > > and then post that JSP here, we can take a look. > > > >>> as you can see in stacktrace, there are many jsps forwarding > >>> request to > > another jsp, i am not sure how can I post jsp code. also one > > observation is, there is a struts action forward in between means > > jsp-> struts action -> jsp , If I remove this action call and > > include jsp directly in jsp then its working ... whether something > > wrong with tiles or struts or tomcat .. ? > > If you are doing a lot of JSP forwarding, you could be generating a > lot of useless whitespace that is all being sent to the output buffer. > Once that buffer fills up, the response headers will be sent to the > client and and response is therefore committed. > thanks for your reply seems logical ... and will try by removing white spaces .. still one question ... this is how it work it flows ... 1. jsp1 includes jsp2, 2. jsp2 forwards to jsp3 (using org.apache.struts.actions.ForwardAction) , 3. jsp3 forwards to strutsaction1, 4. strutsaction1 forwards to strutsaction2, 5. strutsaction2 forwards to jsp4, 6. and jsp4 includes jsp5 to render final view ... now if I remove 3,4,5 and directly include jsp4 into jsp3 it works. even I tried removing all business logic code in strutsaction1, strutsaction2, it is throwing same error .. so conclusion is whenever i am using struts action in between it is causing problem ... any thoughts ... ? > If my analysis is correct, the difference between the Tomcat versions > probably comes down to some small change in the way JSPs are compiled > which may generate more whitespace if you haven't been careful. > > Take a look at all the JSPs that are participating in the request -- > you should be able to inspect them to see why they might be generating > whitespace. Remember, newlines are whitespace ;) > > I can see from your stack trace that you are using *includes*. Is > there some other error that is occurring before this one? Does it > happen on every request to this resource? > > yes this happen on every request for same resource ... this is exception that i can see when I put try catch in one of the jsp ,,, javax.servlet.jsp. JspException: javax.servlet.jsp.JspException: javax.servlet.jsp.JspException: org.apache.jasper.JasperException: java.lang.IllegalStateException: Exception occurred when flushing data > - -chris > -BEGIN PGP SIGNATURE- > Version: GnuPG v1 > Comment: GPGTools - http://gpgtools.org > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iQIcBAEBCAAGBQJTEOt7AAoJEBzwKT+lPKRY6fYP+wWFNBtLRjUi1m6NPPpxajyp > NBp0SZ5TIBs9c1fwAq3oKjodMDsgGMo59HApJpzHYyQhwuKHez3VLdGPss4aeq50 > +Yc/UNhuMor31JWkPHzy05oSEFOQeKFn8Trw//OJ8m2giZSopt/05E8NRu9MIpUw > +9eEsetJHs0502XCEFQ206/6MLxleGLA/sM5HTWJHg0NJczobTsHo40myy201Y1j > Q7tO/gsyRzwljbHf0XByTTYUQNaNCaTzH0ydLiVeWCaPfxCpF4DXzrzdBu+BrL8U > n5BlaizxMp9vd5DPucbRZidC0ihQpcaMjBAXnwg3OtbltX5EsMEYOfgD/TQXh5PC > PFTPRm21OaybgNj13hNOOfmOCDw5AAA+znyVPFl4Ao+z67w0jIgSre49HMXfzYJQ > a2pcDzCUuvbtXl22LJBVcnqlISLETiShulRzvAF5OiYwe2bJS4fOdWNSB8Nn7L7A > +x//HxvTOem1dG5CaFRkCxvnkvK30e4LNCwY0AfErt3eKahHj0rJA+w/qiodTg2U > bzh8kgRv+9v0fqV3RKVV/nO7WFRlyN6QIalCvLKPC+9CdajvBPUVC+gZgizs4pjT > osHuIcGPmXMzycj1FfXzym5ucdy/WlJPUIBtliA4XnJ/RdBu1WfdB0c6rruiNflW > vp1dKzQjPx5Zv58BU2l1 > =pI9J > -END PGP SIGNATURE- > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > -- ~ Prashant Kadam
Re: Difference between process kill and shutdown
2014-03-01 16:11 GMT+04:00 Akash Jain : > On our linux boxes, we have multiple users who run tomcat. > > Currently we are using process kill commands to kill the respective user's > tomcat , instead of using shutdown.sh > > Are there any downsides of using this approach ? > It depends on what process you are killing. If you are killing jsvc (Apache Commons Daemon), then it is OK, as it should call Tomcat' Server.stop() properly. If you are killing a java process, then Tomcat shutdowns thanks to a shutdown hook that it installs in the JVM. The downside to this approach is that all shutdown hooks are started at the same time and run in parallel. E.g. if you have some 3rd party library that installed a shutdown hook (e.g. an embedded database or a logging library), it may shut down earlier than request processing in Tomcat shuts down. It is also possible to kill java process immediately in such way that no shutdown hooks are run. In this case, of course, all bets are off. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: OWF webapp log errors
2014-03-02 1:34 GMT+04:00 J. Brian Hall : > I have installed the OWF webapp in Tomcat and I'm trying to resolve some > errors I'm finding in the log files. I have not had much luck getting > responses to questions on the OWF mailing list, so I'm hoping someone can > help here. Here are the details of my setup: > > > > -Windows 7. > > -Tomcat 7.0.42. > > -MySQL 5.6. > > -JDK 7.51-b13. > > -IE 11 browser. > > > > First, the OWF webapp does start (some features are not working). The > webapp is not generating a stacktrace or an initialization log file anymore > since I resolved earlier errors with help. There are 3 log files remaining > that list SEVERE errors. I will start with the 1 error reported in the > localhost log. > > > > Any idea how to resolve the following error? > > > > Mar 01, 2014 12:19:36 PM org.apache.catalina.core.StandardContext > filterStart > > SEVERE: Exception starting filter springSecurityFilterChain > > org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean > named 'springSecurityFilterChain' is defined > >From my knowledge of Spring Framework and Spring Security libraries, That message means that you have a filter declared in your web.xml (with name "springSecurityFilterChain"), but there is no such filter among Java Beans created by a SpringFramework Context. I cannot say what caused it without knowing what your OWF app is, how it is configured, and what INFO messages were earlier in the log files. I would guess that Spring did not start, or have not found some of its configuration files (context definition files). If you broke application in such way (and you say that even logging is broken), you would better uninstall everything and start over from a blank page, documenting your steps, Unless you provide enough information for others to reproduce your configuration, not much can be said. For reference: http://spring.io/docs http://docs.spring.io/spring/docs/4.0.2.RELEASE/spring-framework-reference/html/ - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: tomcat 7 for production
2014-03-02 23:57 GMT+04:00 Ahmed Dalatony : > hello > thnx for fast reply > but i'm meaning which release > as i see in change log that there is a side text beside each release like > 7.0.51 not released > 7.0.50 released 2014-01-08 > > in other meaning > should i go directly to latest release of tomcat 7 which is 7.0.52 > or there is more stable production ready release??? > 1. The change log page is part of documentation for specific release. At the time when the release is built and proposed for voting, the release date is not yet known (as well as whether the release vote will be successful). The release announcement is on the top page of tomcat.apache.org site, as well as in the archives of announcements mailing list. 2. Please do not top-post http://tomcat.apache.org/lists.html#tomcat-users -> "6." - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: tomcat 7 for production
hello thnx for fast reply but i'm meaning which release as i see in change log that there is a side text beside each release like 7.0.51 not released 7.0.50 released 2014-01-08 in other meaning should i go directly to latest release of tomcat 7 which is 7.0.52 or there is more stable production ready release??? thank you, On Sun, Mar 2, 2014 at 9:33 PM, David Kerber wrote: > On 3/2/2014 2:14 PM, Ahmed Dalatony wrote: > >> hello all, >> i'm planning to use tomcat in production server >> which version is ready for production use ??? >> >> thank you >> >> > The latest released version of 7.0.x is the way to go. > > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
Re: tomcat 7 for production
On 3/2/2014 2:14 PM, Ahmed Dalatony wrote: hello all, i'm planning to use tomcat in production server which version is ready for production use ??? thank you The latest released version of 7.0.x is the way to go. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
tomcat 7 for production
hello all, i'm planning to use tomcat in production server which version is ready for production use ??? thank you
Re: retain context.xml across war updates
On Mar 2, 2014, at 9:58 AM, "Caldarale, Charles R" wrote: > It's reached from the last sentence of this section: > http://tomcat.apache.org/tomcat-7.0-doc/config/host.html#Automatic_Application_Deployment > > That page is reachable from a couple of places in the configuration doc. > > - Chuck Thanks, I missed that. --Jesse Barnum, President, 360Works http://www.360works.com Product updates and news on http://facebook.com/360Works (770) 234-9293 == Don't lose your data! http://360works.com/safetynet/ for FileMaker Server ==
RE: retain context.xml across war updates
> From: Jesse Barnum [mailto:jsb_tom...@360works.com] > Subject: Re: retain context.xml across war updates > > http://tomcat.apache.org/tomcat-7.0-doc/config/automatic-deployment.html > I can't find any way to navigate to that URL from within the Tomcat > documentation. It's reached from the last sentence of this section: http://tomcat.apache.org/tomcat-7.0-doc/config/host.html#Automatic_Application_Deployment That page is reachable from a couple of places in the configuration doc. - 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
Re: retain context.xml across war updates
On Feb 6, 2014, at 1:02 PM, Mark Thomas wrote: > On 06/02/2014 17:55, Steve Lopez wrote: >> Is there a way to ensure an applications context.xml isn't deleted across >> reloads of the war file?We have server-specific settings in each >> context.xml and are looking for a way to deploy the same WAR file across >> each Tomcat instance. >> >> My first attempt at this was to put the context.xml into ~ catalina >> /conf/Catalina/localhost/ROOT.xml. However, Tomcat deletes the file when >> the app is unloaded. >> >> Is there a setting to tell Tomcat *not* to delete the context.xml in >> ~catalina/conf/Catalina/[host]/[app]? If not, what is the 'best practice' >> for providing configuration settings to each Tomcat while also enabling a >> simple continuous integration and deployment of WAR files for an application >> across multiple Tc instances. Creating custom war files (one for each >> server) seems brittle and risky if the wrong war is accidentally deployed on >> the wrong server. >> >> Specifically, context.xml contains custom settings for >> memcached-session-manager which specifies the primary and fallback memcache >> host. These would be different for each server when using sticky sessions. > > http://tomcat.apache.org/tomcat-7.0-doc/config/automatic-deployment.html > > HTH, > > Mark > I can't find any way to navigate to that URL from within the Tomcat documentation. Maybe a link needs to be added somewhere on this page? http://tomcat.apache.org/tomcat-7.0-doc/deployer-howto.html --Jesse Barnum, President, 360Works http://www.360works.com Product updates and news on http://facebook.com/360Works (770) 234-9293 == Don't lose your data! http://360works.com/safetynet/ for FileMaker Server == - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Difference between process kill and shutdown
On 01/03/2014 12:11, Akash Jain wrote: > On our linux boxes, we have multiple users who run tomcat. > > Currently we are using process kill commands to kill the respective user's > tomcat , instead of using shutdown.sh Which signal are you sending to shutdown the process? Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
