![]() For example, if you have the Caching setting set to be a short period of time (less than 15 minutes) then the plugin will be making more requests per hour than if it is set to be 1 hour, especially if you’re using this same setting for multiple feeds. This is usually simple to fix by just changing the caching settings in the plugin under Facebook Feed > Settings > Feeds. If you are using the same Access Token (which is the case if you connect everything to your personal Facebook account) to display a lot of different Facebook feeds – either on your own website or across multiple sites – then you may exceed the API request limit that Facebook has set for your Access Token. This error occurs when the Access Token you’re using is making too many requests to Facebook in a short period of time. Your Access Token is making too many requests You can also do this for an individual feed by going to Facebook Feed > All Feeds > click Edit for the feed > Settings > click Clear Feed Cache. You can clear the plugin cache and force the plugin to check the Facebook API again by going to Facebook Feed > Settings > Feeds > click Clear All Caches. Try waiting a few minutes and then trying again. ![]() You can do this via the setting located under Facebook Feed > All Feeds > select Edit for the relevant feed > Settings > Advanced > API Post Limit Facebook’s API may have a temporary issueįacebook’s API may be unreachable temporarily. If you’re requesting a high number of posts or have the post limit set very high then try reducing the post limit. Facebook has certain limitations on its API and doesn’t allow you to retrieve too much data in one request and put too much load on their servers. * Glassfish server version: 3.1.2.If you request too much data from Facebook’s API then it will occasionally send back an ‘unknown error’ message. daily.Ĭan anyone describe the algorithm Apex uses to determine wether a session is valid or point to relevant documentation? I assume that entries of type b are created when one of the timeout values is reached, but why does Apex sometimes thinks that sessions are invalid/have expired although they still are valid and produces entries of type a?ĭoes anyone have any tips on how to further analyze this problem? Because it cannot be reproduced on demand preferably some protocol mechanism would be needed which could be analyzed e.g. WWV_FLOW_SECURITY FINAL_EXCEPTION_HANDLER WWV_FLOW_SECURITY FINAL_EXCEPTION_HANDLERĪPEX_USER ERROR_MESSAGE ERROR_ON_COMPONENT_TYPE ORA-20987: APEX - Your session has expired - Click here to create a new session. Nobody ORA-20987: APEX - Your session has expired - Contact your application administrator. So the user simply is redirected to the login page.īy querying apex_050000.apex_workspace_activity_log I found two different kinds of entries:ĪPEX_USER ERROR_MESSAGE ERROR_ON_COMPONENT_TYPE ERROR_ON_COMPONENT_NAME The authorization scheme used by the application has the setting "Invalid Session Procedure Name" pointing to a procedure which simply contains: ![]() ![]() Neither value is reached, the problem sometimes also occurs after working with the application for only a few minutes. ![]() The application property "Maximum Session Length in Seconds" is set to 28800 secs (8 hrs), "Maximum Session Idle Time in Seconds" is set to 10800 secs (3 hrs). The behavior is not reproducible on demand. Since that time users complain about getting the error message that their session expired and needing to re-login although they have constantly been working with the application and have not been idle. We have recently upgraded a bug tracking application to Apex 5.0.1. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |