I just received my Bug and installed the SDK.
My system is Atom N270 1.6GHz, 2GB Ram, Windows XP, SP3, 160GB HDD
I tried creating a new application with the following steps:
1. Click New Bug Project
Framework started in 3.75 seconds.
Back in the new program dialog, it just sits there (not sure what is supposed to happen); i still cannot select services; nothing shows up in the target bug frame; no other windows open…
If i try to launch a virtual bug from the toolbar in the IDE…it creates the console output and then nothing. no windows open, nothing changes…
Not sure if this is related…down in the lower right corner of the IDE is a progress bar indicating that something is trying to connect to my local host at port 8082. It never completes. If i click on it to open the progress window, i see 100’s of ‘Testing Connection’ tasks running, but nothing ever connects. If i try to ping the above address in my browser…it cannot find any such page. so it looks like some sort of server service is failing to run.
I did several searches of the forums and cannot find anything that points to this kind of problem.
Thanks for any suggestions for where to look.
Can you open the PDE Error log view and tell me what it says when you try to launch the Virtual BUG?
Window->Show View->Other->PDE Runtime->PDE Error Log
Also, could you tell me which version of the Dragonfly SDK you’re using?
Help->About Eclipse SDK
I will try to clean it up enough to get past the filter…
I am running the latest build: 1_1_7_3
java_net_ConnectException: Connection refused: connect at java_net_PlainSocketImpl_socketConnect(Native Method)
Won’t let me post the rest of the stack trace…
Sorry, That should have been version 1_1_7_39_P20081202
From the stack trace, it looks like the socket connection is being refused.
Looks like i have something on my system that is trying TOO hard to protect me! LOL
The PDE error log lists two errors and one series of warnings….
Continuing series of warnings:
java.net.ConnectException: Connection refused: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(Unknown Source) at java.net.PlainSocketImpl.connectToAddress(Unknown Source) at java.net.PlainSocketImpl.connect(Unknown Source) at java.net.Socket.connect(Unknown Source) at java.net.Socket.connect(Unknown Source) at sun.net.NetworkClient.doConnect(Unknown Source) at sun.net.www.http.HttpClient.openServer(Unknown Source) at sun.net.www.http.HttpClient.openServer(Unknown Source) at sun.net.www.http.HttpClient.<init>(Unknown Source) at sun.net.www.http.HttpClient.New(Unknown Source) at sun.net.www.http.HttpClient.New(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getNewHttpC…(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source) at java.net.URL.openStream(Unknown Source) at com.buglabs.dragonfly.util.WSHelper.get(Unknown Source) at com.buglabs.dragonfly.util.WSHelper.get(Unknown Source) at com.buglabs.dragonfly.util.BugWSHelper.getPrograms(Unknown Source) at com.buglabs.dragonfly.util.BugListener$TestConnectionJob.run(Unknown Source) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Any ideas on what i can try?
I have to do some more digging to figure out what’s going on. I haven’t seen the errors you’re getting. The warning messages are familiar though.
When you start the Virtual Bug, it starts advertising itself using SLP. SLP is a protocol we use that allows the SDK to discover BUGs on the same network. The (Real or Virtual) BUG will advertise it’s IP address. It has some read-only web services on it that tell the SDK (or any http client) some things about itself, such as the modules attached and the applications running. The virtual bug’s default IP address is localhost:8082.
So, what seems to be happening is the virtual bug is starting, perhaps even advertising itself and getting discovered, and then crashing. The SDK meanwhile keeps polling it at it’s expected IP address (http://localhost:8082). I don’t think it’s a firewall issue or anything. I think that it’s simply, there’s nothing there anymore.
If the Virtual Bug started up normally, you should see a little web page being served from the virtual bug at http://localhost:8082.
Now to figure out why the virtual bug isn’t starting for you… I’ll have to dig deeper. Can you start with a fresh clear console and fresh restart of your machine, then start the virtual bug from the toolbar button? I’d like to see the console output from that.
OK, so did a fresh restart of the machine.
Console output is:
Concierge OSGi 1.0.0.RC2 on Windows XP 5.1 starting …
Logger initialized, loglevel is INFO
purging storage …
Mon Dec 15 08:25:31 EST 2008 Debug outputs disabled
Mon Dec 15 08:25:31 EST 2008 Registered servlet /event
Mon Dec 15 08:25:31 EST 2008 Registered servlet at /event.
Mon Dec 15 08:25:31 EST 2008 Registered servlet /module
Mon Dec 15 08:25:31 EST 2008 Registered servlet at /module.
Mon Dec 15 08:25:31 EST 2008 Registered servlet /package
Mon Dec 15 08:25:31 EST 2008 Registered servlet at /package.
Mon Dec 15 08:25:32 EST 2008 Added modlet factory com.buglabs.bug.emulator.module.camera (CAMERA) to map.
Mon Dec 15 08:25:32 EST 2008 Added modlet factory com.buglabs.bug.emulator.module.gps (GPS) to map.
Mon Dec 15 08:25:32 EST 2008 Added modlet factory com.buglabs.bug.emulator.module.lcd (LCD) to map.
Mon Dec 15 08:25:32 EST 2008 Added modlet factory com.buglabs.bug.emulator.module.motion (MOTION) to map.
Mon Dec 15 08:25:32 EST 2008 Added modlet factory com.buglabs.bug.emulator.module.vonhippel (VONHIPPEL) to map.
STARTING file:/D:/BugLabs/eclipse/plugins/com.buglabs.dragonfly.bug.kernel_220.127.116.11_P20081202/kernel/com.buglabs.osgi.shell.jar (:
Framework started in 3.453 seconds.
I did fire up an old linux box that i have and ran virtual bug. it opened normally and opened the small window showing the base unit and would allow me to attach modules to it. So at least i know what it is supposed to look like.
None of that happens on my main windows machine.
If i write a simple program, like the Hello World app. I can select to debug in virtual bug…all the same console output and i can run the app…set breakpoints, the whole magilla. so it seems that virtual bug is running, at least as far as allowing me to debug an app. It just does not seem to support the UI components.
I’m still at a loss as to what’s going on. I see one thing that’s not right to me in your console output—
In my console output I get a few more lines at the end:(:
Framework started in 1.492 seconds.
Mon Dec 15 13:21:04 EST 2008 UserAppManager init: false
Mon Dec 15 13:21:04 EST 2008 Registered servlet /program
Mon Dec 15 13:21:04 EST 2008 Registered servlet /configuration
Mon Dec 15 13:21:04 EST 2008 Registered servlet /service
Mon Dec 15 13:21:04 EST 2008 Registered servlet at /service.
Mon Dec 15 13:21:04 EST 2008 Registered resources /
I don’t see these servlets being registered in your console output, but I see some servlets being registered earlier. The last line I have listed above registers the root servlet, which is what you get when you go to http://localhost:8082. In your output, I see /module is registered, so try that url in a browser after starting the virtual bug—http://localhost:8082/module If that works, then the virtual bug is running, but is missing some services.
The console in eclipse also becomes the osgi interactive console once the virtual bug is running. In the console, after starting the virtual bug, you should be able to hit the enter key a couple of times and the osgi console prompt that looks like a smiley face should appear. At that prompt, type ‘bundles’ and hit enter. Next type ‘services’ and hit enter. I’d like to see the output of those two commands.
One more question. Did you install the SDK via the eclipse plug-in or was it a full install? Another thing that you might consider trying is an older version of the sdk (like the 18.104.22.168 production release at buglabs.net/sdk). It would be interesting to see if you have the same problems there.
In the meantime, I’ll share this thread with the QA team and some of the other devs here to see if someone can reproduce the problem and maybe get closer to an answer.
any chance something else is already using port 8082? ‘netstat -an|grep 8082’ would show ya.
I tried launching virtual bug from the toolbar and then in console window I tried typing carriage returns
Then the virtual bug window opened normally
It looks like I just need to type a few carriage returns into the console each time I launch virtual bug.
One issue is that you can’t launch Virtual Bug in the new project dialog since it is modal and won’t let you type the carriage returns into the console. I tried launching virtual bug first… entered the carriage returns to complete initialization… then opened the new application dialog. The bugs window showed the running virtual bug and allowed selection of services normally. So that seems to be the only work around needed so far.
Thanks to all for helping to track this down.
Now that I know the solution, I did a few searches and I did find where this problem was reported in March 2008 by tevslin. His solution was the same…typing into the console to unlock Virtual Bug. This appears to be a bug in the Win32 version of the toolkit.
I’m glad you were able to find a work-around. This is really helpful for us as well, because it gives us a better indication of problems people might find down the road and at least the start of being able to fix it. So thanks for the feedback. Hopefully we can get this issue resolved for the next SDK release.