Re: [Resin-interest] Limiting access to caucho-status
On Fri, Mar 6, 2009 at 6:12 AM, Ronan Lucio wrote: > I did it. I helped, but caucho-status still answers when accessed via > hostname:resin's port OK, since you are bypassing Apache, try this. A developer here used this method in WEB-INF/resin-web.xml http://caucho.com/ns/resin";> /directory/file.xml 192.168.2.2 192.168.3.3 ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] LDAP Connection Pooling
You probably already found this with a google search, but I'll point it out anyway. Sun describes simple pooling for the JNDI/LDAP stuff: http://java.sun.com/products/jndi/tutorial/ldap/connect/pool.html In addition the Spring framework has their own take on LDAP connection pooling: http://www.springsource.org/ldap Disclaimer: I haven't used any of these. -Knut On Fri, Mar 6, 2009 at 10:04 AM, Matt White wrote: > On Fri, Mar 6, 2009 at 11:48 AM, Scott Ferguson wrote: > > > No, Resin doesn't have LDAP pools. I'm not sure if it's possible. > > Because the LDAP implementations directly hook into javax.naming, > > there's nowhere for Resin to insert itself to pool the connections. > > Thanks Scott! > > Thanks what I needed to know. > > - Matt > > > ___ > 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] LDAP Connection Pooling
On Fri, Mar 6, 2009 at 11:48 AM, Scott Ferguson wrote: > No, Resin doesn't have LDAP pools. I'm not sure if it's possible. > Because the LDAP implementations directly hook into javax.naming, > there's nowhere for Resin to insert itself to pool the connections. Thanks Scott! Thanks what I needed to know. - Matt ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] LDAP Connection Pooling
On Mar 5, 2009, at 6:13 PM, Matt White wrote: > 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. No, Resin doesn't have LDAP pools. I'm not sure if it's possible. Because the LDAP implementations directly hook into javax.naming, there's nowhere for Resin to insert itself to pool the connections. -- Scott > > > Thanks! > > - Matt > > > ___ > 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] [OT] The Resin Linked In group is open for anyone interested in Resin
Those with a Linked In account might find this interesting: http://www.linkedin.com/groupInvitation?gid=132759 ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Limiting access to caucho-status
David, david day escreveu: Is there a way to limit access to "/caucho-status" URL either per IP or per user/password? Have you checked out directive? This works nicely. SetHandler default-handler Order Deny,Allow Deny from all Allow from 192.168. I did it. I helped, but caucho-status still answers when accessed via hostname:resin's port It helps but it isn't 100%. Thanks again, Ronan ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Apache issue
David, david day escreveu: I have a server with apache+resin-3.1.6 installed. Are you running caucho_module? Have you used netstat command during troubleshooting? We had our thread-max fairly high and I was seeing mass quantities of connections to the srun port. Shutting down the JVM would clear the connections, but it could take a long time for the count to drop. Bouncing Apache at the same time had me going quickly. Dropping thread-max helped. Thanks for answering. Well, I did. I'm not an expert in Java Application Servers, so it's possible my answer isn't 100% correct. This issue is really too weird for me. Actually, it seem we have more than one issue. Some times if a only reinit apache it solves the problem, other times not. I do need to restart resin, too. Usually (including times when the problem occurs) netstat doesn't shows a mass quantity of connections. Dropping thread-max took the system more instable. Best number for us seems to be 256. I'm sorry I don't have enough informations about this problem. Perhaps because my inexpertness with Java Application Servers. Thanks, Ronan ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
[Resin-interest] Change Port via web.xml
Hello there! Some weeks ago I rented webspace on a hosted server with JSP-Support - a Resin is running. After enabling JSP-functionality, my websites (html and jsp) were not able to be accessed anymore without appending the port 8080 (e.g. http://myurl.com:8080/index.html, http://myurl.com:8080/test.jsp). Without the port, the only answer was an 500-err. I don't like the fact, that I have to add the port everytime I (or someone else) wants to enter my website. After some correspondence the hoster told me, that I have to edit the web.xml, in which I can map the port 80 to every access. But how? I never found an example of someone doing this, but configuring Resin conf-file (on which I have no access - just my hoster). Any ideas? Greetings, Eric -- View this message in context: http://www.nabble.com/Change-Port-via-web.xml-tp22369236p22369236.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
