Re: [Resin-interest] need help w. 405 server error msg.
Date: Thu, Dec 21, 2006 at 08:42:35PM -0600 Subject: [Resin-interest] need help w. 405 server error msg. I need some help/assistance from someone concerning always getting a 405 server error message everytime that I have tried to view a servlet with an image in it! Here is my code for the servlet : //package test; ... servlet servlet-name=hello servlet-class=HelloServlet/ All java classes have to be in a package. So the HelloServlet source code should be in a file: WEB-INF/classes/test/HelloServlet.java and should start with a line: package test; and the web.xml configuration should include the package in the class name: servlet servlet-name=hello servlet-class=test.HelloServlet/ -- Sam ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Question on db based distributed session
1. I start server A and login to my application At this point, A will get your request and will become your primary server, and B will be your secondary server. 2. I stop Server A and start Server B 3. I continue to work in the browser, my session stays intact and i can proceed normally At this point, you are using secondary server B. Your session updates are saved on B. 4. I logout from my application and logout successfully cleared my session variables (notice this from app log) 5. I stop Server B and start Server A 6. I try to type a password protected page in the browser and i *CAN ACCESS* the protected page At this point, A (the primary) will contact B to try to get any updates to the session that have been made. Since B is down, A cannot get the session from it. So it has to go with the outdated session that it has, because it cannot get the updated session from B. -- Sam ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Error
500 Servlet Exception javax.servlet.ServletException: too many servlet includesI use tomcat and I like to change to resin.But the jsp return this mensseger. Debug logging will be very helpful here, you can enable it by adding the following line in resin.conf: logger name= level=fine/ A level of finer will give even more information. The debug log will show the urls that are being used in the forward, and will help to trace down the source of the problem. -- Sam ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] How to start Resin at bootup time with non-rootuser
Is there a list of changers and er ... fixed bugs in 3.1 please? http://www.caucho.com/resin-3.1/changes/index.xtp -- Sam ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Quercus is fantastic !
Running apt-get install libapache-mod-php5 is a lot easier than running Resin for 99.99% of people in my experience. We are planning on creating a debian package after the 3.1.1 release. With the decision to package the Sun JDK as a debian package that should work fairly well. Why Caucho decided to have php support in their webserver rather than fix the bugs in the Servlet container is something that confuses my and my colleagues almost daily. We did consider that, and we hired more engineers to make sure that Quercus development would not impact the time and effort we had to apply to Resin. We actually have more resources working on Servlet/JSP/Java EE than we did at the time Quercus development was started. We are still looking to hire more people: http://www.caucho.com/sales/jobs.xtp For bug fixes, we follow the bugtracker closely (bugs.caucho.com) and try to prioritize. As mentioned in another post, it is helpful if there is a reproducable test case. Customers who sign up for platinum support almost always have bug fixes completed for the next release, and often we release an interim snapshot so that the bug fix can be tested. -- Sam ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Odd error when starting up container
I'm getting the following error starting up resin-3.0.19 and/or resin-3.0.23 and have yet to figure out what exactly is causing it: java.lang.NoSuchMethodError: com.caucho.jsp.QJspFactory.allocatePageContext(Ljavax/servlet/ Servlet;Lcom/caucho/server/webapp/Application;Ljavax/servlet/ ServletRequest;Ljavax/servlet/ServletResponse;Ljava/lang/ String;Ljavax/servlet/http/HttpSession;IZ)Lcom/caucho/jsp/ PageContextImpl; It looks like there are some old compiled jsp that are not getting deleted, you can try deleting the WEB-INF/work/ directory and Resin will recompile all of the jsp. -- Sam ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Resin 3.x and the system classpath
I need to be able to use $CLASSPATH (and the value it
contains)
jvm-arg-Djava.library.path=$CLASSPATH/jvm-arg
is not going to work now, is it ?
Try:
jvm-arg-Djava.library.path=${CLASSPATH}/jvm-arg
-- Sam
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Running two resin instances in different IPs
Date: Fri, Apr 20, 2007 at 10:07:40AM +0530 Subject: Re: [Resin-interest] Running two resin instances in different IPs Hi, I think it cos of the service... try to run resin-pro-3.1.snap with diff name or something like that.. haven't try it by myself but better to give a try.. I am trying to run two resin servers; resin-pro 3.1.0 and resin- pro-3.1.snap in my server in different IPs say 192.168.1.34 and 192.168.1.35. When Resin binds to a port, it provides both a port number and an address to the operating system. The default address is '*' which means to bind to all addresses. To bind to a specific address, specify a different address in each resin.conf: In 1st resin.conf: http address=192.168.1.34 port=80/ In 2nd resin.conf: http address=192.168.1.35 port=80/ In Resin 3.0 the configuration is called 'host' instead of 'address': http host=192.168.1.35 port=80/ -- Sam ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] LDAPAuthenticator with ActiveDirectory
I'm also interested in LDAP authentification, our new customer is a big organization, and they want our application to use LDAP services for authentification. I must say that I know very few about this. I could not find any class in resin's doc about LDAP Resin includes a class com.caucho.server.security.LdapAuthenticator An example usage is below: authenticator typecom.caucho.server.security.LdapAuthenticator/type init jndi-env java.naming.provider.url=ldap://localhost:389/ dn-suffixdc=example,dc=com/dn-suffix user-attributeuid/user-attribute !-- default is uid -- password-attributeuserPassword/password-attribute !-- default is userPassword -- password-digestnone/password-digest /init /authenticator The current (3.1.0) implementation does not obtain roles, it returns true for any isUserInRole request if the user has successfully been authenticated. Logging at the fine level is useful while setting it up, and the source code is fairly simple and worth taking a look at. -- Sam ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] LDAPAuthenticator with ActiveDirectory
Date: Thu, May 03, 2007 at 07:28:55PM +0200 Subject: Re: [Resin-interest] LDAPAuthenticator with ActiveDirectory thanks that's great, and we may use it for a 3,1 server. Now we are in 3,0,18, so I'll look at openldap The LdapAuthenticator has been available since version 3.0.19. -- Sam ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Quercus and gallery 2.1
Anyone running gallery2.1 successfully with resin-pro-3.1.1 I had gallery 2.1 running successfully on a pre 3.1.1 release of 3.1. Having upgraded to 3..1 I now get loads of usr/web/databases/webapps/gallery2/modules/core/classes/Gallery.class:60 7: Warning: Assertion !empty($key) failed Bug report here: http://bugs.caucho.com/view.php?id=1744 It may be that this is really a bug in gallery, perhaps the assertion should not be failing. Prior to 3.1.1, Quercus did not evaluate assert expressions. Of course, it could also be a bug in Quercus, a bug that causes the $key to be empty when it should not be. -- Sam ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] ssl port
Resin 3.1.1 includes some features in rewrite-dispatch that may be able to help: http://www.caucho.com/resin-3.1/doc/rewrite-tags.xtp#set Basically, there is facility to set the isSecure method of the request to return true if there is some condition of the request (such as a header set by the load balancer) that can be used to determine that the request should be secure. web-app xmlns=http://caucho.com/ns/resin; rewrite-dispatch set request-secure=true when header=X-SSL-cipher/ /set /rewrite-dispatch /web-app If the load balancer is configured to proxy regular requests to port 8080 and SSL requests to port 8443 then something like the following should work: web-app xmlns=http://caucho.com/ns/resin; rewrite-dispatch set request-secure=true when local-port=8443/ /set /rewrite-dispatch /web-app -- Sam ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] application variables, j2ee - php, and shared nothing
im curious about application variables under the j2ee web application paradigm. are these used frequently in the context of application servers, like resin, or are they regarded as taboo? also, has anyone heard of the shared nothing architecture? how does that pertain, if at all, to the j2ee paradigm? i was discussing application variables w/ some members of php-general and from the sound of it; they are taboo in the php world. Application variables are not possible in the php world when using the C implementation. Each php request is served by a different proccess, and those processes cannot share data without using an intermediary like a database, the file system, or a cache server. The processes also cannot share database connections, so connection pooling is not an option, which can be a serious scalability issue. Using the application scope for things like common configuration and caching can be very effective. The cache-coherence problem is a problem if the application requires that the cache have absolutely up to date information in it. Much of the information served on the web can be cached and have some inconsistency for a short period of time. -- Sam ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Resin and transactions (disable autocommit)
Date: Tue, Aug 28, 2007 at 12:52:23PM -0500 Subject: Re: [Resin-interest] Resin and transactions (disable autocommit) ... Long story short I'm trying to run Jasper report server on Resin instead of Tomcat. It seems to work OK except for when it comes to large objects at which point the PostgreSQL driver throws an exception that all LO operations must be performed inside a transaction... Tomcat has an option to turn off auto-commits at the resource definition. Does Resin have anything along these lines? Added a bug report: http://bugs.caucho.com/view.php?id=2001 -- Sam ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Resin and transactions (disable autocommit)
Long story short I'm trying to run Jasper report server on Resin instead of Tomcat. It seems to work OK except for when it comes to large objects at which point the PostgreSQL driver throws an exception that all LO operations must be performed inside a transaction... Tomcat has an option to turn off auto-commits at the resource definition. Does Resin have anything along these lines? Added a bug report: http://bugs.caucho.com/view.php?id=2001 The transaction filter can be used to solve this problem: filter filter-name='transaction-filter' filter-class='com.caucho.filters.TransactionFilter'/ filter-mapping url-pattern='/*' filter-name='transaction-filter'/ The example above causes all requests to be done within a transaction. The url-pattern could be made more specific so that only those requests that use jasper reports are captured by the filter. -- Sam ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Resin 3.1.1 and Struts iterate tag problems
Thanks Jason. I'm now trying this with Resin 3.1.2. However, it's taking a painfully long time to start up - of the order of one hour, where Resin2x and Resin 3.1.1 take 1-2 minutes to startup with the app deployed. Is this related to the new startup listen() change in resin 3.1.2? I'm using the default resin.conf file. There should not be such a difference in startup between those two versions. Actually, I think there was some work done to make the startup of 3.1.2 a bit faster. Obtaining a thread dump from the process while it is doing whatever it is doing during startup that is taking so long would be helpful. Sometimes it's beneficial to get 2 thread dumps, a few seconds or a minute apart. Some documentation about thread dumps: http://www.caucho.com/resin-3.1/doc/troubleshoot.xtp#thread-dump You can also use the startup logging to get a general idea of what is taking so long. -- Sam ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Filters are not run when using rewrite-dispatch forward
Date: Tue, Sep 11, 2007 at 01:10:45PM +0200 Subject: [Resin-interest] Filters are not run when using rewrite-dispatch forward Hi, Filters are not run when requests are forwarded with rewrite-dispatch. According to these bug reports it's fixed in 3.1: http://bugs.caucho.com/view.php?id=1510 http://bugs.caucho.com/view.php?id=1514 Resin 3.0 includes the RewriteFilter. Since it's a filter, you can use the regular ordering of filters to place a filter before it. http://www.caucho.com/resin-3.0/servlet/filter-library.xtp#RewriteFilter -- Sam ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] ThrottleFilter crashing our resin process
Date: Fri, Nov 09, 2007 at 01:22:39PM -0800 Subject: [Resin-interest] ThrottleFilter crashing our resin process Enabling ThrottleFilter on our webapp is not functioning. The resin process will start up, load, open connections, ramp up, then slowly die. The same symptoms for 1, 2, 4, and 6 concurrent allowed connections. We have to turn it off for resin to stay up. There were some changes made for the ThrottleFilter in 3.1. A thread dump from the server that is hung up would help for evaluating the problem. -- Sam ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] 3.0.25 Update
Date: Sun, Dec 09, 2007 at 07:23:06PM +0200 Subject: Re: [Resin-interest] 3.0.25 Update Hi! From caucho.com, go to Bug Track - Change Log - Search for text 3.0.25 and you should see the changelog. If you're lucky, the mantis bug tracker is up and running, it always isn't :) There are also manually maintained changelogs for each release: For 3.0: http://www.caucho.com/resin-3.0/features/changes.xtp For 3.1: http://www.caucho.com/resin-3.1/changes/changes.xtp -- Sam ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Memory leak in mod_caucho.so
We are using Resin 3.1.4 with Apache 1.3.39. If mod_caucho.so is active in httpd.conf and Resin is running, httpd processes become utilizing more and more RAM (each one getting about and more than 100 Megs for Virtual and Resident memory values). When mod_causho is not active, Apache does not use more than 30 Megs for each of the both RAM numbers. The same behaviour was for Resin 3.1.3. Did anybody else have the same issue? How cant it be fixed? I don't mind debugging mod_causho.so, if I can get described how it can be done. There is a bugtrack entry for this: http://bugs.caucho.com/view.php?id=2249 (fixed for 3.1.5) -- Sam ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] 3.0.25 changes?
What changes are included in resin 3.0.25 since 3.0.24? http://www.caucho.com/resin-3.0/features/changes.xtp jsp: tag-file pageEncoding not properly picked up (#2170) configure.in fix with -lc for linux (#2082) session - always-load-session would load for static pages (#2154) win32: isapi_srun.dll should return 503 on backend disconnect (#2040) win32: isapi_srun.dll config of client-read-time (#2039, #2129) win32: isapi_srun.dll saving of config (#1879) proxy cache: redo cache loading for sync issues (#1992) hessian: issue with class serialization (#198) windows issues with webapps and trailing dot request.getInputStream issues with encodings (#1915) -- Sam ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Small problem with quercus
[ ... ] Any way of sending back a valid Not Found code instead of this? Suppose talking the quercus config out of resin-web.xml and putting it into the webapp would cut things down a bit. Any other way? javax.servlet.ServletException: java.io.FileNotFoundException: /usr/web/default-server/VeohTV/campaignServer.php That issue was fixed in 3.1.2: http://bugs.caucho.com/view.php?id=1952 As a workaround, you can use rewrite-dispatch and not-found to match the requests and send a 404: http://www.caucho.com/resin-3.1/doc/rewrite-tags.xtp#not-found -- Sam ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] 3.0.18-3.0.23 = Increased Network Traffic
Date: Thu, Feb 14, 2008 at 04:19:23PM -0500 Subject: [Resin-interest] 3.0.18-3.0.23 = Increased Network Traffic When we upgraded Resin from 3.0.18 to 3.0.23 last month I see about 3 times as many files being requested in the IIS logs. Specifically 600% more CSS files are being requested 300% more GIF files are being requested 4% fewer struts actions were executed. It appears that files are not being cached by the browser. Other than run setup to update the ISAPI DLL no changes were made to the IIS environment. Does anyone have a clue as to what might be happening ? You can look at the headers of the response to see if the cache headers are different. I prefer using curl for that: $ curl -i http:// | less A alternative is the Firebug plugin for Firefox, it has a Net tab that can be used to look at the headers. You can also enable fine logging on the backend Resin server(s), and you will see the headers that are set on each response, which will allow to determine if the headers are different coming from Resin, or are getting changed when the request passes through IIS. -- Sam ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Resin cluster failure with a single node running out of heap space
We are currently looking at our watchdog process config to see why it did not auto-restart Resin. I think we didn't give enough memory buffer for the watchdog to detect a needed restart, and our app lost responsiveness before the watchdog could restart it. But that's just a theory. The memory low detection happens within the server itself. If the server itself detects that the memory is about to be exhausted, it exits. The watchdog then notices that the server did not exit cleanly, and starts a new server to replace it. -- Sam ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Session cookie in a different path than /
Is there a way to set the session cookie (jsessionid) in a different path than the root (/)? I would like Resin sending the browser something like: Set-Cookie: JSESSIONID=a8_9DJBlfsEf; path=/test but Resin always setÑ Set-Cookie: JSESSIONID=a8_9DJBlfsEf; path=/ We are working in a application served by different AppServer throught a proxy. All the requests are in the same domain but our proxy redirect the request to the correct AppServer discriminating by context-path. So we need the session cookie to be set also per context-path not in root, because if not the AppServer will overwrite the other AppServer cookies. If the concern is that you have app servers other than Resin, you can tell Resin to use a cookie name other than JSESSIONID http://caucho.com/resin/doc/cluster-tags.xtp#session-cookie If you have multiple instances of Resin, they will not have a problem using the cookie value that was established by other servers, as long as reuse-session-id is true (which is the default). reuse-session-id is documented here: http://caucho.com/resin/doc/session-tags.xtp -- Sam ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] admin log already exists after server restart
The first time I start the server, everything works fine. But If I restart it, I get an error: C:\resin-pro-3.1\conf\resin.conf:21: java.sql.SQLException: Table 'log_' already exists. CREATE can not override an existing table. I have added a bug report here: http://bugs.caucho.com/view.php?id=2568 -- Sam ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Memory and slowdown...
It's best practice to set ms and mx (and using -server, which is passed to resin as -J-server as the first parameter) because it tells java to grab the entire needed amount of heap right when it starts. Just to clarify, -J-server is for Resin 3.0, for Resin 3.1 you add a jvm-arg in resin.conf for arguments to pass to the server's JVM: jvm-arg-server/jvm-arg jvm-arg-Xms=.../jvm-arg jvm-arg-Xmx=.../jvm-arg -- Sam ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Quercus + Scripting API memory issue [still present in Quercus 3.1.6]
Date: Tue, Jun 17, 2008 at 10:20:12AM +0200 Subject: [Resin-interest] Quercus + Scripting API memory issue [still present in Quercus 3.1.6] Hi again, I tested Quercus 3.1.6 on Resin 3.1.5, and the memory leak is still there. As I'm not using PHP in production, just as a showcase, and it seems nobody else is affected or cares about the leak, I won't probably be doing further tests. I just wanted to do these last set of tests in case the leak had been fixed in 3.1.6 and that explained the lack of response :). There is a bug report for this issue here: http://bugs.caucho.com/view.php?id=2709 Is there anything wrong in the code above that might cause the leak? Unless the PHP script explicitly instantiates or uses a Java object there should be no possibility of a memory leak from a PHP script. If the script is just using straight PHP then any memory leak is a Quercus bug. It is probably the case that the current implementation of the javax.script api is not properly cleaning things up when the script api is used in the pattern you described. Great report, BTW. -- Sam ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] HttpSession.invalidate() doesn't
I'm using resin-pro-3.0.25 in a three-server cluster with session persistence configured using a MySQL database: persistent-store type=jdbc init data-sourcejdbc/session/data-source always-load / always-save / /init /persistent-store What I'm finding is that you can click logout up to 7 or 8 times before your session actually gets invalidated. The implementation of HttpSessionListener is doing its thing. The logout servlet is doing its thing but from what I can see the req.getSession().invalidate() call is NOT being respected. I believe that problem is addressed in 3.0.26, issue #2485 reported in the change log here: http://www.caucho.com/resin-3.0/features/changes.xtp PS. I am loath to switch (back) to using clustered sessions as I've had issues with random logouts and loads of timeout errors in the logs related to the internal Resin session store. There were a number if cluster store issues reported in the 3.1 branch, but the remaining issues in 3.0 have generally not been reported to us, we found them by doing increased stress testing for the 3.1 release. Take care, -- Sam ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
[Resin-interest] Reserve a http thread for admin connection.
Hi, We are running resin pro version 4.0.15 on a windows machine, using the IIS handler to handle the static files forward the application requests to the resin server listening on port 6800. The thread-max is configured to 1024, during normal loads resin is handling 10 requests concurrently. The problem we are having is: If the requests are getting locked, for example waiting on database queries, the request threads fill up the 1024 thread max, and the application stops responding to clients, including local admin requests. Is there a way to configure resin to reserve a thread for administrative request? possible setup resin to listen on another port that will not be affected by the global thread-max limit? Thanks. -- Sam ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Reserve a http thread for admin connection.
Thanks! On Mon, Dec 5, 2011 at 9:31 AM, Scott Ferguson f...@caucho.com wrote: ** On 12/03/2011 08:11 PM, sam munkes wrote: Hi, We are running resin pro version 4.0.15 on a windows machine, using the IIS handler to handle the static files forward the application requests to the resin server listening on port 6800. The thread-max is configured to 1024, during normal loads resin is handling 10 requests concurrently. The problem we are having is: If the requests are getting locked, for example waiting on database queries, the request threads fill up the 1024 thread max, and the application stops responding to clients, including local admin requests. Is there a way to configure resin to reserve a thread for administrative request? possible setup resin to listen on another port that will not be affected by the global thread-max limit? If Resin listens to another port, it will have dedicated threads attached to it. For a port, the accept-thread-min threads are allocated before the accept() call, so they would avoid the thread-max check. You would need to listen to a different port (or IP), though, because there wouldn't be a way to reserve threads just for certain URLs. -- Scott Thanks. -- Sam ___ resin-interest mailing listresin-interest@caucho.comhttp://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
