Outage between 22:06 and 22:27 BST on the 23/10/2015
Posted: Fri Oct 23, 2015 6:23 pm
We had a pretty catastrophic issue with the WURFL service when it appears to have experienced an outage between the times above.
We had a spate of this error in our logs (around 44k):
Which is fine - the service was not available for a short time... but the Java client was taking around 5 minutes to fail... which brought all of our servers to a grinding halt, using up every available thread in the pools and caused a massive spike on the number of open transactions on our db and other general nastiness.
The question for me is, how do I reduce the time out on the Java client to make WURFL fail fast and generally be kind to our servers and not bring our entire operation down?
Regards,
Jason
We had a spate of this error in our logs (around 44k):
Code: Select all
com.scientiamobile.wurflcloud.exc.UnreachableServerException: There is no possibility to answer. Probably the Cloud Service is unreachable, or you don't have required authorization to access it
at com.scientiamobile.wurflcloud.ThrowExceptionRecoveryManager.getRecoveryID(ThrowExceptionRecoveryManager.java:37)
at com.scientiamobile.wurflcloud.CloudClient.tryRecovery(CloudClient.java:487)
at com.scientiamobile.wurflcloud.CloudClient.detectDevice(CloudClient.java:395)
at com.scientiamobile.wurflcloud.CloudClientManager.getDeviceFromRequest(CloudClientManager.java:143)
at co.uk.realistic.regal.decivedetection.api.DeviceDetectionWurflimpl.detect(xxxxx)
The question for me is, how do I reduce the time out on the Java client to make WURFL fail fast and generally be kind to our servers and not bring our entire operation down?
Regards,
Jason