Re: after migration to 1.5 I get "java.lang.IllegalStateException: Header was already written to response!"

[Paul Bors]

On a side note, I had similar issues with IE9 and Wicket 1.5.x but solved
them by upgrading the application server.

In my case it was fixed in GlassFish v3.1.2.2 via
GLASSFISH-17150"GF throws
NPE when IE9 closes connection before the execution of doGet in
a servlet is ready."
~ Thank you,
   Paul Bors
On Wed, Jan 30, 2013 at 7:07 AM, Paul Szulc  wrote:

> Wow! Thank you very much for the response, I will try it right away.
>
> On Wed, Jan 16, 2013 at 2:47 AM, Barrett Snyder 
> wrote:
>
> > I had this same issue and tracked it down to IE9. In my case IE9 was
> first
> > requesting a page in Quirks mode and then midway through requesting
> > resources it would switch to standards mode which caused it to abort all
> > currently active requests and request all resources again. The aborted
> > requests were sometimes for wicket served resources like
> > wicket-ajax-jquery.js which caused wicket to log the referenced stack.
> > Adding a header with x-ua-compatible set to IE=9 fixed the issue by
> making
> > sure IE9 starts in standards mode.
> >
> >
> > On Fri, Aug 24, 2012 at 6:11 AM, dpmihai  wrote:
> >
> > > We also have this problem after migrating to 1.5. Everything seems to
> > work
> > > ok, but the logs get full with this error. We did not find a solution
> to
> > > this.
> > >
> > >
> > >
> > > --
> > > View this message in context:
> > >
> >
> http://apache-wicket.1842946.n4.nabble.com/after-migration-to-1-5-I-get-java-lang-IllegalStateException-Header-was-already-written-to-response-tp4651455p4651475.html
> > > Sent from the Users forum mailing list archive at Nabble.com.
> > >
> > > -
> > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > > For additional commands, e-mail: users-h...@wicket.apache.org
> > >
> > >
> >
>

Re: after migration to 1.5 I get "java.lang.IllegalStateException: Header was already written to response!"

[Paul Szulc]

Wow! Thank you very much for the response, I will try it right away.

On Wed, Jan 16, 2013 at 2:47 AM, Barrett Snyder  wrote:

> I had this same issue and tracked it down to IE9. In my case IE9 was first
> requesting a page in Quirks mode and then midway through requesting
> resources it would switch to standards mode which caused it to abort all
> currently active requests and request all resources again. The aborted
> requests were sometimes for wicket served resources like
> wicket-ajax-jquery.js which caused wicket to log the referenced stack.
> Adding a header with x-ua-compatible set to IE=9 fixed the issue by making
> sure IE9 starts in standards mode.
>
>
> On Fri, Aug 24, 2012 at 6:11 AM, dpmihai  wrote:
>
> > We also have this problem after migrating to 1.5. Everything seems to
> work
> > ok, but the logs get full with this error. We did not find a solution to
> > this.
> >
> >
> >
> > --
> > View this message in context:
> >
> http://apache-wicket.1842946.n4.nabble.com/after-migration-to-1-5-I-get-java-lang-IllegalStateException-Header-was-already-written-to-response-tp4651455p4651475.html
> > Sent from the Users forum mailing list archive at Nabble.com.
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > For additional commands, e-mail: users-h...@wicket.apache.org
> >
> >
>

Re: after migration to 1.5 I get "java.lang.IllegalStateException: Header was already written to response!"

[Barrett Snyder]

I had this same issue and tracked it down to IE9. In my case IE9 was first
requesting a page in Quirks mode and then midway through requesting
resources it would switch to standards mode which caused it to abort all
currently active requests and request all resources again. The aborted
requests were sometimes for wicket served resources like
wicket-ajax-jquery.js which caused wicket to log the referenced stack.
Adding a header with x-ua-compatible set to IE=9 fixed the issue by making
sure IE9 starts in standards mode.


On Fri, Aug 24, 2012 at 6:11 AM, dpmihai  wrote:

> We also have this problem after migrating to 1.5. Everything seems to work
> ok, but the logs get full with this error. We did not find a solution to
> this.
>
>
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/after-migration-to-1-5-I-get-java-lang-IllegalStateException-Header-was-already-written-to-response-tp4651455p4651475.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

Re: after migration to 1.5 I get "java.lang.IllegalStateException: Header was already written to response!"

[dpmihai]

We also have this problem after migrating to 1.5. Everything seems to work
ok, but the logs get full with this error. We did not find a solution to
this.



--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/after-migration-to-1-5-I-get-java-lang-IllegalStateException-Header-was-already-written-to-response-tp4651455p4651475.html
Sent from the Users forum mailing list archive at Nabble.com.

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

after migration to 1.5 I get "java.lang.IllegalStateException: Header was already written to response!"

[Paul Szulc]

Hi, we've recently migrated form wicket 1.4 to 1.5 and we started getting
this weird exception. Any idea what might be the problem?
Below details from our bug report tool. We could not reporduce it, this is
just logs from production.


Time: 09/08/2012 12:34:48
Additional information:
logged user: 
-
Detailed stack trace below:

java.lang.IllegalStateException: Header was already written to response!
at
org.apache.wicket.protocol.http.HeaderBufferingWebResponse.checkHeader(HeaderBufferingWebResponse.java:64)
at
org.apache.wicket.protocol.http.HeaderBufferingWebResponse.sendRedirect(HeaderBufferingWebResponse.java:112)
at
org.apache.wicket.request.handler.render.WebPageRenderer.redirectTo(WebPageRenderer.java:136)
at
org.apache.wicket.request.handler.render.WebPageRenderer.respond(WebPageRenderer.java:214)
at
org.apache.wicket.request.handler.RenderPageRequestHandler.respond(RenderPageRequestHandler.java:167)
at
org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:784)
at
org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
at
org.apache.wicket.request.cycle.RequestCycle.executeExceptionRequestHandler(RequestCycle.java:304)
at
org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:227)
at
org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:283)
at
org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:188)
at
org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:244)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1337)
at
org.springframework.orm.jpa.support.OpenEntityManagerInViewFilter.doFilterInternal(OpenEntityManagerInViewFilter.java:147)
at
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1337)
at
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:486)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:119)
at
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:483)
at
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:233)
at
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:973)
at
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:417)
at
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:192)
at
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:907)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
at
org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:250)
at
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:149)
at
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:110)
at org.eclipse.jetty.server.Server.handle(Server.java:346)
at
org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:442)
at
org.eclipse.jetty.server.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:924)
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:582)
at
org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:218)
at
org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:51)
at
org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:586)
at
org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:44)
at
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:598)
at
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:533)
at java.lang.Thread.run(Thread.java:619)
-
WebRequest stack:
Parameters: (size: 2)

4-1.IBehaviorListener.1-editor-tabbed-panel-invoiceCosts-form-table-body-rows-98-cells-10-cell-link
-
random - 0.49670583384351424
Locale: pl
Path:
wicket/page?4-1.IBehaviorListener.1-editor-tabbed-panel-invoiceCosts-form-table-body-rows-98-cells-10-cell-link&random=0.49670583384351424
Is ajax: true

Headers:
Cookie -  
Host -  
Accept - text/xml
wicket-ajax-baseurl - wicket/page?4
X-Forwarded-For -  
wicket-focusedelementid - idb5e
wicket-ajax - true
X-Forwarded-Server -  
Accept-Language - pl
User-Agent - Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1;
Trident/4.0; GTB7.3; .NET CLR 1.0.3705; .NET CLR 1.1.4322