[
https://issues.apache.org/activemq/browse/SMX4KNL-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45774#action_45774
]
Jamie Goodyear commented on SMX4KNL-88:
---------------------------------------
The behavior of the kernel appears to be to exit upon first failed command.
The question at this point should be do we want the kernel to exit or continue
on to the next command?
If the plan is to exit then this issue may be marked as resolved (OSGI
framework issue will have to be resolved at some other date). Otherwise we'll
need to make the kernel skip along to the next command in the chain.
> Failed kernel commands in command chain will hang processing.
> -------------------------------------------------------------
>
> Key: SMX4KNL-88
> URL: https://issues.apache.org/activemq/browse/SMX4KNL-88
> Project: ServiceMix Kernel
> Issue Type: Bug
> Environment: Unix
> Reporter: Jamie Goodyear
>
> Failed kernel commands in command chain will hang processing.
> Ex 1:
> [EMAIL PROTECTED]:/x1/fuse/esb/bin$ ./servicemix echo hi1 \; echo hi2\; echo
> hi3 \; exit
> The command chain to individually echo "hi1", "hi2" and hi3" will print to
> the terminal screen:
> hi1
> hi2
> hi3
> Then smx will exit, returning the terminal prompt.
> Ex 2:
> [EMAIL PROTECTED]:/x1/fuse/esb/bin$ ./servicemix echo hi1 \; ecco hi2\; echo
> hi3 \; exit
> Here the command chain was intended to individually echo "hi" but in this
> case the second echo command has been mis-spelled. Instead of an error
> message being displayed to the screen and continuing on to echo "hi3" however
> smx stops processing commands (the user then has to ctrl+c the process to
> regain the terminal session).
> Is this the behavior we want to maintain?
> Could we set some property perhaps to allow the kernel to ignore failed
> commands in a chain?
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
