Eclipse Community Forums: AspectJ » AJDT seems to be killing my workspace

Home » Language IDEs » AspectJ » AJDT seems to be killing my workspace

AJDT seems to be killing my workspace [message #22211]

Fri, 16 May 2003 15:33

Eclipse User

Originally posted by: eclipse.wingspread.fastmail.fm

Ever since I've installed the ADJT plugin, my Eclipse environment seems to
be unstable. I can use it for awhile and then suddenly when I start it up
I'll get messages about 'problems occurred while rebuilding workspace' or
something like that. In the .log file I always see something like this:

!MESSAGE Problems occurred when invoking code from plug-in:
"org.eclipse.core.runtime".
org.eclipse.swt.SWTException: Invalid thread access
[...]
!ENTRY org.eclipse.core.runtime 4 2 May 16, 2003 14:23:42.51
!MESSAGE Plug-in org.eclipse.ajdt.ui was unable to load class
org.eclipse.ajdt.internal.builder.Builder.
org.eclipse.core.internal.boot.DelegatingLoaderException:
org.eclipse.core.runtime.CoreException: Problems encountered starting up
plug-in: "org.eclipse.jdt.ui".
at
org.eclipse.core.internal.plugins.PluginDescriptor.internalD oPluginActivation(PluginDescriptor.java:746)
[...]
!ENTRY org.eclipse.core.resources 2 1 May 16, 2003 14:23:42.51
!MESSAGE Skipping builder org.eclipse.ajdt.ui.ajbuilder for project Unit
Test Support. Either the builder is missing from the install, or it belongs
to a project nature that is missing or disabled.
!ENTRY org.eclipse.core.runtime 4 2 May 16, 2003 14:23:42.67
!MESSAGE Plug-in org.eclipse.ajdt.ui was unable to load class
org.eclipse.ajdt.internal.builder.Builder.
org.eclipse.core.internal.boot.DelegatingURLClassLoader$Dele gatingLoaderException:
Attempt to load class "org.eclipse.ajdt.internal.builder.Builder" from
deactivated plug-in "org.eclipse.ajdt.ui".
at
org.eclipse.core.internal.plugins.PluginClassLoader.shouldLo okForClass(PluginClassLoader.java:255)
[...]
!ENTRY org.eclipse.core.resources 2 1 May 16, 2003 14:23:42.67
!MESSAGE Skipping builder org.eclipse.ajdt.ui.ajbuilder for project Junk.
Either the builder is missing from the install, or it belongs to a project
nature that is missing or disabled.
!ENTRY org.eclipse.core.runtime 4 2 May 16, 2003 14:23:47.489
!MESSAGE Plug-in org.eclipse.jdt.ui was unable to load class
org.eclipse.jdt.internal.ui.browsing.ProjectsView.
org.eclipse.core.internal.boot.DelegatingURLClassLoader$Dele gatingLoaderException:
Attempt to load class "org.eclipse.jdt.internal.ui.browsing.ProjectsView"
from deactivated plug-in "org.eclipse.jdt.ui".
at
org.eclipse.core.internal.plugins.PluginClassLoader.shouldLo okForClass(PluginClassLoader.java:255)
[...]
!ENTRY org.eclipse.core.runtime 4 2 May 16, 2003 14:23:47.489
!MESSAGE Plug-in org.eclipse.jdt.ui was unable to load class
org.eclipse.jdt.internal.ui.browsing.PackagesView.
org.eclipse.core.internal.boot.DelegatingURLClassLoader$Dele gatingLoaderException:
Attempt to load class "org.eclipse.jdt.internal.ui.browsing.PackagesView"
from deactivated plug-in "org.eclipse.jdt.ui".
[...]
!ENTRY org.eclipse.core.runtime 4 2 May 16, 2003 14:23:47.504
!MESSAGE Plug-in org.eclipse.jdt.ui was unable to load class
org.eclipse.jdt.internal.ui.browsing.TypesView.
org.eclipse.core.internal.boot.DelegatingURLClassLoader$Dele gatingLoaderException:
Attempt to load class "org.eclipse.jdt.internal.ui.browsing.TypesView"
from deactivated plug-in "org.eclipse.jdt.ui".
[...]
!ENTRY org.eclipse.core.runtime 4 2 May 16, 2003 14:23:47.520
!MESSAGE Plug-in org.eclipse.jdt.ui was unable to load class
org.eclipse.jdt.internal.ui.browsing.MembersView.
org.eclipse.core.internal.boot.DelegatingURLClassLoader$Dele gatingLoaderException:
Attempt to load class "org.eclipse.jdt.internal.ui.browsing.MembersView"
from deactivated plug-in "org.eclipse.jdt.ui".
[...]

I've tried using a clean install of Eclipse and carefully adding new
plugins, but I always end up hosing my environment. I posted something
about this earlier and someone posted something to try to fix my workspace,
but I've lost the message and I can't seem to find it by searching in
eclipse.org. I'm using AJDT 1.1.2.

Thanks.

--
James Howe

Re: AJDT seems to be killing my workspace [message #22412 is a reply to message #22211]

Mon, 19 May 2003 03:55

Eclipse User

Originally posted by: clemas.hursley.ibm.com

James Howe wrote:

> Ever since I've installed the ADJT plugin, my Eclipse environment seems to
> be unstable. I can use it for awhile and then suddenly when I start it up
> I'll get messages about 'problems occurred while rebuilding workspace' or
> something like that. In the .log file I always see something like this:
> -------->8------ big snip -------->8---------
> I've tried using a clean install of Eclipse and carefully adding new
> plugins, but I always end up hosing my environment. I posted something
> about this earlier and someone posted something to try to fix my workspace,
> but I've lost the message and I can't seem to find it by searching in
> eclipse.org. I'm using AJDT 1.1.2.

Hi James,

Sorry to hear you are having such problems. I haven't seen AJDT blow up
in the way you describe for a few months now (it used to happen all the
time). Most recently I saw an error to do with 'thread access' because
incremental compilation was switched on - do you run with incremental on?

Is your project particularly large?

Deleting the .metadata directory in your eclipse workspace would reset the
state of eclipse but thats a bit drastic as it resets *everything*.
Sounds like we need to investigate if its possible to delete just the AJDT
portion of that .metadata directory.

Andy.
AJDT Development.

Re: AJDT seems to be killing my workspace [message #22455 is a reply to message #22412]

Mon, 19 May 2003 10:31

Eclipse User

Originally posted by: eclipse.wingspread.fastmail.fm

On Mon, 19 May 2003 07:55:08 +0000 (UTC), Andy Clement
<clemas@hursley.ibm.com> wrote:

> James Howe wrote:
>
>> Ever since I've installed the ADJT plugin, my Eclipse environment seems
>> to be unstable. I can use it for awhile and then suddenly when I start
>> it up I'll get messages about 'problems occurred while rebuilding
>> workspace' or something like that. [..]
>
> Hi James,
>
> Sorry to hear you are having such problems. I haven't seen AJDT blow up
> in the way you describe for a few months now (it used to happen all the
> time). Most recently I saw an error to do with 'thread access' because
> incremental compilation was switched on - do you run with incremental on?
>
> Is your project particularly large?
>
> Deleting the .metadata directory in your eclipse workspace would reset
> the
> state of eclipse but thats a bit drastic as it resets *everything*.
> Sounds like we need to investigate if its possible to delete just the
> AJDT
> portion of that .metadata directory.
>
>

I have been using incremental compilation, at least some of the time. As
to whether the project is large, how do you define large? I don't think
it's particularly big. I do have 2-3 projects which have AspectJ as their
project type. Two of them are very small (a couple of classes). I'm
currently up and running. I believe what I did was to disable AJDT and
remove AspectJ as the project type for each of the AspectJ projects. After
restarting Eclipse, I then re-enabled (also restarting Eclipse) and then
converted my projects back to AspectJ.

--
James Howe

Re: AJDT seems to be killing my workspace [message #22630 is a reply to message #22455]

Fri, 30 May 2003 09:30

Eclipse User

Originally posted by: clemas.hotmail.com

James Howe wrote:

> I have been using incremental compilation, at least some of the time. As
> to whether the project is large, how do you define large? I don\'t think
> it\'s particularly big. I do have 2-3 projects which have AspectJ as their
> project type. Two of them are very small (a couple of classes). I\'m
> currently up and running. I believe what I did was to disable AJDT and
> remove AspectJ as the project type for each of the AspectJ projects. After
> restarting Eclipse, I then re-enabled (also restarting Eclipse) and then
> converted my projects back to AspectJ.

I have now seen this problem - and I was only on AJDT 1.1.1 - I increased
the memory I use to run eclipse and it improved the stability:

eclipse -vmargs -Xmx512M

But obviously we still need to get to the bottom of it. The projects I
was working with were 100s of classes in size, perhaps the more recent
AJDT 1.1.2 is revealing this problem on much smaller scale. We might have
to put your \'workaround\' in the FAQ.

I hope that with the forthcoming AspectJ 1.1 final release, the matching
AJDT release should get a lot more testing to resolve this kind of problem.

Andy.
AJDT Development

Re: AJDT seems to be killing my workspace [message #23291 is a reply to message #22630]

Fri, 06 June 2003 10:48

Eclipse User

Andy Clement wrote:

> James Howe wrote:

> > I have been using incremental compilation, at least some of the time. As
> > to whether the project is large, how do you define large? I don\'t think
> > it\'s particularly big. I do have 2-3 projects which have AspectJ as
their
> > project type. Two of them are very small (a couple of classes). I\'m
> > currently up and running. I believe what I did was to disable AJDT and
> > remove AspectJ as the project type for each of the AspectJ projects.
After
> > restarting Eclipse, I then re-enabled (also restarting Eclipse) and then
> > converted my projects back to AspectJ.

> I have now seen this problem - and I was only on AJDT 1.1.1 - I increased
> the memory I use to run eclipse and it improved the stability:

> eclipse -vmargs -Xmx512M

> But obviously we still need to get to the bottom of it. The projects I
> was working with were 100s of classes in size, perhaps the more recent
> AJDT 1.1.2 is revealing this problem on much smaller scale. We might have
> to put your \'workaround\' in the FAQ.

> I hope that with the forthcoming AspectJ 1.1 final release, the matching
> AJDT release should get a lot more testing to resolve this kind of problem.

> Andy.
> AJDT Development

Re: AJDT seems to be killing my workspace [message #23311 is a reply to message #22630]

Fri, 06 June 2003 10:51

Eclipse User

Sorry for the previous blank post...

James, I'm trying to look into this problem. It looks like the plugin is
never activated due to the initial SWTException that's thrown. In the
log file excerpts you posted, you have some [...] after each exception.
If the full stack trace for that first exception appeared in the log,
could you post it? Thanks,

Julie Waterhouse
AJDT Development

Andy Clement wrote:

> James Howe wrote:

> > I have been using incremental compilation, at least some of the time. As
> > to whether the project is large, how do you define large? I don\'t think
> > it\'s particularly big. I do have 2-3 projects which have AspectJ as
their
> > project type. Two of them are very small (a couple of classes). I\'m
> > currently up and running. I believe what I did was to disable AJDT and
> > remove AspectJ as the project type for each of the AspectJ projects.
After
> > restarting Eclipse, I then re-enabled (also restarting Eclipse) and then
> > converted my projects back to AspectJ.

> I have now seen this problem - and I was only on AJDT 1.1.1 - I increased
> the memory I use to run eclipse and it improved the stability:

> eclipse -vmargs -Xmx512M

> But obviously we still need to get to the bottom of it. The projects I
> was working with were 100s of classes in size, perhaps the more recent
> AJDT 1.1.2 is revealing this problem on much smaller scale. We might have
> to put your \'workaround\' in the FAQ.

> I hope that with the forthcoming AspectJ 1.1 final release, the matching
> AJDT release should get a lot more testing to resolve this kind of problem.

> Andy.
> AJDT Development

Re: AJDT seems to be killing my workspace [message #23356 is a reply to message #23311]

Fri, 06 June 2003 12:07

Eclipse User

Originally posted by: eclipse.wingspread.fastmail.fm

Is this what you are looking for?

============================================================ ===========

!SESSION May 16, 2003 14:23:42.20 ------------------------------------------
----
java.version=1.4.1_01
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86 -install
file:C:/dev/java/eclipse/
!ENTRY org.eclipse.core.runtime 4 2 May 16, 2003 14:23:42.20
!MESSAGE Problems occurred when invoking code from plug-in:
"org.eclipse.core.runtime".
!STACK 0
org.eclipse.swt.SWTException: Invalid thread access
at org.eclipse.swt.SWT.error(SWT.java:2332)
at org.eclipse.swt.SWT.error(SWT.java:2262)
at org.eclipse.swt.widgets.Widget.error(Widget.java:385)
at org.eclipse.swt.widgets.Shell.<init>(Shell.java:246)
at org.eclipse.swt.widgets.Shell.<init>(Shell.java:237)
at org.eclipse.swt.widgets.Shell.<init>(Shell.java:190)
at org.eclipse.swt.widgets.Shell.<init>(Shell.java:128)
at
org.eclipse.jface.resource.FontRegistry.defaultFont(FontRegi stry.java:293)
at org.eclipse.jface.resource.FontRegistry.get(FontRegistry.jav a:370)
at
org.eclipse.jface.resource.JFaceResources.getFont(JFaceResou rces.java:183)
at org.eclipse.jdt.internal.ui.JavaPlugin.startup(JavaPlugin.ja va:241)
at
org.eclipse.core.internal.plugins.PluginDescriptor$1.run(Plu ginDescriptor.java:728)
at
org.eclipse.core.internal.runtime.InternalPlatform.run(Inter nalPlatform.java:889)
at
org.eclipse.core.internal.plugins.PluginDescriptor.internalD oPluginActivation(PluginDescriptor.java:740)
at
org.eclipse.core.internal.plugins.PluginDescriptor.doPluginA ctivation(PluginDescriptor.java:188)
at
org.eclipse.core.internal.plugins.PluginClassLoader.activate Plugin(PluginClassLoader.java:112)
at
org.eclipse.core.internal.plugins.PluginClassLoader.internal FindClassParentsSelf(PluginClassLoader.java:185)
at
org.eclipse.core.internal.boot.DelegatingURLClassLoader.find ClassParentsSelf(DelegatingURLClassLoader.java:490)
at
org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(DelegatingURLClassLoader.java:882)
at
org.eclipse.core.internal.boot.DelegatingURLClassLoader.acce ss$0(DelegatingURLClassLoader.java:876)
at
org.eclipse.core.internal.boot.DelegatingURLClassLoader$Dele gateLoader.loadClass(DelegatingURLClassLoader.java:90)
at
org.eclipse.core.internal.boot.DelegatingURLClassLoader.find ClassPrerequisites(DelegatingURLClassLoader.java:554)
at
org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(DelegatingURLClassLoader.java:890)
at
org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(DelegatingURLClassLoader.java:862)
at java.lang.ClassLoader.loadClass(ClassLoader.java:255)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:315 )
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Class.java:15 90)
at java.lang.Class.getConstructor0(Class.java:1762)
at java.lang.Class.getConstructor(Class.java:1002)
at
org.eclipse.core.internal.plugins.PluginDescriptor.internalD oPluginActivation(PluginDescriptor.java:701)
at
org.eclipse.core.internal.plugins.PluginDescriptor.doPluginA ctivation(PluginDescriptor.java:188)
at
org.eclipse.core.internal.plugins.PluginClassLoader.activate Plugin(PluginClassLoader.java:112)
at
org.eclipse.core.internal.plugins.PluginClassLoader.internal FindClassParentsSelf(PluginClassLoader.java:185)
at
org.eclipse.core.internal.boot.DelegatingURLClassLoader.find ClassParentsSelf(DelegatingURLClassLoader.java:485)
at
org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(DelegatingURLClassLoader.java:882)
at
org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(DelegatingURLClassLoader.java:862)
at java.lang.ClassLoader.loadClass(ClassLoader.java:255)
at
org.eclipse.core.internal.plugins.PluginDescriptor.createExe cutableExtension(PluginDescriptor.java:130)
at
org.eclipse.core.internal.plugins.PluginDescriptor.createExe cutableExtension(PluginDescriptor.java:167)
at
org.eclipse.core.internal.plugins.ConfigurationElement.creat eExecutableExtension(ConfigurationElement.java:103)
at
org.eclipse.core.internal.events.BuildManager.instantiateBui lder(BuildManager.java:555)
at
org.eclipse.core.internal.events.BuildManager.initializeBuil der(BuildManager.java:509)
at
org.eclipse.core.internal.events.BuildManager.getBuilder(Bui ldManager.java:359)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:170)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:191)
at
org.eclipse.core.internal.events.BuildManager$1.run(BuildMan ager.java:151)
at
org.eclipse.core.internal.runtime.InternalPlatform.run(Inter nalPlatform.java:889)
at org.eclipse.core.runtime.Platform.run(Platform.java:413)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:165)
at
org.eclipse.core.internal.events.BuildManager.basicBuildLoop (BuildManager.java:243)
at
org.eclipse.core.internal.events.BuildManager.build(BuildMan ager.java:212)
at
org.eclipse.core.internal.resources.Workspace.endOperation(W orkspace.java:884)
at org.eclipse.core.internal.resources.Workspace.run(Workspace. java:1600)
at
org.eclipse.ui.actions.WorkspaceModifyOperation.run(Workspac eModifyOperation.java:85)
at
org.eclipse.jface.operation.ModalContext$ModalContextThread. run(ModalContext.java:101)

On Fri, 6 Jun 2003 14:51:54 +0000 (UTC), Julie Waterhouse
<juliew@ca.ibm.com> wrote:

> Sorry for the previous blank post...
>
> James, I'm trying to look into this problem. It looks like the plugin is
> never activated due to the initial SWTException that's thrown. In the
> log file excerpts you posted, you have some [...] after each exception.
> If the full stack trace for that first exception appeared in the log,
> could you post it? Thanks,
>
> Julie Waterhouse
> AJDT Development
>
>
> Andy Clement wrote:
>
>> James Howe wrote:
>
>> > I have been using incremental compilation, at least some of the time.
>> As > to whether the project is large, how do you define large? I don\'t
>> think > it\'s particularly big. I do have 2-3 projects which have
>> AspectJ as
> their
>> > project type. Two of them are very small (a couple of classes). I\'m
>> > currently up and running. I believe what I did was to disable AJDT
>> and > remove AspectJ as the project type for each of the AspectJ
>> projects.
> After
>> > restarting Eclipse, I then re-enabled (also restarting Eclipse) and
>> then > converted my projects back to AspectJ.
>
>> I have now seen this problem - and I was only on AJDT 1.1.1 - I
>> increased
>> the memory I use to run eclipse and it improved the stability:
>
>> eclipse -vmargs -Xmx512M
>
>> But obviously we still need to get to the bottom of it. The projects I
>> was working with were 100s of classes in size, perhaps the more recent
>> AJDT 1.1.2 is revealing this problem on much smaller scale. We might
>> have
>> to put your \'workaround\' in the FAQ.
>
>> I hope that with the forthcoming AspectJ 1.1 final release, the matching
>> AJDT release should get a lot more testing to resolve this kind of
>> problem.
>
>> Andy.
>> AJDT Development
>
>
>
>
>

--
James Howe

Re: AJDT seems to be killing my workspace [message #23529 is a reply to message #23356]

Fri, 06 June 2003 16:14

Eclipse User

Yes, thanks. In fact since I posted, I actually managed to reproduce the
problem. It's been happening a few times for me as I've been trying to
solve something else. I've been switching versions of the plugin between
1.1.1, 1.1.2 and 1.1.3. Several times after restarting after installing a
new version, I've had the workspace error, and seen the same stack trace
as you have here. I haven't had time to narrow it down further yet, but
do know it's always been after switching plugin versions. You seemed to
indicate in your first post that it happened when you were adding the new
plugin too. Have you ever seen this at any other time? When you haven't
just installed the plugin? Thx,

Julie
AJDT Development

James Howe wrote:

> Is this what you are looking for?

> ============================================================ ===========

> !SESSION May 16, 2003 14:23:42.20 ------------------------------------------
> ----
> java.version=1.4.1_01
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
> Command-line arguments: -os win32 -ws win32 -arch x86 -install
> file:C:/dev/java/eclipse/
> !ENTRY org.eclipse.core.runtime 4 2 May 16, 2003 14:23:42.20
> !MESSAGE Problems occurred when invoking code from plug-in:
> "org.eclipse.core.runtime".
> !STACK 0
> org.eclipse.swt.SWTException: Invalid thread access
> at org.eclipse.swt.SWT.error(SWT.java:2332)
> at org.eclipse.swt.SWT.error(SWT.java:2262)
> at org.eclipse.swt.widgets.Widget.error(Widget.java:385)
> at org.eclipse.swt.widgets.Shell.<init>(Shell.java:246)
> at org.eclipse.swt.widgets.Shell.<init>(Shell.java:237)
> at org.eclipse.swt.widgets.Shell.<init>(Shell.java:190)
> at org.eclipse.swt.widgets.Shell.<init>(Shell.java:128)
> at
> org.eclipse.jface.resource.FontRegistry.defaultFont(FontRegi stry.java:293)
> at org.eclipse.jface.resource.FontRegistry.get(FontRegistry.jav a:370)
> at
> org.eclipse.jface.resource.JFaceResources.getFont(JFaceResou rces.java:183)
> at org.eclipse.jdt.internal.ui.JavaPlugin.startup(JavaPlugin.ja va:241)
> at
>
org.eclipse.core.internal.plugins.PluginDescriptor$1.run(Plu ginDescriptor.java:728)
> at
>
org.eclipse.core.internal.runtime.InternalPlatform.run(Inter nalPlatform.java:889)
> at
>
org.eclipse.core.internal.plugins.PluginDescriptor.internalD oPluginActivation(PluginDescriptor.java:740)
> at
>
org.eclipse.core.internal.plugins.PluginDescriptor.doPluginA ctivation(PluginDescriptor.java:188)
> at
>
org.eclipse.core.internal.plugins.PluginClassLoader.activate Plugin(PluginClassLoader.java:112)
> at
>
org.eclipse.core.internal.plugins.PluginClassLoader.internal FindClassParentsSelf(PluginClassLoader.java:185)
> at
>
org.eclipse.core.internal.boot.DelegatingURLClassLoader.find ClassParentsSelf(DelegatingURLClassLoader.java:490)
> at
>
org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(DelegatingURLClassLoader.java:882)
> at
>
org.eclipse.core.internal.boot.DelegatingURLClassLoader.acce ss$0(DelegatingURLClassLoader.java:876)
> at
>
org.eclipse.core.internal.boot.DelegatingURLClassLoader$Dele gateLoader.loadClass(DelegatingURLClassLoader.java:90)
> at
>
org.eclipse.core.internal.boot.DelegatingURLClassLoader.find ClassPrerequisites(DelegatingURLClassLoader.java:554)
> at
>
org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(DelegatingURLClassLoader.java:890)
> at
>
org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(DelegatingURLClassLoader.java:862)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:255)
> at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:315 )
> at java.lang.Class.getDeclaredConstructors0(Native Method)
> at java.lang.Class.privateGetDeclaredConstructors(Class.java:15 90)
> at java.lang.Class.getConstructor0(Class.java:1762)
> at java.lang.Class.getConstructor(Class.java:1002)
> at
>
org.eclipse.core.internal.plugins.PluginDescriptor.internalD oPluginActivation(PluginDescriptor.java:701)
> at
>
org.eclipse.core.internal.plugins.PluginDescriptor.doPluginA ctivation(PluginDescriptor.java:188)
> at
>
org.eclipse.core.internal.plugins.PluginClassLoader.activate Plugin(PluginClassLoader.java:112)
> at
>
org.eclipse.core.internal.plugins.PluginClassLoader.internal FindClassParentsSelf(PluginClassLoader.java:185)
> at
>
org.eclipse.core.internal.boot.DelegatingURLClassLoader.find ClassParentsSelf(DelegatingURLClassLoader.java:485)
> at
>
org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(DelegatingURLClassLoader.java:882)
> at
>
org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(DelegatingURLClassLoader.java:862)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:255)
> at
>
org.eclipse.core.internal.plugins.PluginDescriptor.createExe cutableExtension(PluginDescriptor.java:130)
> at
>
org.eclipse.core.internal.plugins.PluginDescriptor.createExe cutableExtension(PluginDescriptor.java:167)
> at
>
org.eclipse.core.internal.plugins.ConfigurationElement.creat eExecutableExtension(ConfigurationElement.java:103)
> at
>
org.eclipse.core.internal.events.BuildManager.instantiateBui lder(BuildManager.java:555)
> at
>
org.eclipse.core.internal.events.BuildManager.initializeBuil der(BuildManager.java:509)
> at
>
org.eclipse.core.internal.events.BuildManager.getBuilder(Bui ldManager.java:359)
> at
>
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:170)
> at
>
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:191)
> at
> org.eclipse.core.internal.events.BuildManager$1.run(BuildMan ager.java:151)
> at
>
org.eclipse.core.internal.runtime.InternalPlatform.run(Inter nalPlatform.java:889)
> at org.eclipse.core.runtime.Platform.run(Platform.java:413)
> at
>
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:165)
> at
>
org.eclipse.core.internal.events.BuildManager.basicBuildLoop (BuildManager.java:243)
> at
> org.eclipse.core.internal.events.BuildManager.build(BuildMan ager.java:212)
> at
>
org.eclipse.core.internal.resources.Workspace.endOperation(W orkspace.java:884)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace. java:1600)
> at
>
org.eclipse.ui.actions.WorkspaceModifyOperation.run(Workspac eModifyOperation.java:85)
> at
>
org.eclipse.jface.operation.ModalContext$ModalContextThread. run(ModalContext.java:101)

