jmeter-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From papayaseed <nkulka...@firstam.com>
Subject RE: Sending messages to EMS queue using Jmeter running on a machine outside the domain
Date Thu, 11 Sep 2014 15:43:16 GMT
Thanks for your response.

No. I am not using JNDI. Only passing the provider URI as tcp://EMS.DOMAIN2.com:1722

In the error message I see: Error I get is: Response message: javax.jms.JMSException: Failed
to connect to any server at: tcp://EMS:1722,tcp://EMS:1722

So the provider URL is not getting passed as it is. Instead Jmeter is stripping the domain
name.

Thanks,
Nilesh

From: sebb-2-2 [via JMeter] [mailto:ml-node+s512774n5721020h18@n5.nabble.com]
Sent: Thursday, September 11, 2014 6:33 AM
To: Kulkarni, Nilesh
Subject: Re: Sending messages to EMS queue using Jmeter running on a machine outside the domain

Is the check box "use jndi.properties file" selected?
If so, the Provider URL on the GUI page is ignored and it will use
whatever is in the properties file.

In all cases, the provider URL is passed to the JMS library unchanged
so if the URL is being changed, that is not a JMeter issue.

On 10 September 2014 16:34, Kulkarni, Nilesh <[hidden email]</user/SendEmail.jtp?type=node&node=5721020&i=0>>
wrote:

> Thanks for your response.
>
> I am using JMeter 2.11
> Windows 2008 R2 OS and java 1.7.0.
>  The sampler I am using is JMS publisher.
>
> Thanks!
>
> -----Original Message-----
> From: sebb [mailto:[hidden email]</user/SendEmail.jtp?type=node&node=5721020&i=1>]
> Sent: Wednesday, September 10, 2014 4:13 AM
> To: JMeter Users List
> Subject: Re: Sending messages to EMS queue using Jmeter running on a machine outside
the domain
>
> On 9 September 2014 22:20, papayaseed <[hidden email]</user/SendEmail.jtp?type=node&node=5721020&i=2>>
wrote:
>> I am running Jmeter on a machine outside the domain where ems is
>> running. EMS is running on port 1722 and firewall between Jmeter
>> server and EMS server are open on port 1722.
>
> Which version of JMeter?
> OS?
> Java?
>
>> The Jmeter is running on server Perftest.DOMAIN1.com The EMS is
>> running onserver EMS.DOMAIN2.com
>>
>> Even though I am using fully qualified domain name ni the provider URL
>> tcp://EMS.DOMAIN2.com:1722 in JMeter, it is trying to send message to
>> tcp://EMS:1722 and failing since EMS server is not in the same domain
>> as Perftest machine.
>>
>> Error I get is: Response message: javax.jms.JMSException: Failed to
>> connect to any server at: tcp://EMS:1722,tcp://EMS:1722
>
> Which sampler are you using?
>
>> why is JMeter not using FQDN while connecting to EMS server?
>>
>> I tried using IP address, and updating the host file still Jmeter is
>> not using FQDN to connect to EMS server and hencve failing.
>>
>> Is there a workaround for this problem? Can I not use Jmeter outside
>> the domain to test EMS?
>>
>> Thanks!
>>
>>
>>
>> --
>> View this message in context:
>> http://jmeter.512774.n5.nabble.com/Sending-messages-to-EMS-queue-using
>> -Jmeter-running-on-a-machine-outside-the-domain-tp5720990.html
>> Sent from the JMeter - User mailing list archive at Nabble.com.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]</user/SendEmail.jtp?type=node&node=5721020&i=3>
>> For additional commands, e-mail: [hidden email]</user/SendEmail.jtp?type=node&node=5721020&i=4>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]</user/SendEmail.jtp?type=node&node=5721020&i=5>
> For additional commands, e-mail: [hidden email]</user/SendEmail.jtp?type=node&node=5721020&i=6>
>
> ******************************************************************************************
> This message may contain confidential or proprietary information intended only for the
use of the
> addressee(s) named above or may contain information that is legally privileged. If you
are
> not the intended addressee, or the person responsible for delivering it to the intended
addressee,
> you are hereby notified that reading, disseminating, distributing or copying this message
is strictly
> prohibited. If you have received this message by mistake, please immediately notify us
by replying
> to the message and delete the original message and any copies immediately thereafter.
>
> If you received this email as a commercial message and would like to opt out of future
commercial
> messages, please let us know and we will remove you from our distribution list.
>
> Thank you.~
> ******************************************************************************************
> FAFLD

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]</user/SendEmail.jtp?type=node&node=5721020&i=7>
For additional commands, e-mail: [hidden email]</user/SendEmail.jtp?type=node&node=5721020&i=8>


________________________________
If you reply to this email, your message will be added to the discussion below:
http://jmeter.512774.n5.nabble.com/Sending-messages-to-EMS-queue-using-Jmeter-running-on-a-machine-outside-the-domain-tp5720990p5721020.html
To unsubscribe from Sending messages to EMS queue using Jmeter running on a machine outside
the domain, click here<http://jmeter.512774.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5720990&code=bmt1bGthcm5pQGZpcnN0YW0uY29tfDU3MjA5OTB8LTEyNjA5MTQ5OTg=>.
NAML<http://jmeter.512774.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>




--
View this message in context: http://jmeter.512774.n5.nabble.com/Sending-messages-to-EMS-queue-using-Jmeter-running-on-a-machine-outside-the-domain-tp5720990p5721021.html
Sent from the JMeter - User mailing list archive at Nabble.com.
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message