Recently for one of my customers who was using Oracle Discoverer Desktop on Windows over terminal services, I have installed Oracle BI Discoverer on Redhat Linux. When users access the reports over Discoverer plus, it took more than 10 minutes to open in the browser. The same report opens in 1-2 secs in both Discoverer viewer and Discoverer desktop.
In this blog, I will explain how the problem is diagnosed and resolved.
The environment is very complex - the users use Novell login to logon on their desktop. There is a firewall sitting between users desktop and BI Discoverer Weblogic server. The BI Discoverer Weblogic server is not accessed directly but over BIGIP. So I don't know where the problem lies intially.
I ruled out any bottlenecks on Weblogic Server, on the database, and on BIGIP as few users can open the same report in the browser on their desktop very quickly in 1-2 secs. I suspected some configuration issues on the users desktop.
The netstat output showed many TCP connections state to be in CLOSE_WAIT. I tried various Java versions on the client desktop as there are few reports suggesting problems with certain Java versions. Then installed WireShark and started collecting the trace when the report is accessed in the browser. The following picture shows snapshot of the trace.
From the above trace, surprisingly I found that lot of time is spent between the client desktop and the Novell directory server. This was due to the default temporary directory setting of Java which was point to a Novell directory. I changed the temporary directory setting to point to a local directory on the desktop as shown belown and it resolved the problem.
In this blog, I will explain how the problem is diagnosed and resolved.
The environment is very complex - the users use Novell login to logon on their desktop. There is a firewall sitting between users desktop and BI Discoverer Weblogic server. The BI Discoverer Weblogic server is not accessed directly but over BIGIP. So I don't know where the problem lies intially.
I ruled out any bottlenecks on Weblogic Server, on the database, and on BIGIP as few users can open the same report in the browser on their desktop very quickly in 1-2 secs. I suspected some configuration issues on the users desktop.
The netstat output showed many TCP connections state to be in CLOSE_WAIT. I tried various Java versions on the client desktop as there are few reports suggesting problems with certain Java versions. Then installed WireShark and started collecting the trace when the report is accessed in the browser. The following picture shows snapshot of the trace.
From the above trace, surprisingly I found that lot of time is spent between the client desktop and the Novell directory server. This was due to the default temporary directory setting of Java which was point to a Novell directory. I changed the temporary directory setting to point to a local directory on the desktop as shown belown and it resolved the problem.
