You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by "Lahiru Gunathilake (JIRA)" <ji...@apache.org> on 2012/10/26 16:01:12 UTC
[jira] [Resolved] (AIRAVATA-616) Message Box Shutdown thread is
interrupted
[ https://issues.apache.org/jira/browse/AIRAVATA-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lahiru Gunathilake resolved AIRAVATA-616.
-----------------------------------------
Resolution: Invalid
This is not an issue. This is even there in old releases, if you want to reproduce please sumbit a job to interpreter server and try to shutdown.
But there are other issues during shutdown and I will report jiras for them.
Lahiru
> Message Box Shutdown thread is interrupted
> ------------------------------------------
>
> Key: AIRAVATA-616
> URL: https://issues.apache.org/jira/browse/AIRAVATA-616
> Project: Airavata
> Issue Type: Bug
> Components: WS-Messenger
> Affects Versions: 0.5
> Reporter: Suresh Marru
> Fix For: 0.5
>
>
> The message below explains the issue.
> ^C[SimpleHTTPServer] Stop called
> [INFO] Shut down connection listener
> [INFO] Shut down HTTP processors
> [INFO] HTTP protocol handler shut down
> [INFO] broker shutting down
> [WARN] Queue is interrupted to close
> [WARN] Unexpected_exception:
> [INFO] Connection Pool Shutting down
> [INFO] Clean up thread is interrupted to close
> [INFO] Fill up thread is interrupted to close
> [INFO] All connection is closed
> [INFO] Connection Pool Shutdown
> [INFO] Stop ConsumerUrlManager
> [INFO] ConsumerUrlManager Stopped
> [INFO] broker shut down
> [INFO] Message box shutting down
> [INFO] Connection Pool Shutting down
> [INFO] Clean up thread is interrupted to close
> [INFO] Fill up thread is interrupted to close
> [INFO] All connection is closed
> [INFO] Connection Pool Shutdown
> [INFO] broker shutting down
> [INFO] broker shut down
> [WARN] Msgbox cleanup thread is interrupted to close
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira