You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by bu...@apache.org on 2003/08/27 11:23:05 UTC
DO NOT REPLY [Bug 21789] -
Cocoon 2 problems on WAS 5
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21789>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21789
Cocoon 2 problems on WAS 5
sven.macke@rewe.de changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Content-Type not set by |Cocoon 2 problems on WAS 5
|TraxTransformer |
------- Additional Comments From sven.macke@rewe.de 2003-08-27 09:23 -------
A better name for the bug report would be "Cocoon 2 problems on WAS 5". My
first suggestion was wrong, I found a more detailed exception (that was thrown
before the one about the content-type and causes that exception) indicating
that something inside the WAS web container goes wrong.
Here the exception's stack trace:
java.lang.NullPointerException
at com.ibm.ws.webcontainer.srt.SRTServletResponse.setHeader
(SRTServletResponse.java:877)
at com.ibm.ws.webcontainer.srt.SRTServletResponse.addLocaleHeader
(SRTServletResponse.java:313)
at com.ibm.ws.webcontainer.srt.SRTServletResponse.commit
(SRTServletResponse.java:274)
at com.ibm.ws.webcontainer.srt.SRTServletResponse.alertFirstFlush
(SRTServletResponse.java:223)
at com.ibm.ws.webcontainer.srt.BufferedServletOutputStream.
flushBytes (BufferedServletOutputStream.java:347)
at com.ibm.ws.webcontainer.srt.BufferedServletOutputStream.
flush(BufferedServletOutputStream.java:331)
at org.apache.cocoon.caching.CachingOutputStream.flush
(CachingOutputStream.java:118)
at java.io.BufferedOutputStream.flush
(BufferedOutputStream.java(Compiled Code))
at org.apache.xalan.serialize.WriterToUTF8.flush
(WriterToUTF8.java:199)
at org.apache.xalan.serialize.SerializerToXML.flushWriter
(SerializerToXML.java:1468)
at org.apache.xalan.serialize.SerializerToXML.endDocument
(SerializerToXML.java:726)
at org.apache.xalan.transformer.TransformerIdentityImpl.endDocument
(TransformerIdentityImpl.java:907)
at org.apache.cocoon.xml.AbstractXMLPipe.endDocument
(AbstractXMLPipe.java:91)
at org.apache.cocoon.serialization.AbstractTextSerializer$
NamespaceAsAttributes.endDocument
(AbstractTextSerializer.java:516)
at org.apache.cocoon.xml.AbstractXMLPipe.endDocument
(AbstractXMLPipe.java:91)
at org.apache.xalan.transformer.ResultTreeHandler.endDocument
(ResultTreeHandler.java:190)
at org.apache.xalan.transformer.TransformerImpl.transformNode
(TransformerImpl.java:1148)
at org.apache.xalan.transformer.TransformerImpl.run
(TransformerImpl.java:3268)
at java.lang.Thread.run(Thread.java:513)
And I do not think that this some form of the endorsed-libs problem. The stack
trace shows too concrete where the exception occurs: inside the web container.
But I have no idea why and how a NullPointerException should occur at this
place.