Cache Server transport error

[gillrowley]

Getting an HTTP 500 error when trying to access a parameterized report through InfoView. Looking at the event log there are transport error warnings on the Cache Server and sometimes the WCA. When I restart the Cache Server it seems to fix itself for awhile, then breaks again. I've increased the virutal cache on the RAM, and installed SP5, both of which were supposed to fix the problem.

BOE XI R2 SP5, with a WCA outside the firewall accessing the BOE server in house with Infoview embedded in our corporate website. Windows 2003 Servers.

Works fine internally, only get the error when trying to access the report from the outside. This problem has only been occurring for the past 2 months. Before that we went a year with no problems at all.

Thanks.

 

[hilfy]

Has anything changed in your firewall rules? Do you have your BOE services (servers) running on specified ports?

-Dell

A computer only does what you actually told it to do - not what you thought you told it to do.

 

[gillrowley]

Nothing has changed in the firewall settings or the assigned ports. I do have each service configured for specific ports.

 

[hilfy]

When the problem occurs, have you been able to view reports by connecting via a WCA instance on the network? If so, then the problem is in the connection from the web server, through the firewall, to report server. When I've run into similar issues in the past, the problem has been with the firewall or network latency and not with BOE.

-Dell

A computer only does what you actually told it to do - not what you thought you told it to do.

 

[gillrowley]

Haven't tried that yet. I'll check it out. Thanks.

Gill

 

[Turkbear]

Hi,
Your biggest cluse as to where to look is in this part of your post:

Works fine internally, only get the error when trying to access the report from the outside

The only difference is the firewall ( or maybe the server running the WCA, but the firewall is most likely the problem)



To Paraphrase:"The Help you get is proportional to the Help you give.."

 

[gillrowley]

We were getting OutofMemory errors in our websphere logs whenever this report was rendered. Changing the settings for the Java heap and restarting the web server seems to have taken care of the problem.

So, not a BOE problem at all, it seems.