I have incorporated the mini-profiler in mvc app but I have a question. When I have a controller looking like below I can't see the execution that took place, any ideas?
Controller1.Action1 executes and then does RedirectToAction(Action2)
Action2 is run
My problem is that I can't seem to get the execution of step 1 above only step 2. Yes I know that it is a client side redirect involved.
Grab the latest version from the repo, we now display the last N requests that were not displayed, per user.
This way we track redirects and POSTs
Related
I am doing a performance testing in Jmeter I have added the controller and request, but my problem is when I run the script the requests are not automatically/manually navigating to the next controller
Scripts here
Script results here
I my case the scripts jmeter_login_and_view_dashboard running without any issues but is not navigation to next controller login checker or actions per login
I don't know what I am missing
Thanks in advance
We don't know as well because your screenshots don't tell the full story.
I can think of the following reasons:
You have Flow Control Action sampler somewhere which stops the test
An error occurs you have Thread Group configured to stop the test in case of error
There is an If Controller and the condition is not met
The controller is using a CSV Data Set Config and the CSV file is not present
So take a look at jmeter.log file, normally it should provide at least a clue regarding what went wrong.
Recently started to use nestjs/graphql, and trying to add middleware for all /graphql routes. And stuck with one question which is URL http://localhost:8083/graphql ,keep call with post request type in 2 seconds intervals as shown in the attached snap.
Through R&D, I have found that sample in official github, the URL on application running is http://[::1]:3000 and in network, API calls only when query runs(on button click).
so, the query is am I getting this wrong or right and, if it is right then which one is the right way.
My application end to end scenarios are working with single user iteration with all post processors data working fine But when I increase multiple users in thread group and run the same scenario..scripts getting failed in the middle due to some requests are not properly executed leads correlation fails...attached my scripts and error message, scripts files located at below drive link
https://drive.google.com/open?id=13IPlVh-Zi2AJOioGeCuHihyxYiDeRBLK
Please help me how to resolve this issue, as this is highly important to proceed further.
You're not being able to click any order from the search results as there are no order search results - there are simply no orders to choose from as you're not getting logged in by 2nd user
My expectation is that this is due to wrong test structure, i.e. you have the requests like:
/login_check
/user/showInfoBox
etc.
under the Parallel Controller however the Parallel Controller's children are being executed at the same time.
Real browser first executes login_check request followed by / followed by index.php, so you should put only css and ajax calls under the Parallel Controller otherwise you may run into the situation when the AJAX calls are being fired already and you haven't been logged in yet.
Check out How to Debug your Apache JMeter Script article for more information on JMeter tests troubleshooting techniques.
I'm trying to use sw-precache, but I must be doing something wrong!
I'm mostly using the demo code available from the github repo and can't seem to get updates to the app to come through. Once it's cached the first time, it never checks for new versions.
I was expecting that when I publish a new service worker, the browser would request the new service worker and update the cache accordingly in the background. Then using the registration code in the example, I would be able to prompt the user to refresh and get the latest version from their newly refreshed cache.
Would really appreciate if someone could please point me in the right direction.
Example
To demonstrate the problem, I've created an isolated example here:
https://github.com/stevenocchipinti/sw-precache-demo
The example uses a basic skeleton from create-react-app which has a built in build task which take care of fingerprinting the filenames, etc.
I suspect the problem is with me caching everything by using the following sw-precache config:
{
"staticFileGlobs": [ "build/**/*.*" ],
"stripPrefix": "build/"
}
There are more accurate steps in the repo's readme, but the basic steps I'm taking to reproduce the problem are as follows (with my probably incorrect expectations).
Steps and Assumptions
Browse to the app for the first
I should see Content is now available offline! in the console
Reload the page
The message in the console should not appear again because the service worker is installed, but the page should still work.
Go offline and reload the page
The page should still work
Make a visible change to the source code
Rebuild (run the build task and sw-precache)
This is where my understanding must be wrong
Reload the page
The service worker should update the cache in the background
When its done, you should see New or updated content is available. in the console
The actual visible changes should not be visible until the next reload
Reload the page again
The browser will use the new cache this time around
The changes should be visible now!
There shouldn't be any messages in the console
The problem
Once the app has been cached initially, it will never update unless you unregister the service worker or force a reload.
I'm not sure how to make this work - any help would be greatly appreciated!
After replicating your development hosting environment, I can see that you're serving your service-worker.js file with a browser HTTP cache lifetime of one hour:
There's more information as to why this is leading to the behavior you're seeing, along with best practices, in this previous answer. As mentioned at the top of that answer, browsers plan on changing their behavior to stop honoring the HTTP cache for the service worker file by default, mainly due to the type of confusion that you're experiencing here. For the time being, though, the production versions of both Chrome and Firefox continue to honor those headers.
There are plenty of examples of similar problems littered around the web but none of their solutions seem to fix this particular variation. Any suggestions would be appreciated.
Usually this problem occurs because a rogue link is causing a request for a resources like a favicon or css file to hit the dispatcher more than once, thus causing multiple dispatch processes and therefore multiple rows in your database.
I have checked that all the links on this very simple example page do actually resolve to the resource to which they point.
The session handler is setup as follows:
Zend_Db_Table_Abstract::setDefaultAdapter($db);
Zend_Session::setSaveHandler(new
Zend_Session_SaveHandler_DbTable($config->session->toArray()));
The db logging is setup as follows:
$writer = new Zend_Log_Writer_Db($db, $config->log->tableName,
$config->log->columnMap->toArray());
$logger = new Zend_Log($writer);
Both objects are correctly setup and can read and write to and from the database. Only everything happens twice. If I put a test log message anywhere in the application it is written into the database twice. If I increment three variables with every call to the index action - one stored in the session, one passed around via a Zend_Registry object and another local to the indexAction - only the session variable is incremented by 2. The Apache access log shows the correct amount of requests being fired from the page load and all have good response codes of either 200 or 304 (unchanged).
I have tried disabling all head links.
I have tried disabling the layout entirely.
I have localised everything to the dispatcher and exited before dispatch is run.
In all cases the extra write/increment takes place.
Any thoughts?
Thanks in advance for any help.
I seem to have found and fixed the issue. Chrome (and possibly all Webkit browsers) issues an additional HEAD request on top of the GET which means the application is hit twice and anything session based will be triggered as a result of both requests. My temporary solution is to put the following code near the start of my index.php file.
if ("HEAD" == $_SERVER['REQUEST_METHOD']) {
exit;
}
I hope that helps anyone with the same issue.
Google Chrome always asks for the favicon.ico by making annoying requests to the server. Take care about this in Chrome.
For more information:
http://framework.zend.com/issues/browse/ZF-11502?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#issue-tabs
Thanks to the Sebastian Galenski contribution.