[Resin-interest] Load Balancing between resin 3.0.12 and 3.0.26
Hi all We are currently upgrading a project. This project worked with resin 3.0.12 with a class in charge of Load Balancing. This class used a constructor for ClusterClient class from Caucho and some others methods: - openRecycle - getServerList The ClusterClient constructor and the openRecycle method are now protected in resin 3.0.26 and the method getServerList seems to be disappeared. I didn't found any explanation about these modifications. If someone has an idea about this and knows how we can continue to use this class and these methods, his help will be very appreciated. Is there another class to manage load balance with resin 3.0.26 launch as a cluster except com.caucho.servlets.LoadBalanceServlet? Rgds David ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Re sin not picking jars from WEB-INF lib folder
Vidhu, Did you find the solution to your problem. I have the same issue, it is not picking up any of the Jar files in lib directory. Please let me know how you resolved it. Thanks vidhuz wrote: Hi All, There is a strange problem we are encountering while deploying one of our webapp on resin. The problem what it seems is that resin is not able to pick jars present in the WEB-INF lib folder of the deployed web application. Can someone throw some light on why this could happen and the possible remedy/configuration change to be done on our part. It would be great if some can also provide some pointers to how resin classloading process begins, i.e. how. where and in what order resin loads classes and provide it to deployed web app. Any info, or direct link pointing to related information would be utmost appreciated. Thanks in Advance, Vidhu Singhal Tech. Lead. GCS ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest -- View this message in context: http://www.nabble.com/Resin-not-picking-jars-from-WEB-INF-lib-folder-tp20337316p22356827.html 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
Re: [Resin-interest] reverse proxy support like ProxyPass in apache?
Hi, In our case, it is usually enough to use mod_proxy with simply a ProxxPass and ProxyPassReverse directive, forwarding complete directories to the back end. That means we forward all requests to the applications, which reside in another machine in the backend, as they also include styles, images... One could configure some requests to be served directly by Apache, but that would mean we would have to split the applications in two pieces, one to reside in the Apache host, the dynamic one to reside in the application server... and that is something we don't want, due to the number of applications we have to mantain. In any case, in those specific cases where we needed to proxy specific types of requests, we would then use mod_rewrite and then mod_proxy, as the version of Apache we use, for other unrelated reasons, still does not have ProxyPassMatch. So, even if ProxyPassMatch is broken, you could still go back to the good ol' mod_rewrite/mod_proxy combo for those specific needs. S! D. S'està citant david day yaya...@gmail.com: This is a smashing idea, and I feel like an idiot for not seeing it. Unfortunately, ProxyPassMatch is broken in the RPM based RedHat Apache. This is at the same time mod_caucho will not build on any new CentOS or RedHat servers. Is your use of mod_proxy fairly basic, or have you been required to do some imaginative directives with regex? At least with mod_proxy, I can upgrade Apache and utilize ProxyPassMatch where mod_caucho fails under any configuration. I'm not excited about this prospect either, but there is nothing we can do about mod_caucho. You have given me another option out of this problem. David ___ 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] LDAP Connection Pooling
Hello! I have an webapp that we deploy in Resin that does a whole lot of LDAP queries. As the application is written right now each query creates a new connection, performs the query, and then drops the connection. This takes on the order of 300-500ms. We're querying attributes that are indexed, and the queries themselves return results very quickly - it's the connection bring-up and tear down that takes so long. This wasn't much of an issue until we started throwing AJAX-y bits in there that do things like autocomplete fields based on LDAP queries. Obviously, this is the sort of thing that connection pooling was made for. I have started digging looking for examples of how to use LDAP connection pools, and it occurred to me that Resin may have something like this already built in, very similar to JDBC datasources more than once I started implementing something only to realize that Resin already had that functionally built in. I've been searching at the docs feverishly, but I'm not completely sure if I'm understanding what I'm reading. Does Resin have functionally built-in to do high-performance LDAP connection pools? We need to be able to bind to the directory as an authenticated user to perform our searches. Thanks! - Matt ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
