Re: [Resin-interest] Disable watch dog
On Nov 5, 2007, at 10:33 AM, Jaswinder Kaur wrote: Hello How much memory watchdog process takes? As little as the JDK allows. The watchdog itself doesn't take much memory, but the JDK tends to allocate quite a bit. How can I disable watchdog? You can't. Or, really, you don't want to. Resin is designed under the assumption that the watchdog exists. If you really, really want to call Resin directly, start Resin with -verbose and copy the arguments to a batch file to start Resin. -- Scott I am running my web application under resin 3.1.3 and JDK 1.5.0_13 on windows2003 sp1. Thanks in advance Jaswinder == Attention: This message is intended only for the individual to whom it is addressed and may contain information that is confidential or privileged. If you are not the intended recipient, or the employee or person responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution, copying or use is strictly prohibited. If you have received this communication in error, please notify the sender and destroy or delete this communication immediately. == ___ 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] additional Comet questions
On Nov 5, 2007, at 2:35 AM, Robert Varga wrote: Hi Scott, still have some questions :-) 3. What happens if I call CometController.wake() while another thread is executing on a CometServlet with the same CometController instance? Will resume() be called once again after the resume/ service currently executing returned true? Yes. The second wake() is queued. I'll need to check to see if we have a test case for that. And if two or more wake()-s were queued before the service()/resume () completed, will resume() be invoked once or as many times as wake()-s were queued? In other words should we attempt to minimize the number of redundant calls to wake() or would it be optimally handled by Resin? Only once. It's a flag that's tested and cleared at the beginning of the service () call. So if a wake() occurs while you're processing the request, Resin will automatically start a new service(). The assumption is that application has some kind of queue with data. The service will drain the queue, but it's possible that a new request occurs right before the service exists. The idea is that Resin will handle the timing issues for you. You just need to drain the queue in the service() call. And your producer can call wake() after it submits data. So there should be a minimum of application code dealing with this. - Another question: is there a no timeout due to idleness value to CometController.setMaxIdleTime()? setMaxIdleTime(Long.MAX_VALUE) I'm thinking of making the following changes to the API based on the feedback: 1) change isActive() to isClosed() 2) wake the controller after a timeout occurs to allow for cleanup of the output. Either add an isTimeout() or set isClosed() after timeout. (This does not guarantee a resume() call if the socket is dropped, only for timeout.) 3) Make the CometController.getAttribute be in a different scope than the request. I'm concerned that request-scoped thread-unsafe objects will be accessible from the CometController. 4) Remove the return value from wake() -- Scott Thanks and best regards, Robert ___ 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] Quercus PHP throws NullPointerException in urlencode
It looks like a bug in Quercus when urlencode is given an empty $_REQUEST
variable, I changed to code in Phorum to guard the call to urlencode() to
this (lines 192-196 of include/admin/users.php):
[code]
192 if ($_REQUEST[search]) {
$url_safe_search=urlencode($_REQUEST[search]); }
193 if($_REQUEST[posts]) {
$url_safe_search.=posts=.urlencode($_REQUEST[posts]); }
194 if ($_REQUEST[posts_op]) {
$url_safe_search.=posts_op=.urlencode($_REQUEST[posts_op]); }
195 if ($_REQUEST[lastactive]) {
$url_safe_search.=lastactive=.urlencode($_REQUEST[lastactive]); }
196 if ($_REQUEST[lastactive_op]) {
$url_safe_search.=lastactive_op=.urlencode($_REQUEST[lastactive_op]); }
[/code]
That gets past the null pointer exception in Quercus and Phorum's User admin
page loads.
Simon
--
View this message in context:
http://www.nabble.com/Quercus-PHP-throws-NullPointerException-in-urlencode-tf4759896.html#a13615980
Sent from the Resin mailing list archive at Nabble.com.
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
