You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Martin Grigorov <mg...@apache.org> on 2011/07/05 21:37:13 UTC

Re: exception-no clue for the cause

It means that SafeZipFileInputStream is not that safe :-)

On Tue, Jul 5, 2011 at 9:24 PM, fachhoch <fa...@gmail.com> wrote:
> I see an exception from logs no clue what is the cause of this
>
> 2011-07-05 14:05:03,046 [[ACTIVE] ExecuteThread: '21' for queue:
> 'weblogic.kernel.Default (self-tuning)'] ERROR
> org.apache.wicket.RequestCycle -
> java.lang.NullPointerException
>        at java.io.FilterInputStream.close(FilterInputStream.java:155)
>        at
> weblogic.utils.zip.SafeZipFileInputStream.close(SafeZipFileInputStream.java:37)
>        at org.apache.wicket.util.io.Connections.close(Connections.java:113)
>        at
> org.apache.wicket.util.io.Connections.getLastModified(Connections.java:73)
>        at
> org.apache.wicket.util.resource.UrlResourceStream.lastModifiedTime(UrlResourceStream.java:223)
>        at
> org.apache.wicket.markup.html.PackageResource.getResourceStream(PackageResource.java:607)
>        at
> org.apache.wicket.markup.html.PackageResource.getResourceStream(PackageResource.java:565)
>        at org.apache.wicket.Resource.init(Resource.java:213)
>        at org.apache.wicket.Resource.onResourceRequested(Resource.java:117)
>        at
> org.apache.wicket.request.target.resource.SharedResourceRequestTarget.respond(SharedResourceRequestTarget.java:213)
>        at
> org.apache.wicket.request.AbstractRequestCycleProcessor.respond(AbstractRequestCycleProcessor.java:105)
>        at
> org.apache.wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:1258)
>        at org.apache.wicket.RequestCycle.step(RequestCycle.java:1329)
>        at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1436)
>        at org.apache.wicket.RequestCycle.request(RequestCycle.java:545)
>        at
> org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:484)
>        at
> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:317)
>        at
> weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
>        at
> org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:265)
>        at
> org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
>        at
> org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275)
>        at
> org.acegisecurity.util.FilterChainProxy.doFilter(FilterChainProxy.java:149)
>        at
> org.acegisecurity.util.FilterToBeanProxy.doFilter(FilterToBeanProxy.java:98)
>        at
> weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
>        at
> org.springframework.orm.hibernate3.support.OpenSessionInViewFilter.doFilterInternal(OpenSessionInViewFilter.java:198)
>        at
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
>        at
> weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
>        at
> weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684)
>        at
> weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
>        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:2268)
>        at
> weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
>        at
> weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
>        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
>        at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
>
> any suggestion what might   have caused this ?
>
> --
> View this message in context: http://apache-wicket.1842946.n4.nabble.com/exception-no-clue-for-the-cause-tp3646873p3646873.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: exception-no clue for the cause

Posted by Martin Grigorov <mg...@apache.org>.
I'm not sure why it fails.
You'll have to consult with WebLogic support.

Currently this exception drops a request for a resource.
I think Wicket can improve that by using Connections.closeQuietly()
instead of #close(). This way even if the closing fail at least the
request will continue its processing.
File a ticket.

On Tue, Jul 5, 2011 at 9:48 PM, fachhoch <fa...@gmail.com> wrote:
> Thanks for the reply ,can you tell me what could cause this ?  Can I ignore
> this or   this can cause issues ?
>
>
>
>
> --
> View this message in context: http://apache-wicket.1842946.n4.nabble.com/exception-no-clue-for-the-cause-tp3646873p3646914.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: exception-no clue for the cause

Posted by fachhoch <fa...@gmail.com>.
Thanks for the reply ,can you tell me what could cause this ?  Can I ignore
this or   this can cause issues ? 




--
View this message in context: http://apache-wicket.1842946.n4.nabble.com/exception-no-clue-for-the-cause-tp3646873p3646914.html
Sent from the Users forum mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org