"Error destroying an instance" triggered by logout


We are getting

while logout.

Steps to reproduce:

  • Start local zanata instance.

  • Go to zanata home.

  • Login to zanata.

  • then click on logout.

  • Observe the console log/server logs.

Actual Result:

  • Error while logout.

Expected Result:

  • There should not be any error thrown on server side while logout.


Fedora 25
Firefox 50.


Patrick Huang
February 3, 2017, 5:43 AM

To enable debug logging on the console, do:

  • docker exec -it zanata bash

  • wildfly/bin/jboss-cli.sh

  • connect

  • /subsystem=logging/console-handler=CONSOLE:write-attribute(name=level,value=DEBUG)

Sean Flanigan
February 3, 2017, 5:36 AM

This seems to be a problem with AuthenticatedAccountRequestScopeHolder during the logout process (which seems to be in the middle of destroying the request scope). Could you take a look please?

Sean Flanigan
February 3, 2017, 4:26 AM

Thanks .

Okay, so this is the exception we need to debug:

Sachin Pathare
February 3, 2017, 4:19 AM

Attached server1_log.txt logs got using docker exec zanata cat /opt/jboss/wildfly/standalone/log/server.log > server1_log.txt

Sean Flanigan
February 3, 2017, 4:12 AM

We need to see the contents of the file server.log inside the docker container. Unfortunately, the stdout logging is not set up to include DEBUG/TRACE messages (in standalone.xml).

Try something like this:
docker exec zanata cat /opt/jboss/wildfly/standalone/log/server.log

Ready for Release


Patrick Huang


Sachin Pathare


Tested Version/s