Contributions
Re: ReadyAPI 2.8.0 getting 401 error when attempting to send the request
I am running soapUI pro on mac, i have .keytab and .conf files in a directory that are referenced in the vmoptions. we added the following to the file -Djavax.security.auth.useSubjectCredsOnly=false -Djava.security.auth.login.config=/Users/nmowbray/Documents/Kerberos_SoapUI/login.conf -Djava.security.krb5.conf=/Users/nmowbray/Documents/Kerberos_SoapUI/krb5.conf but we still have issues. I have not done the kinit part of the instructions as this is a work computer. Can you explain why we need to run the kinit in order to have kerberos work in soapUI, it was working on previous versions without having to do this5 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.2KViews0likes1CommentReadyAPI 2.8.0 getting 401 error when attempting to send the request
When we attempt to send a request to an endpoint that requires kerberos authentication I keep getting a 401 error Request RAW: POST http://matrix-133-cdi.matrix.sjrb.ad/customers HTTP/1.1 Connection: close Accept-Encoding: gzip,deflate X_SHAW_TRANSACTION_ID: 00005557 User-Agent: Fiddler X_SHAW_ORIGINATING_IP_ADDRESS: 10.15.184.88 X_SHAW_ORIGINAL_MODULE_ID: NetCracker X_SHAW_ORIGINATING_HOST_NAME: devcoreoeml017.matrix.SJRB.AD Content-Type: application/vnd.shaw.customer+xml X_SHAW_ORIGINATING_USER_ID: lruser003 Content-Length: 1697 Host: matrix-133-cdi.matrix.sjrb.ad <Customer xmlns="http://services.sjrb.ad/customer"> <Identity> <Title>Mr</Title> <FirstName>Nate</FirstName> <MiddleNameInitial>M</MiddleNameInitial> <LastName>Phone</LastName> </Identity> <IsOrganization>False</IsOrganization> <Status>New</Status> <SalesLeads> <SalesLead>1</SalesLead> </SalesLeads> <CustomerAlerts> <CustomerAlert>1</CustomerAlert> </CustomerAlerts> <PrivacyRequested>True</PrivacyRequested> <Credentials> <Password>1112</Password> <MembershipNumber>121213</MembershipNumber> <DriversLicense>233334</DriversLicense> </Credentials> <CreditScore>Netural</CreditScore> <CreditScoreDate>2010-04-14T00:00:00Z</CreditScoreDate> <BillingPreferences> <BillingLevelOfDetail>Detail</BillingLevelOfDetail> <BillingDeliveryMethod>Paper</BillingDeliveryMethod> <BillingLanguage>English</BillingLanguage> <BillingDeliveryFormat>Normal</BillingDeliveryFormat> <BillingEmails> <BillingEmail> <Address>hello@here.com</Address> </BillingEmail> </BillingEmails> <BillingAddresses> <BillingAddress> <AisId>272272</AisId> </BillingAddress> </BillingAddresses> </BillingPreferences> <ContactInformation> <ContactEmail> <Address>john.doe@domain.ca</Address> </ContactEmail> <PhoneNumbers> <PhoneNumber> <IsPrimary>True</IsPrimary> <PhoneType>Home</PhoneType> <Number>4032223334</Number> <Extension>78</Extension> </PhoneNumber> <PhoneNumber> <IsPrimary>False</IsPrimary> <PhoneType>Home</PhoneType> <Number>4033332222</Number> <Extension>1</Extension> </PhoneNumber> </PhoneNumbers> </ContactInformation> <Accounts></Accounts> </Customer> Response RAW: HTTP/1.1 401 Unauthorized Content-Type: text/html; charset=us-ascii Server: Microsoft-HTTPAPI/2.0 WWW-Authenticate: Negotiate oXwweqADCgEBoQsGCSqGSIb3EgECAqJmBGRgYgYJKoZIhvcSAQIC Date: Thu, 01 Aug 2019 22:52:11 GMT Connection: close Content-Length: 341 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd"> <HTML><HEAD><TITLE>Not Authorized</TITLE> <META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD> <BODY><h2>Not Authorized</h2> <hr><p>HTTP Error 401. The requested resource requires user authentication.</p> </BODY></HTML> I followed the document for kerberos that smartbear has, added the following to vmoptions.txt -Djavax.security.auth.useSubjectCredsOnly=false -Djava.security.auth.login.config=/Users/nmowbray/Documents/Kerberos_SoapUI/login.conf -Djava.security.krb5.conf=/Users/nmowbray/Documents/Kerberos_SoapUI/krb5.conf Custom Properties Follow Redirects true Follow 302 Redirect with GET false Username user01 Password password Domain shaw Using the exact same setup in ReadyAPI 2.6.0 this request works with no issuesSolved2.2KViews0likes3CommentsReadyAPI 2.7 Failed to Register the JDBC driver
Hi, I recently updated ReadyAPI from 2.6 to 2.7 but now all my test steps that have custom code to connect to a database via JDBC i get the following errors: Mon May 06 10:32:49 MDT 2019: ERROR: Failed to register the JDBC driver [oracle.jdbc.driver.OracleDriver]. Mon May 06 10:32:49 MDT 2019: ERROR: java.lang.ClassNotFoundException: oracle.jdbc.driver.OracleDriver java.lang.ClassNotFoundException: oracle.jdbc.driver.OracleDriver at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:348) at com.eviware.soapui.support.GroovyUtils.registerJdbcDriver(GroovyUtils.java:110) at com.eviware.soapui.support.GroovyUtils$registerJdbcDriver.call(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:125) at Script1.run(Script1.groovy:2) at com.eviware.soapui.support.scripting.groovy.SoapUIGroovyScriptEngine.run(SoapUIGroovyScriptEngine.java:98) at com.eviware.soapui.support.scripting.groovy.SoapUIProGroovyScriptEngineFactory$SoapUIProGroovyScriptEngine.run(SoapUIProGroovyScriptEngineFactory.java:83) at com.eviware.soapui.impl.wsdl.teststeps.WsdlGroovyScriptTestStep.run(WsdlGroovyScriptTestStep.java:158) at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.runTestStep(AbstractTestCaseRunner.java:261) at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.runTestStepByName(AbstractTestCaseRunner.java:240) at com.eviware.soapui.model.testsuite.TestCaseRunner$runTestStepByName$0.call(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:125) at Script1.run(Script1.groovy:8) at com.eviware.soapui.support.scripting.groovy.SoapUIGroovyScriptEngine.run(SoapUIGroovyScriptEngine.java:98) at com.eviware.soapui.support.scripting.groovy.SoapUIProGroovyScriptEngineFactory$SoapUIProGroovyScriptEngine.run(SoapUIProGroovyScriptEngineFactory.java:83) at com.eviware.soapui.impl.wsdl.teststeps.WsdlGroovyScriptTestStep.run(WsdlGroovyScriptTestStep.java:158) at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.runTestStep(AbstractTestCaseRunner.java:261) at com.eviware.soapui.impl.wsdl.testcase.WsdlTestCaseRunner.runCurrentTestStep(WsdlTestCaseRunner.java:52) at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalRun(AbstractTestCaseRunner.java:171) at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalRun(AbstractTestCaseRunner.java:1) at com.eviware.soapui.impl.wsdl.support.AbstractTestRunner.run(AbstractTestRunner.java:130) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Does anyone have a solution? Thanks NathonSolved2.7KViews0likes2CommentsRe: Keep getting Warning More than 80% of the Java heap memory is being used.
HiOlga_T, It happens on all projects when using the application on Mac OS, we have not seen the problem for quite some time on Windows OS. Seems to be an issue when using oracle driver: The JDBC driver [oracle.jdbc.driver.OracleDriver] is already registered. Wed Dec 05 17:27:02 MST 2018: ERROR: More than 95% of the Java heap memory is being used. The test results may be impacted. It is recommended that you increase the value of the VM option -Xmx or -XX:MaxHeapSize in the file ReadyAPI.vmoptions. Wed Dec 05 17:27:02 MST 2018: WARN: More than 80% of the Java heap memory is being used. It is recommended that you increase the value of the VM option -Xmx or -XX:MaxHeapSize in the file ReadyAPI.vmoptions. Wed Dec 05 17:27:03 MST 2018: ERROR: More than 95% of the Java heap memory is being used. The test results may be impacted. It is recommended that you increase the value of the VM option -Xmx or -XX:MaxHeapSize in the file ReadyAPI.vmoptions. Wed Dec 05 17:27:03 MST 2018: WARN: More than 80% of the Java heap memory is being used. It is recommended that you increase the value of the VM option -Xmx or -XX:MaxHeapSize in the file ReadyAPI.vmoptions. Wed Dec 05 17:27:04 MST 2018: ERROR: More than 95% of the Java heap memory is being used. The test results may be impacted. It is recommended that you increase the value of the VM option -Xmx or -XX:MaxHeapSize in the file ReadyAPI.vmoptions. Wed Dec 05 17:27:04 MST 2018: WARN: More than 80% of the Java heap memory is being used. It is recommended that you increase the value of the VM option -Xmx or -XX:MaxHeapSize in the file ReadyAPI.vmoptions. Wed Dec 05 17:27:05 MST 2018: ERROR: More than 95% of the Java heap memory is being used. The test results may be impacted. It is recommended that you increase the value of the VM option -Xmx or -XX:MaxHeapSize in the file ReadyAPI.vmoptions. Wed Dec 05 17:27:05 MST 2018: WARN: More than 80% of the Java heap memory is being used. It is recommended that you increase the value of the VM option -Xmx or -XX:MaxHeapSize in the file ReadyAPI.vmoptions. Wed Dec 05 17:27:06 MST 2018: ERROR: More than 95% of the Java heap memory is being used. The test results may be impacted. It is recommended that you increase the value of the VM option -Xmx or -XX:MaxHeapSize in the file ReadyAPI.vmoptions. Wed Dec 05 17:27:06 MST 2018: WARN: More than 80% of the Java heap memory is being used. It is recommended that you increase the value of the VM option -Xmx or -XX:MaxHeapSize in the file ReadyAPI.vmoptions. Wed Dec 05 17:27:07 MST 2018: ERROR: More than 95% of the Java heap memory is being used. The test results may be impacted. It is recommended that you increase the value of the VM option -Xmx or -XX:MaxHeapSize in the file ReadyAPI.vmoptions. Wed Dec 05 17:27:07 MST 2018: WARN: More than 80% of the Java heap memory is being used. It is recommended that you increase the value of the VM option -Xmx or -XX:MaxHeapSize in the file ReadyAPI.vmoptions. Wed Dec 05 17:27:08 MST 2018: ERROR: More than 95% of the Java heap memory is being used. The test results may be impacted. It is recommended that you increase the value of the VM option -Xmx or -XX:MaxHeapSize in the file ReadyAPI.vmoptions. Wed Dec 05 17:27:08 MST 2018: WARN: More than 80% of the Java heap memory is being used. It is recommended that you increase the value of the VM option -Xmx or -XX:MaxHeapSize in the file ReadyAPI.vmoptions. Wed Dec 05 17:27:09 MST 2018: WARN: More than 80% of the Java heap memory is being used. It is recommended that you increase the value of the VM option -Xmx or -XX:MaxHeapSize in the file ReadyAPI.vmoptions. Wed Dec 05 17:27:10 MST 2018: WARN: More than 80% of the Java heap memory is being used. It is recommended that you increase the value of the VM option -Xmx or -XX:MaxHeapSize in the file ReadyAPI.vmoptions. Wed Dec 05 17:27:11 MST 2018: WARN: More than 80% of the Java heap memory is being used. It is recommended that you increase the value of the VM option -Xmx or -XX:MaxHeapSize in the file ReadyAPI.vmoptions. Wed Dec 05 17:27:12 MST 2018: WARN: More than 80% of the Java heap memory is being used. It is recommended that you increase the value of the VM option -Xmx or -XX:MaxHeapSize in the file ReadyAPI.vmoptions. Wed Dec 05 17:27:13 MST 2018: WARN: More than 80% of the Java heap memory is being used. It is recommended that you increase the value of the VM option -Xmx or -XX:MaxHeapSize in the file ReadyAPI.vmoptions. Wed Dec 05 17:27:14 MST 2018: WARN: More than 80% of the Java heap memory is being used. It is recommended that you increase the value of the VM option -Xmx or -XX:MaxHeapSize in the file ReadyAPI.vmoptions. Wed Dec 05 17:27:15 MST 2018: WARN: More than 80% of the Java heap memory is being used. It is recommended that you increase the value of the VM option -Xmx or -XX:MaxHeapSize in the file ReadyAPI.vmoptions. Wed Dec 05 17:27:16 MST 2018: WARN: More than 80% of the Java heap memory is being used. It is recommended that you increase the value of the VM option -Xmx or -XX:MaxHeapSize in the file ReadyAPI.vmoptions.6 years agoPlace ReadyAPI QuestionsReadyAPI Questions4KViews0likes1CommentKeep getting Warning More than 80% of the Java heap memory is being used.
Keep seeing the following message when the test reads JMS message: Thu Nov 29 10:21:00 MST 2018: WARN: More than 80% of the Java heap memory is being used. It is recommended that you increase the value of the VM option -Xmx or -XX:MaxHeapSize in the file ReadyAPI.vmoptions I have updated vmoptions file with the following -XX:MinHeapFreeRatio=20 -XX:MaxHeapFreeRatio=40 -Xms128m -Xmx8192m After updating the file and restarting Ready API i still have the same issue6 years agoPlace ReadyAPI QuestionsReadyAPI Questions4.2KViews0likes7Commentsset JMSReplyTo Header with Groovy
Hi, I am trying to set the JMSReplyTo header through soapUI but i keep getting an error, i am trying to send to a specific queue that we had created for our test. What we are doing is we send a request into the request queue but we want the response sent to a specific queue that we can use groovy to pull the message of that queue to verify the correct response is returned. Here is how we have the groovy code: // Send Request def String webLogicInitialContextFactory = "weblogic.jndi.WLInitialContextFactory"; def String jmsServerUrl = context.expand( '${#Project#jmsServerUrl}' ); def String jndiQueueConnectionFactory = 'jms/resourceFacingServiceActivationRequest/connectionfactory' def String jndiQueue ='jms/resourceFacingServiceActivationRequest/queue' def String jndiResponseQueueCi = 'jms/ci_resourceFacingServiceActivationResponse/queue' def String username = context.expand( '${#Project#jmsUsername}' ); def String password = context.expand( '${#Project#jmsPassword}' ); def queue = new WeblogicJmsQueue(webLogicInitialContextFactory, jmsServerUrl, username, password, jndiQueueConnectionFactory, jndiQueue); // ask the session for a text message object def msg = queue.qsession.createTextMessage(); def transId = context.expand('${nonunique_properties#transId}') def payload = context.expand( '${Read Test#Execute}' ) + '\n'; //msg.setJMSCorrelationId(transId) msg.setJMSDeliveryMode(2) msg.setJMSExpiration(System.currentTimeMillis() + 5*1000) msg.setJMSMessageID() msg.setJMSPriority(4) msg.setJMSTimestamp(System.currentTimeMillis()) msg.setJMSType() if (jndiResponseQueueCi != ''){ msg.setJMSReplyTo(jndiResponseQueueCi)} msg.setStringProperty("X_SHAW_TRANSACTION_ID", transId) msg.setStringProperty("X_SHAW_ONBEHALFOF_ID", "") msg.setStringProperty("X_SHAW_ORIGINATING_USER_ID", "SJRB'\'proctst_matrix_oem") msg.setStringProperty("X_SHAW_ORIGINATING_IP_ADDRESS", "10.15.185.25") msg.setStringProperty("X_SHAW_ORIGINATING_HOST_NAME", "devcoreoeml006.matrix.SJRB.AD") msg.setStringProperty("X_SHAW_ORIGINAL_MODULE_ID", "NetCracker") msg.setText(payload); queue.sendMessage(msg); log.info("JMS Message Sent: $payload") queue.close(); log.info "Succesfully sent to $jmsServerUrl"; Error Message i get when attempting to send the request this way: groovy.lang.MissingMethodException: No signature of method: weblogic.jms.common.TextMessageImpl.setJMSReplyTo() is applicable for argument types: (java.lang.String) values: [jms/ci_resourceFacingServiceActivationResponse/queue] Possible solutions: setJMSReplyTo(javax.jms.Destination), getJMSReplyTo() error at line: 46735Views0likes0CommentsScript Library set up in CI
I am trying to run my SoapUI suite in TeamCity, some of my tests call a groovy file which i have set up the path in the project under Script Library ${projectDir}/Groovy. Here is my setup and command line i use in TeamCity: Runner type: Powershell Step Name: Email Provisioning Execute Step: Even if some of the previous steps failed Powershell run mode: version Any Bitness x86 Format stderr output as: warning Script: Source code Script source: C:/PROGRA~1/SmartBear/ReadyAPI-2.1.0/bin/testrunner.bat'-sEmail Provisioning' -f%teamcity.build.workingDir%/blahblahblah -R"JUnit-Style HTML Report" -EM10 "%working_dir%/%soapui_project%" When i try to run the test case in team city i get the following error: [BUG! exception in phase 'semantic analysis' in source unit 'Script1.groovy' The lookup for XmlUtils caused a failed compilaton. There should not have been any compilation from this call.] The test step in question assertion looks like this: def responseAsXml = context.expand( '${Verify Xid created in SPSDEL#ResponseAsXml}' ); def expectedXml = context.expand('${spsDelResults#add_xid_result}'); result = XmlUtils.differences(expectedXml, responseAsXml, "ServiceCatalogueItem"); if (result.size() > 0){ result.each(){ log.info it } assert false } else{ log.info "Enterprise View is Correct" } Does anyone have a way to set the script library via command line? I would prefer not to modify testrunner.bat file7 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.4KViews0likes3Comments