Re: [Wicket-user] Unable to render resource stream Exception
looks like a webspehere classloader problem. not sure how to help you since i dont have access to websphere. maybe you can tell it not to create that _wl_user_cls jar -igor On 2/5/07, Konstantinos Lazouras [EMAIL PROTECTED] wrote: Hi all, thanx for your help so far and apologies for getting back so late... to the problem now: To what you suggested, I didn't get something useful from yourkit and tmsMserver is not wicket related. If the problem appears, it happens by clicking the datepicker icon (in a monkey testing context), where WebLogic 9.1 cannot get to the resources. It has nothing to do with browsers (speaking about firefox and ie). It is related to the environment used: For development we use eclipse, tomcat 5.5, java 1.5 on windows and we also test inhouse with BEA WebLogic both on windows and linux. We cannot reproduce the problem locally, no matter what. At the client site, we deploy again on BEA WebLogic but this time on AIX. This is the only environment where we get the Unable to render resource stream error. Inspired by the thread Fighting Too many open files problem related to wicket resource files we unpacked the wicket jars (we only use 2 jars, core+extensions), put everything in classes folder and deployed again. We didn't get much, as the exception now became: 12:16:53,251 ERROR RequestCycle:1043 - Unable to render resource stream zip:/prod/applc/bea9/weblogic91/config/tmsdomain/./servers/tmsMserver/tmp/_WL_user/fc/2eqljk/war/WEB-INF/lib/_wl_cls_gen.jar!/wicket/extensions/markup/html/datepicker/style/aqua/status- bg.gif wicket.WicketRuntimeException: Unable to render resource stream zip:/prod/applc/bea9/weblogic91/config/tmsdomain/./servers/tmsMserver/tmp/_WL_user/fc/2eqljk/war/WEB-INF/lib/_wl_cls_gen.jar!/wicket/extensions/markup/html/datepicker/style/aqua/status- bg.gif at wicket.Resource.respond(Resource.java:279) at wicket.Resource.onResourceRequested(Resource.java:135) at wicket.request.target.resource.SharedResourceRequestTarget.respond( SharedResourceRequestTarget.java:192) ... (the rest are the same) So far, my question is: shouldn't unpacking the jars fix the problem? Searching a bit more, we found that _wl_cls_gen.jar is the way WebLogic handles dynamic libraries (so it shouldn't be something suspicious there). From this I understand that WebLogic makes this jar because it finds the datepicker resources in the /WEB-INF/classes/... dir and not in /, as happens with the other resources. What should I do if I want to move datepicker resources away from /WEB-INF/classes/... dir? Do you think that replacing the whole datepicker component with something external would be a solution (how do I do this)? On the other hand, a few minutes ago I came across the following post while searching for answers: http://opensource.atlassian.com/projects/spring/browse/SPR-3043;jsessionid=anu8vO15emAayNy2Ua?page=all I think the problem described is very similar to mine. Do you have any suggestions on how to apply and test the answer given? Thanks again, Konstantinos - Original Message From: Igor Vaynberg [EMAIL PROTECTED] To: wicket-user@lists.sourceforge.net Sent: Saturday, January 27, 2007 1:17:45 AM Subject: Re: [Wicket-user] Unable to render resource stream Exception well i guess we need to know if this is wicket related or something inside weblogic going bad, or the combination of the two -igor On 1/26/07, Martijn Dashorst [EMAIL PROTECTED] wrote: I never have heard of it... And if you don't like shelling out $$$ for YourKit immediately, they have a 30 day trial. Should be enough to at least find this problem. After that you'll instantly know that the 500 bucks they charge are worth every penny. (I'm not affiliated with them). Martijn On 1/26/07, Igor Vaynberg [EMAIL PROTECTED] wrote: is tmsMserver one of our threads? -igor On 1/26/07, Eelco Hillenius [EMAIL PROTECTED] wrote: Wicket is pretty efficient, so likely there is something very resource heavy in your application, or there is a fat memory leak (resulting in the VM having to do a lot of GC). Can you track down what happens? If you use a profiler like the excellent YourKit (http://www.yourkit.com/), you should be able to track down bottlenecks and/ or memory leaks pretty quickly. Eelco On 1/26/07, Konstantinos Lazouras [EMAIL PROTECTED] wrote: Thanks Martjin, your answer makes sense but doesn't actually solve my problem, which in fact is that users complain that the wicket web-app is slow. A check with the server side shows that the thread for 'tmsMserver' is taking up 100% of CPU resource. After a restart of the server and a walk through, the slowness creeps back almost immediately. All I get in the server log are exceptions like the one I posted. I suppose what happens is users do something -- they wait -- they get bored -- they kill the request -- exception gets
Re: [Wicket-user] Unable to render resource stream Exception
s/websphere/weblogic/ -igor On 2/13/07, Igor Vaynberg [EMAIL PROTECTED] wrote: looks like a webspehere classloader problem. not sure how to help you since i dont have access to websphere. maybe you can tell it not to create that _wl_user_cls jar -igor On 2/5/07, Konstantinos Lazouras [EMAIL PROTECTED] wrote: Hi all, thanx for your help so far and apologies for getting back so late... to the problem now: To what you suggested, I didn't get something useful from yourkit and tmsMserver is not wicket related. If the problem appears, it happens by clicking the datepicker icon (in a monkey testing context), where WebLogic 9.1 cannot get to the resources. It has nothing to do with browsers (speaking about firefox and ie). It is related to the environment used: For development we use eclipse, tomcat 5.5, java 1.5 on windows and we also test inhouse with BEA WebLogic both on windows and linux. We cannot reproduce the problem locally, no matter what. At the client site, we deploy again on BEA WebLogic but this time on AIX. This is the only environment where we get the Unable to render resource stream error. Inspired by the thread Fighting Too many open files problem related to wicket resource files we unpacked the wicket jars (we only use 2 jars, core+extensions), put everything in classes folder and deployed again. We didn't get much, as the exception now became: 12:16:53,251 ERROR RequestCycle:1043 - Unable to render resource stream zip:/prod/applc/bea9/weblogic91/config/tmsdomain/./servers/tmsMserver/tmp/_WL_user/fc/2eqljk/war/WEB-INF/lib/_wl_cls_gen.jar!/wicket/extensions/markup/html/datepicker/style/aqua/status- bg.gif wicket.WicketRuntimeException: Unable to render resource stream zip:/prod/applc/bea9/weblogic91/config/tmsdomain/./servers/tmsMserver/tmp/_WL_user/fc/2eqljk/war/WEB-INF/lib/_wl_cls_gen.jar!/wicket/extensions/markup/html/datepicker/style/aqua/status- bg.gif at wicket.Resource.respond(Resource.java:279) at wicket.Resource.onResourceRequested(Resource.java:135) at wicket.request.target.resource.SharedResourceRequestTarget.respond( SharedResourceRequestTarget.java:192) ... (the rest are the same) So far, my question is: shouldn't unpacking the jars fix the problem? Searching a bit more, we found that _wl_cls_gen.jar is the way WebLogic handles dynamic libraries (so it shouldn't be something suspicious there). From this I understand that WebLogic makes this jar because it finds the datepicker resources in the /WEB-INF/classes/... dir and not in /, as happens with the other resources. What should I do if I want to move datepicker resources away from /WEB-INF/classes/... dir? Do you think that replacing the whole datepicker component with something external would be a solution (how do I do this)? On the other hand, a few minutes ago I came across the following post while searching for answers: http://opensource.atlassian.com/projects/spring/browse/SPR-3043;jsessionid=anu8vO15emAayNy2Ua?page=all I think the problem described is very similar to mine. Do you have any suggestions on how to apply and test the answer given? Thanks again, Konstantinos - Original Message From: Igor Vaynberg [EMAIL PROTECTED] To: wicket-user@lists.sourceforge.net Sent: Saturday, January 27, 2007 1:17:45 AM Subject: Re: [Wicket-user] Unable to render resource stream Exception well i guess we need to know if this is wicket related or something inside weblogic going bad, or the combination of the two -igor On 1/26/07, Martijn Dashorst [EMAIL PROTECTED] wrote: I never have heard of it... And if you don't like shelling out $$$ for YourKit immediately, they have a 30 day trial. Should be enough to at least find this problem. After that you'll instantly know that the 500 bucks they charge are worth every penny. (I'm not affiliated with them). Martijn On 1/26/07, Igor Vaynberg [EMAIL PROTECTED] wrote: is tmsMserver one of our threads? -igor On 1/26/07, Eelco Hillenius [EMAIL PROTECTED] wrote: Wicket is pretty efficient, so likely there is something very resource heavy in your application, or there is a fat memory leak (resulting in the VM having to do a lot of GC). Can you track down what happens? If you use a profiler like the excellent YourKit (http://www.yourkit.com/), you should be able to track down bottlenecks and/ or memory leaks pretty quickly. Eelco On 1/26/07, Konstantinos Lazouras [EMAIL PROTECTED] wrote: Thanks Martjin, your answer makes sense but doesn't actually solve my problem, which in fact is that users complain that the wicket web-app is slow. A check with the server side shows that the thread for 'tmsMserver' is taking up 100% of CPU resource. After a restart of the server and a walk through, the slowness creeps back almost immediately. All I
Re: [Wicket-user] Unable to render resource stream Exception
Hi all, thanx for your help so far and apologies for getting back so late... to the problem now: To what you suggested, I didn't get something useful from yourkit and tmsMserver is not wicket related. If the problem appears, it happens by clicking the datepicker icon (in a monkey testing context), where WebLogic 9.1 cannot get to the resources. It has nothing to do with browsers (speaking about firefox and ie). It is related to the environment used: For development we use eclipse, tomcat 5.5, java 1.5 on windows and we also test inhouse with BEA WebLogic both on windows and linux. We cannot reproduce the problem locally, no matter what. At the client site, we deploy again on BEA WebLogic but this time on AIX. This is the only environment where we get the Unable to render resource stream error. Inspired by the thread Fighting Too many open files problem related to wicket resource files we unpacked the wicket jars (we only use 2 jars, core+extensions), put everything in classes folder and deployed again. We didn't get much, as the exception now became: 12:16:53,251 ERROR RequestCycle:1043 - Unable to render resource stream zip:/prod/applc/bea9/weblogic91/config/tmsdomain/./servers/tmsMserver/tmp/_WL_user/fc/2eqljk/war/WEB-INF/lib/_wl_cls_gen.jar!/wicket/extensions/markup/html/datepicker/style/aqua/status-bg.gif wicket.WicketRuntimeException: Unable to render resource stream zip:/prod/applc/bea9/weblogic91/config/tmsdomain/./servers/tmsMserver/tmp/_WL_user/fc/2eqljk/war/WEB-INF/lib/_wl_cls_gen.jar!/wicket/extensions/markup/html/datepicker/style/aqua/status-bg.gif at wicket.Resource.respond(Resource.java:279) at wicket.Resource.onResourceRequested(Resource.java:135) at wicket.request.target.resource.SharedResourceRequestTarget.respond(SharedResourceRequestTarget.java:192) ... (the rest are the same) So far, my question is: shouldn't unpacking the jars fix the problem? Searching a bit more, we found that _wl_cls_gen.jar is the way WebLogic handles dynamic libraries (so it shouldn't be something suspicious there). From this I understand that WebLogic makes this jar because it finds the datepicker resources in the /WEB-INF/classes/... dir and not in /, as happens with the other resources. What should I do if I want to move datepicker resources away from /WEB-INF/classes/... dir? Do you think that replacing the whole datepicker component with something external would be a solution (how do I do this)? On the other hand, a few minutes ago I came across the following post while searching for answers: http://opensource.atlassian.com/projects/spring/browse/SPR-3043;jsessionid=anu8vO15emAayNy2Ua?page=all I think the problem described is very similar to mine. Do you have any suggestions on how to apply and test the answer given? Thanks again, Konstantinos - Original Message From: Igor Vaynberg [EMAIL PROTECTED] To: wicket-user@lists.sourceforge.net Sent: Saturday, January 27, 2007 1:17:45 AM Subject: Re: [Wicket-user] Unable to render resource stream Exception well i guess we need to know if this is wicket related or something inside weblogic going bad, or the combination of the two -igor On 1/26/07, Martijn Dashorst [EMAIL PROTECTED] wrote: I never have heard of it... And if you don't like shelling out $$$ for YourKit immediately, they have a 30 day trial. Should be enough to at least find this problem. After that you'll instantly know that the 500 bucks they charge are worth every penny. (I'm not affiliated with them). Martijn On 1/26/07, Igor Vaynberg [EMAIL PROTECTED] wrote: is tmsMserver one of our threads? -igor On 1/26/07, Eelco Hillenius [EMAIL PROTECTED] wrote: Wicket is pretty efficient, so likely there is something very resource heavy in your application, or there is a fat memory leak (resulting in the VM having to do a lot of GC). Can you track down what happens? If you use a profiler like the excellent YourKit (http://www.yourkit.com/), you should be able to track down bottlenecks and/ or memory leaks pretty quickly. Eelco On 1/26/07, Konstantinos Lazouras [EMAIL PROTECTED] wrote: Thanks Martjin, your answer makes sense but doesn't actually solve my problem, which in fact is that users complain that the wicket web-app is slow. A check with the server side shows that the thread for 'tmsMserver' is taking up 100% of CPU resource. After a restart of the server and a walk through, the slowness creeps back almost immediately. All I get in the server log are exceptions like the one I posted. I suppose what happens is users do something -- they wait -- they get bored -- they kill the request -- exception gets written. So, the main question is why the wicket application is slow? (also, in web.xml I have no specific statement for development/deployment, and expect deployment to be the default) Konstantinos - Original
[Wicket-user] Unable to render resource stream Exception
Hi all, does anyone know why this exception appears at the logs? (using wicket 1.2.3) 10:18:52,547 ERROR RequestCycle:1043 - Unable to render resource stream zip:/prod/applc/bea9/weblogic91/config/tmsdomain/./servers/tmsMserver/tmp/_WL_user/fc/2eqljk/war/WEB-INF/lib/wicket-extensions-1.2.3.jar!/wicket/extensions/markup/html/datepicker/style/aqua/title-bg.gif wicket.WicketRuntimeException: Unable to render resource stream zip:/prod/applc/bea9/weblogic91/config/tmsdomain/./servers/tmsMserver/tmp/_WL_user/fc/2eqljk/war/WEB-INF/lib/wicket-extensions-1.2.3.jar!/wicket/extensions/markup/html/datepicker/style/aqua/title-bg.gif at wicket.Resource.respond(Resource.java:279) at wicket.Resource.onResourceRequested(Resource.java:135) at wicket.request.target.resource.SharedResourceRequestTarget.respond(SharedResourceRequestTarget.java:192) at wicket.request.compound.DefaultResponseStrategy.respond(DefaultResponseStrategy.java:49) at wicket.request.compound.AbstractCompoundRequestCycleProcessor.respond(AbstractCompoundRequestCycleProcessor.java:66) at wicket.RequestCycle.doProcessEventsAndRespond(RequestCycle.java:902) at wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:934) at wicket.RequestCycle.step(RequestCycle.java:1010) at wicket.RequestCycle.steps(RequestCycle.java:1084) at wicket.RequestCycle.request(RequestCycle.java:454) at wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:219) at javax.servlet.http.HttpServlet.service(HttpServlet.java:751) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:272) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:165) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3153) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1973) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1880) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1310) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207) at weblogic.work.ExecuteThread.run(ExecuteThread.java:179) Caused by: java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:105) at java.net.SocketOutputStream.write(SocketOutputStream.java:149) at weblogic.utils.io.ChunkedOutputStream.writeTo(ChunkedOutputStream.java:185) at weblogic.servlet.internal.ResponseHeaders.writeHeaders(ResponseHeaders.java:346) at weblogic.servlet.internal.ServletResponseImpl.writeHeaders(ServletResponseImpl.java:1098) at weblogic.servlet.internal.ServletOutputStreamImpl.sendHeaders(ServletOutputStreamImpl.java:238) at weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:107) at wicket.Resource.respond(Resource.java:245) ... 24 more Thanks, Konstantinos Finding fabulous fares is fun. Let Yahoo! FareChase search your favorite travel sites to find flight and hotel bargains. http://farechase.yahoo.com/promo-generic-14795097- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Unable to render resource stream Exception
Broken pipe means that users (or their browsers) have killed the request. This log report has been disabled in newer versions. Not sure if that is the case for 1.2.4, but most certainly for 1.3 and 2.0. Martijn On 1/26/07, Konstantinos Lazouras [EMAIL PROTECTED] wrote: Hi all, does anyone know why this exception appears at the logs? (using wicket 1.2.3) 10:18:52,547 ERROR RequestCycle:1043 - Unable to render resource stream zip:/prod/applc/bea9/weblogic91/config/tmsdomain/./servers/tmsMserver/tmp/_WL_user/fc/2eqljk/war/WEB-INF/lib/wicket-extensions-1.2.3.jar!/wicket/extensions/markup/html/datepicker/style/aqua/title-bg.gif wicket.WicketRuntimeException: Unable to render resource stream zip:/prod/applc/bea9/weblogic91/config/tmsdomain/./servers/tmsMserver/tmp/_WL_user/fc/2eqljk/war/WEB-INF/lib/wicket-extensions-1.2.3.jar!/wicket/extensions/markup/html/datepicker/style/aqua/title-bg.gif at wicket.Resource.respond(Resource.java:279) at wicket.Resource.onResourceRequested(Resource.java:135) at wicket.request.target.resource.SharedResourceRequestTarget.respond(SharedResourceRequestTarget.java:192) at wicket.request.compound.DefaultResponseStrategy.respond(DefaultResponseStrategy.java:49) at wicket.request.compound.AbstractCompoundRequestCycleProcessor.respond(AbstractCompoundRequestCycleProcessor.java:66) at wicket.RequestCycle.doProcessEventsAndRespond(RequestCycle.java:902) at wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:934) at wicket.RequestCycle.step(RequestCycle.java:1010) at wicket.RequestCycle.steps(RequestCycle.java:1084) at wicket.RequestCycle.request(RequestCycle.java:454) at wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:219) at javax.servlet.http.HttpServlet.service(HttpServlet.java:751) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:272) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:165) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3153) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1973) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1880) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1310) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207) at weblogic.work.ExecuteThread.run(ExecuteThread.java:179) Caused by: java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:105) at java.net.SocketOutputStream.write(SocketOutputStream.java:149) at weblogic.utils.io.ChunkedOutputStream.writeTo(ChunkedOutputStream.java:185) at weblogic.servlet.internal.ResponseHeaders.writeHeaders(ResponseHeaders.java:346) at weblogic.servlet.internal.ServletResponseImpl.writeHeaders(ServletResponseImpl.java:1098) at weblogic.servlet.internal.ServletOutputStreamImpl.sendHeaders(ServletOutputStreamImpl.java:238) at weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:107) at wicket.Resource.respond(Resource.java:245) ... 24 more Thanks, Konstantinos Finding fabulous fares is fun. Let Yahoo! FareChase search your favorite travel sites to find flight and hotel bargains. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- Vote for Wicket at the http://www.thebeststuffintheworld.com/vote_for/wicket Wicket 1.2.4 is as easy as 1-2-4. Download Wicket now! http://wicketframework.org - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll
Re: [Wicket-user] Unable to render resource stream Exception
Thanks Martjin, your answer makes sense but doesn't actually solve my problem, which in fact is that users complain that the wicket web-app is slow. A check with the server side shows that the thread for 'tmsMserver' is taking up 100% of CPU resource. After a restart of the server and a walk through, the slowness creeps back almost immediately. All I get in the server log are exceptions like the one I posted. I suppose what happens is users do something -- they wait -- they get bored -- they kill the request -- exception gets written. So, the main question is why the wicket application is slow? (also, in web.xml I have no specific statement for development/deployment, and expect deployment to be the default) Konstantinos - Original Message From: Martijn Dashorst [EMAIL PROTECTED] To: wicket-user@lists.sourceforge.net Sent: Friday, January 26, 2007 3:10:34 PM Subject: Re: [Wicket-user] Unable to render resource stream Exception Broken pipe means that users (or their browsers) have killed the request. This log report has been disabled in newer versions. Not sure if that is the case for 1.2.4, but most certainly for 1.3 and 2.0. Martijn On 1/26/07, Konstantinos Lazouras [EMAIL PROTECTED] wrote: Hi all, does anyone know why this exception appears at the logs? (using wicket 1.2.3) 10:18:52,547 ERROR RequestCycle:1043 - Unable to render resource stream zip:/prod/applc/bea9/weblogic91/config/tmsdomain/./servers/tmsMserver/tmp/_WL_user/fc/2eqljk/war/WEB-INF/lib/wicket-extensions-1.2.3.jar!/wicket/extensions/markup/html/datepicker/style/aqua/title-bg.gif wicket.WicketRuntimeException: Unable to render resource stream zip:/prod/applc/bea9/weblogic91/config/tmsdomain/./servers/tmsMserver/tmp/_WL_user/fc/2eqljk/war/WEB-INF/lib/wicket-extensions-1.2.3.jar!/wicket/extensions/markup/html/datepicker/style/aqua/title-bg.gif at wicket.Resource.respond(Resource.java:279) at wicket.Resource.onResourceRequested(Resource.java:135) at wicket.request.target.resource.SharedResourceRequestTarget.respond(SharedResourceRequestTarget.java:192) at wicket.request.compound.DefaultResponseStrategy.respond(DefaultResponseStrategy.java:49) at wicket.request.compound.AbstractCompoundRequestCycleProcessor.respond(AbstractCompoundRequestCycleProcessor.java:66) at wicket.RequestCycle.doProcessEventsAndRespond(RequestCycle.java:902) at wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:934) at wicket.RequestCycle.step(RequestCycle.java:1010) at wicket.RequestCycle.steps(RequestCycle.java:1084) at wicket.RequestCycle.request(RequestCycle.java:454) at wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:219) at javax.servlet.http.HttpServlet.service(HttpServlet.java:751) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:272) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:165) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3153) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1973) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1880) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1310) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207) at weblogic.work.ExecuteThread.run(ExecuteThread.java:179) Caused by: java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:105) at java.net.SocketOutputStream.write(SocketOutputStream.java:149) at weblogic.utils.io.ChunkedOutputStream.writeTo(ChunkedOutputStream.java:185) at weblogic.servlet.internal.ResponseHeaders.writeHeaders(ResponseHeaders.java:346) at weblogic.servlet.internal.ServletResponseImpl.writeHeaders(ServletResponseImpl.java:1098) at weblogic.servlet.internal.ServletOutputStreamImpl.sendHeaders(ServletOutputStreamImpl.java:238) at weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:107) at wicket.Resource.respond(Resource.java:245) ... 24 more Thanks, Konstantinos Finding fabulous
Re: [Wicket-user] Unable to render resource stream Exception
Wicket is pretty efficient, so likely there is something very resource heavy in your application, or there is a fat memory leak (resulting in the VM having to do a lot of GC). Can you track down what happens? If you use a profiler like the excellent YourKit (http://www.yourkit.com/), you should be able to track down bottlenecks and/ or memory leaks pretty quickly. Eelco On 1/26/07, Konstantinos Lazouras [EMAIL PROTECTED] wrote: Thanks Martjin, your answer makes sense but doesn't actually solve my problem, which in fact is that users complain that the wicket web-app is slow. A check with the server side shows that the thread for 'tmsMserver' is taking up 100% of CPU resource. After a restart of the server and a walk through, the slowness creeps back almost immediately. All I get in the server log are exceptions like the one I posted. I suppose what happens is users do something -- they wait -- they get bored -- they kill the request -- exception gets written. So, the main question is why the wicket application is slow? (also, in web.xml I have no specific statement for development/deployment, and expect deployment to be the default) Konstantinos - Original Message From: Martijn Dashorst [EMAIL PROTECTED] To: wicket-user@lists.sourceforge.net Sent: Friday, January 26, 2007 3:10:34 PM Subject: Re: [Wicket-user] Unable to render resource stream Exception Broken pipe means that users (or their browsers) have killed the request. This log report has been disabled in newer versions. Not sure if that is the case for 1.2.4, but most certainly for 1.3 and 2.0. Martijn On 1/26/07, Konstantinos Lazouras [EMAIL PROTECTED] wrote: Hi all, does anyone know why this exception appears at the logs? (using wicket 1.2.3) 10:18:52,547 ERROR RequestCycle:1043 - Unable to render resource stream zip:/prod/applc/bea9/weblogic91/config/tmsdomain/./servers/tmsMserver/tmp/_WL_user/fc/2eqljk/war/WEB-INF/lib/wicket-extensions-1.2.3.jar!/wicket/extensions/markup/html/datepicker/style/aqua/title-bg.gif wicket.WicketRuntimeException: Unable to render resource stream zip:/prod/applc/bea9/weblogic91/config/tmsdomain/./servers/tmsMserver/tmp/_WL_user/fc/2eqljk/war/WEB-INF/lib/wicket-extensions-1.2.3.jar!/wicket/extensions/markup/html/datepicker/style/aqua/title-bg.gif at wicket.Resource.respond(Resource.java:279) at wicket.Resource.onResourceRequested(Resource.java:135) at wicket.request.target.resource.SharedResourceRequestTarget.respond(SharedResourceRequestTarget.java:192) at wicket.request.compound.DefaultResponseStrategy.respond(DefaultResponseStrategy.java:49) at wicket.request.compound.AbstractCompoundRequestCycleProcessor.respond(AbstractCompoundRequestCycleProcessor.java:66) at wicket.RequestCycle.doProcessEventsAndRespond(RequestCycle.java:902) at wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:934) at wicket.RequestCycle.step(RequestCycle.java:1010) at wicket.RequestCycle.steps(RequestCycle.java:1084) at wicket.RequestCycle.request(RequestCycle.java:454) at wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:219) at javax.servlet.http.HttpServlet.service(HttpServlet.java:751) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:272) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:165) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3153) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1973) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1880) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1310) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207) at weblogic.work.ExecuteThread.run(ExecuteThread.java:179) Caused by: java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:105) at java.net.SocketOutputStream.write(SocketOutputStream.java:149) at weblogic.utils.io.ChunkedOutputStream.writeTo(ChunkedOutputStream.java:185
Re: [Wicket-user] Unable to render resource stream Exception
is tmsMserver one of our threads? -igor On 1/26/07, Eelco Hillenius [EMAIL PROTECTED] wrote: Wicket is pretty efficient, so likely there is something very resource heavy in your application, or there is a fat memory leak (resulting in the VM having to do a lot of GC). Can you track down what happens? If you use a profiler like the excellent YourKit (http://www.yourkit.com/), you should be able to track down bottlenecks and/ or memory leaks pretty quickly. Eelco On 1/26/07, Konstantinos Lazouras [EMAIL PROTECTED] wrote: Thanks Martjin, your answer makes sense but doesn't actually solve my problem, which in fact is that users complain that the wicket web-app is slow. A check with the server side shows that the thread for 'tmsMserver' is taking up 100% of CPU resource. After a restart of the server and a walk through, the slowness creeps back almost immediately. All I get in the server log are exceptions like the one I posted. I suppose what happens is users do something -- they wait -- they get bored -- they kill the request -- exception gets written. So, the main question is why the wicket application is slow? (also, in web.xml I have no specific statement for development/deployment, and expect deployment to be the default) Konstantinos - Original Message From: Martijn Dashorst [EMAIL PROTECTED] To: wicket-user@lists.sourceforge.net Sent: Friday, January 26, 2007 3:10:34 PM Subject: Re: [Wicket-user] Unable to render resource stream Exception Broken pipe means that users (or their browsers) have killed the request. This log report has been disabled in newer versions. Not sure if that is the case for 1.2.4, but most certainly for 1.3 and 2.0. Martijn On 1/26/07, Konstantinos Lazouras [EMAIL PROTECTED] wrote: Hi all, does anyone know why this exception appears at the logs? (using wicket 1.2.3) 10:18:52,547 ERROR RequestCycle:1043 - Unable to render resource stream zip:/prod/applc/bea9/weblogic91/config/tmsdomain/./servers/tmsMserver/tmp/_WL_user/fc/2eqljk/war/WEB-INF/lib/wicket- extensions-1.2.3.jar!/wicket/extensions/markup/html/datepicker/style/aqua/title-bg.gif wicket.WicketRuntimeException: Unable to render resource stream zip:/prod/applc/bea9/weblogic91/config/tmsdomain/./servers/tmsMserver/tmp/_WL_user/fc/2eqljk/war/WEB-INF/lib/wicket- extensions-1.2.3.jar!/wicket/extensions/markup/html/datepicker/style/aqua/title-bg.gif at wicket.Resource.respond(Resource.java:279) at wicket.Resource.onResourceRequested(Resource.java:135) at wicket.request.target.resource.SharedResourceRequestTarget.respond( SharedResourceRequestTarget.java:192) at wicket.request.compound.DefaultResponseStrategy.respond( DefaultResponseStrategy.java:49) at wicket.request.compound.AbstractCompoundRequestCycleProcessor.respond( AbstractCompoundRequestCycleProcessor.java:66) at wicket.RequestCycle.doProcessEventsAndRespond(RequestCycle.java:902) at wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:934) at wicket.RequestCycle.step(RequestCycle.java:1010) at wicket.RequestCycle.steps(RequestCycle.java:1084) at wicket.RequestCycle.request(RequestCycle.java:454) at wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:219) at javax.servlet.http.HttpServlet.service(HttpServlet.java:751) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run( StubSecurityHelper.java:225) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet( StubSecurityHelper.java:127) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java :272) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java :165) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run (WebAppServletContext.java:3153) at weblogic.security.acl.internal.AuthenticatedSubject.doAs( AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java :121) at weblogic.servlet.internal.WebAppServletContext.securedExecute( WebAppServletContext.java:1973) at weblogic.servlet.internal.WebAppServletContext.execute( WebAppServletContext.java:1880) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java :1310) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207) at weblogic.work.ExecuteThread.run(ExecuteThread.java:179) Caused by: java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:105) at java.net.SocketOutputStream.write(SocketOutputStream.java:149
Re: [Wicket-user] Unable to render resource stream Exception
I never have heard of it... And if you don't like shelling out $$$ for YourKit immediately, they have a 30 day trial. Should be enough to at least find this problem. After that you'll instantly know that the 500 bucks they charge are worth every penny. (I'm not affiliated with them). Martijn On 1/26/07, Igor Vaynberg [EMAIL PROTECTED] wrote: is tmsMserver one of our threads? -igor On 1/26/07, Eelco Hillenius [EMAIL PROTECTED] wrote: Wicket is pretty efficient, so likely there is something very resource heavy in your application, or there is a fat memory leak (resulting in the VM having to do a lot of GC). Can you track down what happens? If you use a profiler like the excellent YourKit (http://www.yourkit.com/), you should be able to track down bottlenecks and/ or memory leaks pretty quickly. Eelco On 1/26/07, Konstantinos Lazouras [EMAIL PROTECTED] wrote: Thanks Martjin, your answer makes sense but doesn't actually solve my problem, which in fact is that users complain that the wicket web-app is slow. A check with the server side shows that the thread for 'tmsMserver' is taking up 100% of CPU resource. After a restart of the server and a walk through, the slowness creeps back almost immediately. All I get in the server log are exceptions like the one I posted. I suppose what happens is users do something -- they wait -- they get bored -- they kill the request -- exception gets written. So, the main question is why the wicket application is slow? (also, in web.xml I have no specific statement for development/deployment, and expect deployment to be the default) Konstantinos - Original Message From: Martijn Dashorst [EMAIL PROTECTED] To: wicket-user@lists.sourceforge.net Sent: Friday, January 26, 2007 3:10:34 PM Subject: Re: [Wicket-user] Unable to render resource stream Exception Broken pipe means that users (or their browsers) have killed the request. This log report has been disabled in newer versions. Not sure if that is the case for 1.2.4, but most certainly for 1.3 and 2.0. Martijn On 1/26/07, Konstantinos Lazouras [EMAIL PROTECTED] wrote: Hi all, does anyone know why this exception appears at the logs? (using wicket 1.2.3) 10:18:52,547 ERROR RequestCycle:1043 - Unable to render resource stream zip:/prod/applc/bea9/weblogic91/config/tmsdomain/./servers/tmsMserver/tmp/_WL_user/fc/2eqljk/war/WEB-INF/lib/wicket- extensions-1.2.3.jar!/wicket/extensions/markup/html/datepicker/style/aqua/title-bg.gif wicket.WicketRuntimeException: Unable to render resource stream zip:/prod/applc/bea9/weblogic91/config/tmsdomain/./servers/tmsMserver/tmp/_WL_user/fc/2eqljk/war/WEB-INF/lib/wicket- extensions-1.2.3.jar!/wicket/extensions/markup/html/datepicker/style/aqua/title-bg.gif at wicket.Resource.respond(Resource.java:279) at wicket.Resource.onResourceRequested (Resource.java:135) at wicket.request.target.resource.SharedResourceRequestTarget.respond(SharedResourceRequestTarget.java:192) at wicket.request.compound.DefaultResponseStrategy.respond (DefaultResponseStrategy.java:49) at wicket.request.compound.AbstractCompoundRequestCycleProcessor.respond(AbstractCompoundRequestCycleProcessor.java:66) at wicket.RequestCycle.doProcessEventsAndRespond(RequestCycle.java:902) at wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:934) at wicket.RequestCycle.step(RequestCycle.java:1010) at wicket.RequestCycle.steps(RequestCycle.java:1084) at wicket.RequestCycle.request(RequestCycle.java:454) at wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:219) at javax.servlet.http.HttpServlet.service(HttpServlet.java:751) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java :272) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:165) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run (WebAppServletContext.java:3153) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs (SecurityManager.java:121) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1973
Re: [Wicket-user] Unable to render resource stream Exception
well i guess we need to know if this is wicket related or something inside weblogic going bad, or the combination of the two -igor On 1/26/07, Martijn Dashorst [EMAIL PROTECTED] wrote: I never have heard of it... And if you don't like shelling out $$$ for YourKit immediately, they have a 30 day trial. Should be enough to at least find this problem. After that you'll instantly know that the 500 bucks they charge are worth every penny. (I'm not affiliated with them). Martijn On 1/26/07, Igor Vaynberg [EMAIL PROTECTED] wrote: is tmsMserver one of our threads? -igor On 1/26/07, Eelco Hillenius [EMAIL PROTECTED] wrote: Wicket is pretty efficient, so likely there is something very resource heavy in your application, or there is a fat memory leak (resulting in the VM having to do a lot of GC). Can you track down what happens? If you use a profiler like the excellent YourKit (http://www.yourkit.com/), you should be able to track down bottlenecks and/ or memory leaks pretty quickly. Eelco On 1/26/07, Konstantinos Lazouras [EMAIL PROTECTED] wrote: Thanks Martjin, your answer makes sense but doesn't actually solve my problem, which in fact is that users complain that the wicket web-app is slow. A check with the server side shows that the thread for 'tmsMserver' is taking up 100% of CPU resource. After a restart of the server and a walk through, the slowness creeps back almost immediately. All I get in the server log are exceptions like the one I posted. I suppose what happens is users do something -- they wait -- they get bored -- they kill the request -- exception gets written. So, the main question is why the wicket application is slow? (also, in web.xml I have no specific statement for development/deployment, and expect deployment to be the default) Konstantinos - Original Message From: Martijn Dashorst [EMAIL PROTECTED] To: wicket-user@lists.sourceforge.net Sent: Friday, January 26, 2007 3:10:34 PM Subject: Re: [Wicket-user] Unable to render resource stream Exception Broken pipe means that users (or their browsers) have killed the request. This log report has been disabled in newer versions. Not sure if that is the case for 1.2.4, but most certainly for 1.3 and 2.0. Martijn On 1/26/07, Konstantinos Lazouras [EMAIL PROTECTED] wrote: Hi all, does anyone know why this exception appears at the logs? (using wicket 1.2.3) 10:18:52,547 ERROR RequestCycle:1043 - Unable to render resource stream zip:/prod/applc/bea9/weblogic91/config/tmsdomain/./servers/tmsMserver/tmp/_WL_user/fc/2eqljk/war/WEB-INF/lib/wicket- extensions-1.2.3.jar!/wicket/extensions/markup/html/datepicker/style/aqua/title-bg.gif wicket.WicketRuntimeException: Unable to render resource stream zip:/prod/applc/bea9/weblogic91/config/tmsdomain/./servers/tmsMserver/tmp/_WL_user/fc/2eqljk/war/WEB-INF/lib/wicket- extensions-1.2.3.jar!/wicket/extensions/markup/html/datepicker/style/aqua/title-bg.gif at wicket.Resource.respond(Resource.java:279) at wicket.Resource.onResourceRequested (Resource.java:135) at wicket.request.target.resource.SharedResourceRequestTarget.respond( SharedResourceRequestTarget.java:192) at wicket.request.compound.DefaultResponseStrategy.respond (DefaultResponseStrategy.java:49) at wicket.request.compound.AbstractCompoundRequestCycleProcessor.respond( AbstractCompoundRequestCycleProcessor.java:66) at wicket.RequestCycle.doProcessEventsAndRespond(RequestCycle.java:902) at wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:934) at wicket.RequestCycle.step(RequestCycle.java:1010) at wicket.RequestCycle.steps(RequestCycle.java:1084) at wicket.RequestCycle.request(RequestCycle.java:454) at wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:219) at javax.servlet.http.HttpServlet.service(HttpServlet.java:751) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run( StubSecurityHelper.java:225) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet( StubSecurityHelper.java:127) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java :272) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java :165) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run (WebAppServletContext.java:3153) at weblogic.security.acl.internal.AuthenticatedSubject.doAs( AuthenticatedSubject.java:321
