Community
Participate
Working Groups
Build Identifier: Virgo Server Version 3.0.1.RELEASE The command runs properly when run from the OSGi framework within eclipse. It is only from Virgo that the problem occurs. When the command is run repeatedly, it fails one time, then succeeds the next time, the fails again the third time, and so on. The command as code: public Object _run(CommandInterpreter intp) { intp.println("_run==>"); intp.println("<==_run"); return null; } The command in use: osgi> run gogo: CommandNotFoundException: Command not found: run osgi> run osgi> run gogo: CommandNotFoundException: Command not found: run osgi> run osgi> Reproducible: Always Steps to Reproduce: 1.Implement CommandProvider in a bundle. 2.Deploy bundle to Virgo 3.Attempt to run the command from the osgi prompt.
Created attachment 206139 [details] Bundle with source included This is the actual code that produces the problem described in the bug report.
(In reply to comment #1) > Created attachment 206139 [details] > Bundle with source included > > This is the actual code that produces the problem described in the bug report. Is this happening only from within Eclipse? I tried to reproduce it by using only Virgo RELEASE 3.0.1, but I couldn't. I took Virgo, started it, deployed the attached bundle through the pickup folder, and then I called more than ten times the run command from telnet console. Always the result was _run==> <==_run So I guess this is a problem only when Virgo is run from Eclipse. I continue the investigation.
(In reply to comment #2) > I continue the investigation. Any progress to report, please?
(In reply to comment #3) > (In reply to comment #2) > > I continue the investigation. > > Any progress to report, please? Most probably there is a race condition between the input streams of the Gogo shell and the IDE shell. I haven't debugged it yet to confirm this.
Thanks for the update. If you can find time to look into this in the next couple of weeks, that would be great.
(In reply to comment #5) > Thanks for the update. If you can find time to look into this in the next > couple of weeks, that would be great. I will try to have a look on it in the next couple of days. It's been waiting for quite a long time now.
I couldn't reproduce the issue. Since there is no answer to my comment, and I cannot reproduce the problem according to the steps, I close the issue. If you could provide more details how to reproduce it, please feel free to re-open it.
Closing the issue.
