Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » DSDP - Target Management » remote project / remote debug
remote project / remote debug [message #7738] Fri, 20 April 2007 05:12 Go to next message
Eclipse User
Originally posted by: john_w_john2001.yahoo.com

Hi folks,

I am trying to setup a remote debug environment where the source and
debuggable java process are on a remote windows XP machine.

Now, my host machine is windows XP too and has eclipse 3.2 + RSE 2.0
installed. I am trying various options to attach to remote java process to
debug and cant get the debugger to locate the source. I figure debug
launcher does not seem to know anything about RSE yet?

I then tried creating a remote project (from the context menu) hoping I
could point the debug launcher to this project, but the create remote
project step throws an "Internal Error" dialog box with the following
message:
" org.osgi.framwork.Bundle.getBundleContext()Lorg/osgi/framewo rk/BundleContext; "


I also tried creating a new project (new->project->general->RSE location),
which also fails with the following error "Invalid project. A Link
location must be specified."

Is there something I am missing here?

Thanks
V
Re: remote project / remote debug [message #7760 is a reply to message #7738] Fri, 20 April 2007 06:22 Go to previous messageGo to next message
Eclipse User
Originally posted by: john_w_john2001.yahoo.com

the log shows me the following exception

!ENTRY org.eclipse.core.jobs 4 2 2007-04-20 03:20:19.647
!MESSAGE An internal error occurred during: "Checking resources".
!STACK 0
java.lang.NoSuchMethodError:
org.osgi.framework.Bundle.getBundleContext()Lorg/osgi/framew ork/BundleContext;
at
org.eclipse.rse.internal.eclipse.filesystem.RSEFileStore.isR esourcesPluginUp(RSEFileStore.java:197)
at
org.eclipse.rse.internal.eclipse.filesystem.RSEFileStore.get Impl(RSEFileStore.java:183)
at
org.eclipse.rse.internal.eclipse.filesystem.RSEFileStore.fet chInfo(RSEFileStore.java:258)
at
org.eclipse.rse.internal.eclipse.filesystem.RSEFileStore.fet chInfo(RSEFileStore.java:240)
at
org.eclipse.core.internal.localstore.FileSystemResourceManag er.attributes(FileSystemResourceManager.java:150)
at
org.eclipse.core.internal.resources.Resource.getResourceAttr ibutes(Resource.java:1042)
at
org.eclipse.ui.actions.ReadOnlyStateChecker.checkReadOnlyRes ources(ReadOnlyStateChecker.java:156)
at
org.eclipse.ui.actions.ReadOnlyStateChecker.checkReadOnlyRes ources(ReadOnlyStateChecker.java:109)
at
org.eclipse.ui.actions.DeleteResourceAction.getResourcesToDe lete(DeleteResourceAction.java:667)
at
org.eclipse.ui.actions.DeleteResourceAction.access$0(DeleteR esourceAction.java:656)
at
org.eclipse.ui.actions.DeleteResourceAction$2.run(DeleteReso urceAction.java:558)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
Re: remote project / remote debug [message #7799 is a reply to message #7760] Tue, 24 April 2007 06:59 Go to previous messageGo to next message
Martin Oberhuber is currently offline Martin Oberhuber
Messages: 975
Registered: July 2009
Senior Member
Hello V W,

Don't run TM 2.0 with Eclipse 3.2 -- it does not work.
The download pages clearly say that under "Requirements"
on top.

Please get Eclipse 3.3M6, and TM 2.0M6a
http://download.eclipse.org/dsdp/tm/downloads/

With these, remote Projects and EFS work properly. Then,
for your Java Source, create a new local java project:
File > New > Project (ON THE LOCAL WORKSPACE).
Inside that project, create a new folder linked to
your remote location:
File > New > Folder > Advanced > Link to folder
in filesystem > Remote > RSE ...

Now, in the Debug Launcher, you should be able to specify
this folder (or any folder below it) as the source of
your debuggee.

Thanks,
--
Martin Oberhuber
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm
Re: remote project / remote debug [message #7819 is a reply to message #7799] Tue, 24 April 2007 16:07 Go to previous messageGo to next message
Eclipse User
Originally posted by: john_w_john2001.yahoo.com

Martin,

Thanks! Yeah, I figured this out thro' the docs and tried 3.3M6 and was
able to get past those setup errors. I didnt think this news group was
active - glad its been watched!

Back to the discussion - I am working on selling the idea of RSE + remote
projects to my dev team and trying to setup a prototype. After moving to
3.3M6, I am able to add the remote folder as a resource, however the
refresh never completes and I need to keep terminating eclipse. Its a
fairly large project with about 2000 files to refresh and I have left it
running overnight just in case I wasn't giving it enough time.

The "create remote project" step fails on windows XP with the following
error -

!ENTRY org.eclipse.rse.ui 4 0 2007-04-24 00:45:47.203
!MESSAGE Error creating foo project
!STACK 0
java.lang.RuntimeException: org.eclipse.core.runtime.CoreException: Could
not get remote file
at
org.eclipse.rse.internal.eclipse.filesystem.RSEFileStore.fet chInfo(RSEFileStore.java:249)
at
org.eclipse.core.internal.localstore.FileSystemResourceManag er.hasSavedDescription(FileSystemResourceManager.java:414)
at org.eclipse.core.internal.resources.Project.create(Project.j ava:245)
at
org.eclipse.rse.internal.eclipse.filesystem.ui.actions.Creat eRemoteProjectActionDelegate.createRemoteProject(CreateRemot eProjectActionDelegate.java:196)
at
org.eclipse.rse.internal.eclipse.filesystem.ui.actions.Creat eRemoteProjectActionDelegate.access$0(CreateRemoteProjectAct ionDelegate.java:173)
at
org.eclipse.rse.internal.eclipse.filesystem.ui.actions.Creat eRemoteProjectActionDelegate$1.run(CreateRemoteProjectAction Delegate.java:135)
at
org.eclipse.jface.operation.ModalContext$ModalContextThread. run(ModalContext.java:113)
Caused by: org.eclipse.core.runtime.CoreException: Could not get remote
file
at
org.eclipse.rse.internal.eclipse.filesystem.RSEFileStoreImpl .getRemoteFileObject(RSEFileStoreImpl.java:277)
at
org.eclipse.rse.internal.eclipse.filesystem.RSEFileStoreImpl .fetchInfo(RSEFileStoreImpl.java:470)
at
org.eclipse.rse.internal.eclipse.filesystem.RSEFileStore.fet chInfo(RSEFileStore.java:258)
at
org.eclipse.rse.internal.eclipse.filesystem.RSEFileStore.fet chInfo(RSEFileStore.java:240)
... 6 more
Re: remote project / remote debug [message #7840 is a reply to message #7819] Thu, 26 April 2007 04:42 Go to previous message
Martin Oberhuber is currently offline Martin Oberhuber
Messages: 975
Registered: July 2009
Senior Member
Hello VW,

As documented, "Create Remote Project" should not be used right
now, due to some issues with the Platform core.resources during
early startup.

It's much better to create a LOCAL empty project, and then add
remote folders as linked resource.

Your backtrace seems to indicate that there is some communication
problem to the remote side. Perhaps a threading issue. At any
rate, the problem happens when creating the .project file (I
see this due to the "hasSaveDescription()" stack frame), so with
a local project + linked resources you should be able to work
around it.

Note that the linked resources are saved in your .project file,
so you'll be able to team-share the .project file through CVS
or whatever tool you use, and all your team members will easily
get access to the same remote folders you set up once. At some
point you should also be able to team-share the RSE connection
but there are currently some bugs in there.

Thanks,
--
Martin Oberhuber
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm


V W wrote:
Re: remote project / remote debug [message #566987 is a reply to message #7738] Fri, 20 April 2007 06:22 Go to previous message
Eclipse User
Originally posted by: john_w_john2001.yahoo.com

the log shows me the following exception

!ENTRY org.eclipse.core.jobs 4 2 2007-04-20 03:20:19.647
!MESSAGE An internal error occurred during: "Checking resources".
!STACK 0
java.lang.NoSuchMethodError:
org.osgi.framework.Bundle.getBundleContext()Lorg/osgi/framew ork/BundleContext;
at
org.eclipse.rse.internal.eclipse.filesystem.RSEFileStore.isR esourcesPluginUp(RSEFileStore.java:197)
at
org.eclipse.rse.internal.eclipse.filesystem.RSEFileStore.get Impl(RSEFileStore.java:183)
at
org.eclipse.rse.internal.eclipse.filesystem.RSEFileStore.fet chInfo(RSEFileStore.java:258)
at
org.eclipse.rse.internal.eclipse.filesystem.RSEFileStore.fet chInfo(RSEFileStore.java:240)
at
org.eclipse.core.internal.localstore.FileSystemResourceManag er.attributes(FileSystemResourceManager.java:150)
at
org.eclipse.core.internal.resources.Resource.getResourceAttr ibutes(Resource.java:1042)
at
org.eclipse.ui.actions.ReadOnlyStateChecker.checkReadOnlyRes ources(ReadOnlyStateChecker.java:156)
at
org.eclipse.ui.actions.ReadOnlyStateChecker.checkReadOnlyRes ources(ReadOnlyStateChecker.java:109)
at
org.eclipse.ui.actions.DeleteResourceAction.getResourcesToDe lete(DeleteResourceAction.java:667)
at
org.eclipse.ui.actions.DeleteResourceAction.access$0(DeleteR esourceAction.java:656)
at
org.eclipse.ui.actions.DeleteResourceAction$2.run(DeleteReso urceAction.java:558)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
Re: remote project / remote debug [message #567026 is a reply to message #7760] Tue, 24 April 2007 06:59 Go to previous message
Martin Oberhuber is currently offline Martin Oberhuber
Messages: 975
Registered: July 2009
Senior Member
Hello V W,

Don't run TM 2.0 with Eclipse 3.2 -- it does not work.
The download pages clearly say that under "Requirements"
on top.

Please get Eclipse 3.3M6, and TM 2.0M6a
http://download.eclipse.org/dsdp/tm/downloads/

With these, remote Projects and EFS work properly. Then,
for your Java Source, create a new local java project:
File > New > Project (ON THE LOCAL WORKSPACE).
Inside that project, create a new folder linked to
your remote location:
File > New > Folder > Advanced > Link to folder
in filesystem > Remote > RSE ...

Now, in the Debug Launcher, you should be able to specify
this folder (or any folder below it) as the source of
your debuggee.

Thanks,
--
Martin Oberhuber
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm
Re: remote project / remote debug [message #567049 is a reply to message #7799] Tue, 24 April 2007 16:07 Go to previous message
Eclipse User
Originally posted by: john_w_john2001.yahoo.com

Martin,

Thanks! Yeah, I figured this out thro' the docs and tried 3.3M6 and was
able to get past those setup errors. I didnt think this news group was
active - glad its been watched!

Back to the discussion - I am working on selling the idea of RSE + remote
projects to my dev team and trying to setup a prototype. After moving to
3.3M6, I am able to add the remote folder as a resource, however the
refresh never completes and I need to keep terminating eclipse. Its a
fairly large project with about 2000 files to refresh and I have left it
running overnight just in case I wasn't giving it enough time.

The "create remote project" step fails on windows XP with the following
error -

!ENTRY org.eclipse.rse.ui 4 0 2007-04-24 00:45:47.203
!MESSAGE Error creating foo project
!STACK 0
java.lang.RuntimeException: org.eclipse.core.runtime.CoreException: Could
not get remote file
at
org.eclipse.rse.internal.eclipse.filesystem.RSEFileStore.fet chInfo(RSEFileStore.java:249)
at
org.eclipse.core.internal.localstore.FileSystemResourceManag er.hasSavedDescription(FileSystemResourceManager.java:414)
at org.eclipse.core.internal.resources.Project.create(Project.j ava:245)
at
org.eclipse.rse.internal.eclipse.filesystem.ui.actions.Creat eRemoteProjectActionDelegate.createRemoteProject(CreateRemot eProjectActionDelegate.java:196)
at
org.eclipse.rse.internal.eclipse.filesystem.ui.actions.Creat eRemoteProjectActionDelegate.access$0(CreateRemoteProjectAct ionDelegate.java:173)
at
org.eclipse.rse.internal.eclipse.filesystem.ui.actions.Creat eRemoteProjectActionDelegate$1.run(CreateRemoteProjectAction Delegate.java:135)
at
org.eclipse.jface.operation.ModalContext$ModalContextThread. run(ModalContext.java:113)
Caused by: org.eclipse.core.runtime.CoreException: Could not get remote
file
at
org.eclipse.rse.internal.eclipse.filesystem.RSEFileStoreImpl .getRemoteFileObject(RSEFileStoreImpl.java:277)
at
org.eclipse.rse.internal.eclipse.filesystem.RSEFileStoreImpl .fetchInfo(RSEFileStoreImpl.java:470)
at
org.eclipse.rse.internal.eclipse.filesystem.RSEFileStore.fet chInfo(RSEFileStore.java:258)
at
org.eclipse.rse.internal.eclipse.filesystem.RSEFileStore.fet chInfo(RSEFileStore.java:240)
... 6 more
Re: remote project / remote debug [message #567061 is a reply to message #7819] Thu, 26 April 2007 04:42 Go to previous message
Martin Oberhuber is currently offline Martin Oberhuber
Messages: 975
Registered: July 2009
Senior Member
Hello VW,

As documented, "Create Remote Project" should not be used right
now, due to some issues with the Platform core.resources during
early startup.

It's much better to create a LOCAL empty project, and then add
remote folders as linked resource.

Your backtrace seems to indicate that there is some communication
problem to the remote side. Perhaps a threading issue. At any
rate, the problem happens when creating the .project file (I
see this due to the "hasSaveDescription()" stack frame), so with
a local project + linked resources you should be able to work
around it.

Note that the linked resources are saved in your .project file,
so you'll be able to team-share the .project file through CVS
or whatever tool you use, and all your team members will easily
get access to the same remote folders you set up once. At some
point you should also be able to team-share the RSE connection
but there are currently some bugs in there.

Thanks,
--
Martin Oberhuber
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm


V W wrote:
Previous Topic:remote project / remote debug
Next Topic:Reminder: DSDP-TM Monthly Phone Call Wed, 2-May at 9am PST
Goto Forum:
  


Current Time: Fri Apr 18 22:07:04 EDT 2014

Powered by FUDForum. Page generated in 0.02226 seconds