Hello again
Using the internal telnetd does not fix the problem, output of this one
command is still going to the java exe std-out instead of the gogo shell.
But the command giving me problems is maybe not very standard:
For one, it executes in a separate thread (not the shell/gogo thread).
This thread comes from a ExecutorService.newFixedThreadPool(1).
Second, the actual command (and its System.out.println) are implemented
in a separate service (not the bundle which exports the gogo command).
Could any of these create the problem as described?
Regards Philipp
On 21.01.2015 09:12, Bulu wrote:
Hello Derek
I then access gogo through telnet (Felix Remote Shell 1.1.2).
Sometimes (rarely), certain of my commands do no longer output to
the shell, instead the output is really going to the std-out of the
java application. Note that at the same time, other of my own
commands in the same bundle still work as expected and output to the
gogo shell.
The Felix remote shell was designed to work before gogo was introduced.
gogo has its own simple telnet daemon:
Welcome to Apache Felix Gogo
g! type telnetd
telnetd is void gogo:telnetd(String[])
true
g! telnetd -?
telnetd - start simple telnet server
Usage: telnetd [-i ip] [-p port] start | stop | status
-i --ip=INTERFACE listen interface (default=127.0.0.1)
-p --port=PORT listen port (default=2019)
-? --help show help
g! telnetd start
telnetd is running on 127.0.0.1:2019
g!
Thanks - I wasn't aware of that internal telnet daemon. I currently
start the framework in non-interactive mode
(gosh.args=--nointeractive) and rely on the telnet daemon to connect
to the shell. How can I make gogo's telnetd start by itself?
Regards Philipp
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
