Error "Document could not be opened"

When we try to open any of the jasper reports in pdf, csv or rtf format, it results in an error saying that the document can't be opened. However, when we first save the report then it can be opened. This problem only occurs when we connect directly to Websphere 6.1. When there is a HTTP server in between, everything works ok.

Analysis:
We studied the HTTP header information being transmitted in both the cases; with HTTP Server and without HTTP server. Realized that the issue does occur because in case of no HTTP Server the HTTP had the cache settings as "Cache-Control: no-cache"

Following is what we have suggested the customer:
If you have 'CookiesConfigureNoCache' property already configured in your server, then please change its value to False, restart the server and try to replicate the problem. Otherwise, please add this property following the steps mentioned below.

Steps to configure custom property CookiesConfigureNoCache on WAS 6.1:

Login to the Administrative console of application server.

1. Click Servers > Application servers > server_name .
2. Under Container Settings, expand Web Container Settings and click Web container transport chains.

There are four Web container transport chains:
WCInboundAdmin
WCInboundAdminSecure
WCInboundDefault
WCInboundDefaultSecure
Click on WCInboundDefault if you are not using https (SSL disabled) or click on WCInboundDefaultSecure if you are
using https (SSL enabled).

Please refer the Note below before proceeding further.

3. Under Transport Channels, click HTTP Inbound Channel (HTTP_2).
4. Under Additional properties, click Custom Properties > New .
5. Under General Properties specify the name of the custom property i.e. CookiesConfigureNoCache in the Name field and a
value 'False' for this property in the Value field. You can also specify a description of this property in the Description field.
6. Click Apply or OK.
7. Click Save to save your configuration changes.
8. Restart the server.

Note:
An application server inherits the custom property values that are specified for the WCInboundAdmin or WCInboundAdminSecure transport chain because one of these chains is usually the first chain to get activated when the application server is initialized. Therefore, before specifying any custom properties for a Web container transport chain, you should disable the WCInboundAdmin and WCInboundAdminSecure transport chains. After specifying the custom property, enable both the transport chains. For more information on this issue please refer the following links.

http://www-01.ibm.com/support/docview.wss?uid=swg1PK51274 http://www.ibm.com/developerworks/forums/thread.jspa?threadID=28910

Comments

Popular posts from this blog

Hibernate: a different object with the same identifier value was already associated with the session

BeanDefinitionStoreException: Failed to parse configuration class: Could not find class [javax.jms.ConnectionFactory]