This is indeed suspicious. Can you create a jira ticket? According to the spec
this is really an error:
--> Either this method or {...@link #getWriter} may be called to write the
body, not both.
> Anyone else attempting to run Magnolia on glassfish 3?
> I'm using a vanilla Magnolia 4.2.3 bundled-webapp war to test with.
> I'm unable to use the admin interface because of this error - as soon as I
> log in I get this problem and the page isn't rendered.
> This has been an issue in previous version of glassfish too (from at least
> magnolia 3.5 - and I think from earlier) - every admin page has always dumped
> a warning to the glassfish logfile that getWriter() was being called more
> than once,
If I read the posted exception correctly it is not thrown because getWriter()
has been called multiple times but that both getWriter() and getOutputSream()
are called on the same response.
> however in older versions of glassfish this just used to be a warning - now
> it seems to be a full fledged error that stops the page from rendering. This
> was only a problem with the admin interface - normal pages didn't have the
> problem.
> Obviously this makes Magnolia completely unusable on Glassfish 3 at the
> moment, unless someone has found a workaround. It also sounds like a
> legitimate problem that probably should be looked into because presumably it
> could be causing weird behaviour on other platforms too.
> Any ideas?
>
> Josh
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <[email protected]>
> ----------------------------------------------------------------
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