> On Fri, 6 Jun 2003 14:51:54 +0000 (UTC), Julie Waterhouse
> <juliew@ca.ibm.com> wrote:

> > Sorry for the previous blank post...
> >
> > James, I'm trying to look into this problem. It looks like the plugin is
> > never activated due to the initial SWTException that's thrown. In the
> > log file excerpts you posted, you have some [...] after each exception.
> > If the full stack trace for that first exception appeared in the log,
> > could you post it? Thanks,
> >
> > Julie Waterhouse
> > AJDT Development
> >
> >
> > Andy Clement wrote:
> >
> >> James Howe wrote:
> >
> >> > I have been using incremental compilation, at least some of the time.
> >> As > to whether the project is large, how do you define large? I don\'t
> >> think > it\'s particularly big. I do have 2-3 projects which have
> >> AspectJ as
> > their
> >> > project type. Two of them are very small (a couple of classes). I\'m
> >> > currently up and running. I believe what I did was to disable AJDT
> >> and > remove AspectJ as the project type for each of the AspectJ
> >> projects.
> > After
> >> > restarting Eclipse, I then re-enabled (also restarting Eclipse) and
> >> then > converted my projects back to AspectJ.
> >
> >> I have now seen this problem - and I was only on AJDT 1.1.1 - I
> >> increased
> >> the memory I use to run eclipse and it improved the stability:
> >
> >> eclipse -vmargs -Xmx512M
> >
> >> But obviously we still need to get to the bottom of it. The projects I
> >> was working with were 100s of classes in size, perhaps the more recent
> >> AJDT 1.1.2 is revealing this problem on much smaller scale. We might
> >> have
> >> to put your \'workaround\' in the FAQ.
> >
> >> I hope that with the forthcoming AspectJ 1.1 final release, the matching
> >> AJDT release should get a lot more testing to resolve this kind of
> >> problem.
> >
> >> Andy.
> >> AJDT Development
> >
> >
> >
> >
> >

