Contributions
Re: SOAPUI is not recording the Mocking logs
Hello Mock logging was not enabled in the HTTP preferences tab. Now it is, but the problem still exists. Here is the ouput of the help/system properties dialog: awt.toolkit=sun.awt.windows.WToolkit file.encoding=Cp1252 file.encoding.pkg=sun.io file.separator=\ java.awt.graphicsenv=sun.awt.Win32GraphicsEnvironment java.awt.printerjob=sun.awt.windows.WPrinterJob java.class.path=C:\Program Files\eviware\soapUI-2.5\bin\soapui-2.5.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\activation-1.1.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\javamail-1.4.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\wsdl4j-1.6.2-fixed.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\junit-4.4.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\rsyntaxtextarea-1.0-soapui.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\log4j-1.2.14.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\looks-2.2.0.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\binding-2.0.1.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\forms-1.0.7.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\commons-logging-1.1.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\commons-collections-3.2.1.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\commons-lang-2.4.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\commons-io-1.3.2.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\not-yet-commons-ssl-0.3.10.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\commons-cli-1.0.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\commons-beanutils-1.7.0.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\commons-httpclient-3.1.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\json-lib-2.2.2-jdk15.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\ezmorph-1.0.5.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\xom-1.1.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\swingx-SNAPSHOT.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\l2fprod-common-fontchooser-0.2-dev.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\commons-codec-1.3.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\groovy-all-1.5.7.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\jetty-6.1.11.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\jetty-util-6.1.11.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\servlet-api-2.5-6.1.11.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\xbean-fixed-2.4.0.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\xbean_xpath-2.4.0.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\xmlpublic-2.4.0.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\jsr173_1.0_api-xmlbeans-2.4.0.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\soapui-xmlbeans-2.5.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\policy-xmlbeans-1.5.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\soap-xmlbeans-1.2.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\wadl-xmlbeans-1.0.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\j2ee-xmlbeans-1.4.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\ext-xmlbeans-1.0.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\saxon-9.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\saxon-dom-9.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\xmlunit-1.2.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\xmlsec-1.4.0.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\opensaml-1.1.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\xalan-2.7.0.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\xercesImpl-2.9.1.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\wss4j-1.5.4.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\bcprov-jdk15-138.jar;C:\Program Files\eviware\soapUI-2.5\bin\..\lib\jtidy-20000804r7-noxml.jar java.class.version=49.0 java.endorsed.dirs=D:\Java\JDK\jdk1.5.0_15\jre\lib\endorsed java.ext.dirs=D:\Java\JDK\jdk1.5.0_15\jre\lib\ext java.home=D:\Java\JDK\jdk1.5.0_15\jre java.io.tmpdir=C:\DOCUME~1\GBO\LOCALS~1\Temp\ java.library.path=D:\Java\JDK\jdk1.5.0_15\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\apache-ant-1.7.0\bin;D:\Java\JDK\jdk1.5.0_15\bin;D:\Python\ActivePython 2.5\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\PostgreSQL\8.3\bin;d:\smartjava\maven-2.0.9\bin;d:\smartjava\tools\putty-0.60;d:\smartjava\tools\cvsclient-1.11.17;d:\smartjava\tools\svnwin32-1.5.2-2 java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition java.runtime.version=1.5.0_15-b04 java.specification.name=Java Platform API Specification java.specification.vendor=Sun Microsystems Inc. java.specification.version=1.5 java.vendor=Sun Microsystems Inc. java.vendor.url=http://java.sun.com/ java.vendor.url.bug=http://java.sun.com/cgi-bin/bugreport.cgi java.version=1.5.0_15 java.vm.info=mixed mode, sharing java.vm.name=Java HotSpot(TM) Client VM java.vm.specification.name=Java Virtual Machine Specification java.vm.specification.vendor=Sun Microsystems Inc. java.vm.specification.version=1.0 java.vm.vendor=Sun Microsystems Inc. java.vm.version=1.5.0_15-b04 line.separator= org.mortbay.log.class=com.eviware.soapui.support.log.JettyLogger os.arch=x86 os.name=Windows XP os.version=5.1 path.separator=; soapui.ext.actions=C:\Program Files\eviware\soapUI-2.5\bin\actions soapui.ext.libraries=C:\Program Files\eviware\soapUI-2.5\bin\ext soapui.ext.listeners=C:\Program Files\eviware\soapUI-2.5\bin\listeners soapui.home=C:\Program Files\eviware\soapUI-2.5\bin\ soapui.properties=soapui.properties sun.arch.data.model=32 sun.boot.class.path=D:\Java\JDK\jdk1.5.0_15\jre\lib\rt.jar;D:\Java\JDK\jdk1.5.0_15\jre\lib\i18n.jar;D:\Java\JDK\jdk1.5.0_15\jre\lib\sunrsasign.jar;D:\Java\JDK\jdk1.5.0_15\jre\lib\jsse.jar;D:\Java\JDK\jdk1.5.0_15\jre\lib\jce.jar;D:\Java\JDK\jdk1.5.0_15\jre\lib\charsets.jar;D:\Java\JDK\jdk1.5.0_15\jre\classes sun.boot.library.path=D:\Java\JDK\jdk1.5.0_15\jre\bin sun.cpu.endian=little sun.cpu.isalist=pentium_pro+mmx pentium_pro pentium+mmx pentium i486 i386 i86 sun.desktop=windows sun.io.unicode.encoding=UnicodeLittle sun.java.launcher=SUN_STANDARD sun.jnu.encoding=Cp1252 sun.management.compiler=HotSpot Client Compiler sun.os.patch.level=Service Pack 3 user.country=NL user.dir=C:\Program Files\eviware\soapUI-2.5\bin user.home=C:\Documents and Settings\GBO user.language=nl user.name=GBO user.timezone=Europe/Berlin user.variant=1.5KViews0likes0CommentsRe: loadtest not correct when using JDBC MySQL datasource
Hi Ole and Others, Finally I understand what is happening. When a datasource is used in a testcase. The testcase will never finish until the datasource is empty. So the test delay is not used in this case during a loadtest. Except between testcase 0 and testcase 1!! If you want a delay you can add a teststep with a delay, as mentioned in the previous topic by Ole. I thought that the testcase was finished after all teststeps were executed. But the datasource loop will prevent this. When I remove the datasource loop, the testcase will finish when all teststeps are exectued. In this case what will happen with the datasource: 1) same record is used in next testcase execution? or 2) next record is used in next testcase execution? regards, Toby.875Views0likes0CommentsRe: loadtest not correct when using JDBC MySQL datasource
Hi Ole, Thanks for the answer. I understand the cancel running option, it is working correctly. Unfortunately I don't understand the first part :-( Maybe you can explain how I can achieve what I want. Hopefully i will then understand what you are meaning. What i want is a loadtest that sends every 4 seconds a request to the server. In the testcase there is a datasource teststep, the webservice request and a datasource loop teststep. I thought i can manage this with the following settings: threads: 1 strategy: simple Test Delay: 4000 (ms) Random: 0.0 Limit: 60 seconds But if i understand you correct, these settings are not correct. regards, Toby.875Views0likes0Commentsloadtest not correct when using JDBC MySQL datasource
Hello, For this question i use the following settings: threads: 1 strategy: simple Test Delay: 4000 (ms) Random: 0.0 Limit: 60 seconds When there is no datasource, these settings are working correct. So every 4 seconds a request is send to the server for 60 seconds. When I add a datasource teststep with a datasource loop, the webserver receives 2 or 3 requests per second and the testrun will not finish in 60 seconds. When i cancel the test the results in the "cnt" column are about 180 (when runned for about 60 seconds, instead of 60/4 = 15) I have played with datasource options but nothing helps. Is this a bug or did I something wrong? The datasource is working correct. Hopefully somebody can help me. Regards!2.1KViews0likes5Comments- 16 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.4KViews0likes0Comments