Hi, I've tried the Java example the last view weeks and I think it's pretty amazing! Everything worked fine and I didin't had any problems. Until today.
I used the Java example code (without any changes) but I didn't got any result. It's stucking in the "Waiting..." loop.
I don't know whats the problem. Are there any problems with the cloud server??
For ABBYY developer: Here are some information of an example task which didn't work:
[credits="0", estimatedProcessingTime="1", filesCount="1", id="8b8b3a13-aa69-4c56-a881-8b12f896625e", registrationTime="2012-06-30T16:51:41Z", status="Queued", statusChangeTime="2012-06-30T16:51:41Z"]
Using a .tiff-file with a size of 24kb.
If you need additional information (e.g. the file itself), please let me know.
Thanks for your help!!
Greetings from Germany!
Comments
17 comments
Hi, I just try the service too and have the same problem. Looks like the service is down somewhat. Let's see how good the monitoring of this service is.
After 90 minutes the task was processed, a new task still stays again long time in the queue. Not really what I expect from a cloud service.
I've waited about 100 minutes to get an result. Is this service still a beta?
mhh, comment to a comment doesn't works. So here my comment as a new answer.
I don't think the service is in Beta. Most Betas on the web don't charge money for the service. All my documents took about 85 to 100 minutes to process. There should be a monitoring which constantly monitors the processtime of documents and if the average is exceeding a certain time there should be an notification sent the the sysadmins. I'm wondering now if they provide a SLA.
And now the service throws a licence exception. It should be not a problem to get a new license from the own company. Please install one that will expire in 10 years again :-(
Dear friends,
Some of you were affected by the ABBYY Cloud OCR SDK service failure occurred yesterday.
We apologize for potential impact to your business and thank you for your patience. The problem has been already resolved, please see the details below.
Issue summary
Corrective and Preventive measures taken by ABBYY Cloud OCR SDK team
Please be assured that system reliability is a top priority at ABBYY, and we are making continuous improvements to make our service the best on the web.
Sincerely yours, Alsu. ABBYY, Marketing manager, SDK products.
PS: This was the first serious failure since the service started its work on Feb, 2012 (Public Beta).
Hi, just wanted to know when will the service be available at full capacity and with no extended waiting.
Thanks,
Hi Carlos!
Currently service is running in its normal mode and is available at full capacity. Occasional processing delay issues should be fixed with the new release planned for the beginning of the next week.
Thanks Alsu for your quick response.
The thing is that I've been trying all day and the delays are not occasional for me, they just keep happening, but I can live with that if it's going to be fixed next week.
One more thing, are we going to have to make major changes to our programs or is it going to be all server-side?
The current REST API will be preserved, we regularly make changes to the service internals without breaking the API contract.
Btw it'd be great if you shared what delays you consider to be permissible for your usecase.
In our use case case is a really small delay essential: We develop software for German fire departments. In Germany it is possible to receive additional information for every fire run via a fax message. Our software now uses the OCR service to get these information out of the fax (e.g. destination ("where the fire is burning")). After ABBYY delivers us the converted fax, our software now can submit these information via SMS, eMail, ... A few seconds (or up to 1 minute) for each conversion are ok, but 90 minutes is much too long. I hope you now understand why fast conversion is necessary for us
How many documents per day you expect to recognize?
Difficult to say. From 10 to 200. In depends on how many costumer we can get and how many fire runs they have.
How flies, I am really surprised to see such an old thread.
I apologize for the confusion. If you're not getting any result or seeing "Waiting..." in a Java example, it's likely that the code you're running is waiting for some input or action to proceed. Here are a few possible reasons and solutions:
Input required: The Java code might be expecting some input from the user before it can proceed further. Check the code for any
ScannerorSystem.instatements that prompt for user input. Make sure you provide the required input in the console to move the program forward.Infinite loop: The Java code could be stuck in an infinite loop, causing it to keep running without producing any output. Check for any loops in the code and ensure that there is a condition or mechanism to exit the loop.
Synchronization or threading issues: If the Java code involves multi-threading or synchronization, there might be a situation where the program is waiting for a thread to complete or a lock to be released. Review the code for any synchronization constructs like
wait(),notify(), orsynchronizedblocks and ensure they are used correctly.External dependencies: The Java code might rely on external resources or services that are not available or taking longer to respond. Make sure that any necessary resources, such as databases or web services, are accessible and functioning properly.
It would be helpful if you could provide the specific code snippet or more context about the Java example you are working with. That way, I can assist you further in identifying the issue and providing a more accurate solution.
MyCenturaHealth
I had a problem like this before, and I'm still looking for a good answer. The same problem still hasn't been fixed.
mynorthsidehr
We create software for German fire departments, thus a very low latency is crucial in those situations. In Germany, you can get a fax with further details about each fire run you conduct. In order to extract data from faxes, such as the location ("where the fire is burning"), our programme now makes use of an OCR service. Once ABBYY sends us the converted fax, our programme can send the details in question through SMS, eMail,... A minute or less for each conversion is fine, but 90 minutes is excessive. I think you see why we need a quick turnaround on this conversion. aim provider portal
Please sign in to leave a comment.