[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: AW: [dsdp-tm-dev] My first cautious steps with RSE M2

Hi Norbert,
1) Connecting to the dstore server directly (w/o daemon)
I go through the creation steps with the wizard as you described.
Then in RSE Explorer I go to the Files node and open the properties dialog.
In the Server Launcher Settings I note that here the Remote daemon launching method is still selected. I change it to Connect to running server.
In the Service category, I leave dstore.files and select the Launcher Properties in the Available Services box. I notice that the Launcher property still says Daemon and change it to Running.
In the subsystem category I notice that the value for Port is set to 0; after pressing the little arrow beside the text box I can change it to (in my case) 8799.

After all these changes I can actually see the filesystem on the remote machine.
So here are some questions that arise:
- Are the settings I made in the creation wizard are accepted in the system?
- The Properties _dialog_ and _view_ differ in content, is this acceptable?
The settings from the creation wizard are accepted indeed, I tried this out yesterday (on CVS HEAD). Modifying the server launcher settings on subsystem level after the wizard is not required.

I guess there is a bug with displaying the settings on subsystem level. I know a few modifications have been made here since M2, so I suggest you try CVS HEAD - if it still fails, please file a bug report. You can use the "Submit new bugs" link from the http://www.eclipse.org/dsdp/tm homepage, it will fill some fields for you automatically.

The Properties dialog and view should show the same settings, if not this is a bug. Please file a bug report, thanks.

2) Connecting to the daemon:
Now I changed the launcher properties back to Daemon, set the port to 8799.
In the RSE Explorer I first go the the connection node and from the context menu choose "Connect ...". This starts a background task (visible in the Progress view, title "Connect (RSE subsystem operation)") whose comment says 

"Connecting to NB14520D.ATS1TEST.NBGM.SEIMENS.DE at port 8799: Starting Remote Systems Explorer host server using daemon"

The progress bar keeps moving left to right and has done so for several minutes. Apart from that nothing happens.

Next I select the Files subsystem and from the context menu select Connect. Connecting starts another background task ("Connect (RSE subsystem operation)") with the comment:

"Connecting to NB14520D.ATS1TEST.NBGM.SEIMENS.DE at port 8799"

The progress bar moves, nothing else happens.

Finally I expand the Root node of the Files subsystem. Another background task ("Resolve filter strings") starts, the comment as above. The progress bar moves. Nothing else moves. Below the Root node appears an "Empty List" node.

This goes on until I kill the daemon on the server. If I do this I get a number of error messages which say, more or less:

"Failed to connect to the daemon on NB14520D.ATS1TEST.NBGM.SIEMENS.DE using port 8799 with an unexpected exception"

Can you make anything of this?
Hm, let's rule out all simple possible problem causes first:
  • Make sure the server is stopped on port 8799 before you launch the daemon
  • Launch the daemon on port 8799
  • Create a NEW connection in the wizard for systemtype Linux; set the daemon port 8799 in the wizard / Server Launcher Settings; press finish and try to connect.
I tested connecting a daemon on a nonstandard port yesterday, so this should normally work.

One reason why this could fail is, that when the daemon is about to start a server, it might use a port not suitable for your firewall. Consequently, daemon would start the server but client could not connect it due to the firewall - this would explain the never-ending progress.

The daemon.pl script allows specifying a port range, please try doing so with a range acceptable for your firewall.

Another problem might be that you're trying to use the gcj based Java on SuSE Linux. Try typing "java -version" as root and see what JVM you are running - only Sun and IBM JVMs are supported for now.

If it still fails, the reason for failure might be similar to

Such startup problems can be debugged by adding some debug output to auth.pl, as shown here:

Please let us know if this helps.

-----Ursprüngliche Nachricht-----
Von: dsdp-tm-dev-bounces@xxxxxxxxxxx [mailto:dsdp-tm-dev-bounces@xxxxxxxxxxx] Im Auftrag von Oberhuber, Martin
Gesendet: Montag, 29. Mai 2006 10:24
An: Target Management developer discussions
Betreff: RE: [dsdp-tm-dev] My first cautious steps with RSE M2

Hello Norbert,

I think your misunderstanding was, that you started a server
(and not a daemon) on port 8799, but you tried contacting a
daemon (and not a server). Your test will run alright when
you do the following on your target:
   su -                  #become root
   perl daemon.pl 8799

The daemon's purpose is to start servers. But you can also 
start a server manually (as you did). Note that when you 
manually start a server, you can do this with a normal user
id (and not root). The password and username that you enter
in RSE is unnecessary in this case -- you can enter just
anything, it is not used.

When you manually start the dstore server on the target, you 
need to configure the connection such that the already-running
server is selected:

* Start RSE
* New > Connection > Systemtype Linux
* On the second wizard page ("Files"),
  - keep dstore.files selected in the upper left
  - select "Launcher Properties" in the lower left
  - select "Launcher" : "Running" in the right pane
* Press Finish
* Back in the RSE tree, select the "Files" node of your new connection
  - In the Properties View, select "Port" and enter your port 8799
* Now you can expand the Files node to connect.

Having to edit the port outside the wizard is a workaround for
now, bugzilla https://bugs.eclipse.org/bugs/show_bug.cgi?id=142969
tracks the request to have this in the wizard.

When you want to do more with the RSE, I recommend you connect
to the CVS Repository directly. This is really simple now: just
launch Eclipse 3.2, and choose File > Import > Team > Project Set.
You find the "rse-anonymous.psf" project set in the top left 
paragraph of our main developer page, at

The remotecdt example will not compile unless you have CDT 
installed, but you can ignore these errors and simply close
the remotecdt project in your workspace.

Martin Oberhuber - WindRiver, Austria
dsdp-tm-dev mailing list