> --
> James Howe

Re: AJDT seems to be killing my workspace [message #23573 is a reply to message #23529]

Fri, 06 June 2003 21:43

Eclipse User

Originally posted by: news.wingspread.fastmail.fm

I can't really answer your question only because it's one of those things
that you aren't expecting and when it happens you don't always remember
what it was that you were doing. What I seem to recall doing was starting
from a clean Eclipse install, I installed the plugin. I created a couple
AspectJ projects, built them, did some other work and at some point got the
error that you saw. I don't remember if this occurred the first time I
restarted Eclipse after installing the plugin. I don't think it was. I
remember thinking that I thought I had solved the problem by using a newer
version of the plugin and running with a clean Eclipse and then the problem
happened again. I'm not sure if this information is much help. If I can
come up with a scenario to make it happen I'll let you know, but I likely
won't have much time to spend on that right now.

On Fri, 6 Jun 2003 20:14:03 +0000 (UTC), Julie Waterhouse
<juliew@ca.ibm.com> wrote:

> [...] Have you ever seen this at any other time? When you haven't
> just installed the plugin? Thx,
>
> Julie
> AJDT Development
>

--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

Re: AJDT seems to be killing my workspace [message #23659 is a reply to message #23573]

Wed, 11 June 2003 16:02

Eclipse User

Thanks to Adrian for finding this answer - the SWT Exception on updating
the plugin turned out to be a known and fixed bug in JDT. Here's a copy
of the response from the jdt mailing list:

-------------------
To: jdt-dev@eclipse.org
From: Daniel Megert <daniel_megert@ch.ibm.com>
Date: Tue, 10 Jun 2003 16:53:55 +0200
Reply-To: jdt-dev@eclipse.org

Adrian,

I assume you run on 2.1. This bug 36554 has been fixed in the 3.0 and the
2.1 maintenance stream.

HTH
Dani
-------------------
Regards,

~Julie
AJDT Development

James Howe wrote:

> I can't really answer your question only because it's one of those things
> that you aren't expecting and when it happens you don't always remember
> what it was that you were doing. What I seem to recall doing was starting
> from a clean Eclipse install, I installed the plugin. I created a couple
> AspectJ projects, built them, did some other work and at some point got the
> error that you saw. I don't remember if this occurred the first time I
> restarted Eclipse after installing the plugin. I don't think it was. I
> remember thinking that I thought I had solved the problem by using a newer
> version of the plugin and running with a clean Eclipse and then the problem
> happened again. I'm not sure if this information is much help. If I can
> come up with a scenario to make it happen I'll let you know, but I likely
> won't have much time to spend on that right now.

> On Fri, 6 Jun 2003 20:14:03 +0000 (UTC), Julie Waterhouse
> <juliew@ca.ibm.com> wrote:

> > [...] Have you ever seen this at any other time? When you haven't
> > just installed the plugin? Thx,
> >
> > Julie
> > AJDT Development
> >

> --
> Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

Re: AJDT seems to be killing my workspace [message #567606 is a reply to message #22211]

Mon, 19 May 2003 03:55

Eclipse User

James Howe wrote:

> Ever since I've installed the ADJT plugin, my Eclipse environment seems to
> be unstable. I can use it for awhile and then suddenly when I start it up
> I'll get messages about 'problems occurred while rebuilding workspace' or
> something like that. In the .log file I always see something like this:
> -------->8------ big snip -------->8---------
> I've tried using a clean install of Eclipse and carefully adding new
> plugins, but I always end up hosing my environment. I posted something
> about this earlier and someone posted something to try to fix my workspace,
> but I've lost the message and I can't seem to find it by searching in
> eclipse.org. I'm using AJDT 1.1.2.

Hi James,

Sorry to hear you are having such problems. I haven't seen AJDT blow up
in the way you describe for a few months now (it used to happen all the
time). Most recently I saw an error to do with 'thread access' because
incremental compilation was switched on - do you run with incremental on?

Is your project particularly large?

Deleting the .metadata directory in your eclipse workspace would reset the
state of eclipse but thats a bit drastic as it resets *everything*.
Sounds like we need to investigate if its possible to delete just the AJDT
portion of that .metadata directory.

Andy.
AJDT Development.

Re: AJDT seems to be killing my workspace [message #567663 is a reply to message #22412]

Mon, 19 May 2003 10:31

Eclipse User

On Mon, 19 May 2003 07:55:08 +0000 (UTC), Andy Clement
<clemas@hursley.ibm.com> wrote:

> James Howe wrote:
>
>> Ever since I've installed the ADJT plugin, my Eclipse environment seems
>> to be unstable. I can use it for awhile and then suddenly when I start
>> it up I'll get messages about 'problems occurred while rebuilding
>> workspace' or something like that. [..]
>
> Hi James,
>
> Sorry to hear you are having such problems. I haven't seen AJDT blow up
> in the way you describe for a few months now (it used to happen all the
> time). Most recently I saw an error to do with 'thread access' because
> incremental compilation was switched on - do you run with incremental on?
>
> Is your project particularly large?
>
> Deleting the .metadata directory in your eclipse workspace would reset
> the
> state of eclipse but thats a bit drastic as it resets *everything*.
> Sounds like we need to investigate if its possible to delete just the
> AJDT
> portion of that .metadata directory.
>
>

I have been using incremental compilation, at least some of the time. As
to whether the project is large, how do you define large? I don't think
it's particularly big. I do have 2-3 projects which have AspectJ as their
project type. Two of them are very small (a couple of classes). I'm
currently up and running. I believe what I did was to disable AJDT and
remove AspectJ as the project type for each of the AspectJ projects. After
restarting Eclipse, I then re-enabled (also restarting Eclipse) and then
converted my projects back to AspectJ.

--
James Howe

Re: AJDT seems to be killing my workspace [message #567804 is a reply to message #22455]

Fri, 30 May 2003 09:30

Eclipse User

James Howe wrote:

> I have been using incremental compilation, at least some of the time. As
> to whether the project is large, how do you define large? I don\'t think
> it\'s particularly big. I do have 2-3 projects which have AspectJ as their
> project type. Two of them are very small (a couple of classes). I\'m
> currently up and running. I believe what I did was to disable AJDT and
> remove AspectJ as the project type for each of the AspectJ projects. After
> restarting Eclipse, I then re-enabled (also restarting Eclipse) and then
> converted my projects back to AspectJ.

I have now seen this problem - and I was only on AJDT 1.1.1 - I increased
the memory I use to run eclipse and it improved the stability:

eclipse -vmargs -Xmx512M

But obviously we still need to get to the bottom of it. The projects I
was working with were 100s of classes in size, perhaps the more recent
AJDT 1.1.2 is revealing this problem on much smaller scale. We might have
to put your \'workaround\' in the FAQ.

I hope that with the forthcoming AspectJ 1.1 final release, the matching
AJDT release should get a lot more testing to resolve this kind of problem.

Andy.
AJDT Development

Re: AJDT seems to be killing my workspace [message #568532 is a reply to message #22630]

Fri, 06 June 2003 10:48

Eclipse User

Re: AJDT seems to be killing my workspace [message #568543 is a reply to message #22630]

Fri, 06 June 2003 10:51

Eclipse User

Re: AJDT seems to be killing my workspace [message #568612 is a reply to message #23311]

Fri, 06 June 2003 12:07

Eclipse User

Is this what you are looking for?

============================================================ ===========

!SESSION May 16, 2003 14:23:42.20 ------------------------------------------
----
java.version=1.4.1_01
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86 -install
file:C:/dev/java/eclipse/
!ENTRY org.eclipse.core.runtime 4 2 May 16, 2003 14:23:42.20
!MESSAGE Problems occurred when invoking code from plug-in:
"org.eclipse.core.runtime".
!STACK 0
org.eclipse.swt.SWTException: Invalid thread access
at org.eclipse.swt.SWT.error(SWT.java:2332)
at org.eclipse.swt.SWT.error(SWT.java:2262)
at org.eclipse.swt.widgets.Widget.error(Widget.java:385)
at org.eclipse.swt.widgets.Shell.<init>(Shell.java:246)
at org.eclipse.swt.widgets.Shell.<init>(Shell.java:237)
at org.eclipse.swt.widgets.Shell.<init>(Shell.java:190)
at org.eclipse.swt.widgets.Shell.<init>(Shell.java:128)
at
org.eclipse.jface.resource.FontRegistry.defaultFont(FontRegi stry.java:293)
at org.eclipse.jface.resource.FontRegistry.get(FontRegistry.jav a:370)
at
org.eclipse.jface.resource.JFaceResources.getFont(JFaceResou rces.java:183)
at org.eclipse.jdt.internal.ui.JavaPlugin.startup(JavaPlugin.ja va:241)
at
org.eclipse.core.internal.plugins.PluginDescriptor$1.run(Plu ginDescriptor.java:728)
at
org.eclipse.core.internal.runtime.InternalPlatform.run(Inter nalPlatform.java:889)
at
org.eclipse.core.internal.plugins.PluginDescriptor.internalD oPluginActivation(PluginDescriptor.java:740)
at
org.eclipse.core.internal.plugins.PluginDescriptor.doPluginA ctivation(PluginDescriptor.java:188)
at
org.eclipse.core.internal.plugins.PluginClassLoader.activate Plugin(PluginClassLoader.java:112)
at
org.eclipse.core.internal.plugins.PluginClassLoader.internal FindClassParentsSelf(PluginClassLoader.java:185)
at
org.eclipse.core.internal.boot.DelegatingURLClassLoader.find ClassParentsSelf(DelegatingURLClassLoader.java:490)
at
org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(DelegatingURLClassLoader.java:882)
at
org.eclipse.core.internal.boot.DelegatingURLClassLoader.acce ss$0(DelegatingURLClassLoader.java:876)
at
org.eclipse.core.internal.boot.DelegatingURLClassLoader$Dele gateLoader.loadClass(DelegatingURLClassLoader.java:90)
at
org.eclipse.core.internal.boot.DelegatingURLClassLoader.find ClassPrerequisites(DelegatingURLClassLoader.java:554)
at
org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(DelegatingURLClassLoader.java:890)
at
org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(DelegatingURLClassLoader.java:862)
at java.lang.ClassLoader.loadClass(ClassLoader.java:255)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:315 )
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Class.java:15 90)
at java.lang.Class.getConstructor0(Class.java:1762)
at java.lang.Class.getConstructor(Class.java:1002)
at
org.eclipse.core.internal.plugins.PluginDescriptor.internalD oPluginActivation(PluginDescriptor.java:701)
at
org.eclipse.core.internal.plugins.PluginDescriptor.doPluginA ctivation(PluginDescriptor.java:188)
at
org.eclipse.core.internal.plugins.PluginClassLoader.activate Plugin(PluginClassLoader.java:112)
at
org.eclipse.core.internal.plugins.PluginClassLoader.internal FindClassParentsSelf(PluginClassLoader.java:185)
at
org.eclipse.core.internal.boot.DelegatingURLClassLoader.find ClassParentsSelf(DelegatingURLClassLoader.java:485)
at
org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(DelegatingURLClassLoader.java:882)
at
org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(DelegatingURLClassLoader.java:862)
at java.lang.ClassLoader.loadClass(ClassLoader.java:255)
at
org.eclipse.core.internal.plugins.PluginDescriptor.createExe cutableExtension(PluginDescriptor.java:130)
at
org.eclipse.core.internal.plugins.PluginDescriptor.createExe cutableExtension(PluginDescriptor.java:167)
at
org.eclipse.core.internal.plugins.ConfigurationElement.creat eExecutableExtension(ConfigurationElement.java:103)
at
org.eclipse.core.internal.events.BuildManager.instantiateBui lder(BuildManager.java:555)
at
org.eclipse.core.internal.events.BuildManager.initializeBuil der(BuildManager.java:509)
at
org.eclipse.core.internal.events.BuildManager.getBuilder(Bui ldManager.java:359)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:170)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:191)
at
org.eclipse.core.internal.events.BuildManager$1.run(BuildMan ager.java:151)
at
org.eclipse.core.internal.runtime.InternalPlatform.run(Inter nalPlatform.java:889)
at org.eclipse.core.runtime.Platform.run(Platform.java:413)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:165)
at
org.eclipse.core.internal.events.BuildManager.basicBuildLoop (BuildManager.java:243)
at
org.eclipse.core.internal.events.BuildManager.build(BuildMan ager.java:212)
at
org.eclipse.core.internal.resources.Workspace.endOperation(W orkspace.java:884)
at org.eclipse.core.internal.resources.Workspace.run(Workspace. java:1600)
at
org.eclipse.ui.actions.WorkspaceModifyOperation.run(Workspac eModifyOperation.java:85)
at
org.eclipse.jface.operation.ModalContext$ModalContextThread. run(ModalContext.java:101)

On Fri, 6 Jun 2003 14:51:54 +0000 (UTC), Julie Waterhouse
<juliew@ca.ibm.com> wrote:

> Sorry for the previous blank post...
>
> James, I'm trying to look into this problem. It looks like the plugin is
> never activated due to the initial SWTException that's thrown. In the
> log file excerpts you posted, you have some [...] after each exception.
> If the full stack trace for that first exception appeared in the log,
> could you post it? Thanks,
>
> Julie Waterhouse
> AJDT Development
>
>
> Andy Clement wrote:
>
>> James Howe wrote:
>
>> > I have been using incremental compilation, at least some of the time.
>> As > to whether the project is large, how do you define large? I don\'t
>> think > it\'s particularly big. I do have 2-3 projects which have
>> AspectJ as
> their
>> > project type. Two of them are very small (a couple of classes). I\'m
>> > currently up and running. I believe what I did was to disable AJDT
>> and > remove AspectJ as the project type for each of the AspectJ
>> projects.
> After
>> > restarting Eclipse, I then re-enabled (also restarting Eclipse) and
>> then > converted my projects back to AspectJ.
>
>> I have now seen this problem - and I was only on AJDT 1.1.1 - I
>> increased
>> the memory I use to run eclipse and it improved the stability:
>
>> eclipse -vmargs -Xmx512M
>
>> But obviously we still need to get to the bottom of it. The projects I
>> was working with were 100s of classes in size, perhaps the more recent
>> AJDT 1.1.2 is revealing this problem on much smaller scale. We might
>> have
>> to put your \'workaround\' in the FAQ.
>
>> I hope that with the forthcoming AspectJ 1.1 final release, the matching
>> AJDT release should get a lot more testing to resolve this kind of
>> problem.
>
>> Andy.
>> AJDT Development
>
>
>
>
>

--
James Howe

Re: AJDT seems to be killing my workspace [message #568687 is a reply to message #23356]

Fri, 06 June 2003 16:14

Eclipse User

Re: AJDT seems to be killing my workspace [message #568741 is a reply to message #23529]

Fri, 06 June 2003 21:43

Eclipse User

I can't really answer your question only because it's one of those things
that you aren't expecting and when it happens you don't always remember
what it was that you were doing. What I seem to recall doing was starting
from a clean Eclipse install, I installed the plugin. I created a couple
AspectJ projects, built them, did some other work and at some point got the
error that you saw. I don't remember if this occurred the first time I
restarted Eclipse after installing the plugin. I don't think it was. I
remember thinking that I thought I had solved the problem by using a newer
version of the plugin and running with a clean Eclipse and then the problem
happened again. I'm not sure if this information is much help. If I can
come up with a scenario to make it happen I'll let you know, but I likely
won't have much time to spend on that right now.

On Fri, 6 Jun 2003 20:14:03 +0000 (UTC), Julie Waterhouse
<juliew@ca.ibm.com> wrote:

> [...] Have you ever seen this at any other time? When you haven't
> just installed the plugin? Thx,
>
> Julie
> AJDT Development
>

--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

Re: AJDT seems to be killing my workspace [message #568833 is a reply to message #23573]

Wed, 11 June 2003 16:02

Eclipse User

Previous Topic:	Some other strange compile problems with AJDT 1.1.2
Next Topic:	Latest build still not creating any class files

Goto Forum:

-=] Back to Top [=-

Current Time: Wed May 07 15:44:01 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter