We're updating the issue view to help you get more done. 

Log files full of NonexistentConversationException

Description

It looks like there are bots out there which have previously indexed Zanata pages (especially /error/) with cid parameters (from Seam's conversation scope). When Zanata 3.9 sees these requests, Weld tries to interpret the cid parameter as a CDI conversation, even though we don't use CDI's conversation scope. As a result, we get a lot of useless logging like this:

1 2 3 4 5 6 19:29:34,267 ERROR [org.zanata.exception.handler.AbstractExceptionHandler] [Mozilla/5.0 (compatible; MJ12bot/v1.4.5; http://www.majestic12.co.uk/bot.php?+)] [/error/ cid=492 129] [] (http-10.5.106.36:8080-10) [] exception happened in view: /error.xhtml: org.jboss.weld.context.NonexistentConversationException: WELD-000321 No conversation found to restore for id 492129 at org.jboss.weld.context.AbstractConversationContext.activate(AbstractConversationContext.java:227) [weld-core.jar:1.1.33.Final-redhat-1] at org.jboss.weld.jsf.WeldPhaseListener.activateConversations(WeldPhaseListener.java:108) [weld-core.jar:1.1.33.Final-redhat-1] ...

We should install a custom exception handler for NonexistentConversationException, and probably avoid logging them at all, or perhaps log them as DEBUG without the stack trace.

Environment

None

Status

Assignee

Sean Flanigan

Reporter

Sean Flanigan

Labels

None

Tested Version/s

None

Sprint

None

Fix versions

Affects versions

server-3.9.3

Priority

unspecified