[Resin-interest] mod_caucho filter mapping issue
Hi .. I know this has been posed before but problem similar to item http://maillist.caucho.com/pipermail/resin-interest/2007-October/001703.html . I am using URLrewrite filter to remap old pages to current ones. This works fine in resin standalone mode but I have now setup with apache fronting as i need to setup other sites on the server. I have everything working but this urlrewrite issue as it only uses filter-mappings and not a servlet-mapping. The previous resin-interest article states he managed to solve with a sethandler request. Can anyone elaborate how i could adapt to work with URLrewrite as at the mo i'm just getting 404's from apache.. can i use this sethandler command in the httpd.conf for my virtual host? any suggestions will be greatly appreciated.. _ View your Twitter and Flickr updates from one place – Learn more! http://clk.atdmt.com/UKM/go/137984870/direct/01/___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
[Resin-interest] select() vs poll()
Looks like Solaris has an epoll() alternative via port_create(). http://developers.sun.com/solaris/articles/event_completion.html T ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Classloader issues with Axis and Resin 3.1
Hai Scott, I ran into this problem recently and fixed it by replacing the saaj.jar with the axis-saaj-1.4.jar. This appeared to have no effect on resin (v3.1.8) whatsoever. Was this wise to do? Is it really not used in 3.1.x anymore? Greetz, Ronald On May 28, 2008, at 1:23 AM, Mattias Jiderhamn wrote: Of course, the LinkageError also appears when the application is restarted/reloaded. Reported as a bug at http://bugs.caucho.com/view.php?id=2705 Hmm. Resin shouldn't have any dependencies on saaj any more. I can put saaj back in 3.1 and remove the dependencies in 3.2 -- Scott -- View this message in context: http://www.nabble.com/Classloader-issues-with-Axis-and-Resin-3.1-tp17490804p22600548.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] Still have NullPointerException in ClusterStoreManager of 3.2.1
On Mar 19, 2009, at 2:08 AM, Riccardo Cohen wrote:
I'm testing my application with 3.2.1 (it is still running 3.2.0 in
prod)
The first time I connect to the app after start, I always have the
following error , is it normal ?
resin-pro 3.2.1 / macosx with :
persistent-store type=cluster
init path=session/
/persistent-store
Thanks.
That's somewhat tricky because that code is entirely different in 4.0
and 3.2.1 is really 4.0.0 - 1, so I'm not exactly sure of the right
response.
-- Scott
[10:02:04.499] {http--8000-1} java.lang.NullPointerException
[10:02:04.499] {http--8000-1} at
com
.caucho
.server
.cluster.ClusterStoreManager.accessImpl(ClusterStoreManager.java:947)
[10:02:04.499] {http--8000-1} at
com
.caucho.server.cluster.ClusterObject.objectAccess(ClusterObject.java:
346)
[10:02:04.499] {http--8000-1} at
com.caucho.server.session.SessionImpl.setAccess(SessionImpl.java:890)
[10:02:04.499] {http--8000-1} at
com.caucho.server.session.SessionManager.load(SessionManager.java:
1258)
[10:02:04.499] {http--8000-1} at
com
.caucho.server.session.SessionManager.getSession(SessionManager.java:
1161)
[10:02:04.499] {http--8000-1} at
com
.caucho
.server
.connection
.AbstractHttpRequest.createSession(AbstractHttpRequest.java:1518)
[10:02:04.499] {http--8000-1} at
com
.caucho
.server
.connection.AbstractHttpRequest.getSession(AbstractHttpRequest.java:
1326)
[10:02:04.499] {http--8000-1} at
com
.caucho
.server
.connection
.HttpServletRequestImpl.getSession(HttpServletRequestImpl.java:722)
[10:02:04.499] {http--8000-1} at
_jsp._index__jsp._jspService(_index__jsp.java:30)
[10:02:04.499] {http--8000-1} at
com.caucho.jsp.JavaPage.service(JavaPage.java:61)
[10:02:04.499] {http--8000-1} at
com.caucho.jsp.Page.pageservice(Page.java:580)
[10:02:04.499] {http--8000-1} at
com
.caucho
.server.dispatch.PageFilterChain.doFilter(PageFilterChain.java:195)
[10:02:04.499] {http--8000-1} at
com
.caucho.server.cache.CacheFilterChain.doFilter(CacheFilterChain.java:
201)
[10:02:04.499] {http--8000-1} at
com
.caucho
.server.webapp.WebAppFilterChain.doFilter(WebAppFilterChain.java:189)
[10:02:04.499] {http--8000-1} at
com
.caucho
.server.dispatch.ServletInvocation.service(ServletInvocation.java:266)
[10:02:04.499] {http--8000-1} at
com.caucho.server.http.HttpRequest.handleRequest(HttpRequest.java:292)
[10:02:04.499] {http--8000-1} at
com
.caucho.server.port.TcpConnection.handleRequests(TcpConnection.java:
577)
[10:02:04.499] {http--8000-1} at
com.caucho.server.port.TcpConnection
$AcceptTask.doAccept(TcpConnection.java:1211)
[10:02:04.499] {http--8000-1} at
com.caucho.server.port.TcpConnection
$AcceptTask.run(TcpConnection.java:1152)
[10:02:04.499] {http--8000-1} at
com.caucho.util.ThreadPool$Item.runTasks(ThreadPool.java:759)
[10:02:04.499] {http--8000-1} at
com.caucho.util.ThreadPool$Item.run(ThreadPool.java:681)
[10:02:04.499] {http--8000-1} at java.lang.Thread.run(Thread.java:
613)
--
Riccardo Cohen
Architecte du Logiciel
http://www.architectedulogiciel.fr
+33 (0)6.09.83.64.49
___
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] Still have NullPointerException in ClusterStoreManager of 3.2.1
All right, thanks for the answer. I'll wait for the 4.0 stable :)
Scott Ferguson wrote:
On Mar 19, 2009, at 2:08 AM, Riccardo Cohen wrote:
I'm testing my application with 3.2.1 (it is still running 3.2.0 in
prod)
The first time I connect to the app after start, I always have the
following error , is it normal ?
resin-pro 3.2.1 / macosx with :
persistent-store type=cluster
init path=session/
/persistent-store
Thanks.
That's somewhat tricky because that code is entirely different in 4.0
and 3.2.1 is really 4.0.0 - 1, so I'm not exactly sure of the right
response.
-- Scott
[10:02:04.499] {http--8000-1} java.lang.NullPointerException
[10:02:04.499] {http--8000-1}at
com
.caucho
.server
.cluster.ClusterStoreManager.accessImpl(ClusterStoreManager.java:947)
[10:02:04.499] {http--8000-1}at
com
.caucho.server.cluster.ClusterObject.objectAccess(ClusterObject.java:
346)
[10:02:04.499] {http--8000-1}at
com.caucho.server.session.SessionImpl.setAccess(SessionImpl.java:890)
[10:02:04.499] {http--8000-1}at
com.caucho.server.session.SessionManager.load(SessionManager.java:
1258)
[10:02:04.499] {http--8000-1}at
com
.caucho.server.session.SessionManager.getSession(SessionManager.java:
1161)
[10:02:04.499] {http--8000-1}at
com
.caucho
.server
.connection
.AbstractHttpRequest.createSession(AbstractHttpRequest.java:1518)
[10:02:04.499] {http--8000-1}at
com
.caucho
.server
.connection.AbstractHttpRequest.getSession(AbstractHttpRequest.java:
1326)
[10:02:04.499] {http--8000-1}at
com
.caucho
.server
.connection
.HttpServletRequestImpl.getSession(HttpServletRequestImpl.java:722)
[10:02:04.499] {http--8000-1}at
_jsp._index__jsp._jspService(_index__jsp.java:30)
[10:02:04.499] {http--8000-1}at
com.caucho.jsp.JavaPage.service(JavaPage.java:61)
[10:02:04.499] {http--8000-1}at
com.caucho.jsp.Page.pageservice(Page.java:580)
[10:02:04.499] {http--8000-1}at
com
.caucho
.server.dispatch.PageFilterChain.doFilter(PageFilterChain.java:195)
[10:02:04.499] {http--8000-1}at
com
.caucho.server.cache.CacheFilterChain.doFilter(CacheFilterChain.java:
201)
[10:02:04.499] {http--8000-1}at
com
.caucho
.server.webapp.WebAppFilterChain.doFilter(WebAppFilterChain.java:189)
[10:02:04.499] {http--8000-1}at
com
.caucho
.server.dispatch.ServletInvocation.service(ServletInvocation.java:266)
[10:02:04.499] {http--8000-1}at
com.caucho.server.http.HttpRequest.handleRequest(HttpRequest.java:292)
[10:02:04.499] {http--8000-1}at
com
.caucho.server.port.TcpConnection.handleRequests(TcpConnection.java:
577)
[10:02:04.499] {http--8000-1}at
com.caucho.server.port.TcpConnection
$AcceptTask.doAccept(TcpConnection.java:1211)
[10:02:04.499] {http--8000-1}at
com.caucho.server.port.TcpConnection
$AcceptTask.run(TcpConnection.java:1152)
[10:02:04.499] {http--8000-1}at
com.caucho.util.ThreadPool$Item.runTasks(ThreadPool.java:759)
[10:02:04.499] {http--8000-1}at
com.caucho.util.ThreadPool$Item.run(ThreadPool.java:681)
[10:02:04.499] {http--8000-1}at java.lang.Thread.run(Thread.java:
613)
--
Riccardo Cohen
Architecte du Logiciel
http://www.architectedulogiciel.fr
+33 (0)6.09.83.64.49
___
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
--
Riccardo Cohen
Architecte du Logiciel
http://www.architectedulogiciel.fr
+33 (0)6.09.83.64.49
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Remote programmatic authentication
Answering my own question #1, I found the HessionProxyFactory.setUser() and setPassword() methods. Great. #2 is still a mystery to me. I'm in a servlet, how do I programmatically tell the container to log me in with a username and password? Thanks, Jeff On Thu, Mar 19, 2009 at 2:08 PM, Jeff Schnitzer j...@infohazard.org wrote: First of all, I'd just like to say wow, I'm happy to re-discover Resin - I recall using it briefly in 2002 and I'm impressed with what you've been doing since. It's a sharp contrast to the progress of JBoss, which has sadly become a complete wreck in the last few years. The web beans stuff is fantastic and you're way ahead of the game. I've read most of the docs now and I'm a bit confused about how you authenticate to the container in two different scenarios: #1) A remote caller using hessian, either from another Resin instance (using DI) or from a standalone client. I presume at a protocol level this involves basic or digest auth, but I don't see the API hooks. #2) Within the container, how do you authenticate programmatically? Ie, not using login forms or basic auth. This is the common case of a signup form; after the user has filled out their chosen username and password I want to authenticate them to the container without forcing them to re-enter the credentials. Thanks, Jeff ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Remote programmatic authentication
#2 is still a mystery to me. I'm in a servlet, how do I programmatically tell the container to log me in with a username and password? This page has a good overview of how to do it: http://www.informit.com/articles/article.aspx?p=24253seqNum=7 So you set up your security constraints in your resin.xml and reference a custom authenticator inside the login-config. The create your custom authenticator by AbstractAuthenticator. Note the code in the example is referencing: com.caucho.server.http.AbstractAuthenticator but I think you want to extend com.caucho.server.AbstractAuthenticator instead, as I think the .http. version is deprecated. - Aaron ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Remote programmatic authentication
Thanks, but that is not what I'm looking for. The document describes building an authentication source and using automatic authentication (aka web.xml security constraints). The problem is, j2ee automatic authentication is nearly useless. It doesn't allow for autologin cookies nor does it allow me to sign up new users - they would have to then log in again. It blows my mind that a decade later the servlet spec hasn't addressed these simple needs. I need a way, in my web app, to programmatically say to the container authenticate as this user/pass. Then these credentials will be used for further calls into the EJB tier or for responding to HttpServletRequest.isUserInRole() calls. Of course at the SPI level these will end up calling into my Resin Authenticator. This is a pretty common problem, there must be a Resin way to do it. In JBoss5, it looks like this: SecurityClient securityClient = SecurityClientFactory.getSecurityClient(); securityClient.setSimple(user, password); securityClient.login(); Thanks, Jeff On Thu, Mar 19, 2009 at 7:38 PM, Aaron Freeman aaron.free...@layerz.com wrote: #2 is still a mystery to me. I'm in a servlet, how do I programmatically tell the container to log me in with a username and password? This page has a good overview of how to do it: http://www.informit.com/articles/article.aspx?p=24253seqNum=7 So you set up your security constraints in your resin.xml and reference a custom authenticator inside the login-config. The create your custom authenticator by AbstractAuthenticator. Note the code in the example is referencing: com.caucho.server.http.AbstractAuthenticator but I think you want to extend com.caucho.server.AbstractAuthenticator instead, as I think the .http. version is deprecated. - Aaron ___ 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] Remote programmatic authentication
I need a way, in my web app, to programmatically say to the container authenticate as this user/pass. Then these credentials will be used for further calls into the EJB tier or for responding to HttpServletRequest.isUserInRole() calls. Of course at the SPI level these will end up calling into my Resin Authenticator. Ah, well I haven't used it before but there is a JdbcAuthenticator that has a cookie-auth-query and cookie-auth-update to let you automatically log someone in using a persistent cookie. It's still not what you are describing below, but may suffice to solve automatic logins if that's the end goal. Here is a link to some details on the JdbcAuthenticator: https://www.gopay.com.cn/resin-doc/security/authentication.xtp That link might be out of date though, depending on which version of Resin you are using. Sorry if this is still on the wrong track .. I'll let the gurus give you the answer. - Aaron This is a pretty common problem, there must be a Resin way to do it. In JBoss5, it looks like this: SecurityClient securityClient = SecurityClientFactory.getSecurityClient(); securityClient.setSimple(user, password); securityClient.login(); Thanks, Jeff On Thu, Mar 19, 2009 at 7:38 PM, Aaron Freeman aaron.free...@layerz.com wrote: #2 is still a mystery to me. I'm in a servlet, how do I programmatically tell the container to log me in with a username and password? This page has a good overview of how to do it: http://www.informit.com/articles/article.aspx?p=24253seqNum=7 So you set up your security constraints in your resin.xml and reference a custom authenticator inside the login-config. The create your custom authenticator by AbstractAuthenticator. Note the code in the example is referencing: com.caucho.server.http.AbstractAuthenticator but I think you want to extend com.caucho.server.AbstractAuthenticator instead, as I think the .http. version is deprecated. - Aaron ___ 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
