Thanks! That should help at least for shell commands.
On Wed, Oct 19, 2016 at 11:11 AM, Jean-Baptiste Onofré
wrote:
> It's a command.
>
> Regards
> JB
>
> On 10/19/2016 11:09 AM, Jens Reimann wrote:
>
>> Thanks for the help. Is this a command? Or a configuration option in
>> some file?
>>
>> On
It's a command.
Regards
JB
On 10/19/2016 11:09 AM, Jens Reimann wrote:
Thanks for the help. Is this a command? Or a configuration option in
some file?
On Wed, Oct 19, 2016 at 10:02 AM, Jean-Baptiste Onofré mailto:j...@nanthrax.net>> wrote:
stack-traces-print is useful in dev mode to get t
Thanks for the help. Is this a command? Or a configuration option in some
file?
On Wed, Oct 19, 2016 at 10:02 AM, Jean-Baptiste Onofré
wrote:
> stack-traces-print is useful in dev mode to get the whole stack trace
> directly on the shell console.
>
> Regards
> JB
>
> On 10/19/2016 09:59 AM, Jens
stack-traces-print is useful in dev mode to get the whole stack trace
directly on the shell console.
Regards
JB
On 10/19/2016 09:59 AM, Jens Reimann wrote:
This may be a "noob" question, but to me it looks like that in the karaf
log file and this "log:display" command all exception are missing
This may be a "noob" question, but to me it looks like that in the karaf
log file and this "log:display" command all exception are missing the
"cause" stack traces.
Is there a way to enable this. Google did not turn up anything useful.
Thanks
Jens
--
Jens Reimann
Senior Software Engineer / EME
