I've created a Jira issue (MAGNOLIA-2989) for the problem.
I probably should have reported this for previous version of Magnolia, but
since it only ever logged a warning before, rather than causing a full error I
just thought i was an inconvenience - and since it was quite an obvious problem
I assumed someone else must have already spotted it.
> 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.
I assume that getOutputStream must itself call getWriter (or maybe vice versa),
but I haven't explored it yet. I will try to do some debugging this evening.
J
On 4 Jan 2010, at 17:33, Philipp Bärfuss wrote:
>
> 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]>
> ----------------------------------------------------------------
>
>
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
