Bug: Custom sentence count setting in annotation view causes internal errors

21 views
Skip to first unread message

Matthias Grabmair

unread,
Sep 20, 2016, 2:28:02 PM9/20/16
to webanno-user
I am running Webanno 2.3.1 on tomcat 7. Some of our annotators (who have user-only accounts) are getting internal errors when opening files to annotate. 

I could reproduce it using those logins only, so I checked the user-specific settings files. No custom settings were made (i.e. no change in layers), but the sentence count was increased from 5 to 200 or other numbers. I removed the settings files for those users and the problem went away. When I increased the sentence display number again, it happened with 200, but not with 50. The total sentence count for that file was ~230. It was also fine with 10 but after forwarding a couple of "pages" it produced internal errors again. I was not able to figure out a pattern in this. Can one of the devs look into this to see where this may come from and if there is hack/trick I can use to prevent this from happening?

For now I instructed our annotators to not change the setting, but the default value of 5 is uncomfortable for the kinds of documents we are annotating.

Thanks!

Richard Eckart de Castilho

unread,
Sep 20, 2016, 2:31:30 PM9/20/16
to Matthias Grabmair, webanno-user
I would guess that towards the end of the document, there is some inconsistency/problem with the data such that it fails to render whenever the section containing that problem is part of the render window. So e.g. if you have a very large window or if you have a smaller window and page forward, you'd eventually hit that.

Can you try triggering the problem and check what gets logged to catalina.out when you do so?

Cheers,

-- Richard

Matthias Grabmair

unread,
Sep 20, 2016, 2:36:57 PM9/20/16
to webanno-user, matthias...@gmail.com
Interestingly nothing gets logged on Catalina. The files in /opt/webanno/logs do not show any exception. Only the server startup.

I can go through the document in 5-sentence-steps and it displays fine. It occurs only when the setting is changed. I am using a custom sentence segmenter, maybe there is some problem there. I will export the file and check.

Matthias Grabmair

unread,
Sep 20, 2016, 6:12:42 PM9/20/16
to webanno-user, matthias...@gmail.com
Ok, I did a sanity check and I have not overlapping sentence annotation. The one anomaly I could find is a period in the sofa that is not covered by a sentence annotation (segmentation curation error) followed by special characters. The sofa string displays as:

[... text ...].








[... text ...]

Now the funny thing: When I log in with user privileges and I forward to this part of the sofa, I get the internal error. When I log in as admin, it displays fine.

I am attaching the exported zip (xmi + typsesystem) of the document here.
webanno489244915003725016export.zip

Richard Eckart de Castilho

unread,
Oct 2, 2016, 6:23:30 AM10/2/16
to Matthias Grabmair, webanno-user
Hi Matthias,

> On 21.09.2016, at 00:12, Matthias Grabmair <matthias...@gmail.com> wrote:
>
> Ok, I did a sanity check and I have not overlapping sentence annotation. The one anomaly I could find is a period in the sofa that is not covered by a sentence annotation (segmentation curation error) followed by special characters. The sofa string displays as:
>
> [... text ...].&#10;&#10;&#10;&#10;&#10;&#10;&#10;&#10;&#10;[... text ...]
>
> Now the funny thing: When I log in with user privileges and I forward to this part of the sofa, I get the internal error. When I log in as admin, it displays fine.
>
> I am attaching the exported zip (xmi + typsesystem) of the document here.

Can you export the whole project via the project settings pane and send it to me privately?
That would greatly facilitate the debugging process.

Best,

-- Richard

Richard Eckart de Castilho

unread,
Oct 2, 2016, 6:31:41 AM10/2/16
to Matthias Grabmair, webanno-user
Btw. I have imported the XMI file into the latest WebAnno 3 SNAPSHOT version and cannot reproduce a crash there.

Again, maybe I could reproduce it if I could import your project as-is into WebAnno 3... or maybe the bug does
not exist there anymore.

Cheers,

-- Richard
Reply all
Reply to author
Forward
0 new messages