AJaensson
StaffJoined 12 years ago
User Profile
Staff
User Widgets
Contributions
Re: ERROR [LiquibaseDbInitializer] Failed to initialize database after upgrading to 1.4.1 ReadyAPI.
Strange, I just tried it and it should definitely work in 1.6.0. I'll report that so that we can find out if there are problems in certain situations. As for deleting the test history db, you should be able to put this at the start of your jenkins shell command: rm -rf ~/.readyapi/db3.3KViews0likes0CommentsRe: ERROR [LiquibaseDbInitializer] Failed to initialize database after upgrading to 1.4.1 ReadyAPI.
Hi, In 1.5+ you can use the flag -Dtest.history.disabled=true to disable test history completely. In 1.4.x the easiest way to fix this is to delete your test history database. It's located in $HOME/.readyapi/db. Of course this means that you will loose any test history. Hope this helps, Anders Ready! API developer3.3KViews0likes2CommentsRe: ERROR [LiquibaseDbInitializer] Failed to initialize database after upgrading to 1.4.1 ReadyAPI.
Ok, that makes sense although running multiple instances at once should work. I will have to investigate that. Unfortunately there is no way to turn this feature off completely at the moment, but it will be possible in the next release. Regards, Anders Ready! API developer3.8KViews1like2CommentsRe: ERROR [LiquibaseDbInitializer] Failed to initialize database after upgrading to 1.4.1 ReadyAPI.
Hi dabrochu! I'm sorrry that you experience these problems. Ready! API uses an internal database to collect test run history, so you can compare runs with each other etc, so it's not really related to your tests. This feature was introduced in 1.4.0. For some reason this is not working for you and I will try to figure our why. Does it stop you from running tests or is it more of an annoyance that you get these ugly messages in the log? Regards, Anders Ready! API developer3.8KViews0likes4CommentsRe: How to handle transaction management while invoking webservice?
Still not sure if I fully understand the problem. SoapUI acts as a client to your API. It is never the clients responsibility to rollback transactions on the server if something fails in the business logic. I advice you to look at how you handle transactions in the web service, as something seems to be wrong there. Regards, Anders Ready! API developer1.4KViews2likes0CommentsRe: Ready! API 1.4.1 - failure in groovy script after upgrade
Hi, You should be able to work around this by providing a context object instead of null. Try helper.getTestSuiteByName('Set Up Test Case - Clean Up Logs') .run(new StringToObjectMap(), false) Regards, Anders Ready! API developer924Views1like0CommentsRe: How to handle transaction management while invoking webservice?
Hi, I'm not sure which transactions you are talking about. Are you talking about transactions within your web service? Can you try to elaborate a little bit about what you are trying to achieve? Regards, Anders Ready! API developer1.5KViews0likes2CommentsRe: very large HTTP GET Requests are getting ArrayOutOfBoundException: 4096 (HTTP/1.1 413 FULL head)
Hi, This has been fixed in the maintenance builds of Ready! API (available here). Using that build, the -Dsoapui.mock.connector.headerBufferSize=<my new value> option is available again. We do have plans to upgrade jetty, but it is a pretty big change and it has to be prioritized against other tasks. Regards, Anders Ready! API developer5KViews2likes3CommentsRe: Can't add WADL ReadyAPI 1.4.0
Hi bzzup, I was able to reproduce this, and it definitely looks like a problem with the WADL importer in Ready! API. I'll report this in our bug tracker and we'll hopefully have it fixed in future releases. Thanks for reporting this and I hope you can work around it by importing local files until this is fixed. Regards, Anders Ready! API developer1.6KViews2likes1Comment