• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: "Did not receive any response from application. It is possible that the application does not exist, or that the requested url is incorrect"
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: "Did not receive any response from application. It is possible that the application does not exist, or that the requested url is incorrect"


  • Subject: Re: "Did not receive any response from application. It is possible that the application does not exist, or that the requested url is incorrect"
  • From: Chuck Hill <email@hidden>
  • Date: Wed, 25 Feb 2015 17:18:24 +0000
  • Thread-topic: "Did not receive any response from application. It is possible that the application does not exist, or that the requested url is incorrect"

I just thought of something else.  Is this app running with a single instance?  If so, this might mean that the response was no received from the app before the Receive Timeout expired  (see Adaptor Settings in on the application page in Java Monitor).  The solution to that is to make your app faster :-) or increase the timeout.

 Is this app running without concurrent request dispatch enabled?  That could explain the slow response time from the user perspective if requests got queued up behind something slow.  That also explains why the app log does not correspond to the user’s perception.  With concurrent dispatch enabled, the app logs tend to be closer to the user’s view of elapsed time as it blocks after awake (e.g. On the EOF lock)  

It sounds like either the CSV import is doing too much before handing off to the second stack, the second stack is not getting used correctly (I doubt, but will mention), or some other action in the app is slow.  If there is a lot of constant database access (like a big save or big fetch) from one request, it will cause other requests (using the same OSC) to queue up for the EOF lock.

Chuck


On 2015-02-25, 8:57 AM, "OC" wrote:

Oh, and since I'm writing anyway...

On 24. 2. 2015, at 18:48, Chuck Hill <email@hidden> wrote:

I don’t see that one very often.  IIRC, it means that it sent the request to an instance and got a null response back.  That probably means the app threw an exception either very early or very late in the R-R loop.

Thanks!

Check the app logs for exceptions.

None. Far as I can say, the request -- it was CSV import, too, but none of those which went wrong -- did spawn its background thread and finished all right -- I'm logging R/Rs from application's awake/sleep, and all looks OK. Definitely no exception in my application log nearby.

Did an instance run out of memory?

Hardly. I log the heap (and lately also the Perm Gen stuff which bit my back a couple of days ago), and there was plenty of both.

Check the Apache error.log just to be sure.

Thanks again, I've asked the system admin to do that. I did that anyway, for that day there _was_ something fishy (hmmmm... perhaps it even might be related):

The thing is, I've got a report from a user that one request took more than 20 seconds to reload in his browser. I have found it in my logs, and App.awake to App.sleep it took 1.818 seconds. Another request reported to last a dozen of seconds from the user's point of view took 0.577 seconds App.awake to App.sleep. Weird.

Thanks again,
OC

On 2015-02-24, 8:35 AM, "OC" wrote:
Hello there,
what the $subject means and who reports it?
I've googled a bit before coming here, and found
(a) it seems to be a Wonder error report (https://github.com/wocommunity/wonder/blob/master/Utilities/Adaptors/Adaptor/errors.h)
(b) it seems to be quite common to see with Apple own applications (http://forums.appleinsider.com/t/418/apple-store-seems-to-be-down-right-now/40 and more similar ones, with Knowlegde Base, with Apple WebMail, etc.)
(Incidentally, Apple uses Wonder? That's nice to know.)
But what I haven't been able to find (yet) is what it actually means? :-O I did succeed to find the appopriate source (transaction.c in the Adaptor) and function (_errorResponse) which seem to generate the report, but without a detailed study of the adaptor code I'm none the smarter of what condition causes this (well, the condition is that WOAppReq.error contains 4, but... :))
Does somebody here know, or am I to dive into the adaptor sources?
Not that I would care, but one of the users of my application did see the thing today :(
Thanks a lot,
OC
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: "Did not receive any response from application. It is possible that the application does not exist, or that the requested url is incorrect"
      • From: OC <email@hidden>
References: 
 > "Did not receive any response from application. It is possible that the application does not exist, or that the requested url is incorrect" (From: OC <email@hidden>)
 >Re: "Did not receive any response from application. It is possible that the application does not exist, or that the requested url is incorrect" (From: Chuck Hill <email@hidden>)
 >Re: "Did not receive any response from application. It is possible that the application does not exist, or that the requested url is incorrect" (From: OC <email@hidden>)

  • Prev by Date: Re: "Did not receive any response from application. It is possible that the application does not exist, or that the requested url is incorrect"
  • Next by Date: Re: "Did not receive any response from application. It is possible that the application does not exist, or that the requested url is incorrect"
  • Previous by thread: Re: "Did not receive any response from application. It is possible that the application does not exist, or that the requested url is incorrect"
  • Next by thread: Re: "Did not receive any response from application. It is possible that the application does not exist, or that the requested url is incorrect"
  • Index(es):
    • Date
    • Thread