[
https://issues.apache.org/jira/browse/FELIX-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14294016#comment-14294016
]
Bruce Edge commented on FELIX-4766:
-----------------------------------
One fix for this is to update the docs for the gogo shell. When run from a
container with no available stdout, one needs to use
{code}
-Dgosh.args=--nointeractive
{code}
AFAICT this detail is only available in email list archives and the source and
not in any docs.
Although, IMO it shouldn't bring down the entire OSGi framework just because
the shell can't access stdout, so I could see this as a gogo shell bug in how
it handles the stdout open failure case.
> If stdout is not available, gosh shell terminates felix runtime unless
> -Dgosh.args=--nointeractive used
> -------------------------------------------------------------------------------------------------------
>
> Key: FELIX-4766
> URL: https://issues.apache.org/jira/browse/FELIX-4766
> Project: Felix
> Issue Type: Bug
> Components: Gogo Shell
> Affects Versions: gogo.shell-0.10.0
> Environment: ubuntu linux 14.04, oracle java 7u72, sling launchpad-8
> Reporter: Bruce Edge
> Priority: Trivial
>
> Filed as a sling bug initially, but I realized that this is a shell issue.
> SLING-4328
> If stdout is not available, as in the case of the sling embedded felix build,
> gosh shell terminates the felix runtime unless -Dgosh.args=--nointeractive is
> passed to the JVM:
> INFO [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.gogo.shell
> BundleEvent STARTED
> INFO [FelixShutdown] org.apache.felix.framework BundleEvent STOPPING
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
