|Re: Question: Jubula database on Amazon RDS [message #1143793 is a reply to message #1143303]
||Fri, 18 October 2013 08:31
| Alejo Abdala
Registered: September 2012
Hi Alex, it's not actually that i'm hitting a problem but when trying to connect to the database it seems like it takes quite a long time to load. I couldn't tell how much time because I couldn't see it finishing after half an hour more or less. I can tell that it is loading projects because I can see it in the console:|
Connection to Database successful.
Reading project file /resources/library/unbound_modules_rcp_6.1.xml.
Reading project file /resources/library/unbound_modules_concrete_6.1.xml.
Reading project file /resources/library/unbound_modules_swt_6.1.xml.
Project "unbound_modules_swt" in version 6.1 requires the following project(s):
- project "unbound_modules_concrete" in version 6.1
Reading project file /resources/library/unbound_modules_html_6.1.xml.
Finished reading projects.
Finished importing unbound_modules_rcp_6.1.
I was wondering if there was something in Jubula about how it handles database connections that causes this kind of behavior when working with non-local (ping > 100 ms) databases. I've been playing around a little bit (creating a new project) and it seems like every step (creating a category, a test case, adding steps to a test case) takes a while, between 5~10 secs.
Being that the database is the main support of Jubula's architecture it would be great if we could have that support in a realiable infrastructure such as AWS.
Powered by FUDForum
. Page generated in 0.13584 seconds