[SOLVED]EXL07 output gives HTTP 500 error

November 16, 2017, 04:48 AM

Martin vK

Hi,

I am outputting for a long time already to EXL07 but yesterday I ran into a strange problem.
I have a simple table request providing 315K rows output, which is working fine with EXL2K output, but not with EXL07 output.

TABLE FILE HLDCTGVGS
PRINT *
ON TABLE HOLD AS 'G:\DATA\CTG\MARTIN.XLS' FORMAT EXL2K
END
-RUN
-TYPE &LINES
TABLE FILE HLDCTGVGS
PRINT *
ON TABLE HOLD AS 'G:\DATA\CTG\MARTIN.XLSX' FORMAT EXL07
END
-RUN
-TYPE &LINES

WebFOCUS does not give any error and both &LINES give same number of 315349 lines.
The resulting XLS is fine, but the XLSX is only 660 bytes large.

When I open the 660 bytes XLSX with Notepad++it contains following:

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
   "http://www.w3.org/TR/html4/loose.dtd">
<HTML>
<HEAD>
<STYLE type="text/css">
	.bdymre { background-image:url('/ibi_html/workbnch/bdy_bgw.gif'); background-repeat:no-repeat}
</STYLE>
	<TITLE>Application Server Error Page</TITLE>
</HEAD>
<body BGCOLOR="#FFFFFF" class="bdymre">
	[b]<FONT SIZE="-1" FACE="Arial">An HTTP 500 error has been returned while processing the web components.  The application server log contains information on why this error has occurred.  Contact your application administrator or your software vendor support center for further assistance.</FONT>[/b]
</BODY>
</HTML>

Has anyone encountered this before and can explain to me what the problem is? It refers to the "application server log". Where do I find this for finding more information?

I am outputting in this same environment frequently without any problem to EXL07, so I do not understand why this one is not working.

This message has been edited. Last edited by: Martin vK,

November 16, 2017, 04:59 AM

Frans

Could you check the edaprint.log? I once had a similar issue and it showed an out of memory error in the logs.

Reason xlsx needs more momory is because it's doing a compression of the data.

November 16, 2017, 05:37 AM

Chaudhary

http://forums.informationbuild...1057331/m/2897030406

November 16, 2017, 06:13 AM

Martin vK

Hi Frans,

I did check the edaprint.log, but it is not showing any error. I also checked the Tomcat log files (jakarta/stderr/stdout) and that is not showing anything either.

I found an old FP post of 2010 which refers to java app server log and increasing java memory size.
I am not sure where exactly to look....
I am now looking at the Java Services in the Webconsole. I do note that the agent taking care of the request indicates a memory usage of 1GB, and I do see that at the Java Services in the JVM Settings where is a initial and maximum Java Heap Size of 1024MB, so this might be indeed the limit.
After increasing this to 2048MB and restarting, the job still gives http 500, so this is not helping or still not enough.

It seems EXL07 just takes too much memory when used with large files, although I do not consider this large yet....
With small reports EXL07 is okay, but with larger data sets it seems we have to stick with EXL2K.

November 16, 2017, 07:43 AM

Frans

Hi Martin,

Could it be that there are some special charachters in the endresult? I can remember url's could also cause issues.

You could also consider to upgrade to 8.2...lot's of stuf has been improved with exl07 exports.

November 16, 2017, 08:43 AM

BabakNYC

What version of WebFOCUS are you using?
What happens if you switch to PCHOLD FORMAT XLS instead of HOLD?

November 16, 2017, 01:07 PM

Martin vK

I finally found and solved the problem.
It had to do with the EXCELSERVURL setting. We had this pointing to the WebFOCUS client, which works fine with a web application or ReportCaster output going through the WF client. But as this was a hold file stored on a data disk on the Reporting Server (separate server from WF client) this seemed to cause the problem. With small files no problem, but getting a bit larger, it becomes very slow and reaching this limit.

By SET EXCELSERVURL = '' for these cases I have solved this, and I do get the xlsx again, even for much larger files.

Thanks for all your questions and remarks.