| AUT is getting hanged up and gets timed out randomly [message #1702257] |
Tue, 21 July 2015 06:49  |
 Jeevan Rex
Messages: 80
Registered: March 2015
Location: Bangalore |
Member |
|
|
Hi,
I have some 15 test cases. The AUT gets hang randomly. Often just after restart of the aut or checking out some data from server. Also it happens randomly when it switches between contexts. I am not able to point out a specific time when this happens.
What will be the issue? I am able to do this without RCPTT, but when using RCPTT this issue appears and it happens very often. Is anyone else facing this issue and is there a solution? How can I debug this?
This is one of the scenario which gets hanged randomly which I have noticed
proc "has-item" [val tree -input] [val titem] {
try {
$tree | get-item $titem
bool true // return true
} -catch {
bool false // return false
}
}
if [get-view "Resource Navigator" | get-tree | has-item "QTa" ]{
log "abc item exist"
} -else {
get-menu "Databank/Checkout Composite Tag" | click
with [get-window "Checkout Composite Tag Wizard"] {
get-button "Next >" | click
get-table | select "test server master"
with [get-window "Authentication required"] {
with [get-combo -after [get-label Username]] {
set-text jeevan
key-type "TRAVERSE_TAB_NEXT"
}
get-editbox -after [get-label Password] | set-text [decrypt "8g="]
get-button OK | click
}
get-button "Next >" | click
get-combo | select "Masrer_Test_Data (created by: super @Tue May 26 19:35:44 PDT 2015)"
get-button "Clear All" | click
with [get-table] {
get-item "QTa1.1" | check
select "QTa1.1" | get-item "QTa1.1" | check
select "QTa1.1"
}
get-button Finish | click
// It's Hanging here
}}
This code is in AUT Context where we can write a AUT code. After this I have a context to switch perspective. It is not even entering that context. It goes on playing this context itself.
In log I found something like this:
!ENTRY org.eclipse.rcptt.runtime.ui 1 0 2015-07-21 00:41:36.629
!MESSAGE Tesla server started on port 7003
java.lang.Exception: Bad call to getCoolBarManager()
at org.eclipse.ui.internal.WorkbenchWindow.getCoolBarManager(WorkbenchWindow.java:2634)
at org.eclipse.rcptt.tesla.ui.Q7KeyFormatter.installQ7Formatter(Q7KeyFormatter.java:66)
at org.eclipse.rcptt.tesla.ui.SWTTeslaStartup.earlyStartup(SWTTeslaStartup.java:18)
at org.eclipse.ui.internal.EarlyStartupRunnable.runEarlyStartup(EarlyStartupRunnable.java:87)
at org.eclipse.ui.internal.EarlyStartupRunnable.run(EarlyStartupRunnable.java:66)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.Workbench$55.run(Workbench.java:2555)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Kindly let me know.
Thank you
Jeevan
[Updated on: Tue, 21 July 2015 07:58] Report message to a moderator |
|
|
| Re: AUT is getting hanged up and gets timed out randomly [message #1702411 is a reply to message #1702257] |
Wed, 22 July 2015 08:29  |
|
Hello,
Could you please attach AUT log files (how to get it) and the whole RCPTT log (in rcptt workspace) after hanging?
Have you tried to increase -Xmx AUT parameter? For that you can select AUT in Applications view, click "Configure...", click "Advance..." and change it in Arguments tab.
As I understand, that context sets workspace initial state, please correct me if I'm wrong. Why don't you use workspace context for that purpose?
Yours sincerely,
Olga.
|
|
|
|
| Re: AUT is getting hanged up and gets timed out randomly [message #1702580 is a reply to message #1702573] |
Thu, 23 July 2015 11:53 |
|
Hi,
Thank you for additional details!
It will take some time to investigate it.
Is it correct, that ECL context fails by timeout when application hangs up?
Could you please wait until test execution is failed and send us Details from Execution view and HTML-report?
To get HTML report click "Report" in Execution view -> choose HTML format and set location-> Finish.
Please let me know if you have any questions!
Yours sincerely,
Olga.
|
|
|
|
| Re: AUT is getting hanged up and gets timed out randomly [message #1703669 is a reply to message #1702594] |
Tue, 04 August 2015 06:24 |
Jeevan Rex
Messages: 80
Registered: March 2015
Location: Bangalore |
Member |
|
|
Hi,
I have a new log file attached PFA.
It is taken on the same scenario that is given in my ECL command above.
Before I checkout data I can see the following content in the log.
!ENTRY org.eclipse.osgi 2 0 2015-08-03 03:57:33.505
!MESSAGE While loading class "org.eclipse.rcptt.reporting.core.ReportHelper", thread "Thread[main,6,main]" timed out waiting (5008ms) for thread "Thread[Worker-1,5,main]" to finish starting bundle "org.eclipse.rcptt.reporting_2.0.0.201506110605 [464]". To avoid deadlock, thread "Thread[main,6,main]" is proceeding but "org.eclipse.rcptt.reporting.core.ReportHelper" may not be fully initialized.
!STACK 0!ENTRY org.eclipse.osgi 2 0 2015-08-03 03:57:33.505
!MESSAGE While loading class "org.eclipse.rcptt.reporting.core.ReportHelper", thread "Thread[main,6,main]" timed out waiting (5008ms) for thread "Thread[Worker-1,5,main]" to finish starting bundle "org.eclipse.rcptt.reporting_2.0.0.201506110605 [464]". To avoid deadlock, thread "Thread[main,6,main]" is proceeding but "org.eclipse.rcptt.reporting.core.ReportHelper" may not be fully initialized.
After checkout has happened I find
ENTRY org.eclipse.rcptt.ecl.core 4 0 2015-08-03 04:05:41.409
!MESSAGE Result is already set for click
!STACK 0
java.lang.IllegalStateException: Result is already set for click
at org.eclipse.rcptt.reporting.core.ReportHelper$2.apply(ReportHelper.java:146)
It is not fully initialized in the first message. Since it is an issue with threads and deadlock, it is very expected to be not fully reproducible.
Let me know how to solve this.
Thank you,
Jeevan
Attachment: log.log
(Size: 50.47KB, Downloaded 110 times)
|
|
|
|
Powered by
FUDForum. Page generated in 0.02362 seconds
] 
Search
Help
Register
Login
Home
