Re: [Resin-interest] Resin V Glassfish
Hi, From my personal point of view, I prefer Resin because its philosophy suits me better as it is more open and flexible, meaning it usually accomodates different ways of doing things. OTOH, GlassFish is for me more opinionated and it tries to guide you on how you should do things, so if you deviate from the norm you are usually on your own with scarce documentation and no support because nobody tried that. Similarly, Resin's community of users is smaller but they are usually more hardcore and knowledgeable, as they have to survive Resin's documentation ;) and have to choose their own path from the multiple ones allowed by Resin, but GlassFish is more popular which makes it easier for newcomers to start with, as they have more basic guides, it integrates transparently with IDES (meaning they don't have to have a clue about what's going on) etc. With that I don't want to imply that users of one server are better/smarter/whatever than users of the other, just that I think they are geared towards different markets, with both its benefits and drawbacks. S! D. Wesley Wu escribió: Yes, congratulations to Gavin King. Competition is a good thing. I think Scott will produce products with less bugs or we'll change to Weld :) 2009/11/28 Kai Virkki kai.vir...@gmail.com mailto:kai.vir...@gmail.com Well, JBoss already has a CDI implementation called Weld, so Resin really isn't exceptional in this account. CDI is actually based on JBoss Seam and Google Guice. Cheers, -Kai On 27.11.2009, at 12.10, Wesley Wu wumen...@gmail.com mailto:wumen...@gmail.com wrote: As long as Scott continue to work for the Resin's future I'll never switch to other platform. I loved the WebBeans so much from December 2007, now called CDI. I don't think other vendors could produce a competitive implementation of CDI versus Resin, in at least next 12 months. They have to throw in lots of labor and money to keep up with the more than two years hard work of Scott and his stuff. The forthcoming failure of OpenJPA is an example, which can nowhere compete with Hibernate EclipseLink in every aspect. -Wesley ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Multi-Part request error when using HmuxRequest in Resin 4.0.2(GA)
Without this bug fixed, 4.0.2 can't be used in production environment. I use two machines with two resin as a load balance cluster, one with a web-tier and a app-tier the other only a app-tier. Every file upload block it. 2009/11/30 Wesley Wu wumen...@gmail.com This bug should be marked as block because it prevents resin load-balancer and third-party web server integration from working properly. It seems caucho QA team did not pay much attention to Hmux stuff, because I suffered a lot from it... -Wesley 2009/11/29 Alex a...@caucho.com Multi-Part request error when using HmuxRequest. Thanks Wesley, I reported a bug: http://bugs.caucho.com/view.php?id=3790 Alex My resin 4.0.2 was behind an apache 2.1.x using CauchoRequest to forward all request for a virtual host to resin. If I use 8080 port without apache, everything goes fine. 2009-11-28 13:14:28.916 ERROR [server-127.0.0.1:6800-5] c.b.c.s.MultiPartRequest (103) - Unable to parse request org.apache.commons.fileupload.FileUploadBase$IOFileUploadException: Processing of multipart/form-data request failed. Stream ended unexpectedly at org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.java:367) [FileUploadBase.class:1.2.1] at com.buysou.cms.servlet.JakartaMultiPartRequest.parse(JakartaMultiPartRequest.java:61) [classes:na] at com.buysou.cms.servlet.MultiPartRequestWrapper.init(MultiPartRequestWrapper.java:47) [classes:na] at com.buysou.cms.servlet.CmsPageFilter.wrapRequest(CmsPageFilter.java:268) [classes:na] at com.buysou.cms.servlet.CmsPageFilter.doFilter(CmsPageFilter.java:138) [classes:na] at com.caucho.server.dispatch.FilterFilterChain.doFilter(FilterFilterChain.java:88) [resin.jar:4.0.2] at com.buysou.servlet.filters.encoding.EnhancedEncodingFilter.doFilter(EnhancedEncodingFilter.java:85) [classes:na] at com.caucho.server.dispatch.FilterFilterChain.doFilter(FilterFilterChain.java:88) [resin.jar:4.0.2] at com.caucho.server.webapp.WebAppFilterChain.doFilter(WebAppFilterChain.java:183) [resin.jar:4.0.2] at com.caucho.server.cache.CacheFilterChain.doFilter(CacheFilterChain.java:169) [pro.jar:4.0.2] at com.caucho.server.webapp.AccessLogFilterChain.doFilter(AccessLogFilterChain.java:103) [resin.jar:4.0.2] at com.caucho.server.dispatch.ServletInvocation.service(ServletInvocation.java:290) [resin.jar:4.0.2] at com.caucho.server.hmux.HmuxRequest.handleInvocation(HmuxRequest.java:475) [resin.jar:4.0.2] at com.caucho.server.hmux.HmuxRequest.handleRequestImpl(HmuxRequest.java:394) [resin.jar:4.0.2] at com.caucho.server.hmux.HmuxRequest.handleRequest(HmuxRequest.java:357) [resin.jar:4.0.2] at com.caucho.server.port.TcpConnection.handleRequestsImpl(TcpConnection.java:619) [resin.jar:4.0.2] at com.caucho.server.port.TcpConnection.handleRequests(TcpConnection.java:556) [resin.jar:4.0.2] at com.caucho.server.port.TcpConnection$AcceptTask.doTask(TcpConnection.java:1194) [resin.jar:4.0.2] at com.caucho.server.port.TcpConnection$ConnectionReadTask.runThread(TcpConnection.java:1127) [resin.jar:4.0.2] at com.caucho.server.port.TcpConnection$AcceptTask.run(TcpConnection.java:1158) [resin.jar:4.0.2] at com.caucho.util.ThreadPool$PoolThread.runTasks(ThreadPool.java:901) [resin.jar:4.0.2] at com.caucho.util.ThreadPool$PoolThread.run(ThreadPool.java:866) [resin.jar:4.0.2] Caused by: org.apache.commons.fileupload.MultipartStream$MalformedStreamException: Stream ended unexpectedly at org.apache.commons.fileupload.MultipartStream$ItemInputStream.makeAvailable(MultipartStream.java:983) [MultipartStream$ItemInputStream.class:1.2.1] at org.apache.commons.fileupload.MultipartStream$ItemInputStream.read(MultipartStream.java:887) [MultipartStream$ItemInputStream.class:1.2.1] at java.io.InputStream.read(InputStream.java:85) [na:1.6.0_14] at org.apache.commons.fileupload.util.Streams.copy(Streams.java:94) [Streams.class:1.2.1] at org.apache.commons.fileupload.util.Streams.copy(Streams.java:64) [Streams.class:1.2.1] at org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.java:362) [FileUploadBase.class:1.2.1] ... 21 common frames omitted ___ 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] Resin 3.1: resin:import of jvm-args
I have a situation where different servers should have different jvm-args, but I would like to have a single resin.xml. I tried doing a resin:import on a jvm.xml file that has just jvm-args in it, but I haven't found a combination that works. I have tried surrounding the jvm-arg tags like this: Try1: server ...jvm-args.. /server Try 2: server-default...jvm-args../server-default Try 3: server server-default...jvm-args../server-default /server Try 4: cluster server-default...jvm-args../server-default /cluster None of these are working. Any thoughts? Thanks, Aaron ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Multi-Part request error when using HmuxRequest in Resin 4.0.2(GA)
Resin 4.x is a development version, so it's not supposed to be used in a production environment anyway :) Cheers, Kai 2009/11/30 Wesley Wu wumen...@gmail.com: Without this bug fixed, 4.0.2 can't be used in production environment. I use two machines with two resin as a load balance cluster, one with a web-tier and a app-tier the other only a app-tier. Every file upload block it. 2009/11/30 Wesley Wu wumen...@gmail.com This bug should be marked as block because it prevents resin load-balancer and third-party web server integration from working properly. It seems caucho QA team did not pay much attention to Hmux stuff, because I suffered a lot from it... -Wesley 2009/11/29 Alex a...@caucho.com Multi-Part request error when using HmuxRequest. Thanks Wesley, I reported a bug: http://bugs.caucho.com/view.php?id=3790 Alex My resin 4.0.2 was behind an apache 2.1.x using CauchoRequest to forward all request for a virtual host to resin. If I use 8080 port without apache, everything goes fine. 2009-11-28 13:14:28.916 ERROR [server-127.0.0.1:6800-5] c.b.c.s.MultiPartRequest (103) - Unable to parse request org.apache.commons.fileupload.FileUploadBase$IOFileUploadException: Processing of multipart/form-data request failed. Stream ended unexpectedly at org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.java:367) [FileUploadBase.class:1.2.1] at com.buysou.cms.servlet.JakartaMultiPartRequest.parse(JakartaMultiPartRequest.java:61) [classes:na] at com.buysou.cms.servlet.MultiPartRequestWrapper.init(MultiPartRequestWrapper.java:47) [classes:na] at com.buysou.cms.servlet.CmsPageFilter.wrapRequest(CmsPageFilter.java:268) [classes:na] at com.buysou.cms.servlet.CmsPageFilter.doFilter(CmsPageFilter.java:138) [classes:na] at com.caucho.server.dispatch.FilterFilterChain.doFilter(FilterFilterChain.java:88) [resin.jar:4.0.2] at com.buysou.servlet.filters.encoding.EnhancedEncodingFilter.doFilter(EnhancedEncodingFilter.java:85) [classes:na] at com.caucho.server.dispatch.FilterFilterChain.doFilter(FilterFilterChain.java:88) [resin.jar:4.0.2] at com.caucho.server.webapp.WebAppFilterChain.doFilter(WebAppFilterChain.java:183) [resin.jar:4.0.2] at com.caucho.server.cache.CacheFilterChain.doFilter(CacheFilterChain.java:169) [pro.jar:4.0.2] at com.caucho.server.webapp.AccessLogFilterChain.doFilter(AccessLogFilterChain.java:103) [resin.jar:4.0.2] at com.caucho.server.dispatch.ServletInvocation.service(ServletInvocation.java:290) [resin.jar:4.0.2] at com.caucho.server.hmux.HmuxRequest.handleInvocation(HmuxRequest.java:475) [resin.jar:4.0.2] at com.caucho.server.hmux.HmuxRequest.handleRequestImpl(HmuxRequest.java:394) [resin.jar:4.0.2] at com.caucho.server.hmux.HmuxRequest.handleRequest(HmuxRequest.java:357) [resin.jar:4.0.2] at com.caucho.server.port.TcpConnection.handleRequestsImpl(TcpConnection.java:619) [resin.jar:4.0.2] at com.caucho.server.port.TcpConnection.handleRequests(TcpConnection.java:556) [resin.jar:4.0.2] at com.caucho.server.port.TcpConnection$AcceptTask.doTask(TcpConnection.java:1194) [resin.jar:4.0.2] at com.caucho.server.port.TcpConnection$ConnectionReadTask.runThread(TcpConnection.java:1127) [resin.jar:4.0.2] at com.caucho.server.port.TcpConnection$AcceptTask.run(TcpConnection.java:1158) [resin.jar:4.0.2] at com.caucho.util.ThreadPool$PoolThread.runTasks(ThreadPool.java:901) [resin.jar:4.0.2] at com.caucho.util.ThreadPool$PoolThread.run(ThreadPool.java:866) [resin.jar:4.0.2] Caused by: org.apache.commons.fileupload.MultipartStream$MalformedStreamException: Stream ended unexpectedly at org.apache.commons.fileupload.MultipartStream$ItemInputStream.makeAvailable(MultipartStream.java:983) [MultipartStream$ItemInputStream.class:1.2.1] at org.apache.commons.fileupload.MultipartStream$ItemInputStream.read(MultipartStream.java:887) [MultipartStream$ItemInputStream.class:1.2.1] at java.io.InputStream.read(InputStream.java:85) [na:1.6.0_14] at org.apache.commons.fileupload.util.Streams.copy(Streams.java:94) [Streams.class:1.2.1] at org.apache.commons.fileupload.util.Streams.copy(Streams.java:64) [Streams.class:1.2.1] at org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.java:362) [FileUploadBase.class:1.2.1] ... 21 common frames omitted ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com
Re: [Resin-interest] Multi-Part request error when using HmuxRequest in Resin 4.0.2(GA)
Kai Virkki wrote: Resin 4.x is a development version, so it's not supposed to be used in a production environment anyway :) The intent of 4.0.2 was to bring the quality up to be production worthy, so this is a significant issue. It looks like we'll be releasing a 4.0.3 earlier than planned to take care of these issue. -- Scott Cheers, Kai 2009/11/30 Wesley Wu wumen...@gmail.com: Without this bug fixed, 4.0.2 can't be used in production environment. I use two machines with two resin as a load balance cluster, one with a web-tier and a app-tier the other only a app-tier. Every file upload block it. 2009/11/30 Wesley Wu wumen...@gmail.com This bug should be marked as block because it prevents resin load-balancer and third-party web server integration from working properly. It seems caucho QA team did not pay much attention to Hmux stuff, because I suffered a lot from it... -Wesley 2009/11/29 Alex a...@caucho.com Multi-Part request error when using HmuxRequest. Thanks Wesley, I reported a bug: http://bugs.caucho.com/view.php?id=3790 Alex My resin 4.0.2 was behind an apache 2.1.x using CauchoRequest to forward all request for a virtual host to resin. If I use 8080 port without apache, everything goes fine. 2009-11-28 13:14:28.916 ERROR [server-127.0.0.1:6800-5] c.b.c.s.MultiPartRequest (103) - Unable to parse request org.apache.commons.fileupload.FileUploadBase$IOFileUploadException: Processing of multipart/form-data request failed. Stream ended unexpectedly at org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.java:367) [FileUploadBase.class:1.2.1] at com.buysou.cms.servlet.JakartaMultiPartRequest.parse(JakartaMultiPartRequest.java:61) [classes:na] at com.buysou.cms.servlet.MultiPartRequestWrapper.init(MultiPartRequestWrapper.java:47) [classes:na] at com.buysou.cms.servlet.CmsPageFilter.wrapRequest(CmsPageFilter.java:268) [classes:na] at com.buysou.cms.servlet.CmsPageFilter.doFilter(CmsPageFilter.java:138) [classes:na] at com.caucho.server.dispatch.FilterFilterChain.doFilter(FilterFilterChain.java:88) [resin.jar:4.0.2] at com.buysou.servlet.filters.encoding.EnhancedEncodingFilter.doFilter(EnhancedEncodingFilter.java:85) [classes:na] at com.caucho.server.dispatch.FilterFilterChain.doFilter(FilterFilterChain.java:88) [resin.jar:4.0.2] at com.caucho.server.webapp.WebAppFilterChain.doFilter(WebAppFilterChain.java:183) [resin.jar:4.0.2] at com.caucho.server.cache.CacheFilterChain.doFilter(CacheFilterChain.java:169) [pro.jar:4.0.2] at com.caucho.server.webapp.AccessLogFilterChain.doFilter(AccessLogFilterChain.java:103) [resin.jar:4.0.2] at com.caucho.server.dispatch.ServletInvocation.service(ServletInvocation.java:290) [resin.jar:4.0.2] at com.caucho.server.hmux.HmuxRequest.handleInvocation(HmuxRequest.java:475) [resin.jar:4.0.2] at com.caucho.server.hmux.HmuxRequest.handleRequestImpl(HmuxRequest.java:394) [resin.jar:4.0.2] at com.caucho.server.hmux.HmuxRequest.handleRequest(HmuxRequest.java:357) [resin.jar:4.0.2] at com.caucho.server.port.TcpConnection.handleRequestsImpl(TcpConnection.java:619) [resin.jar:4.0.2] at com.caucho.server.port.TcpConnection.handleRequests(TcpConnection.java:556) [resin.jar:4.0.2] at com.caucho.server.port.TcpConnection$AcceptTask.doTask(TcpConnection.java:1194) [resin.jar:4.0.2] at com.caucho.server.port.TcpConnection$ConnectionReadTask.runThread(TcpConnection.java:1127) [resin.jar:4.0.2] at com.caucho.server.port.TcpConnection$AcceptTask.run(TcpConnection.java:1158) [resin.jar:4.0.2] at com.caucho.util.ThreadPool$PoolThread.runTasks(ThreadPool.java:901) [resin.jar:4.0.2] at com.caucho.util.ThreadPool$PoolThread.run(ThreadPool.java:866) [resin.jar:4.0.2] Caused by: org.apache.commons.fileupload.MultipartStream$MalformedStreamException: Stream ended unexpectedly at org.apache.commons.fileupload.MultipartStream$ItemInputStream.makeAvailable(MultipartStream.java:983) [MultipartStream$ItemInputStream.class:1.2.1] at org.apache.commons.fileupload.MultipartStream$ItemInputStream.read(MultipartStream.java:887) [MultipartStream$ItemInputStream.class:1.2.1] at java.io.InputStream.read(InputStream.java:85) [na:1.6.0_14] at org.apache.commons.fileupload.util.Streams.copy(Streams.java:94) [Streams.class:1.2.1] at org.apache.commons.fileupload.util.Streams.copy(Streams.java:64) [Streams.class:1.2.1] at org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.java:362) [FileUploadBase.class:1.2.1] ... 21 common frames omitted ___ resin-interest mailing list resin-interest@caucho.com
Re: [Resin-interest] Multi-Part request error when using HmuxRequest in Resin 4.0.2(GA)
Wesley Wu wrote: Without this bug fixed, 4.0.2 can't be used in production environment. I use two machines with two resin as a load balance cluster, one with a web-tier and a app-tier the other only a app-tier. Can you turn on finer logging for both machines and send the protocol part of the logs? I can't reproduce the issue here; posts are going through fine. So there must be some difference in the request or the reading that's triggering the problem. -- Scott Every file upload block it. 2009/11/30 Wesley Wu wumen...@gmail.com This bug should be marked as block because it prevents resin load-balancer and third-party web server integration from working properly. It seems caucho QA team did not pay much attention to Hmux stuff, because I suffered a lot from it... -Wesley 2009/11/29 Alex a...@caucho.com Multi-Part request error when using HmuxRequest. Thanks Wesley, I reported a bug: http://bugs.caucho.com/view.php?id=3790 Alex My resin 4.0.2 was behind an apache 2.1.x using CauchoRequest to forward all request for a virtual host to resin. If I use 8080 port without apache, everything goes fine. 2009-11-28 13:14:28.916 ERROR [server-127.0.0.1:6800-5] c.b.c.s.MultiPartRequest (103) - Unable to parse request org.apache.commons.fileupload.FileUploadBase$IOFileUploadException: Processing of multipart/form-data request failed. Stream ended unexpectedly at org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.java:367) [FileUploadBase.class:1.2.1] at com.buysou.cms.servlet.JakartaMultiPartRequest.parse(JakartaMultiPartRequest.java:61) [classes:na] at com.buysou.cms.servlet.MultiPartRequestWrapper.init(MultiPartRequestWrapper.java:47) [classes:na] at com.buysou.cms.servlet.CmsPageFilter.wrapRequest(CmsPageFilter.java:268) [classes:na] at com.buysou.cms.servlet.CmsPageFilter.doFilter(CmsPageFilter.java:138) [classes:na] at com.caucho.server.dispatch.FilterFilterChain.doFilter(FilterFilterChain.java:88) [resin.jar:4.0.2] at com.buysou.servlet.filters.encoding.EnhancedEncodingFilter.doFilter(EnhancedEncodingFilter.java:85) [classes:na] at com.caucho.server.dispatch.FilterFilterChain.doFilter(FilterFilterChain.java:88) [resin.jar:4.0.2] at com.caucho.server.webapp.WebAppFilterChain.doFilter(WebAppFilterChain.java:183) [resin.jar:4.0.2] at com.caucho.server.cache.CacheFilterChain.doFilter(CacheFilterChain.java:169) [pro.jar:4.0.2] at com.caucho.server.webapp.AccessLogFilterChain.doFilter(AccessLogFilterChain.java:103) [resin.jar:4.0.2] at com.caucho.server.dispatch.ServletInvocation.service(ServletInvocation.java:290) [resin.jar:4.0.2] at com.caucho.server.hmux.HmuxRequest.handleInvocation(HmuxRequest.java:475) [resin.jar:4.0.2] at com.caucho.server.hmux.HmuxRequest.handleRequestImpl(HmuxRequest.java:394) [resin.jar:4.0.2] at com.caucho.server.hmux.HmuxRequest.handleRequest(HmuxRequest.java:357) [resin.jar:4.0.2] at com.caucho.server.port.TcpConnection.handleRequestsImpl(TcpConnection.java:619) [resin.jar:4.0.2] at com.caucho.server.port.TcpConnection.handleRequests(TcpConnection.java:556) [resin.jar:4.0.2] at com.caucho.server.port.TcpConnection$AcceptTask.doTask(TcpConnection.java:1194) [resin.jar:4.0.2] at com.caucho.server.port.TcpConnection$ConnectionReadTask.runThread(TcpConnection.java:1127) [resin.jar:4.0.2] at com.caucho.server.port.TcpConnection$AcceptTask.run(TcpConnection.java:1158) [resin.jar:4.0.2] at com.caucho.util.ThreadPool$PoolThread.runTasks(ThreadPool.java:901) [resin.jar:4.0.2] at com.caucho.util.ThreadPool$PoolThread.run(ThreadPool.java:866) [resin.jar:4.0.2] Caused by: org.apache.commons.fileupload.MultipartStream$MalformedStreamException: Stream ended unexpectedly at org.apache.commons.fileupload.MultipartStream$ItemInputStream.makeAvailable(MultipartStream.java:983) [MultipartStream$ItemInputStream.class:1.2.1] at org.apache.commons.fileupload.MultipartStream$ItemInputStream.read(MultipartStream.java:887) [MultipartStream$ItemInputStream.class:1.2.1] at java.io.InputStream.read(InputStream.java:85) [na:1.6.0_14] at org.apache.commons.fileupload.util.Streams.copy(Streams.java:94) [Streams.class:1.2.1] at org.apache.commons.fileupload.util.Streams.copy(Streams.java:64) [Streams.class:1.2.1] at org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.java:362) [FileUploadBase.class:1.2.1] ... 21 common frames omitted ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list
Re: [Resin-interest] Multi-Part request error when using HmuxRequest in Resin 4.0.2(GA)
Scott Ferguson wrote: Wesley Wu wrote: Without this bug fixed, 4.0.2 can't be used in production environment. I use two machines with two resin as a load balance cluster, one with a web-tier and a app-tier the other only a app-tier. Can you turn on finer logging for both machines and send the protocol part of the logs? I can't reproduce the issue here; posts are going through fine. So there must be some difference in the request or the reading that's triggering the problem. Nevermind. I found it. -- Scott ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Resin 3.1: resin:import of jvm-args
I have a situation where different servers should have different jvm-args, but I would like to have a single resin.xml. You should be able to achieve this by using jvm-arg inside the server server id=a address=127.0.0.1 port=6800 jvm-arg-Dserver=A/jvm-arg /server server id=b address=127.0.0.1 port=6801 jvm-arg-Dserver=B/jvm-arg /server Regards, Alex I tried doing a resin:import on a jvm.xml file that has just jvm-args in it, but I haven't found a combination that works. I have tried surrounding the jvm-arg tags like this: Try1: server ...jvm-args.. /server Try 2: server-default...jvm-args../server-default Try 3: server server-default...jvm-args../server-default /server Try 4: cluster server-default...jvm-args../server-default /cluster None of these are working. Any thoughts? Thanks, 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] 3.1.9 - Database Session Clustering Problem
Hi everyone, I'm seeing some strange behavior on Resin 3.1.9 with database session clustering. I have two app servers in the cluster. If I take one of the servers down. I see in the database all the data for the server's sessions cleared. The sessions remain in the database just without any data except for I'm guessing an identification value like - 0xACED00057704. Is there a reason why this happens? I'm not using always-load or always save attributes. Any help would be appreciated. Cheers, Matt. Matt Garner Senior Java Developer --- mgar...@limehousesoftware.co.uk Limehouse Software Ltd DDI: 01628 640 451 Main: 01628 640 401 Fax: 01628 640 461 Limehouse Software Ltd St Cloud Gate St Cloud Way Cookham Road Maidenhead, Berks SL6 8XD www.limehousesoftware.co.uk - Unifying Information Limehouse Software Limited - An Objective Company The information contained in this e-mail or in any attachments is confidential and is intended solely for the named addressee only. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Limehouse Software Ltd immediately by returning this e-mail to sender or calling 01628 640 401 and do not read, use or disseminate the information. Opinions expressed in this e-mail are those of the sender and not necessarily the company. Although an active anti-virus policy is operated, the company accepts no liability for any damage caused by any virus transmitted by this e-mail, including any attachments.___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Multi-Part request error when using HmuxRequest in Resin 4.0.2(GA)
Thanks, Scott. You rocks. We're planning a launch of a new version of my website on December 18. All codes in this new version rely on JSR 299 (hopefully I'll see the final ballot today). So it's a bit emergency for me to solve this problem. I'll be happy if 4.0.3 will be ready by then, but a snapshot with fixes will be ok. Or I'll have to switch back to the 4.0.2 snapshot 091013 (which has performance/logging issue and JPA issues). 2009/12/1 Scott Ferguson f...@caucho.com: Scott Ferguson wrote: Wesley Wu wrote: Without this bug fixed, 4.0.2 can't be used in production environment. I use two machines with two resin as a load balance cluster, one with a web-tier and a app-tier the other only a app-tier. Can you turn on finer logging for both machines and send the protocol part of the logs? I can't reproduce the issue here; posts are going through fine. So there must be some difference in the request or the reading that's triggering the problem. Nevermind. I found it. -- Scott ___ 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] Resin 3.1: resin:import of jvm-args
I have a situation where different servers should have different jvm-args, but I would like to have a single resin.xml. You should be able to achieve this by using jvm-arg inside the server server id=a address=127.0.0.1 port=6800 jvm-arg-Dserver=A/jvm-arg /server server id=b address=127.0.0.1 port=6801 jvm-arg-Dserver=B/jvm-arg /server Regards, Alex Hmm, that's exactly what I tried first, as mentioned below. Can you have jvm-arg inside a resin:import'ed file? Aaron I tried doing a resin:import on a jvm.xml file that has just jvm-args in it, but I haven't found a combination that works. I have tried surrounding the jvm-arg tags like this: Try1: server ...jvm-args.. /server Try 2: server-default...jvm-args../server-default Try 3: server server-default...jvm-args../server-default /server Try 4: cluster server-default...jvm-args../server-default /cluster None of these are working. Any thoughts? Thanks, Aaron ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Resin 3.1: resin:import of jvm-args
You should be able to achieve this by using jvm-arg inside the server server id=a address=127.0.0.1 port=6800 jvm-arg-Dserver=A/jvm-arg /server server id=b address=127.0.0.1 port=6801 jvm-arg-Dserver=B/jvm-arg /server Regards, Alex Hmm, that's exactly what I tried first, as mentioned below. Did it work for you? What version of Resin 3.1 did you try it with if it did not work? Can you have jvm-arg inside a resin:import'ed file? Nope, the server does not allow resin:import tag. Alex Aaron I tried doing a resin:import on a jvm.xml file that has just jvm-args in it, but I haven't found a combination that works. I have tried surrounding the jvm-arg tags like this: Try1: server ...jvm-args.. /server Try 2: server-default...jvm-args../server-default Try 3: server server-default...jvm-args../server-default /server Try 4: cluster server-default...jvm-args../server-default /cluster None of these are working. Any thoughts? Thanks, 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] Resin 3.1: resin:import of jvm-args
You should be able to achieve this by using jvm-arg inside the server server id=a address=127.0.0.1 port=6800 jvm-arg-Dserver=A/jvm-arg /server server id=b address=127.0.0.1 port=6801 jvm-arg-Dserver=B/jvm-arg /server Regards, Alex Hmm, that's exactly what I tried first, as mentioned below. Did it work for you? What version of Resin 3.1 did you try it with if it did not work? No, none of those scenarios worked. It is with Resin 3.1.9. I was trying to resin:import the jvm-args, so I guess that's why it was failing. I have unique jvm-arg needs for different servers so I was hoping I could pull that off. Can you have jvm-arg inside a resin:import'ed file? Nope, the server does not allow resin:import tag. Alex Bummer. Thanks for clarifying. Aaron ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Resin 3.1: resin:import of jvm-args
No, none of those scenarios worked. It is with Resin 3.1.9. I was trying to resin:import the jvm-args, so I guess that's why it was failing. I have unique jvm-arg needs for different servers so I was hoping I could pull that off. The excerpt below should work and it will allow you to have all the configuration in one file. server id=a address=127.0.0.1 port=6800 jvm-arg-Dserver=A/jvm-arg /server server id=b address=127.0.0.1 port=6801 jvm-arg-Dserver=B/jvm-arg /server Thanks, Alex Can you have jvm-arg inside a resin:import'ed file? Nope, the server does not allow resin:import tag. Alex Bummer. Thanks for clarifying. 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] Resin 3.1: resin:import of jvm-args
The excerpt below should work and it will allow you to have all the configuration in one file. server id=a address=127.0.0.1 port=6800 jvm-arg-Dserver=A/jvm-arg /server server id=b address=127.0.0.1 port=6801 jvm-arg-Dserver=B/jvm-arg /server Thanks Alex. My problem isn't with multiple servers on a single machine though. I have multiple machines, each with one server, and a few of the machines need a different set of jvm-args. I was trying to get by with one Resin configuration file where I could pass in a -Dconfiguration={something} and then resin:import path=.../${configuration}/*.xml (not literally, I was using the fileset option of resin:import). It's working great except the one little snafu of not being able to import jvm-arg settings. I think I will just have to throw some resin:choose around the jvm-arg stuff. Aaron ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Multi-Part request error when using HmuxRequest in Resin 4.0.2(GA)
Wesley Wu wrote: Thanks, Scott. You rocks. We're planning a launch of a new version of my website on December 18. All codes in this new version rely on JSR 299 (hopefully I'll see the final ballot today). So it's a bit emergency for me to solve this problem. I'll be happy if 4.0.3 will be ready by then, but a snapshot with fixes will be ok. I've uploaded a new snapshot, so it would be great if you can check if this fix is the same one as you're seeing. -- Scott Or I'll have to switch back to the 4.0.2 snapshot 091013 (which has performance/logging issue and JPA issues). 2009/12/1 Scott Ferguson f...@caucho.com: Scott Ferguson wrote: Wesley Wu wrote: Without this bug fixed, 4.0.2 can't be used in production environment. I use two machines with two resin as a load balance cluster, one with a web-tier and a app-tier the other only a app-tier. Can you turn on finer logging for both machines and send the protocol part of the logs? I can't reproduce the issue here; posts are going through fine. So there must be some difference in the request or the reading that's triggering the problem. Nevermind. I found it. -- Scott ___ 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
Re: [Resin-interest] 4.0.2 schedule
Jan Kriesten wrote: Hi Georg, i can't reproduce this behaviour, * Resin-4.0.2 (Apache2 (2.2.9), mod_ssl, mod_caucho) I'm using Resin-4.0.2 with Apache/2.2.14 and mod_caucho The problem is a bit difficult to reproduce. Out of 5 times posting form data only once the content reaches Wicket. Else the posted data is null! It seems to be a general problem and not just for the 'login-form'. If you get a chance, can you check the snapshot? The issue fixed in the snapshot is related, but I'm not sure if it's the same problem as you're seeing. -- Scott It looks like there might be a timing problem. I.e. when Wicket processes the form data, these seems not to be available in the request object yet! This doesn't happen with resin-4.0.1 at all. Best regards, --- Jan. ___ 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] Resin 3.1: resin:import of jvm-args
Hi Aaron, Maybe I am missing something, but if you can pass in -Dconfiguration=wherever to your individual machines (in your /etc/init.d/resin script or wherever, I assume?), can't you pass in your server specific JVM args there too? Rachel On Mon, Nov 30, 2009 at 12:08 PM, Aaron Freeman aaron.free...@layerz.comwrote: Thanks Alex. My problem isn't with multiple servers on a single machine though. I have multiple machines, each with one server, and a few of the machines need a different set of jvm-args. I was trying to get by with one Resin configuration file where I could pass in a -Dconfiguration={something} and then resin:import path=.../${configuration}/*.xml (not literally, I was using the fileset option of resin:import). It's working great except the one little snafu of not being able to import jvm-arg settings. I think I will just have to throw some resin:choose around the jvm-arg stuff. 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] 4.0.2 schedule
Hi Scott, If you get a chance, can you check the snapshot? The issue fixed in the snapshot is related, but I'm not sure if it's the same problem as you're seeing. I just checked with Resin-4.0.s091130 (built Mon, 30 Nov 2009 11:11:59 PST) and a quick first check didn't have any problems any more. So you may consider the problem solved - thanks for the quick effort! :) Best regards, --- Jan. ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Resin 3.1: resin:import of jvm-args
Aaron, Maybe I am missing something, but if you can pass in -Dconfiguration=wherever to your individual machines (in your /etc/init.d/resin script or wherever, I assume?), can't you pass in your server specific JVM args there too? Rachel Probably. The configuration is passed in via an environment variable, but I could pass those in dynamically too if I have too. If we set those from our resin script will the ResinWatchdogManager pass the same values to the actual Resin server, when it launches it? I wasn't sure, so I was just going by the example resin.conf file that comes with Resin 3.1.9. Aaron ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
[Resin-interest] meaning of / in rewrite-dispatch
I have a (hopefully) quick question about the meaning of / in regexp attributes of the rewrite-dispatch tags. For example: dispatch regexp=/|\.html name=... ... /dispatch Does the / have the same meaning as in servlet mappings, i.e. default? Or does it only match requests for /? That is, does the above dispatch match a request for /foo.jpg, in addition to / and /bar.html? Thanks, Ethan ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Resin 3.1: resin:import of jvm-args
Well, they are JVM system variables so it isn't so much that ResinWatchdogManager would pass them to the server, but that they're set in the JVM when it's started and anything in that runtime instance will have them available. My startup script uses this technique and it works great. I suppose it is possible that a later version changed this behavior (we're still on 3.0.21) but I'd be extremely surprised if that's the case. Rachel On Mon, Nov 30, 2009 at 1:25 PM, Aaron Freeman aaron.free...@layerz.comwrote: Aaron, Maybe I am missing something, but if you can pass in -Dconfiguration=wherever to your individual machines (in your /etc/init.d/resin script or wherever, I assume?), can't you pass in your server specific JVM args there too? Rachel Probably. The configuration is passed in via an environment variable, but I could pass those in dynamically too if I have too. If we set those from our resin script will the ResinWatchdogManager pass the same values to the actual Resin server, when it launches it? I wasn't sure, so I was just going by the example resin.conf file that comes with Resin 3.1.9. 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] Resin 3.1: resin:import of jvm-args
Aaron, Maybe I am missing something, but if you can pass in -Dconfiguration=wherever to your individual machines (in your /etc/init.d/resin script or wherever, I assume?), can't you pass in your server specific JVM args there too? Rachel Probably. The configuration is passed in via an environment variable, but I could pass those in dynamically too if I have too. If we set those from our resin script will the ResinWatchdogManager pass the same values to the actual Resin server, when it launches it? Yes. The variable needs to be exported !#/bin/bash export foo=foo-value bin/httpd.sh -server a start resin.conf file: server id=a address=127.1 port=6080 jvm-arg-Dbar=${Var[foo]}/jvm-arg /server Alex I wasn't sure, so I was just going by the example resin.conf file that comes with Resin 3.1.9. 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] Resin 3.1: resin:import of jvm-args
I've got this, which is a slightly different but equivalent technique that doesn't require the jvm-arg tag (applicable bits only, my startup script does other things too): Just for the benefit of understanding the use case: is this to support n environments that are identical but serve two distinct purposes e.g. - development - testing - production where let's suppose 'testing' runs on a different set of servers and therefor needs different bindings and jvm arguments? Alex USER=username HTTPD=/usr/local/resin/bin/httpd.sh su $USER -c $HTTPD start -verbose -J-server -Dvar1=value1 -Dvar2=value2 $* Rachel On Mon, Nov 30, 2009 at 2:28 PM, Alex a...@caucho.com wrote: Aaron, Maybe I am missing something, but if you can pass in -Dconfiguration=wherever to your individual machines (in your /etc/init.d/resin script or wherever, I assume?), can't you pass in your server specific JVM args there too? Rachel Probably. The configuration is passed in via an environment variable, but I could pass those in dynamically too if I have too. If we set those from our resin script will the ResinWatchdogManager pass the same values to the actual Resin server, when it launches it? Yes. The variable needs to be exported !#/bin/bash export foo=foo-value bin/httpd.sh -server a start resin.conf file: server id=a address=127.1 port=6080 jvm-arg-Dbar=${Var[foo]}/jvm-arg /server Alex I wasn't sure, so I was just going by the example resin.conf file that comes with Resin 3.1.9. 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 ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] meaning of / in rewrite-dispatch
Thanks for the reply Alex. So how would I match only / and .html? Something like this? dispatch regexp=(^/$)|(\.html) name=... Cheers, Ethan - Original Message - From: Alex a...@caucho.com To: General Discussion for the Resin application server resin-interest@caucho.com Sent: Monday, November 30, 2009 2:52:45 PM Subject: Re: [Resin-interest] meaning of / in rewrite-dispatch I have a (hopefully) quick question about the meaning of / in regexp attributes of the rewrite-dispatch tags. For example: dispatch regexp=/|\.html name=... This will match any request that has a '/' (basically every request has a '/') Something like the following will change .html to .jsp http://www.caucho.com/resin/admin/rewrite.xtp web-app rewrite-dispatch dispatch regexp=\.html target=.jsp/ Thanks, Alex ... /dispatch Does the / have the same meaning as in servlet mappings, i.e. default? Or does it only match requests for /? That is, does the above dispatch match a request for /foo.jpg, in addition to / and /bar.html? Thanks, Ethan ___ 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
Re: [Resin-interest] meaning of / in rewrite-dispatch
Thanks for the reply Alex. So how would I match only / and .html? Something like this? dispatch regexp=(^/$)|(\.html) name=... That looks right, Ethan. The parenthesis are optional here but they do make regexp more readable. Alex Cheers, Ethan - Original Message - From: Alex a...@caucho.com To: General Discussion for the Resin application server resin-interest@caucho.com Sent: Monday, November 30, 2009 2:52:45 PM Subject: Re: [Resin-interest] meaning of / in rewrite-dispatch I have a (hopefully) quick question about the meaning of / in regexp attributes of the rewrite-dispatch tags. For example: dispatch regexp=/|\.html name=... This will match any request that has a '/' (basically every request has a '/') Something like the following will change .html to .jsp http://www.caucho.com/resin/admin/rewrite.xtp web-app rewrite-dispatch dispatch regexp=\.html target=.jsp/ Thanks, Alex ... /dispatch Does the / have the same meaning as in servlet mappings, i.e. default? Or does it only match requests for /? That is, does the above dispatch match a request for /foo.jpg, in addition to / and /bar.html? Thanks, Ethan ___ 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 ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Resin 3.1: resin:import of jvm-args
Hi, This works with 3.1.9 but careful as it does not work with 3.1.5, I think it was a new feature introduced later in 3.1 or a bug fixed. We had to go back to 3.1.5 due to JPA issues and had to change our scripts accordingly. In our case, we use different Node.conf configuration files that import the common pieces from a set of files shared between all the nodes. If you share the whole configuration file, be aware that modifying it will bump all of your nodes. S! D. Alex escribió: Aaron, Maybe I am missing something, but if you can pass in -Dconfiguration=wherever to your individual machines (in your /etc/init.d/resin script or wherever, I assume?), can't you pass in your server specific JVM args there too? Rachel Probably. The configuration is passed in via an environment variable, but I could pass those in dynamically too if I have too. If we set those from our resin script will the ResinWatchdogManager pass the same values to the actual Resin server, when it launches it? Yes. The variable needs to be exported !#/bin/bash export foo=foo-value bin/httpd.sh -server a start resin.conf file: server id=a address=127.1 port=6080 jvm-arg-Dbar=${Var[foo]}/jvm-arg /server Alex I wasn't sure, so I was just going by the example resin.conf file that comes with Resin 3.1.9. Aaron ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest