student role users experiencing timeout when taking exam

For the last 3 weeks our users who have a student role are experiencing periodic timeouts when submitting exam results. THe rest of the site/functions is a-ok. And this has not happened before. We have had many more concurrent users in the past without this issue. We have looked in the Apache logs and see nothing. We have upgraded our database. We have looked at the network traffic packets. We have increased the timeout in PHP and on our Load Balancer. We have increased the execution time of scripts. We have increased our max_post size. We don't see any server/network errors. We have asked our hosting server (Amazon Web Service) and they can't find anything. So we are confused.

About the time a user experiences the problem we do see this in the log (I have changed the IPs and domans)::
[14/Apr/2017:13:15:05 +0000] "GET /en/?option=com_joomdle&task=enrol&course_id=984&url=https%3A%2F%2Feducation.ourcompany.com%2Fmoodle%2Fmod%2Furl%2Fview.php%3Fredirect%3D1%26id%3D4715 HTTP/1.1" 303 -

[14/Apr/2017:13:15:06 +0000] "GET /moodle/mod/url/view.php?redirect=1&id=4715 HTTP/1.1" 303 438

Does anyone have any idea where I should troubleshoot?

I should point out also that if I am logged in as admin and take the same quiz in Moodle directly and submit it takes milliseconds to submit the quiz answers. It is only if the user is a student and comes from the Joomla side through Joomdle that the submission of quiz answers is slow and appears to time out. But I should mention that the student's answers do make it into the database. It just appears that the website choked on the submission. But it is processing behind the scene. It is causing a lot of user issues/stress. So any help would be appreciated.

Hi.

Are you able to replicate the problem with a non-admin user?
Also, are Joomdle users using Moodle in a wrapper, or Moodle on its own window?
This problem does not seem related to Joomdle, but more Moodle itself. If you can replicate the problem with a joomdle user, you could just create a moodle-only user in Moodle and test again, to confirm.
Also, if you are using the wrapper, you can test without it.

You could also check Moodle forums to see if anyone has experienced similar problems.

Sorry I guess I didn't communicate myself well.

When in Moodle directly we do not experience the slowness or the time outs.

When we go through Joomla/Joomdle with a student role we experience the slowness/the time outs. So it is definitely a Joomdle issue.

We are using Joomdle 1.0.5 We use cURL as the connection method. We use redirectless SSO and single sign out.Joomdle health checks are all green checks
XMLRPC PHP Extension
Joomdlehooks User Plugin enabled
cURL Enabled
Joomla to Moodle HTTP connectivity
Moodle to Joomla HTTP connectivity
Joomdle Web Services

We do use a wrapper.

But again this has not been happening until about 3 weeks ago. Now 4 weeks ago. All students taking quizzes are complaining now. They did not before.

The only thing we did back in February was upgrade PHP. to 5.6.29.

> When in Moodle directly we do not experience the slowness or the time outs.

If you go with a Joomdle user and log in to Moodle directly, and do the same thing, you don't get the problem?

Using Moodle in the wrapper should not have any effect on submitting a quiz, as Joomla page would not even reload, just the wrapper, which is just loading Moodle.

No I don't have the same problem going from Joomla directly to Moodle without the wrapper (as admin). But given your advice I turned the wrapper off and was not able to experience the slowness with the student user either. So it has something to do with the student role and the wrapper. Again this all of a sudden started happening 3-4 weeks ago, for every student.

I have never seen a similar problem before.
If you want, you can send me accessinfo to your site and instructions to reproduce the problem to antonio at joomdle dot com and I will test it out, to see if I notice something odd.

I appreciate your willingness to help out there. Unfortunately they wouldn't go for a t hird party having access even view only access like on a screen share. We still have no found the issue. AWS can't find it in the network packets. I cannot. I cannot find it in the Apache logs. AWS cannot. I cannot find it in the db logs and neither can AWS. So I have no idea.

I am sorry, but there is not much else I can tell from here.