CLOSED: MAPVIEWER LONG PREPARATION TIME AFTER LONG IDLE TIME

Question

SR # 6896831.994
Customer: NEDGRAPHICS BV
Mapviewer Release: 9.0.4
This issue was posted to the Field Service Forum. They responded with
For Map, we do create the datasource and related maps, themes, styles to be used for Map. The exeuction part is done by Mapviewer and we don't have much control on the mapviewer code on performance tuning point of view.
Please post this question in mapviewer forum
Issue:
After MapViewer being idle for some time (+/- 60 minutes) it takes a long time to generate the first map image --> 5 minutes.
In the MapViewer logfile with log-level=finest, I see that there is a very long preparation time.
After producing the first map image the next (same!) image is produced very fast.
What could be the reason?
What does MapViewer do during "preparation"?
Customer statement:
I am a very experienced Oracle specialist and a very experienced MapViewer developer.
Could you please pass on my request to the MapViewer developers?
I have to know what is going on during preparation time.
Is there a possibility to get more detailed logging of the preparation time?
SEE log file at:
http://workbench.oraclecorp.com/cgi-bin/tools/its_reltar?tar=6896831.994
FILE: mapviewer_37.log
Additional customer info.
UPDATE from customer
================
The first time after long idle time it takes between 100 and 300 seconds.
After that it takes less than 2 seconds.
Can it be a dabase connection issue?
Will it make a difference if I use a database connection via data-sources.xml
instead of a direct data-source in mapviewerConfig.xml?
This is what I mean :
Method 1:
<map_data_source name="NBG"
jdbc_host="plutonium"
jdbc_sid="ods"
jdbc_port="1521"
jdbc_user="nbgex"
jdbc_password="ELvaJ7axzKQl0aKtjikuKT7JUFTjukU3"
jdbc_mode="thin"
number_of_mappers="3"
/>
Method 2:
<map_data_source name="NBG"
container_ds="jdbc/NBG"
number_of_mappers="3"
/>
data-sources.xml:
<data-source
class="oracle.jdbc.pool.OracleDataSource"
name="NBG"
location="jdbc/OracleCache"
ejb-location="jdbc/NBG"
xa-location="jdbc/xa/OracleXADS"
connection-driver="oracle.jdbc.driver.OracleDriver"
username="nbgex"
password="nbgex
url="jdbc:oracle:thin:@plutonium:1521:ods"
inactivity-timeout="30">
<property name="connectionCacheName" value="ICC"/>
<property name="connectionCachingEnabled" value="true"/>
<property name="fastConnectionFailoverEnabled" value="true"/>
</data-source>
Thanks
Message was edited by:
user639281

Answer 1

RESPONSE from customer
====================
The database is restarted once a day in the morning. That could explain the problems in the morning. But there are also problems during day time after some hours of idle time when the database in not restarted.
After testing we noticed that we don't have the problem if we use database connection through OC4J (data-sources.xml).
If we use that method every database connection is cleaned up if it is not used for 15 seconds or so.
If we use the other method (database connection in mapviewerconfig.xml) then the database connection is open for a long time and then we have the problem with the long preparation time.
This problem only occurs in a DMZ environment. MapViewer is installed on a DMZ server and connects through the firewall with a intranet database.
Is it possible that the firewall software prevents communication of an open database connection after a long period of idle time?
Thanls.