Re: [Resin-interest] Out of PermGen space
On 4/24/2012 5:13 PM, Bill Au wrote: Wow, something I'm actually qualified to talk about on this list! :) Out of PermGen space is almost always caused by a classloader leak which occurs when a webapp is reloaded. It could be caused by either your own code, third-party code, or in some case Java core classes. I debug PermGen errors quite a bit. Some of our apps have a cache of dynamically generated classes (Drools does this) that, if held onto long enough, will make the the JVM run out of PermGen. This isn't really a mistake, it's just how it works, sadly. You need to take heap dumps before and after webapp reload and use a heap analyzer to see what is holding onto the leaked classloader(s). That's how I debug them. Take a series of heap dumps and start comparing the differences between them -- YourKit even makes this easy for you with a tool that diffs heap dumps. - Matt ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
[Resin-interest] Wildcard Servlet Mappings with IIS
Hello! Is there a trick to getting IIS to pass off wildcard servlet mappings off to Resin? I have an application that's deployed on IIS with the ISAPI plugin. If a request comes in for a .jsp page Resin is invoked correctly, but if a request comes in for a URL that's mapped to a servlet with a wildcard mapping (ie /view/4, when the mapping is /view/*), IIS returns a 404. This is easy to do on Apache, but I'm struggling to make it work on IIS. Thanks! - Matt ___ 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
Re: [Resin-interest] Resin's JSTL vs the W3C's HTML Validation Engine
On 10/4/07, Scott Ferguson [EMAIL PROTECTED] wrote: a href=c:url value=someFile.jspc:param name=w value=1/c:param name=h value=2//c:urlClick Me!/a I've added a bug report as http://bugs.caucho.com/view.php?id=2042, but I'll need to check the spec. Thanks Scott. Glad to know I wasn't overlooking something obvious in the documentation. - Matt ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
[Resin-interest] Caucho.com Website Error
Caucho.com seems to be throwing up an error when I attempt to access the Hessian website located at: http://www.caucho.com/hessian/ Could someone please go kick the webserver? :) - Matt ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
