Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Jubula » Jubula takes longer to save the changes
Jubula takes longer to save the changes [message #1105807] Tue, 10 September 2013 05:46 Go to next message
Bhupendra Mahajan is currently offline Bhupendra Mahajan
Messages: 10
Registered: September 2013
Junior Member
Hi,

I have few hundred testcases in my test suite(s)

From last couple of days the Jubula takes quite longer (on an aerage 2mints) to save the changes made at suite/testcase level and every time it displays a progress bar "Checking for project completeness ..."

I have verified with the database admin that there is no issue with the database, which must be causing the delay

I have also tried to,
- Delete the workspace and start a fresh
- Increase memory in jubula.ini
- Delete the older test results


Is there any other way to figure out the root cause ?

Any help/suggestion is much appreciated.


Following stats may be helpful
"TESTRESULT"                       54.85 MB   20871 rows
"PARAMETER_DETAILS"                2.202 MB   37376 rows
"NODE"                             1.035 MB    6588 rows
"TESTRESULT_SUMMARY"               1.158 MB    2552 rows
"LOCALE_TO_TD"                     764.0 KB   20526 rows
"TD_MANAGER_PARAM_ID"              442.6 KB   10594 rows
"COMP_NAME_PAIRS"                  307.3 KB    2571 rows
"PARAM_DESC"                       303.4 KB    4318 rows
"HIERARCHY_NAMES"                  260.5 KB    5310 rows
"COMPONENT_NAMES"                  157.4 KB    1328 rows
"PARAM_INTERFACE"                  175.0 KB    6398 rows
"PARAM_NAMES"                      143.9 KB    2377 rows
"TEST_DATA"                        177.8 KB    8505 rows
"NEIGHBOURS"                       119.7 KB    2611 rows
"NODE_LIST"                        105.7 KB    6092 rows
"COMP_ID"                          63.29 KB     529 rows
"LOGICAL_NAME"                     54.42 KB    1126 rows
"TD_MANAGER"                       87.50 KB    6398 rows
"TD_MANAGER_TEST_DATA_LIST"        52.37 KB    2989 rows
"TEST_DATA_LIST"                   43.74 KB    2989 rows
"APPLICATION"                      5.929 KB       2 rows
"AUT"                              8.937 KB       4 rows
"AUT_AUT_CONF"                     5.570 KB       4 rows
"AUT_CONF"                         6.539 KB       4 rows
"AUT_CONF_ATTR"                    7.062 KB      33 rows
"AUT_CONT"                         6.070 KB       8 rows
"AUT_LANGUAGES"                    5.523 KB       4 rows
"CHECKCONFPO_ATTR"                 6.429 KB      24 rows
"CHECKCONFPO_CONTEXTS"             10.06 KB     148 rows
"CHECK_CONF"                       7.875 KB      76 rows
"CHECK_CONF_CONT"                  6.539 KB       8 rows
"CHECK_CONF_CONT_MAP"              11.58 KB      76 rows
"DB_GUARD"                         5.054 KB       1 rows
"DB_VERSION"                       6.414 KB       1 rows
"DEF_EVENTH"                       9.242 KB      92 rows
"EVENT_HANDLERS"                   22.12 KB     414 rows
"EXEC_CONT"                        6.070 KB       8 rows
"EXEC_CONT_NODE"                   6.335 KB      23 rows
"LOCKED_OBJECTS"                   5.968 KB       1 rows
"OBJ_MAP"                          8.382 KB       4 rows
"OM_ASSOC"                         23.67 KB     550 rows
"OM_CATEGORY"                      7.203 KB      12 rows
"OM_PROFILE"                       7.382 KB       4 rows
"PROJECT_NAMES"                    6.789 KB       8 rows
"PROJECT_PROPERTIES"               9.625 KB       8 rows
"PROJ_LANGUAGES"                   6.140 KB      48 rows
"REUSED_PROJECTS"                  8.484 KB      13 rows
"SEQUENCE"                         5.523 KB       3 rows
"SPEC_CONT"                        6.070 KB       8 rows
"SPEC_CONT_NODE"                   6.640 KB      44 rows
"TEST_DATA_CAT"                    6.929 KB       8 rows
"USED_TOOLKITS"                    7.703 KB       7 rows
"AUT_IDS"                              0 KB       0 rows
"DB_LOCKS"                             0 KB       0 rows
"MONITORING_REPORT"                    0 KB       0 rows
"MONITORING_VALUE"                     0 KB       0 rows



Regards,
Bhupendra
  • Attachment: project.JPG
    (Size: 10.40KB, Downloaded 9 times)

[Updated on: Tue, 10 September 2013 06:16]

Report message to a moderator

Re: Jubula takes longer to save the changes [message #1107211 is a reply to message #1105807] Thu, 12 September 2013 01:06 Go to previous messageGo to next message
Bhupendra Mahajan is currently offline Bhupendra Mahajan
Messages: 10
Registered: September 2013
Junior Member
Hi,

Can anyone please comment why every time jubula checks for project completeness ?

Are there any settings to turn it off ?

Thanks,
Bhupendra
Re: Jubula takes longer to save the changes [message #1107300 is a reply to message #1105807] Thu, 12 September 2013 04:06 Go to previous messageGo to next message
Bhupendra Mahajan is currently offline Bhupendra Mahajan
Messages: 10
Registered: September 2013
Junior Member
This has been resolved now.

The issue was due to event handler configurations, where one event handler 1 was calling 2 and 2 was calling 3 ... the depth was till 5

Removing them, helped jubula to restore workable env.


Thanks,
Bhupendra
Re: Jubula takes longer to save the changes [message #1110797 is a reply to message #1107300] Tue, 17 September 2013 06:34 Go to previous message
Alexandra Schladebeck is currently offline Alexandra Schladebeck
Messages: 875
Registered: July 2009
Senior Member
Thanks for the update Bhupendra.
Previous Topic:Problem by deploying the fragment for the AUT extension
Next Topic:Problem by extending an existing TesterClass
Goto Forum:
  


Current Time: Mon Oct 07 19:47:22 EDT 2013

Powered by FUDForum. Page generated in 0.01459 seconds