You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Richard S. Hall (Commented) (JIRA)" <ji...@apache.org> on 2012/02/26 16:44:49 UTC

[jira] [Commented] (FELIX-3354) InterruptedException with uninformative message

    [ https://issues.apache.org/jira/browse/FELIX-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13216770#comment-13216770 ] 

Richard S. Hall commented on FELIX-3354:
----------------------------------------

Do you have some suggestions for how to handle this? The difficulty is the Gogo thread has no way of knowing why it is being interrupted. For this particular case, I guess it could check the state of the framework and see if it is stopping and not print anything or something.
                
> InterruptedException with uninformative message
> -----------------------------------------------
>
>                 Key: FELIX-3354
>                 URL: https://issues.apache.org/jira/browse/FELIX-3354
>             Project: Felix
>          Issue Type: Improvement
>          Components: Gogo Shell
>    Affects Versions: gogo.shell-0.8.0
>            Reporter: Lazar Kirchev
>            Priority: Minor
>
> When the OSGi framework, in which the Gogo shell is started, is stopped before the Gogo shell has finished initializing, the following exception occurs:
> gogo: InterruptedException: sleep interrupted
> java.lang.InterruptedException: sleep interrupted
> 	at java.lang.Thread.sleep(Native Method)
> 	at org.apache.felix.gogo.shell.Activator.run(Activator.java:72)
> 	at java.lang.Thread.run(Unknown Source)
> gogo.shell calls Thread.sleep(100) to wait for the gosh command to be registered. The exception occurs when this wait gets interrupted by the stopping of the framework. 
> Since the framework is stopping this interruption does not cause any errors, but the message is not informative and users are getting confused that it is caused by an error in their code.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira