[Resin-interest] changes page broker

http://caucho.com/resin-4.0/changes/changes.xtp 500 Servlet Exception /var/www/hosts/www.caucho.com/webapps/resin-4.0/changes/changes.xtp:48: `' expected `>' at `<'. Closing tags must close immediately after the tag name. 46: config: app-oinf in cluster wasn't picked up properly (#5004) 47: clou

Re: [Resin-interest] Resin 4 stable for production ?

resin-interest mailing list > resin-interest@caucho.com > http://maillist.caucho.com/mailman/listinfo/resin-interest > -- *Wesley Wu 吴萌野* QQ:18990702 Mobile: 18601033886 Email: wesley...@yinyuetai.com 工体北路8号三里屯SOHO办公D座1103 邮编100027 [image: U3%8Y%PN7N{6ZGQY1F)PI_P] www.yinyuetai

[Resin-interest] It seems resin 4.0.x does not implement Unified EL 2.2 properly

spec but not the EL 2.2 one. I looked at the source of resin el implementation and found java.el.CompositeELResolver did not implemented the public Object invoke(ELContext context, Object base, Object method, Class[] paramTypes, Object[] params); method which was added since EL 2.2. any tho

[Resin-interest] It seems resin 4.0.x does not implement Unified EL 2.2 properly

spec but not the EL 2.2 one. I looked at the source of resin el implementation and found java.el.CompositeELResolver did not implemented the public Object invoke(ELContext context, Object base, Object method, Class[] paramTypes, Object[] params); method which was added since EL 2.2. any thou

[Resin-interest] ScheduledThreadPool randomly failed to start throwing NullPointerException

Hi Scott, I found resin sometimes can't start ScheduledThreadPool, resulting in @Inject ExecutorService executorService not work (executorService is null). can't precisely reproduce it coz it happened randomly when server restarts. affected resin version: Resin 4.0.s100809 Resin 4.0.18 [11-07

[Resin-interest] "no JMX ObjectName detected" with jrockit vm

Hi Scott, Resin 4.0.14 log many warnings about no JMX ObjectName detected [11-02-11 00:19:23.324] {resin-34} MemoryTenuredHealthCheck: WARNING: MemoryTenuredHealthCheck[] has no JMX ObjectName detected [11-02-11 00:19:23.324] {resin-34} MemoryPermGenHealthCheck: WARNING: MemoryPermGenHealthCheck[

[Resin-interest] too many user transaction pool broken message in log

Hi, After upgrading to Resin 4.0.14, in resin.log I found too many exceptions but I've got no idea why they were thrown. When using 4.0.10 there were no such exception logs with the same webapp code. 2~4 times per seconds. 4.0.13 also have the issue. java.lang.IllegalStateException: Internal er

Re: [Resin-interest] InjectManager._selfBeanMap should be ConcurrentHashMap?

Thanks, Scott. Would you give out a snapshot and I will do some stress test on it. -Wesley 2010/11/30 Scott Ferguson : > Thanks. I've fixed it for the next release (changing to ConcurrentHashMap) > > - Scott > > Wesley Wu wrote: >> Or this method sync the wr

Re: [Resin-interest] InjectManager._selfBeanMap should be ConcurrentHashMap?

n.getBean()); } } return beans; } } maybe should synchronized (_selfBeanMap) instead. -Wesley 2010/11/30 Wesley Wu : > 2010-11-30 02:35:13.697 ERROR [Thread-48] > c.b.c.j.MessageReceiverDaemon - > java.util.ConcurrentModificationException >      

[Resin-interest] InjectManager._selfBeanMap should be ConcurrentHashMap?

2010-11-30 02:35:13.697 ERROR [Thread-48] c.b.c.j.MessageReceiverDaemon - java.util.ConcurrentModificationException at java.util.HashMap$HashIterator.nextEntry(HashMap.java:977) at java.util.HashMap$KeyIterator.next(HashMap.java:1012) at java.util.HashMap.buildCache(HashMap.

Re: [Resin-interest] Resin CanDI not support @Alternative ?

I just checked with that example and it's working fine. Where are the > files/classes located, and how is JmsTemplate instantiated? > > -- Scott > > Wesley Wu wrote: >> ==beans.xml=== >> >> >> http://java.sun.com/xml/ns/javaee"; >

[Resin-interest] Resin CanDI not support @Alternative ?

==beans.xml=== http://java.sun.com/xml/ns/javaee"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/beans_1_0.xsd";> com.buysou.cms.jms.q

[Resin-interest] ConnectionPool pool overflow issue again in resin 4.0.10

Hi Scott, I experienced ConnectionPool pool overflow issue again in resin 4.0.10. Some time (probably 20 minutes) after resin started, resin reported: [10-10-08 01:07:28.555] {server://*:6801-5523} ConnectionPool[jdbc/mypool] pool overflow [10-10-08 01:07:28.555] {server://*:6801-5109} Connectio

Re: [Resin-interest] Possible memory leak in Resin 4.0.9

I'll tried to do so. 2010/8/20 Scott Ferguson : > Wesley Wu wrote: >> 2010/8/20 Scott Ferguson : >> >>> I still think there's a chance for a Resin leak; I just don't understand >>> where it's coming from. >>> >> >> I think

Re: [Resin-interest] Possible memory leak in Resin 4.0.9

2010/8/20 Scott Ferguson : > I still think there's a chance for a Resin leak; I just don't understand > where it's coming from. I think so. The same code worked fine (no leak) in Resin 4.0.5. > > It shouldn't matter what context you're injecting from, as long as > you're creating a new top-level

Re: [Resin-interest] Possible memory leak in Resin 4.0.9

Hi Scott, I believe I've fixed this issue by adding @ApplicationScoped and @RequestedScoped annotation to my beans. :) Thanks for your efforts. -Wesley 2010/8/18 Wesley Wu : > Hi Scott, > > Thanks for the checking. > > Today I double checked the CDI spec and got some new k

Re: [Resin-interest] ConcurrentModificationException when InjectManager.findByName

it's the Resin code that's modifying the HashMap. It's an easy fix. > > -- Scott >> Here is a more detailed explanation: >> http://forums.sun.com/thread.jspa?threadID=5335803 >> >> Aaron >> >> >> On 8/19/2010 4:20 AM, Wesley Wu wrote: >>

[Resin-interest] ConcurrentModificationException when InjectManager.findByName

Often happened at 30 seconds after appserver start. [10-08-19 17:11:44.378] {server://*:6801-487} java.util.ConcurrentModificationException at java.util.HashMap$HashIterator.nextEntry(HashMap.java:977)

Re: [Resin-interest] Possible memory leak in Resin 4.0.9

Hi Scott, Thanks for the checking. Today I double checked the CDI spec and got some new knowledge. Nearly all my beans were not annotated with any scope, so that they should be @Dependent. Some of the beans were created (not injected) in a servlet filter via a static ObjectFactory. I think the

Re: [Resin-interest] Possible memory leak in Resin 4.0.9

My BeanManager wrapper code @Singleton @Startup public class MDIObjectFactory { private static BeanManager beanManager; private static BeanManager getBeanManager() { if (beanManager == null) { try { InitialCon

Re: [Resin-interest] Possible memory leak in Resin 4.0.9

Hi Scott, The memory leak circumstance was not spotted in Resin 4.0.5 and early 4.0.x versions. One of the inject path is: * A filter CmsPageFilter dispatch a request to a Jsp page through javax.servlet.RequestDispatcher.forward(request, response) * Jsp page called a BeanMethod custom jsp tag *

Re: [Resin-interest] Resin 4.0.9 release

Hi Jan, Did your resin server have a busy traffic? Did u observed any memory leak or heap overflow? -Wesley ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest

[Resin-interest] Possible memory leak in Resin 4.0.9

Hi Scott, I've applied the 4.0.10 snapshot and the Alarm issue went away. Thanks. But Resin consumed all memory after certain hours and resulted in a halt or restart. I did a jrockit flight recording and found there was a slow heap increase during various GCs. The recording file shows the objec

Re: [Resin-interest] ConnectionPool pool overflow issue in Resin 4.0.9

Thanks. Be sure to notify in the mailing list when the snapshot is out. :) 2010/8/7 Scott Ferguson : > Wesley Wu wrote: >> Hi Scott, >> >> I've experienced weird connection pool issue in 4.0.9 these days. >> >> After every hour (exactly), the 4.0.9 resin

[Resin-interest] ConnectionPool pool overflow issue in Resin 4.0.9

Hi Scott, I've experienced weird connection pool issue in 4.0.9 these days. After every hour (exactly), the 4.0.9 resin refused to service any request and occasionally report "ConnectionPool [...] pool overflow". This situation never occurred in prior resin releases and neither my webapp nor conf

[Resin-interest] Severe InjectManager.getCurrent synchronization problem at high load, fixed in 4.0.9?

Hi Scott, We're running Resin 4.0.5 for a heavy traffic site (100K+ Pageviews in an hour) for a couple of months. In the past several days I've experienced frequent failing responding of requests after two or three hours a Resin instance was started. The environment: Hardware: 16 cores with 24GB

[Resin-interest] Servlet 3.0 file upload feature (javax.servlet.http.Part) improperly implemented

Hi Scott, I found a frustrating problem when porting my framework to accommodate the Servlet 3.0 file upload spec in Resin 4.0.8/4.0.9. There did has a (private Object _value) in com.caucho.server.http.HttpServletRequestImpl.PartImpl, however, if it's not a file upload but a common text form fiel

Re: [Resin-interest] Resin 4.0.9 release

Oh my god Scott, you rule it! /** * Returns the current environment container. */ public static InjectManager getCurrent(ClassLoader loader) { return _localContainer.get(loader); } finally the synchronized (_localContainer) was gone! You have no idea how I suffered from the lo

Re: [Resin-interest] A request for caucho apache module - connect to an instance only after CDI deployment finished

Thanks for the Priority => normal :) -Wesley ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest

[Resin-interest] A request for caucho apache module - connect to an instance only after CDI deployment finished

Hi Scott, The request: Make caucho apache module to act (maybe should be configurable) as below : When check a Resin instance whether it is ready to accept connections, make sure it's not only started normally, but also all CDI startup beans were already initialized and deployed (after @PostCons

Re: [Resin-interest] Numerous problems moving to 4.0.8

ot problem in classes/META-INF 2010/7/5 Rick Mann : > > On Jul 4, 2010, at 21:55:34, Wesley Wu wrote: > >> Hi Rick >> >> Try to place the tld at WEB-INF/classes/META-INF/your_tld_file.tld. > > I don't think that should be necessary. You're supposed to be

Re: [Resin-interest] Resin 4.0.8 passed the tck?

Another minor issue about file uploading. I used commons upload to parse the request: org.apache.commons.fileupload.parseRequest but now it don't parsed it well. Instead all upload files all turned into something like: myUploadFile.file myUploadFile.filename myUploadFile.content-type plain fi

Re: [Resin-interest] Numerous problems moving to 4.0.8

Hi Rick Try to place the tld at WEB-INF/classes/META-INF/your_tld_file.tld. -Wesley ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest

[Resin-interest] Resin 4.0.8 passed the tck?

Hi, I noticed there is a 4.0.8 release at 6/30, and I tried it out. Seems fine besides some minor problem described below. ***. MDBs implements MessageListener can't have an @Override on onMessage method. I have to remove these annos to make it run. @Override @TransactionAttribu

Re: [Resin-interest] Hibernate transactions

More to mention about MDBs (Message Driven Beans): 1. Always use @TransactionAttribute(TransactionAttributeType.NOT_SUPPORTED) on public void onMessage(Message message). because the impl of Resin MDBs has severe reenter synchronization problem. If I start a transaction before onMessage() being cal

Re: [Resin-interest] Hibernate transactions

I will not call UserTransaction.begin() when all db operations are SELECT. I create a EntityManager from emf to do SELECT stuff with no transaction at all. When I detected there're some update/delete operations, I'll do this: 1. close the former created EntityManager if there is one (for precedent

Re: [Resin-interest] Hibernate transactions

like @TransactionAttribute. I never inject a @PersistentContext or never use a container provided EntityManager. I use ThreadLocal to maintain every EntityManager instance. -Wesley 2010/3/30 Stargazer > On 30-Mar-2010 09:34, Wesley Wu wrote: > > To make set method auto translated

Re: [Resin-interest] Hibernate transactions

To make set method auto translated into a UPDATE clause, the entitymanager should be opened after a transaction begins. @PersistenceUnit(unitName="example") EntityManagerFactory emf; EntityManager em; try { ut.begin(); EntityManager em= emf.createEntityManager(); CourseBean u

Re: [Resin-interest] Hibernate transactions

try { ut.begin(); CourseBean updateCourse = _manager.find(CourseBean.class, new Integer(1)); updateCourse.setCourse("Magic"); ut.commit(); } catch (Exception e) { e.printStackTrace(); } will work. -Wesley __

Re: [Resin-interest] Hibernate transactions

Not a version issue. An entitymanager should not get transaction by itself. Transaction in a modern java appserver should be XA or JTA transaciton. An entitymanager will detect if there is a JTA transaction existing and will join it if there is an open one. You need to use an injected UserTransac

Re: [Resin-interest] CanDI java.lang.StackOverflowError

ve two independent issues. If I remove the constructor > initialization by creating an empty constructor and use setter instead > of it, then the CanDI initialization does completes. However, if I add > @Startup annotation, so a class instance is actually created, then I > again recei

Re: [Resin-interest] CanDI java.lang.StackOverflowError

This could be a lazy init problem I think. The scheduled tasks would be inited before some of other beans which the tasks need. I've met this before. The workaround: Inject the Injector into your task, no other webbeans. When the task starts (run()), create webbeans instances via the injector.

Re: [Resin-interest] Where is javax.inject.Current ?

the docs should be updated I can't agree more. :) 2010/2/7 smallufo : > Oops , thanks for replying so soon. > BTW , the docs should be updated ... > > 2010/2/7 Wesley Wu >> >> according to the JSR299 & JSR330 final spec >> >> should use javax.

Re: [Resin-interest] Where is javax.inject.Current ?

according to the JSR299 & JSR330 final spec should use javax.inject.Inject instead 2010/2/7 smallufo : > I am migrating from Spring to JSR-299 , > I followed this http://blog.caucho.com/?p=137 , > but the first frustration is that I cannot find @Current . > > I extracted javaee-16.jar from resin

Re: [Resin-interest] @ApplicationScoped/@Singleton bean lazy init problem

ey 2010/1/29 Scott Ferguson : > Wesley Wu wrote: >> Hi Scott, >> >> When a @ApplicationScoped/@Singleton bean is designed to be initialized >> after webapp starts (I.E. when first http request was fired) instead of being >> initialized during startup stage, in

[Resin-interest] @ApplicationScoped/@Singleton bean lazy init problem

Hi Scott, When a @ApplicationScoped/@Singleton bean is designed to be initialized after webapp starts (I.E. when first http request was fired) instead of being initialized during startup stage, in given circumstance, it won't be injected correctly. This is my test case: == StartBean

Re: [Resin-interest] the response time

Hi Jon & Scott, I don't like apache either but resin 4.0.2 cluster web-tier seems unstable for me. I've not tested the 4.0.3 cluster. My Apache config: ResinHost 192.168.1.4 6801 ResinBackup 192.168.1.5 6801 Which load balancer will be more appropriate for this usage? Thanks. -Wesley __

[Resin-interest] WebSocket binary stream read error

My log output this error: [09-12-23 04:24:00.017] {hmtp-aaa-to-aaa-2} com.caucho.hemp.broker.HempMemoryQueue consumeQueue java.lang.IllegalStateException: WebSocket binary must begin with a 0x80 packet at 0x51 (Q) [09-12-23 04:24:00.017] {hmtp-aaa-to-aaa-2} at com.caucho.hessian.io.Hessian2Str

[Resin-interest] HempMemoryQueue consumeQueue NullPointerException

My log output this error: [09-12-23 04:16:12.154] {hmtp-baa-to-aaa-5} com.caucho.hemp.broker.HempMemoryQueue consumeQueue java.lang.NullPointerException [09-12-23 04:16:12.154] {hmtp-baa-to-aaa-5} at com.caucho.server.cluster.HmuxQueue.authenticate(HmuxQueue.java:263) [09-12-23 04:16:12.154] {

Re: [Resin-interest] HempMemoryQueue Exception when synchronizing sessions between two nodes in a cluster

I gave some code for the request: Cache cache = cacheManager.getCache("forumPageCache"); cache.put("forum_1_page_1", postListInForum1Page1); cache.put("forum_1_page_2", postListInForum1Page2); cache.put("forum_1_page_3", postListInForum1Page3); cache.put("forum_2_page_1", postListInForum2Page1); c

Re: [Resin-interest] HempMemoryQueue Exception when synchronizing sessions between two nodes in a cluster

corrections or suggestions? Thanks very much, Jon. -Wesley 2009/12/19 Wesley Wu : > Great Jon, you help me to make a critical decision (not to use JBC any > more and switch to EHC & Terracotta). > > I'll give it a shot. > > -Wesley > > 2009/12/19 Jon Stevens : >&g

Re: [Resin-interest] HempMemoryQueue Exception when synchronizing sessions between two nodes in a cluster

oducts. > jon > > On Thu, Dec 17, 2009 at 11:42 PM, Wesley Wu wrote: >> >> Thanks Jon, I'll definitely give terracotta a try. >> >> As far as I know, EHCache was a opensymphony project one or two years >> ago. I noticed that ehcache was acquired by terr

Re: [Resin-interest] HempMemoryQueue Exception when synchronizing sessions between two nodes in a cluster

Thanks Jon, I'll definitely give terracotta a try. As far as I know, EHCache was a opensymphony project one or two years ago. I noticed that ehcache was acquired by terracotta and became a key component of terracotta. That's great! -Wesley ___ resin-

Re: [Resin-interest] HempMemoryQueue Exception when synchronizing sessions between two nodes in a cluster

t;> ehcache + terracotta (yes, there is an oss free version) = love. >> I'm not super clear on what you want, but it sounds like you want the >> TIM-MasterWorker (ExecutorService): >> http://forge.terracotta.org/releases/projects/tim-messaging/docs/about.html >> jon >&g

Re: [Resin-interest] HempMemoryQueue Exception when synchronizing sessions between two nodes in a cluster

So if I want my beans synchronized across the cluster, I have to use either JMS or some thirdparty cluster middleware like JBossCache? -Wesley ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-i

Re: [Resin-interest] HempMemoryQueue Exception when synchronizing sessions between two nodes in a cluster

Thanks. I switched back to 091202 snapshot and this issue was resolved. Would u take some time to look at my other mail about @ApplicationScoped bean distribution? -Wesley 2009/12/18 Scott Ferguson : > Wesley Wu wrote: >> this node is using Resin-4.0.s091216 >> the other is

Re: [Resin-interest] HempMemoryQueue Exception when synchronizing sessions between two nodes in a cluster

this node is using Resin-4.0.s091216 the other is using Resin-4.0.s091202 -Wesley ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest

[Resin-interest] HempMemoryQueue Exception when synchronizing sessions between two nodes in a cluster

[09-12-18 01:43:05.221] {hmtp-baa-to-aaa-0} com.caucho.hemp.broker.HempMemoryQueue consumeQueue java.lang.IllegalStateException: WebSocket binary must begin with a 0x80 packet at 0x51 (Q) [09-12-18 01:43:05.221] {hmtp-baa-to-aaa-0} at com.caucho.hessian.io.Hessian2StreamingInput$StreamingInputS

Re: [Resin-interest] Lots of Connection reset

If u'r using apache or other web server backended by resin instead of running resin standalone, I think the 1202 snapshot should fix this issue. 2009/12/16 Mattias Jiderhamn : > We are seeing a lot of "Connection reset" with Hessian since the upgrade > of our production environment to 4.0.2 (both

[Resin-interest] To make @ApplicationScoped Bean distributed

Hi Scott, I'm deploying Resin 4.0.2 snapshot to a cluster and found my @ApplicationScoped bean not distributed across the cluster nodes. Is there anything to config to make it possible? I searched Gavin's blog and found some examples regarding @Observes to resolve this situation. If I dispatch

[Resin-interest] hmux broken pipe

when running resin in load-balance cluster with a web-tier(one server) and a app-tier(two server) my app-tier console display the error [09-12-15 00:14:34.369] {server-192.168.1.5:6801-34} com.caucho.java.JavaCompiler compileInt Compiling _jsp/_person/_Index__jsp.java [09-12-15 00:14:34.723] {ser

Re: [Resin-interest] new Resin 4.0 snapshot

that GET was the subsequent redirect after the POST. I use redirect after post pattern. A request first POST to "/register" and after some processing, redirect to "/register" again using a GET request. -Wesley 2009/12/3 Scott Ferguson : > Wesley Wu wrote: >

Re: [Resin-interest] new Resin 4.0 snapshot

1 +0800] "GET /css/style05.css HTTP/1.1" 304 - "http://localhost:889/register/"; "Mozilla/5.0 (Windows; U; Windows NT 6.0; zh-CN; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5 GTB6 (.NET CLR 3.5.30729)" -Wesley 2009/12/3 Wesley Wu : > I think the win32/win64 dlls should

Re: [Resin-interest] new Resin 4.0 snapshot

I think the win32/win64 dlls should be recompiled against the new modification. 2009/12/3 Wesley Wu : > I wonder why this happened. > I encountered this in all 4.0.2 versions in my developer machine while > not occurred in production machine. > > I'll do some investigation

Re: [Resin-interest] new Resin 4.0 snapshot

I wonder why this happened. I encountered this in all 4.0.2 versions in my developer machine while not occurred in production machine. I'll do some investigation next. Thanks Scoot. 2009/12/3 Wesley Wu : > I turned it on: > > [09-12-03 05:59:44.722] {

Re: [Resin-interest] new Resin 4.0 snapshot

:00:43.513] {http--8080-1} com.caucho.server.http.HttpRequest parseHeaders Http[1] Accept-Language: zh-CN,zh;q=0.8 [09-12-03 06:00:43.513] {http--8080-1} com.caucho.server.http.HttpRequest parseHeaders Http[1] Accept-Charset: gb18030,utf-8;q=0.7,*;q=0.3 2009/12/3 Scott Ferguson : > Wesley Wu wr

Re: [Resin-interest] new Resin 4.0 snapshot

Another SEVERE issues with this snapshot. All "POST" request was dramatically CHANGED to "GET" request. -Wesley 2009/12/3 Scott Ferguson : > Jamison Novak wrote: >> You can ignore this. After further investigation, the developer in charge of >> the app says that it's returning a similar error

Re: [Resin-interest] new Resin 4.0 snapshot

Thanks Scott. This snapshot finally fix it all. I'll have to fix it for you if you don't get this snapshot out in a week :) -Wesley 2009/12/3 Scott Ferguson : > There's a new Resin 4.0 snapshot with additional fixes for the > hmux/forwarding issues. > > -- Scott > > > >

Re: [Resin-interest] Multi-Part request error when using HmuxRequest in Resin 4.0.2(GA)

e the forwarding. If I use 8080 port, everything goes fine. 2009/12/1 Scott Ferguson : > 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 (h

Re: [Resin-interest] Multi-Part request error when using HmuxRequest in Resin 4.0.2(GA)

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 : > Scott Ferguson wrote: >> Wesley Wu wrote: >> >>> Without this bug fix

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 > > This bug should be marked as "b

Re: [Resin-interest] Multi-Part request error when using HmuxRequest in Resin 4.0.2(GA)

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 > > Multi-Part request error

Re: [Resin-interest] Resin V Glassfish

CDI is actually based on > JBoss Seam and Google Guice. > > Cheers, > > -Kai > > > On 27.11.2009, at 12.10, Wesley Wu wrote: > > > As long as Scott continue to work for the Resin's future I'll never > > switch to other platform. > > > &g

[Resin-interest] Multi-Part request error when using HmuxRequest in Resin 4.0.2(GA)

Multi-Part request error when using HmuxRequest. 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.MultiPartReq

Re: [Resin-interest] Resin V Glassfish

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 thro

[Resin-interest] change log page broken

http://www.caucho.com/resin/changes/changes.xtp [show] /var/www/hosts/www.caucho.com/webapps/resin/changes/changes.xtp:116: expected name at ` ' 114: quercus: Drupal and OpenID (#3609, rep by B. Wu) 115: quercus: QuercusParseException - missing semicolon within a scriptlet php tag. (#3668, rep by

Re: [Resin-interest] url rewriting / search engine friendly

ionnal point of view. > > On the other hand, you may think of the SEF url as a request by itself, > > and the controller is in charge of handling requests, of any syntax. So > > if my controller parses the url "/servlet?command=showuser&id=1354", why > > couldn&#

Re: [Resin-interest] url rewriting / search engine friendly

Not recommended. I think filter should handle this, which is not relative to business logic. 2009/10/30 Riccardo Cohen > Thanks Wesley I'll try to use filter. > Now in term of performance, isn't it better to integrate the url > processing directly into the controller serv

Re: [Resin-interest] url rewriting / search engine friendly

You may use http://tuckey.org/urlrewrite/ UrlRewriteFilter. I wrote a similar filter doing the same thing which loads rewrite config from database. 2009/10/30 Riccardo Cohen > Hello > > I didn't have yet the opportunity to work with search engine friendly > urls with resin (I did it with apache

[Resin-interest] UnsatisfiedLinkError: com/caucho/vfs/JniSocketImpl.writeCloseNative

Every request cause this stacktrace [09-10-29 00:26:51.777] {http--80-6} com.caucho.server.webapp.ErrorPageManager sendServletErrorImpl java.lang.UnsatisfiedLinkError: com/caucho/vfs/JniSocketImpl.writeCloseNative [09-10-29 00:26:51.777] {http--80-6} at com.caucho.vfs.JniSocketImpl.write(JniSocket

[Resin-interest] LazyEntityManagerFactory is initialized too late to be injected into scheduled tasks

Hi Scott, I got two new problems. I have a scheduled task need to inject a @PersistenceUnit, as the config below: 0 2 * I turned log level to finer, and found Resin tried to initialize my task before creating the persistence unit. But my task need the persistence unit to be injected in it!

Re: [Resin-interest] 4.0.2 schedule

Yes, I turned on (simply copied from my previous 4.0.0 conf file). When I turned it off (commented them out) @SessionScope worked fine. Thanks. -Wesley 2009/10/14 Scott Ferguson > > On Oct 13, 2009, at 1:49 PM, Wesley Wu wrote: > > > I found two issues so far: >

Re: [Resin-interest] 4.0.2 schedule

"I think I could only use @SessionScoped annotation on "SINGLE" beans, though not tested yet." sorry, I mean SIMPLE beans not SINGLE. -Wesley 2009/10/14 Wesley Wu > Seems 4.0.2 snapshot passed most of my web test. > Passed: > Thirdparty Hibernate JPA integration (

Re: [Resin-interest] 4.0.2 schedule

Seems 4.0.2 snapshot passed most of my web test. Passed: Thirdparty Hibernate JPA integration (* see issues below) @Inject @Qualifier @Observes (with @Qualifier bindings) @ApplicationScoped @RequestScoped Failed: @SessionScoped not tested: @InterceptorBinding I found two issues so far: 1. I hav

Re: [Resin-interest] 4.0.2 schedule

Thanks Scott. I'll test the JPA & JSR299/330 stuff. 2009/10/14 Scott Ferguson > The 4.0.2 snapshot is now available. Bugs can be reported at > bugs.caucho.com. The snapshot isn't clean yet, so a bug report might > duplicate one of our failing regression tests, but it's better to have > two repo

Re: [Resin-interest] resin 4.0.1 : Chinese UTF8 characters problems in Quercus

That's a long live problem which exists in all Quercus version. I believe that's because of the poor unicode implementation of mysql (or all db specific) functions. I raised the question to Scott one years before, yet not solved now. - Wesley 2009/10/6