Unanswered question

script recording method for .net thick client?

Hi I need to record a desktop app developed in .net and communicates over TCP/IP. I tried using the below method. "First option is to configure inside your application a proxy (<neoload controller IP>:8090)

If in your application Proxy configuration si not possible, you can launch your application trhough Internet Explorer (configure the proxy in IE and then use IE File menu to open your application Exec file)" from Neotys answers. Didn't help. please suggest a way. No option to add proxy in the application. so I tried adding the proxy 8090 in IE proxy setting with VM's IP address where I try to record. ask me for more info

Shankar N.
Shankar N.

Shankar N.

Level
0
1 / 100
point

Answers

So I'm going to assume it's HTTPs (as that's what our recorder records) and the issue is you can't force it to go via a proxy...

Fiddler allows you to set forwarding rules, so in your .Net app, you can just set the server components IP to be localhost:8888 (aka fiddler), Fiddler will then forward it on to the actual server <MyAppServer:9443>. Now in Fiddler you can set a proxy to be used by Fiddler to reach the server, this can be Neoload on localhost:8090

...so .NET Client >>> Fiddler >>> Neoload >>> AppServer

Jay G.
Jay G.

Jay G.

Level
0
52 / 100
points

I was able to record the script without any issues but while replaying the recorded traffic it get's stuck at the first request itself.

My understanding is request is not able to reach server itself but while recording there were no issues. Response which I get is below:

Error detected by NeoLoad
Error Code: NL-NETWORK-01 Message: Network error: An IO error occurred sending the request. Details: java.util.concurrent.TimeoutException: Idle timeout 300000ms

Jay G.
Jay G.

Jay G.

Level
0
52 / 100
points

Ping works perfectly fine

As you are not the original poster, I don't know your setup, I assume this is a web site and as mentioned, you LG has connectivity to the server. I can only assume that either your site is down or the request you are sending is incorrect in some way, you will need to provide more detail on the issue

Jay G.
Jay G.

Jay G.

Level
0
52 / 100
points

I understand that I've not initiated this thread but I too have .NET thick client communicating with backend IIS and DB using HTTP/S as protocol. Servers are not down otherwise recording wouldn't have been possible. During replay it just doesn't seem to find a way to server. What further info. Will be required here?

ah, okay, so you were able to configure the proxy with your app. I just meant during playback the server might have gone down. from the LG, I assume you are using localhost one, you need to make sure there is network connectivity. If there is a corporate proxy in use at you company, you also need to make sure the zone is configured with the settings just like in Internet options.

Jay G.
Jay G.

Jay G.

Level
0
52 / 100
points

Neither LG (same machine from where script was recorded) nor servers hosting Application under test were down. If there is an issue with firewall/DMZ I should have faced it during recording too. Why only at the time of replay?

Keith L.
Keith L.

Keith L.

Level
2
1400 / 2000
points
Team

The Recording uses the NeoLoadGUI.exe main Controller process, but the playback uses the /jre/bin/java.exe process, as it is created as a child process for any Load Generator Agent. In this scenario, the NeoLoadGUI.exe is the LG Agent that creates this java.exe process. It is likely your Firewall is blocking this process, but not the NeoLoadGUI.exe process. Make sure to add an exception in your firewall rules for the <NeoLoad install dir>\jre\bin\java.exe executable. You can also test for any simple recording to http://www.google.com perhaps if you can access the internet with your Controller. If that fails as well, it confirms that the java.exe executable is not able to access outside resources. Give this executable full access through firewall if possible.

Jay G.
Jay G.

Jay G.

Level
0
52 / 100
points

Well that's good to know difference between processes. I'd keep that in mind. Meanwhile tried with Google.com. It just works fine both record and replay.