You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am experimenting with tess4j for about 2 weeks in total. When i run my junit test case, everything is good. Also it gives great results.
Now i implemented it into an war application and deployed it to payara app server.
If i dont run any OCR with tess4j (not creating instance), the war can be redeployed infinity number of times. But when i do run OCR (also working great as expected from tests) then i cannot redeploy the app any more via IDE (IntelliJ).
it uses constantly 20% of the CPU after OCR , even in idle condition when OCR finished OK with the ocr text.
Error from redeploy:
[2019-11-25 01:22:53,352] Artifact doksis-ui:war exploded: java.io.IOException: com.sun.enterprise.admin.remote.RemoteFailureException: Error occurred during deployment: Exception while loading the app : EJB Container initialization error. Please see server.log for more details.
And there is no additional errors in server.log about this issue.
Hello there.
I am experimenting with tess4j for about 2 weeks in total. When i run my junit test case, everything is good. Also it gives great results.
Now i implemented it into an war application and deployed it to payara app server.
If i dont run any OCR with tess4j (not creating instance), the war can be redeployed infinity number of times. But when i do run OCR (also working great as expected from tests) then i cannot redeploy the app any more via IDE (IntelliJ).
Error from redeploy:
[2019-11-25 01:22:53,352] Artifact doksis-ui:war exploded: java.io.IOException: com.sun.enterprise.admin.remote.RemoteFailureException: Error occurred during deployment: Exception while loading the app : EJB Container initialization error. Please see server.log for more details.
And there is no additional errors in server.log about this issue.
Any idea ?
Using like this:
The text was updated successfully, but these errors were encountered: