[Resin-interest] IPConstraint not taking error-code and error-message in 3.1.6?
Has anyone gotten ip-constraint to work with error-code and error- message? I've been trying to add the two properties to the config but it won't allow me to add it because the Relax Schema doesn't define or allow these two additional params. Is this a bug or is there another special way to initial the ip- constraint with my own custom error-code and error-message? -ck ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Resin 3.2.0 is available
Quick question which I cannot find the answer to on the BAM page. How reliable is the BAM service? Does it provide a persistent subscription feature like JMS? In critical services where packets are sent and must be processed by a subscriber without losing that information, does BAM take care of this? Is there also a transaction feature to BAM where a message could either be put back into the queue to be retried if transaction fails and rolls back? it may be that BAM is currently geared towards the chat architecture such as twitter/IM/comet/etc so this may not apply, but I'd like to know the options available. What's the plan for Resin's BAM and JMS implementation? Separate or may be integrated into one? -Chris On Aug 7, 2008, at 8:58 AM, Scott Ferguson wrote: Resin 3.2.0 is now available at the usual download http://caucho.com/download . Release notes are at http://caucho.com/resin/changes/resin-3.2.0.xtp . Resin 3.2.x is the development branch. We have a full roadmap of stuff to add to 3.2.x, so 3.2.x will be changing considerably for each release. For sites that don't want that kind of code-upheaval, use the 3.1.x stable branch. Much of the 3.2.0 work was underlying refactoring and distribution/ release refactoring. Jars have been merged, so resin.jar and javaee-16.jar are the only needed jars for Resin OpenSource. Resin Pro also needs pro.jar. Also, the resin.xml replaces resin.conf (to make editors/mail happy), and a bunch of smaller changes in the distribution layout. The 3.2.0 release now includes a 32-bit debian package at the download site, which will make installation easier for Debian Linux sites including Ubuntu. For administration, the /resin-admin has been reworked and enhanced. New capabilities include: * graphing of critical statistics * revised and enhanced summary page * monitoring and display of slow requests * new JMX page displaying all MBeans and attributes in the system * revised web-app page including start/stop/restart For alerts, we've added a mail: log-handler, which can email you a compilation of the severe and critical log messages (this is very handy.) The threading and socket management has been refactored to better handle comet and jabber connections. During the checkout process, we loaded it with 25,000 simultaneous comet connections as a stress test. The distributed sessions have been reworked to use BAM as the underlying transport, and the database restructured to handle planned distributed object enhancements like distributed caching, and better startup performance. Both the threading and session refactorings are major changes, so sites relying on them should do their own stress testing. Our JSF implementation now includes a handy debugging page, to better show the state of the JSF system. The example at http://caucho.com/resin/examples/jsf-webbeans.xtp shows this capability (see the bottom right corner.) BAM (http://caucho.com/resin/doc/bam.xtp) has been refactored and cleaned up. It can now act as a SEDA/queue replacement for memory- based JMS queues. The client and service have been simplified, so the housekeeping overhead is now minimal. In addition, you can now program to BAM using PHP, which is a very cool feature. Share and Enjoy! -- Scott ___ 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] Resin 3.2.0 is available
On Aug 7, 2008, at 9:56 AM, Scott Ferguson wrote: On Aug 7, 2008, at 9:22 AM, Chris Chen wrote: Quick question which I cannot find the answer to on the BAM page. How reliable is the BAM service? Does it provide a persistent subscription feature like JMS? In critical services where packets are sent and must be processed by a subscriber without losing that information, does BAM take care of this? Is there also a transaction feature to BAM where a message could either be put back into the queue to be retried if transaction fails and rolls back? Not yet. The current queue capability is a simple memory-based queue. Since we only added/cleaned-up the queue at the last minute, there wasn't time to also add the persistent capabilities. It's definitely in the plan. (I just added a bug report at http://bugs.caucho.com/view.php?id=2826 to make it concrete.) The subscriber issue is interesting since Jabber defines persistence as one of their XEP capabilities (XEP are mini-specs, basically defining mixin capabilities.) I haven't quite figured out how to make those capabilities work in a generic fashion, i.e. available for anyone, not just tied to a specific chat implementation. I wrote an open source jabber client library before so JEP/XEPs are quite familiar to me. :) I don't have a fully concrete idea either but there are two sides to this subscription feature - client and server. The server side may be similar to how JMS EJB beans or Jabber Server side components work. The EJB side has a defined set of beans listening to a particular topic/queue. This is considered a subscription. As for persistent subscriptions, it can be similar to how JMS works as well. A client registers as a subscriber for a particular topic. Unless the client unsubscribes, the system will continue to store messages for this subscriber when the subscriber is offline. Of course, this comes with its own set of challenges. Fiorano MQ and ESB has a setting to periodically flush out any persistent messages. XMPP by nature has persistence message supported in some sense (ie. I get chat messages that were sent when I wasn't logged on). I wonder if a Jini-like persistence capability may be something to model after or even relevant in this case. Either way, persistent and subscription do go hand in hand. it may be that BAM is currently geared towards the chat architecture such as twitter/IM/comet/etc so this may not apply, but I'd like to know the options available. The persistence and XA does fit into the architecture. It's interesting, as I work more with BAM examples, it's really more capable than the lightweight IM/comet framework that we'd initially envisioned. In the 3.2.1 timeframe, I'm planning on some ESB/SOA experiments to see how well it works in that space. What's the plan for Resin's BAM and JMS implementation? Separate or may be integrated into one? I'm going to try to integrate them. It'll be interesting, since BAM is a slightly lower layer than JMS, since its payload is just a Serializable and the only meta information are the to and from. So the JMS Message classes may define a JMS layer on top of BAM. It'll take some experimentation to see how that will work. A nice thing about developing in BAM is that it's so stripped-down, that you can consider more use-case combinations than a more complicated model like JMS. I think integration is interesting, but more relevant are the use cases surrounding each type of system. *) BAM - lightweight for super fast and scalable message brokering for things such as stock market price streaming (no need for persistence) or twittering type messages. The main thing here is as fast as computerly possible. *) JMS/persistent subscriptions - These are for those that broker highly mission-critical data. The primary interest here is as reliable as possible. Speed is less of a concern compared to the data. Inherently, this type of use conflicts with BAM. Transactions will bog down the speed. *) ESB/SOA activities - these, in my view, are for those that require high data/service compatibility and integration. The message here is as promiscuous as possible. The focus is on the adapters and being able to communicate and connect to many different systems. I think all of them centers around a hub-spoke model. It's possible to integrate all of them together through layers. The lowest layer (in this case, BAM) focuses entirely on speed. A secondary layer can add the reliability that can be similar to XEP persistence. Possibly a persistence component that subscribes and listens to any topic/queue that requires such a service and separately deals with reliability. A third component can create a set of adapters to connect to different systems. This third component mainly focuses on data/message translation. Breaking the system up in these parts seems
[Resin-interest] Filter's dispatcher defaults
This is a question aimed at Resin's support team. I'm wondering what the defaults for a Filter's dispatcher setting is. This is only valid for 2.4 webapps. So if I were to exclude these parameters, does this mean that Resin 3.1.5 will filter all types of dispatched requests? I ask this because I'm looking at the example configuration for the GzipFilter and I'm not sure if it filters only on REQUEST or the other ones as well. Should I be worried if I don't include the dispatcher config? I had this issue regarding filter dispatchers when configuring Confluence. -Chris ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Filter's dispatcher defaults
I am using your configurations and it's working, but only because the responses are not getting encoded. I think this may be caused by the load balancer web tier that I have running. I believe you are probably on the right track on that one. I have resin cache enabled on both the web and the app tiers. It's likely that somehow the caching mechanism on the web tier is causing havoc. Looks like I will have to dig a little deeper into the caching mechanism of resin. I am going to disable caching to see if things are ok first. -Chris On Jul 11, 2008, at 3:11 AM, Haroon Rasheed wrote: Also I would like to know, whether your server is running under a LoadBalancer? if yes... please send the details on the same... Please try the following configuration and lemme know if this helps. !--gzip changes start-- filter filter-name=gzip filter- class=com.caucho.filters.GzipFilter init use-varytrue/use-vary /init /filter filter-mapping filter-name=gzip url-pattern exclude-pattern*.pdf/exclude-pattern exclude-pattern*.zip/exclude-pattern include-pattern/*/include-pattern /url-pattern /filter-mapping !--gzip changes end-- Regards, Haroon 2008/7/11 Chris Chen [EMAIL PROTECTED]: Thanks for the reply, my configuration comes directly from the documentation: filter filter-name=gzip filter- class=com.caucho.filters.GzipFilter/ filter-mapping filter-name=gzip url-pattern=/*/ The interesting thing is that other files seem to zip fine. I am consistently hitting encoding issues with this particular GWT cache.html file. Gzip and Resin appears to be returning the code just fine. Yet somehow I am getting content encoding errors from Safari, Firefox, and now-tested Curl (I was trying to use curl to figure out what exactly is the problem, but no go). The files are all accessed through SSL if that has any relevance. I'm also running under Linux -Chris On Jul 11, 2008, at 2:32 AM, Haroon Rasheed wrote: Chris, We have been using gzip filter on production servers for the past 8 months, and didn't face any such issues. Please send the gzip filter configuration from web.xml, lemme see if anything is different in your conf? Thanks regards, Haroon 2008/7/11 Chris Chen [EMAIL PROTECTED]: Actually, I have a further problem using GzipFilter. I enabled it using no dispatcher, which according to Servlet Spec 2.4, means that it defaults to only REQUEST. When I started using the GzipFilter, I noticed a few things 1) Gzip appears to work on static files that are served through FileServlet, so that takes care of mostly the JS, CSS, and image files. 2) However, when it comes to the primary pages served by Grails, these do not get compressed. I have a feeling that this is because of the internal forwarding that's going on with the URL Mapping, GSP servlet, etc. So my question is - is it safe to enable GzipFilter for FORWARDed requests in the dispatcher? 3) I am using GWT (google web toolkit) and it serves out javascript files. There is a nocache.js file and then there are cache.html javascript files. It appears that the nocache.js files are downloaded properly, but my primary cache.html files are being compressed improperly for some reason. Here's the request: GET /v1/gwt/com.bbb.Mail/1B5800A70AEC91E23D018344A2E80852.cache.html HTTP/1.1 The error I get on Firefox is Content Encoding Error: The page you are trying to view cannot be shown because it uses an invalid or unsupported form of compression. The error I get on Safari is cannot decode raw data (NSURLErrorDomain:-1015) The response header for this request looks like everything is ok: (Status-Line) HTTP/1.1 200 OK Server Resin/3.1.5 EtagClNcVcwhyDQ Last-Modified Fri, 11 Jul 2008 08:13:24 GMT Cache-Control private Content-Encodinggzip Content-Typetext/html; charset=UTF-8 Content-Length 85824 DateFri, 11 Jul 2008 08:39:45 GMT Yet, I am getting this error. I think it's something caused by GzipFilter, but then I'm not sure what could have went wrong here. This file should have been served directly from FileServlet. Scott, do you have any ideas? -Chris On Jul 11, 2008, at 1:11 AM, Chris Chen wrote: This is a question aimed at Resin's support team. I'm wondering what the defaults for a Filter's dispatcher setting is. This is only valid for 2.4 webapps. So if I were to exclude these parameters, does this mean that Resin 3.1.5 will filter all types of dispatched requests? I ask this because I'm looking at the example configuration for the GzipFilter and I'm not sure if it filters only on REQUEST or the other ones as well. Should I be worried if I don't include the dispatcher config? I had this issue regarding filter dispatchers when configuring Confluence. -Chris ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com
Re: [Resin-interest] Filter's dispatcher defaults
I just disabled resin caching proxy and tested it. Some response headers are now going through and it appears that caching is working better at the moment. However, the system is still unable to decode that specific GWT cache.html file. No matter what happens, this file is somehow not being encoded properly or something. In fact, trying to encode any of the GWT-generated cache.html files just won't work. It seems like it's a very specific problem with these files. And they're not even gzipped. I should try a test where I gzip it unzip it myself to see what happens. -Chris On Jul 11, 2008, at 3:33 AM, Chris Chen wrote: I am using your configurations and it's working, but only because the responses are not getting encoded. I think this may be caused by the load balancer web tier that I have running. I believe you are probably on the right track on that one. I have resin cache enabled on both the web and the app tiers. It's likely that somehow the caching mechanism on the web tier is causing havoc. Looks like I will have to dig a little deeper into the caching mechanism of resin. I am going to disable caching to see if things are ok first. -Chris On Jul 11, 2008, at 3:11 AM, Haroon Rasheed wrote: Also I would like to know, whether your server is running under a LoadBalancer? if yes... please send the details on the same... Please try the following configuration and lemme know if this helps. !--gzip changes start-- filter filter-name=gzip filter- class=com.caucho.filters.GzipFilter init use-varytrue/use-vary /init /filter filter-mapping filter-name=gzip url-pattern exclude-pattern*.pdf/exclude-pattern exclude-pattern*.zip/exclude-pattern include-pattern/*/include-pattern /url-pattern /filter-mapping !--gzip changes end-- Regards, Haroon 2008/7/11 Chris Chen [EMAIL PROTECTED]: Thanks for the reply, my configuration comes directly from the documentation: filter filter-name=gzip filter- class=com.caucho.filters.GzipFilter/ filter-mapping filter-name=gzip url-pattern=/*/ The interesting thing is that other files seem to zip fine. I am consistently hitting encoding issues with this particular GWT cache.html file. Gzip and Resin appears to be returning the code just fine. Yet somehow I am getting content encoding errors from Safari, Firefox, and now-tested Curl (I was trying to use curl to figure out what exactly is the problem, but no go). The files are all accessed through SSL if that has any relevance. I'm also running under Linux -Chris On Jul 11, 2008, at 2:32 AM, Haroon Rasheed wrote: Chris, We have been using gzip filter on production servers for the past 8 months, and didn't face any such issues. Please send the gzip filter configuration from web.xml, lemme see if anything is different in your conf? Thanks regards, Haroon 2008/7/11 Chris Chen [EMAIL PROTECTED]: Actually, I have a further problem using GzipFilter. I enabled it using no dispatcher, which according to Servlet Spec 2.4, means that it defaults to only REQUEST. When I started using the GzipFilter, I noticed a few things 1) Gzip appears to work on static files that are served through FileServlet, so that takes care of mostly the JS, CSS, and image files. 2) However, when it comes to the primary pages served by Grails, these do not get compressed. I have a feeling that this is because of the internal forwarding that's going on with the URL Mapping, GSP servlet, etc. So my question is - is it safe to enable GzipFilter for FORWARDed requests in the dispatcher? 3) I am using GWT (google web toolkit) and it serves out javascript files. There is a nocache.js file and then there are cache.html javascript files. It appears that the nocache.js files are downloaded properly, but my primary cache.html files are being compressed improperly for some reason. Here's the request: GET /v1/gwt/com.bbb.Mail/1B5800A70AEC91E23D018344A2E80852.cache.html HTTP/1.1 The error I get on Firefox is Content Encoding Error: The page you are trying to view cannot be shown because it uses an invalid or unsupported form of compression. The error I get on Safari is cannot decode raw data (NSURLErrorDomain:-1015) The response header for this request looks like everything is ok: (Status-Line) HTTP/1.1 200 OK Server Resin/3.1.5 EtagClNcVcwhyDQ Last-Modified Fri, 11 Jul 2008 08:13:24 GMT Cache-Control private Content-Encodinggzip Content-Typetext/html; charset=UTF-8 Content-Length 85824 DateFri, 11 Jul 2008 08:39:45 GMT Yet, I am getting this error. I think it's something caused by GzipFilter, but then I'm not sure what could have went wrong here. This file should have been served directly from FileServlet. Scott, do you have any ideas? -Chris On Jul 11, 2008, at 1:11 AM, Chris Chen wrote: This is a question aimed at Resin's support team. I'm wondering what the defaults
Re: [Resin-interest] Filter's dispatcher defaults
I think I have figured out the problem. It appears to be filter orders. I have my gzip filter in my resin-web.xml. I thought and assumed that resin-web.xml take priority over web.xml, but I was wrong. I then found that app-defaults.xml indicates the loading order. So basically, my gzip filter has been loading as the last filter out of all the other filter (ie. grails filter, spring framework filters, etc). Most of these filters don't modify the content except for probably one of them (one that has to do with .html files is my guess). It's too late and I don't really care which one is the culprit, but I think I found my solution. Thanks for all the help. :) Chris On Jul 11, 2008, at 4:01 AM, Chris Chen wrote: I have now narrowed the situation down to the file extension. Specifically, Gzip is causing encoding problems when the file extension ends with .html. I renamed the same file to some other extension and the file get encoded and decoded properly with no problems. Yet, when the filter tries to encode/decode files with HTML extensions, somehow, the file is not encoded right. What could possibly be going on here? My only guess right now is that there may be other filters running before mine. I will turn on deep logging to see if I can catch something in the resin log. -chris On Jul 11, 2008, at 3:48 AM, Chris Chen wrote: I just disabled resin caching proxy and tested it. Some response headers are now going through and it appears that caching is working better at the moment. However, the system is still unable to decode that specific GWT cache.html file. No matter what happens, this file is somehow not being encoded properly or something. In fact, trying to encode any of the GWT-generated cache.html files just won't work. It seems like it's a very specific problem with these files. And they're not even gzipped. I should try a test where I gzip it unzip it myself to see what happens. -Chris On Jul 11, 2008, at 3:33 AM, Chris Chen wrote: I am using your configurations and it's working, but only because the responses are not getting encoded. I think this may be caused by the load balancer web tier that I have running. I believe you are probably on the right track on that one. I have resin cache enabled on both the web and the app tiers. It's likely that somehow the caching mechanism on the web tier is causing havoc. Looks like I will have to dig a little deeper into the caching mechanism of resin. I am going to disable caching to see if things are ok first. -Chris On Jul 11, 2008, at 3:11 AM, Haroon Rasheed wrote: Also I would like to know, whether your server is running under a LoadBalancer? if yes... please send the details on the same... Please try the following configuration and lemme know if this helps. !--gzip changes start-- filter filter-name=gzip filter- class=com.caucho.filters.GzipFilter init use-varytrue/use-vary /init /filter filter-mapping filter-name=gzip url-pattern exclude-pattern*.pdf/exclude-pattern exclude-pattern*.zip/exclude-pattern include-pattern/*/include-pattern /url-pattern /filter-mapping !--gzip changes end-- Regards, Haroon 2008/7/11 Chris Chen [EMAIL PROTECTED]: Thanks for the reply, my configuration comes directly from the documentation: filter filter-name=gzip filter- class=com.caucho.filters.GzipFilter/ filter-mapping filter-name=gzip url-pattern=/*/ The interesting thing is that other files seem to zip fine. I am consistently hitting encoding issues with this particular GWT cache.html file. Gzip and Resin appears to be returning the code just fine. Yet somehow I am getting content encoding errors from Safari, Firefox, and now-tested Curl (I was trying to use curl to figure out what exactly is the problem, but no go). The files are all accessed through SSL if that has any relevance. I'm also running under Linux -Chris On Jul 11, 2008, at 2:32 AM, Haroon Rasheed wrote: Chris, We have been using gzip filter on production servers for the past 8 months, and didn't face any such issues. Please send the gzip filter configuration from web.xml, lemme see if anything is different in your conf? Thanks regards, Haroon 2008/7/11 Chris Chen [EMAIL PROTECTED]: Actually, I have a further problem using GzipFilter. I enabled it using no dispatcher, which according to Servlet Spec 2.4, means that it defaults to only REQUEST. When I started using the GzipFilter, I noticed a few things 1) Gzip appears to work on static files that are served through FileServlet, so that takes care of mostly the JS, CSS, and image files. 2) However, when it comes to the primary pages served by Grails, these do not get compressed. I have a feeling that this is because of the internal forwarding that's going on with the URL Mapping, GSP servlet, etc. So my question is - is it safe to enable
Re: [Resin-interest] Change TimeZone
I think this has to do with your system clock time. You need to change your server timezone through your system configuration commands. The way to change it depends on what operating system you're running on. -Chris On Jun 5, 2008, at 5:44 AM, Laurent MAGNIEZ wrote: Hello, I'm using Resin3.0.18 under Debian. All the dates in my application are staggered by one hour, since the transition to summer time. I explain : when i launch Resin, i can see in log : Starting Resin on Fri, 16 May 2008 16:44:16 +0100 (GMT+01:00) For all my other servers, TimeZone is +0200 (CEST) and it works fine. How can i specify the TimeZone ? Thanks for any help Laurent MAGNIEZ ___ 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] Smarty - 3.1.4, 3.1.5
, 2008, at 4:41 PM, Chris Chen wrote:
I've narrowed this down to the regular expression issue. It's
failing on a regular expression that appears to work initially but
later on fails for some very strange reason. I have not yet been
able to pinpoint, but let me show you what I have so far.
In PHPBB3's includes/function_template.php file, there is a regular
expression line:
preg_match_all('#!-- ([^].*?) (.*?)? ?--#', $code, $blocks,
PREG_SET_ORDER);
I've filed that as http://bugs.caucho.com/view.php?id=2526
The (.*?)? is more complicated than you'd think.
-- Scott
The $code is actually the template file to parse. This line fails
miserably. Interestingly, the regex a few lines above it works well:
preg_match_all('#!-- INCLUDE ([a-zA-Z0-9\_\-\+\./]+) --#', $code,
$matches);
It's parsing the same $code file.
I am currently testing the possible differences between the two
expressions to narrow down the cause. It appears to be the ?
that may be causing serious issues or it could be more than that.
Still checking.
I'm hoping that this may give either Scott or you some ideas on
where to look cuz this is a serious issue if the regex parser is
badly written. Too many php codes rely on regex.
-Chris
On Mar 13, 2008, at 1:59 PM, Andrew Fritz wrote:
Chris Chen wrote:
Your problem is similar to mine.
I spent the entire day yesterday trying to debug phpbb3 running on
quercus. Phpbb3 appears to be using either Smarty or something
similar and I am getting almost the exact problem that you're
getting.
It was super difficult to debug scripts under quercus. Debugging
under IntelliJ is driving me nuts. :)
Yah, IntelliJ is the bomb... To bad they don't have PHP support
yet... (make sure you leave a comment in their suggestion box that
they need it).
Since i am able to consistently get quercus to not process smarty
tags, I am a bit closer to finding the real cause to the
problem. I
believe I've at least narrowed it down to either the Regex module
or
the Array storage/processing in Quercus.
If I get some time, I may continue to debug and find out why
Quercus
simply hates these regular expressions.
I'd guess Array, but that is based only on my experience with lazy
initialization in hibernate not working on contained lists (but it
works fine everywhere else). Of course, regex is probably equally
likely. I spent the better part of the day trying to get
HTMLPurifier working. The end result was a java class that
System.executes native php to clean html and print the results...
I never got it to run under Resin. It would fail to tokenize the
HTML... In any case, I would appreciate any info you have if you
manage to sort it out.
Perhaps spending the time trying to get vbulletin to work under
quercus might be a more productive use of my time. :)
-Chris
On Mar 13, 2008, at 1:06 PM, Andrew Fritz wrote:
Sorry if this is the wrong list, but the Quercus list appears to
be
KIA.
There is no mail in the archive and mail to quercus-
[EMAIL PROTECTED]
bounces.
Now to my question/statement:
Smarty works great in 3.1.3, but is broken in 3.1.4 and 3.1.5. I
opens
the template file and returns the contents unprocessed. All the
tags
remain in the file. Is there a work around to make it work
again? I
need
to upgrade to try to get around another bug, but can't right now
since
our side is pretty much 100% smarty templates.
Andrew
___
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
___
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
Re: [Resin-interest] Smarty - 3.1.4, 3.1.5
Your problem is similar to mine. I spent the entire day yesterday trying to debug phpbb3 running on quercus. Phpbb3 appears to be using either Smarty or something similar and I am getting almost the exact problem that you're getting. It was super difficult to debug scripts under quercus. Debugging under IntelliJ is driving me nuts. :) Since i am able to consistently get quercus to not process smarty tags, I am a bit closer to finding the real cause to the problem. I believe I've at least narrowed it down to either the Regex module or the Array storage/processing in Quercus. If I get some time, I may continue to debug and find out why Quercus simply hates these regular expressions. Perhaps spending the time trying to get vbulletin to work under quercus might be a more productive use of my time. :) -Chris On Mar 13, 2008, at 1:06 PM, Andrew Fritz wrote: Sorry if this is the wrong list, but the Quercus list appears to be KIA. There is no mail in the archive and mail to quercus- [EMAIL PROTECTED] bounces. Now to my question/statement: Smarty works great in 3.1.3, but is broken in 3.1.4 and 3.1.5. I opens the template file and returns the contents unprocessed. All the tags remain in the file. Is there a work around to make it work again? I need to upgrade to try to get around another bug, but can't right now since our side is pretty much 100% smarty templates. Andrew ___ 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] Quercus with phpbb3
Scott, I've been trying multiple times to get Quercus to run phpbb3 properly and I continue to have problems with getting the generated cached template files to render consistently. After a server restart, things work for a few pages until it hits some sort of snag. This consistently happens after I tried accessing different pages that requires the template caching mechanism to kick in. Once that happens, the comments in the template fails to get parsed afterwards. Turning on full debugging output (finest level) produces exceptions that are not entirely helpful: [2008/03/11 20:18:52.873] idle PoolItem[jdbc/mpm, 4,ManagedConnectionImpl] [2008/03/11 20:18:52.874] com.caucho.quercus.QuercusExitException [2008/03/11 20:18:52.874] at com.caucho.quercus.env.Env.exit(Env.java:3852) [2008/03/11 20:18:52.874] at com.caucho.quercus.expr.ExitExpr.eval(ExitExpr.java:82) [2008/03/11 20:18:52.874] at com.caucho.quercus.program.ExprStatement.execute(ExprStatement.java:64) [2008/03/11 20:18:52.874] at com.caucho.quercus.program.BlockStatement.execute(BlockStatement.java: 99) [2008/03/11 20:18:52.874] at com.caucho.quercus.program.Function.callImpl(Function.java:354) [2008/03/11 20:18:52.874] at com.caucho.quercus.program.Function.call(Function.java:294) [2008/03/11 20:18:52.874] at com.caucho.quercus.expr.FunctionExpr.evalImpl(FunctionExpr.java:182) [2008/03/11 20:18:52.874] at com.caucho.quercus.expr.FunctionExpr.eval(FunctionExpr.java:126) [2008/03/11 20:18:52.874] at com.caucho.quercus.program.ExprStatement.execute(ExprStatement.java:64) [2008/03/11 20:18:52.874] at com.caucho.quercus.program.BlockStatement.execute(BlockStatement.java: 99) [2008/03/11 20:18:52.874] at com.caucho.quercus.program.Function.callImpl(Function.java:354) [2008/03/11 20:18:52.874] at com.caucho.quercus.program.Function.call(Function.java:294) [2008/03/11 20:18:52.874] at com.caucho.quercus.expr.FunctionExpr.evalImpl(FunctionExpr.java:182) [2008/03/11 20:18:52.874] at com.caucho.quercus.expr.FunctionExpr.eval(FunctionExpr.java:126) [2008/03/11 20:18:52.874] at com.caucho.quercus.program.ExprStatement.execute(ExprStatement.java:64) [2008/03/11 20:18:52.874] at com.caucho.quercus.program.BlockStatement.execute(BlockStatement.java: 99) [2008/03/11 20:18:52.874] at com.caucho.quercus.program.QuercusProgram.execute(QuercusProgram.java: 239) [2008/03/11 20:18:52.874] at com.caucho.quercus.page.InterpretedPage.execute(InterpretedPage.java:70) [2008/03/11 20:18:52.874] at com.caucho.quercus.page.QuercusPage.executeTop(QuercusPage.java:119) [2008/03/11 20:18:52.874] at com .caucho .quercus.servlet.ResinQuercusServlet.service(ResinQuercusServlet.java: 146) [2008/03/11 20:18:52.874] at com.caucho.quercus.servlet.QuercusServlet.service(QuercusServlet.java: 353) [2008/03/11 20:18:52.874] at javax.servlet.http.HttpServlet.service(HttpServlet.java:91) [2008/03/11 20:18:52.874] at com .caucho .server.dispatch.ServletFilterChain.doFilter(ServletFilterChain.java: 103) [2008/03/11 20:18:52.874] at com .caucho .server.webapp.WebAppFilterChain.doFilter(WebAppFilterChain.java:181) [2008/03/11 20:18:52.874] at com .caucho .server.dispatch.ServletInvocation.service(ServletInvocation.java:266) [2008/03/11 20:18:52.874] at com.caucho.server.hmux.HmuxRequest.handleRequest(HmuxRequest.java:435) [2008/03/11 20:18:52.874] at com.caucho.server.port.TcpConnection.run(TcpConnection.java:603) [2008/03/11 20:18:52.874] at com.caucho.util.ThreadPool $Item.runTasks(ThreadPool.java:721) [2008/03/11 20:18:52.874] at com.caucho.util.ThreadPool $Item.run(ThreadPool.java:643) [2008/03/11 20:18:52.874] at java.lang.Thread.run(Thread.java:595) I wish the exception output would be a bit more information so I know where the exception occurred. Aside from that, I've tried different file caching mechanisms that is supported by phpbb3's newest SVN trunk source tree. I tried out APC and Memcache. APC is still giving me similar problems but appeared more consistent than the default file one. Memcache has problems starting up so it appears that memcache is still not fully implemented yet. Tried with compile off and on. That didn't work either. Are there any plans to get phpbb3 to work properly? I guess if I get some time, the only way is to run quercus within Eclipse or Idea and do a full break debug to see what's wrong. Thanks, Chris ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Resin listens unexplained ports?
This is likely because you enabled management or the jmx management port through your -D system property. Just remove the -D system property from your server config and you should see those additional port go away. -Dcom.sun.management.jmxremote -Chris On Mar 6, 2008, at 8:28 AM, Scott Ferguson wrote: On Mar 6, 2008, at 8:07 AM, Tomi Po wrote: Hello, I am running Resin Pro 3.1.5 and I see it is listening 4 ports in total. TCP 127.0.0.1:6600 TCP 127.0.0.1:6800 TCP *:37140 TCP *:59408 First two are clear; Resin Watchdog port listens 6600, and server at 6800, but these other two that listen foreign ports. I have not found explanation for those ports - maybe I am missing something? Are you sure that's Resin? Try getting a thread dump (see /resin- admin). The thread dump would show what's listening to the sockets. -- Scott Somewhere in the Resin documentation there was mentioned that Resin shows all ports that it is listening when it boots up. Those ports are not mentioned in the startup messages. (And before anyone suggests the obvious: those ports really belong to resin java process). What are they? How to disable them? Or modify them to listen localhost only? Thanks in advance! Tomi ___ 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
[Resin-interest] Disabling display of server info
Does anyone know if there is a configuration setting that allows me to either disable server info or server version info when an error code/ page is shown? Currently, if a 404 or 500 or other error occurs, resin outputs an error with the server + version appended at the end. I'd like to be able to either modify this or remove it for increased security. Thanks, Chris ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
[Resin-interest] New 3.1.5 watchdog causing some config issues
Scott, With all the new changes to the watchdog process to make it more secure (which is a good thing), I have come across behavior that is limited: I have two config files, one for the web tier and one for the backend app tiers. The configuration is fairly similar to how the documentation states. 1) the resin-web.conf (for the web tier) has its own set of configuration settings. However, in order for the Load Balancing Servlet to see the app tier clusters and servers, I need to include minimal cluster config inside resin-web.conf: cluster id='abc' server id='abc' port='6800' .../ /cluster This is the minimal that will allow the load balancing servlet to understand where to dispatch the requests in the rewrite section. 2) I then have resin.conf file that contains all the app tier config settings for all clusters. This configuration worked well even in 3.1.5 snapshots, but when I upgraded to 3.1.5, I started seeing duplicate server id exceptions thrown by the watchdog process. From what I can gather, I believe that the watchdog process is tying configuration filenames to the settings now. So in this case, if I start up the web tier cluster on the same machine as the app tier and then start up one of the app tier cluster servers, watchdog will think that it's trying to register a duplicate server id. By putting all the resin-web.conf configuration info into resin.conf, watchdog process doesn't complain any longer. Given the new watchdog process monitoring, I'm thinking that the Load Balancer Servlet can be enhanced to work with the new watchdog process. Here's what I'm proposing: 1) Watchdog process contains all the cluster names and server ids. 2) web tier's load balancer servlet only needs to know the cluster name and doesn't require any additional cluster configurations in the CONF file. It will then query the cluster information from the watchdog process in some way to determine where to redirect the request to. Or is there perhaps another way to configure the watchdog process so that it won't think that the web tier config is trying to register new clusters? Or possibly I need to create three config files, one for web tier, one for app tier, and one shared conf file that contains all the cluster configurations that will be resin:import'ed into the web and app tier? -Chris ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] xfire issue
Try enabling servlet hack for that specific webapp. I believe that should resolve the issue. THanks, Chris On Jan 18, 2008, at 6:57 AM, Jason Wang wrote: I run into this trouble for several days resin 3.0.24 is ok Jason On 1/18/08, Akhil Kodali [EMAIL PROTECTED] wrote: Hi, I'm exposing webservices using xfire-1.2.6 on resin-3.1.2-pro with the evaluation license. For some reason data the webservices is unable to receive the data I send from the client The same app seems to work fine on jboss. Regards, Akhil Kodali ___ 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
Re: [Resin-interest] xfire issue
It's part of the resin configuration... in your resin-web.xml, just add web-app class-loader servlet-hacktrue/servlet-hack /class-loader /web-app the configuration is inside your web-app/ configuration. Search for the configuration setting in Resin docs. -Chris On Jan 18, 2008, at 8:27 AM, Akhil Kodali wrote: Hi, How do I do that, any samples or references. And I have to use jdk1.6 Regards, Akhil Chris Chen wrote: Try enabling servlet hack for that specific webapp. I believe that should resolve the issue. THanks, Chris On Jan 18, 2008, at 6:57 AM, Jason Wang wrote: I run into this trouble for several days resin 3.0.24 is ok Jason On 1/18/08, *Akhil Kodali* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi, I'm exposing webservices using xfire-1.2.6 on resin-3.1.2- pro with the evaluation license. For some reason data the webservices is unable to receive the data I send from the client The same app seems to work fine on jboss. Regards, Akhil Kodali ___ resin-interest mailing list resin-interest@caucho.com mailto:resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com mailto: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 ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
[Resin-interest] Caucho bug tracker
Scott, Is it just me or is the bug tracker database down? I can't seem to reach it from different ISP locations. -Chris ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
[Resin-interest] Running what instances under the same watchdog process
I have a quick question. This may possibly be directed to Scott. How does resin determine what resin server instances run under the same watchdog process? This relates to a bug issue that I just posted in bug track. Does resin use the server root, the monitored ports, the resin.conf, and others to determine this or does it simply allow anyone to write a matching (even if it's a hacking attempt) resin.conf to run under the same watchdog process. I would like to know how resin does this as I described the security concern in more detail on bug track: http://bugs.caucho.com/view.php?id=2201 Thanks, Chris ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
[Resin-interest] Resin and Confluence
I've found talks about how Confluence web.xml needed to be modified to work around some bug issues with how Resin parses web.xml. I'm wondering what Caucho's take on this is? It seems like this is causing quite a lot of grief, and apparently there seems to be some problem with handling large image uploads as per the JIRA issue: http://jira.atlassian.com/browse/CONF-8637 There are also configuration issues. Has the configuration parsing been addressed in 3.1.3? I've actually had this configuration issue since the old days. -Chris ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Filter mapping to /* with no servlets mapped to /
Yea, I saw that.. unfortunately, the /controller/action is actually determined dynamically. It's actually not the static string controller but a controller name that is based on the available action controllers. The job of the UrlMapper filter is to parse this URL and then dispatch the request to the proper controller with the proper action method to handle the request. Since it's dynamic, I am unable to create the servlet mapping patterns. -Chris On Oct 30, 2007, at 12:20 PM, Sam wrote: [ ... ] Here's the thing. Grails' web.xml has filter mappings for the url- pattern of /*. One of the filters, the UrlMapper, will actually process the URL and then dispatch the request to the proper controller and action to process the request. However, there is no servlet mapping that is mapped to pass all / requests to resin for processing. Thus, mod_caucho simply assumes that requests should not be passed to resin for processing. To get this working, I actually added a SetHandler caucho-request to my .htaccess file under the webapp directory. Now, the requests are passed over to resin for processing. You can also do this using the plugin_match servlet in your web.xml, something like: servlet-mapping url-pattern='/controller/*' servlet- name='plugin_match'/ Documentation is here: http://caucho.com/resin-3.1/doc/plugin-dispatch.xtp under special servlet-mappings -- Sam ___ 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] Resin's watchdog starting multiple resin servers
Considering that Resin now has a watchdog process that monitors the servers, is it possible to simply have the watchdog monitor and start multiple resin servers? Here's what I'm thinking why this is good. 1) One startup script to startup resin. No need to create multiple startup scripts that each runs a separate resin instance. 2) One resin watchdog process. 3) One resin configuration file (which already contains all the configurations anyways). I can create multiple resin cluster segments that launches hosts all the same apps and services within each cluster. I can also have multiple hosts specified that launches only the services/apps specific to that host. I'm not sure if this is possible at the moment or not. But it'd be great. Resin's watchdog can actually look at different clustered hosts, check if each the host it's running on matches a host inside each cluster, and then launch a separate resin server for each cluster. This way, it's like running one MySQL service manager that can start up multiple instances of mysql server (different versions, different databases, etc). MySQL also only uses one config file for all the configurations. Thanks, Chris ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Slooow file reads (really weird!)
Yea, This is a good way. Unfortunately, I believe resin-admin uses Quercus. I have disabled Quercus because I have php apps running that are not running properly under it. When I enable php processing, Resin takes control over ALL files with the php extension, which shouldn't be the case (btw, I do run an Apache frontend). mod_caucho is taking over all control of all files with the php extension. I guess I should consider this a bug since mod_caucho should only pass php processing to Resin only for the specific web- app paths and not all PHP files. This way, I can have Resin Quercus coexisting peacefully with PHP itself. -Chris On Oct 6, 2007, at 12:35 PM, Scott Ferguson wrote: On Oct 6, 2007, at 12:03 PM, Chris Chen wrote: Rather than doing all the profiling like you (which I would have liked to but i was too lazy), I just did a thread dump. By the way, the Resin admin now has a quick-and-dirty profiler (and thread dumper and heap dumper) which is really handy when you're too lazy to configure a full profiler, or on a live system when you want some data immediately. -- Scott ___ 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
