zijst005
Occasional Contributor
Joined 13 years ago
User Profile
User Widgets
Contributions
Re: Hi Guys
Hi Tientran, What nmrao suggested is to store the ID on test case level, this is useful when you have more then 1 test step using the property as an input/reference. For more details on properties i would suggest reading: https://www.soapui.org/scripting---properties/working-with-properties.html1.2KViews0likes0CommentsRe: Can we test JMS messages to ActiveMQ using SOAPUI free version? Or it will need Pro version?
Hiaherraosachin, Yes you can! SoapUI comes with HermesJMS which is required to interact with your ActiveMQ To setup your HermesJMS Configuration i would suggest reading: http://activemq.apache.org/hermes-jms.html After setting up your hermes configuration you should have no problems sending messages to you ActiveMQ bus.2.3KViews1like1CommentRe: Ready! API 1.4 Always refering to tcp://localhost:7222 eventough HermesJMS is correctly configured
Hi nmrao, First of all thanks for all your support/time. I have taken the hermes-config-sample.xml and with some minor adjustments i updated the the path to the jar files and adjusted the serverUrl. however the result remained the same, a colleage of mine is facing the same issue.. and currently Smartbear has acknowledged/reproduced the issue. they created a case for it, so hopefully they are diving into it :) Personally i don't think it is related to the hermes-config.xml. The reason i don't think its related to that, is because HermesJMS which is using the Same config is able to Contact the server and is able to discover the queues. So from an configuration point of view i would expect the Config file along with the Providers (jar files) to be correct.10 years agoPlace ReadyAPI QuestionsReadyAPI Questions5.5KViews0likes2CommentsRe: Ready! API 1.4 Always refering to tcp://localhost:7222 eventough HermesJMS is correctly configured
don't know if this helps you but here is an extract taken from the SoapUI debug window: This happens when i sent the message: 14:07:20,112 WARN [HermesJmsRequestTransport] Invalid timeout extracted (not a number): null 14:07:23,407 ERROR [SoapUI] An error occurred [Failed to connect to the server a t tcp://localhost:7222], see error log for details javax.jms.JMSException: Failed to connect to the server at tcp://localhost:7222 at com.tibco.tibjms.TibjmsxLinkTcp._createSocket(TibjmsxLinkTcp.java:831 ) at com.tibco.tibjms.TibjmsxLinkTcp.connect(TibjmsxLinkTcp.java:922) at com.tibco.tibjms.TibjmsConnection._create(TibjmsConnection.java:1299) at com.tibco.tibjms.TibjmsConnection.<init>(TibjmsConnection.java:4155) at com.tibco.tibjms.TibjmsTopicConnection.<init>(TibjmsTopicConnection.j ava:36) at com.tibco.tibjms.TibjmsxCFImpl._createImpl(TibjmsxCFImpl.java:191) at com.tibco.tibjms.TibjmsxCFImpl._createConnection(TibjmsxCFImpl.java:2 53) at com.tibco.tibjms.TibjmsConnectionFactory.createConnection(TibjmsConne ctionFactory.java:36) at com.eviware.soapui.impl.wsdl.submit.transports.jms.JMSConnectionHolde r.createConnection(JMSConnectionHolder.java:87) at com.eviware.soapui.impl.wsdl.submit.transports.jms.HermesJmsRequestSe ndReceiveTransport.execute(HermesJmsRequestSendReceiveTransport.java:39) at com.eviware.soapui.impl.wsdl.submit.transports.jms.HermesJmsRequestTr ansport.sendRequest(HermesJmsRequestTransport.java:100) at com.eviware.soapui.impl.wsdl.WsdlSubmit.run(WsdlSubmit.java:119) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) 14:07:23,436 WARN [HermesJmsRequestTransport] Error Response javax.jms.JMSException: Failed to connect to the server at tcp://localhost:7222 at com.eviware.soapui.impl.wsdl.submit.transports.jms.JMSConnectionHolde r.createConnection(JMSConnectionHolder.java:102) at com.eviware.soapui.impl.wsdl.submit.transports.jms.HermesJmsRequestSe ndReceiveTransport.execute(HermesJmsRequestSendReceiveTransport.java:39) at com.eviware.soapui.impl.wsdl.submit.transports.jms.HermesJmsRequestTr ansport.sendRequest(HermesJmsRequestTransport.java:100) at com.eviware.soapui.impl.wsdl.WsdlSubmit.run(WsdlSubmit.java:119) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)10 years agoPlace ReadyAPI QuestionsReadyAPI Questions5.5KViews0likes6CommentsRe: Ready! API 1.4 Always refering to tcp://localhost:7222 eventough HermesJMS is correctly configured
Thanks for your reply, I did the steps that you suggested, however the result remains the same. i restarted SoapUI but still the JMS call is sent to Localhost:722210 years agoPlace ReadyAPI QuestionsReadyAPI Questions5.6KViews0likes0CommentsReady! API 1.4 Always refering to tcp://localhost:7222 eventough HermesJMS is correctly configured
Hi all, I hope there is someone here who can help me out with the following scenario: I installed Ready API 1.4 and I have Created an HermesJMS Connection to a remote EMS server From within HermesJMS i was able to discover the Queues... so far so good. From the "Project View" i added an End point to the Interface from which i will be using the opperation, To do this, i used the JMS endpoint wizzard here i set the "To" Queue and the "Reply" Queue. After this, i switched to SoapUI NG (pro) where i created an Testcase and added an JMS step to the testcase. i selected the operation that i wanted to use and set the correct endpoint (which was already available). After filling in the details required for my JMS call i pressed the sent button.... it took some Miliseconds but it stated that the message was sent. (but there was no reply) (Please note that i did specify the reply queue in the Wizard) because there was no reply, I restarted Ready API 1.4 with the .bat file... running it in debug mode. when i initiated the JMS call again i noticed that the Debug window stated that it could not connect to tcp://localhost:7222. my question is as followed: why is the request sent to tcp://localhost:7222 eventought the endpoint is pointing to the hermesJMS configuration and the configuration is pointing towards an remote server on which the EMS is running.Solved10 years agoPlace ReadyAPI QuestionsReadyAPI Questions5.6KViews0likes9CommentsRe: Unable to edit 'ReadyAPI-1.2.1.vmoptions' or ready-api.bat files,
Try Opening your Text Editor with the Option (Run as Administrator) Then Click on "File" and then "Open" and locate your 'ReadyAPI-1.2.1.vmoptions' file you should now be able to edit it10 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.3KViews0likes0Comments