You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@servicemix.apache.org by "Chris Custine (JIRA)" <ji...@apache.org> on 2014/11/17 23:40:34 UTC

[jira] [Assigned] (SMX4-299) OSGi Activator exception and location of stacktrace

     [ https://issues.apache.org/jira/browse/SMX4-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Custine reassigned SMX4-299:
----------------------------------

    Assignee:     (was: Chris Custine)

> OSGi Activator exception and location of stacktrace
> ---------------------------------------------------
>
>                 Key: SMX4-299
>                 URL: https://issues.apache.org/jira/browse/SMX4-299
>             Project: ServiceMix 4
>          Issue Type: Bug
>    Affects Versions: 4.0-m1
>            Reporter: Hadrian Zbarcea
>
> When starting a bundle (i.e., smx@root:osgi> start 167, "runs the start method in the Activator class") and an exception occurs it seems that the shell silently swallows the stacktrace.   The servicemix console only gives the following message:
> ERROR CommandLineExecutionFailed: org.apache.geronimo.gshell.command.CommandException: org.osgi.framework.BundleException: Activator start error in bundle com.example.xxx.yyy.spring_osgi 167.
> It's probably ok that the the stack trace is not displayed in the console, as it would clutter the output, but it should be logged then.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)