Self-Solve Knowledge Search

Minimize Maximize
TeMIP Client never start after close
Title :
TeMIP Client never start after close
Document ID :
KM01497321
Product - Version:
temip client 6.3 ;
OS :
Updated :
Tue Apr 07 03:22:31 GMT 2015
Summary :
TeMIP Client never start after close TeMIP Client by close button. After problem happen, TeMIP Client never startup
Problem
TeMIP Client never start after close TeMIP Client by close button. After problem happen, TeMIP Client never startup
Cause

- Through investigation, this error often happened when TeMIP client is launched with
specified workspace.
- When TeMIP Client is launched with no workspace, this issue is not happened.
- When we load workspace after 10 secs Client launching (without workspace load),
this issue is not happened, but when we load workspace as soon as launching TeMIP Client,
this issue happens.
- Through these result, loading workspace is possible cause of this issue (memory violation)

According to document, we added the following parameter in startup.conf,
After this parameter modification, we have not seen this issue with over 10 times trial, different patch level.

TAL_DICTIONARY_CACHE_MAX_ENTRIES=20000
(Default is 20)

Fix

After further investigation, we found that TEMIP_LOADING_VIEWS=0 seems to work fine for resolving this issue through many tests (no failure happened with TEMIP_LOADING_VIEWS=0).
The parameter "TEMIP_LOADING_VIEWS" is available in both TeMIP Client V630 and V640. It can be set in startup.conf file.
It has 0/1 two values. To decide whether load all the entity classes in cache while start the TeMIP Client. The default value is “1”.
1.    If “TEMIP_LOADING_VIEWS=0”, the TeMIP Client will not load all the entity classes to the cache while start the TeMIP Client. Just some of the necessary classes will be stored in cache. That will reduce the TeMIP Client loading time if the server has a huge dictionary or the network is heavy.
2.    If “TEMIP_LOADING_VIEWS=1”. That is the default value, the TeMIP Client will load all the entity classes to the cache in starting procedure.