Re: [Resin-interest] Resin 4.0.10 release
Hi Scott, thanks for 4.0.10 - it seems that the restart-problems have been solved with this build. Our system looks healthy again. :) Best regards, --- Jan. ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Resin 4.0.10 release
On August 26, 2010, Jan Kriesten wrote: thanks for 4.0.10 - it seems that the restart-problems have been solved with this build. Our system looks healthy again. :) I second this. The 4.0.10 release seems to be the best 4.0 release yet. All of the problems we've encountered in the past seem to be gone and performance actually seems to be better. (It wasn't bad before, but our load testing results did actually seem better with our configuration on this release.) Congratulations! -Jamie ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
[Resin-interest] java.io.IOException: can't clear response after writing headers
Hi all, Some JSPs produce following error Stacktrace in our Java-log: java.io.IOException: can't clear response after writing headers at com.caucho.server.http.ResponseStream.clear(ResponseStream.java:233) at com.caucho.server.http.HttpServletResponseImpl.getOutputStream(HttpServl etResponseImpl.java:137) : : The Exception gets thrown at the line sosOut = response.getOutputStream(); This code work on all other resin installations (for years now) The only difference to our other resin installations that I'm aware of, is that resin and apache are on two separate machines now. We use Resin Pro 4.0.9. Any ideas what might cause this exception? Regards, Martin The information in this e-mail and in any attachments is confidential and intended solely for the attention and use of the named addressee(s). This information may be subject to legal, professional or other privilege and further distribution of it is strictly prohibited without our authority. If you are not the intended recipient, you are not authorised to and must not disclose, copy, distribute, or retain this message or any part of it, and should notify us immediately. This footnote also confirms that this email has been automatically scanned for the presence of computer viruses, profanities and certain file types. ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] php.ini and include_path
Hi,
I don't think we support the ${RESIN} variable in php.ini at the moment,
but out of curiosity, why do you need the Resin root if you're using
Jetty?
Thanks,
Emil
On Wed, Aug 25, 2010 at 07:57:48PM -0400, Alexandre Bertails wrote:
Hi all,
I have this worky partial web.xml:
[[
servlet
servlet-nameQuercus Servlet/servlet-name
servlet-classcom.caucho.quercus.servlet.QuercusServlet/servlet-class
init-param
param-nameini-file/param-name
param-valueWEB-INF/php.ini/param-value
/init-param
/servlet
]]
and this WEB-INF/php.ini:
[[
include_path = .:${RESIN}/webapps/WEB-INF/php
]]
The include_path value is set as expected.
The question is: how can I make Quercus to interpret ${RESIN}?
(I'm using Quercus 4.0.10 and Jetty.)
Alexandre Bertails, W3C Systems Team.
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] php.ini and include_path
2010/8/26 Emil Ong e...@caucho.com:
Hi,
I don't think we support the ${RESIN} variable in php.ini at the moment,
but out of curiosity, why do you need the Resin root if you're using
Jetty?
I'm trying to write a Java/Scala wrapper for some existing code in PHP.
The first step is to make everything to work without modification in
the existing code. There are plenty of require_once-like functions
spread all over the code and I need to modify include_path because of
them.
I have found some examples on the web (basically in the forums) where
you can set variables directly in web.xml but none of them worked
for me, I don't know why. If you have an example using ${RESIN},
that's of course a perfect workaround.
Alexandre Bertails, W3C Systems, Team.
Thanks,
Emil
On Wed, Aug 25, 2010 at 07:57:48PM -0400, Alexandre Bertails wrote:
Hi all,
I have this worky partial web.xml:
[[
servlet
servlet-nameQuercus Servlet/servlet-name
servlet-classcom.caucho.quercus.servlet.QuercusServlet/servlet-class
init-param
param-nameini-file/param-name
param-valueWEB-INF/php.ini/param-value
/init-param
/servlet
]]
and this WEB-INF/php.ini:
[[
include_path = .:${RESIN}/webapps/WEB-INF/php
]]
The include_path value is set as expected.
The question is: how can I make Quercus to interpret ${RESIN}?
(I'm using Quercus 4.0.10 and Jetty.)
Alexandre Bertails, W3C Systems Team.
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
