Recently, we have experienced an unexpected system error.
Some authors might had problem submitting their revised manuscript through EER system from 20 April-22 April.
We apologize for any inconvenience caused.
The server has been restored and the issue has been resolved now.
But if there's any further issue or problem, please let us know. (email to: firstname.lastname@example.org)
And for your information, detailed information on the error is written below.
- Editorial Manager (EM) and ProduXion Manager (PM) sites began to receive a significant influx of traffic beginning on April 19th at midnight which persisted intermittently throughout the following 24 hour period. Peak periods were detected at approximately 11:00am ET on April 19th and 12:00am ET and 4:00am ET on April 20th. These peaks were followed by periods of decreased activity but still tracking above our normal baseline. The increased volume of attempted connections to EM/PM sites caused our web servers, which normally process and distribute this work evenly across our system, to drop connections. These dropped connections peaked at approximately 3:00am ET on April 20th, which generated yellow error screens for users for the following 45 minutes.
The Aries Operations team was alerted to the downtime through automated monitoring and began investigating to identify the root cause just as the first reports from customers came through to the Aries Client Services team. Our Operations team restarted all of the web servers in an effort to re-establish their connection to the system that balances and distributes work evenly to those servers. This, along with some additional remediation and prioritization protocols, has resolved the issue and we believe will prevent future sudden influxes of traffic from disrupting service. We are actively monitoring the queues and servers to ensure the steps taken have resolved the issues going forward and will be investigating ways to enhance processing and monitoring in the future to prevent further similar downtime.