You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by j alex <st...@gmail.com> on 2007/10/18 17:29:51 UTC

Jasper basic issue (with websphere?)

Hi,

I just started using the S2 - Jasper plugin ; new to Jasper as well ; but
not able to get a simple report to show.

Below is my struts xml entry :

    <package name="cap-default"
extends="struts-default,jasperreports-default">

            <action name="newapp" class="com.mypage.TestAction">
                  <result name="success" type="jasper">
                   <param name="location">/jasper_compiled.jasper</param>
                   <param name="dataSource">ds</param>
                   <param name="format">PDF</param>
                 </result>
            </action>
    </package>

and in TestAction :

        JREmptyDataSource ds = new JREmptyDataSource();
        return SUCCESS;

The jasper_compiled.jasper is a compiled report (generated using a
standalone Java program) in WebContent.

The console trace is :

[10/18/07 11:23:20:839 EDT] 0000002e ValueStackDat W
org.apache.commons.logging.impl.Jdk14Logger warn Data source value for data
source ds was null
[10/18/07 11:23:22:742 EDT] 0000002e ServiceLogger I
com.ibm.ws.ffdc.IncidentStreamImpl initialize FFDC0009I: FFDC opened
incident stream file
d:\IRAD\SDP70\runtimes\base_v61\profiles\AppSrv03\logs\ffdc\server1_76007600_07.10.18_11.23.22_0.txt
[10/18/07 11:23:22:812 EDT] 0000002e ServiceLogger I
com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC
closed incident stream file
d:\IRAD\SDP70\runtimes\base_v61\profiles\AppSrv03\logs\ffdc\server1_76007600_07.10.18_11.23.22_0.txt
[10/18/07 11:23:22:822 EDT] 0000002e SRTServletRes W   WARNING: Cannot set
status. Response already committed.
[10/18/07 11:23:22:822 EDT] 0000002e SRTServletRes W   WARNING: Cannot set
header. Response already committed.
[10/18/07 11:23:22:903 EDT] 0000002e ServiceLogger I
com.ibm.ws.ffdc.IncidentStreamImpl open FFDC0009I: FFDC opened incident
stream file
d:\IRAD\SDP70\runtimes\base_v61\profiles\AppSrv03\logs\ffdc\server1_76007600_07.10.18_11.23.22_1.txt
[10/18/07 11:23:23:003 EDT] 0000002e ServiceLogger I
com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC
closed incident stream file
d:\IRAD\SDP70\runtimes\base_v61\profiles\AppSrv03\logs\ffdc\server1_76007600_07.10.18_11.23.22_1.txt
[10/18/07 11:23:23:003 EDT] 0000002e WebApp        A   SRVE0180I:
[JasperDemoEAR#JasperDemo.war] [/JasperDemo] [Servlet.LOG]: Error page
exception  The server cannot use the error page specified for your
application because of the exception printed below.
[10/18/07 11:23:23:003 EDT] 0000002e WebApp        A   SRVE0181I:
[JasperDemoEAR#JasperDemo.war] [/JasperDemo] [Servlet.LOG]: Error Page
Exception: : com.ibm.ws.webcontainer.webapp.WebAppErrorReport:
    at com.ibm.ws.webcontainer.webapp.WebApp.sendError(WebApp.java:2746)
    at
com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.handleRequest(
DefaultExtensionProcessor.java:601)
    at
com.ibm.ws.wswebcontainer.extension.DefaultExtensionProcessor.handleRequest(
DefaultExtensionProcessor.java:111)
    at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3129)
    at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java
:238)
    at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java
:811)
    at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(
WebContainer.java:1433)
    at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(
WCChannelLink.java:93)
    at
com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(
HttpInboundLink.java:465)
    at
com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(
HttpInboundLink.java:394)
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(
HttpInboundLink.java:274)
    at
com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators
(NewConnectionInitialReadCallback.java:214)
    at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete
(NewConnectionInitialReadCallback.java:113)
    at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted
(AioReadCompletionListener.java:152)
    at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(
AbstractAsyncFuture.java:213)
    at com.ibm.io.async.AbstractAsyncFuture.fireCompletionActions(
AbstractAsyncFuture.java:195)
    at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
    at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:194)
    at com.ibm.io.async.ResultHandler.runEventProcessingLoop(
ResultHandler.java:741)
    at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:863)
    at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1510)
Caused by: com.ibm.ws.webcontainer.srt.WriteBeyondContentLengthException
    at com.ibm.wsspi.webcontainer.util.BufferedServletOutputStream.print(
BufferedServletOutputStream.java:369)
    at javax.servlet.ServletOutputStream.println(ServletOutputStream.java
:286)
    at com.ibm.ws.webcontainer.webapp.WebApp.sendError(WebApp.java:2682)
    ... 20 more


I'm not sure if this is a websphere specific issue since all the messages
are coming from the container.

Please advise.

Thanks,
Joseph