Simple OBIEE table report(1miilion 10 columns) unable to Export to XL using FF browser but Chrome working fine
In OBIEE, simple table 1 million rows with 10 columns BI report, we able to export to Excel2007(download) using Chrome browser successfully but with latest FF or any version, export(download) failed with below error in UI and backend OHS log. we see some timeout happens b/w browser and OHS.
Looks like this is FF issue and help to give some workaround.
we tried below workarounds but didn't help. in FF-> about:config -> network.http.keep-alive.timeout and network.http.response.timeout to 3600.
From FF browser UI, getting "There was an error processing your download. Please check with your administrator" and backend OHS observing below error.
> ohs1.log <
[2018-06-12T10:30:23.0707+00:00] [OHS] [ERROR:32] [] [core.c] [client_id: 10.242.111.7] [host_id: slc05rhc.us.oracle.com] [host_addr: 10.245.71.2] [tid: 139745503561472] [user: oracle] [ecid: 005RawzRIovCgoPLIep2if0003XD0001XN] [rid: 0] [VirtualHost: fuscdrmsmc271-fa-ext.us.oracle.com:443] ap_proxy: trying POST /analytics/saw.dll at backend host 10.245.71.1/11438, client 10.242.111.7/2062, total tries 1; got exception 'WRITE_ERROR_TO_CLIENT [os error=0, line 544 of BaseProxy.cpp]: '; state: writing response body to client; not failing over, referer: https://fuscdrmsmc271-fa-ext.us.oracle.com/analytics/saw.dll?PortalGo&Action=prompt&path=%2Fusers%2Ffaadmin%2F75k_30c_report
> weblogic.log <
2018-06-12T10:35:43.1535+00:00 <1443915287992686407> Write to the client failed: calling URL::close at line 543 of BaseProxy.cpp 2018-06-12T10:35:43.1535+00:00 <1443915287992686407> *******Exception type [WRITE_ERROR_TO_CLIENT] raised at line 544 of BaseProxy.cpp 2018-06-12T10:35:43.1537+00:00 <1443915287992686407> request /analytics/saw.dll?Go did NOT process successfully..................
Kaikki vastaukset (3)
Is there any difference between the requests sent by the respective browsers? Please compare all of the headers and parameters using the browsers' respective developer tools, or any applicable logs on the server.
If the requests are different, we could try to sort out why that is.
If the requests are the same, I would ask the vendor of the server-side software if they know what could cause this error.
As I mentioned Chrome working fine but FF/IE it got failed and even we did not change any setting in browser side. we see looks like same requests sent in fiddler.
I think you need to check with the vendor on what can cause WRITE_ERROR_TO_CLIENT other than bad parameters. For example, is it possible Firefox is terminating the connection (timing out) faster than Chrome?
(The entries from your two logs are 5 minutes apart. I assume those are different requests and that generating the file takes far less than 5 minutes.)