Log entries claiming "error in opening zip file" accessing dsld support related folders

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Minor Minor
  • Resolution: Won't Fix
  • Affects Version/s: 2.6.1.M1
  • Fix Version/s: 2.6.1.Release
  • Component/s: None
  • Labels:
    None
  • Environment:
    Groovy-Eclipse 2.6.1.xx-20120118-1100-e37-M1
    on
    SpringSource Tool Suite - Version: 2.9.0.M2 - Build Id: 201201191000 (upgraded from 2.8.1)

Description

I've noticed some errors on my workspaces logs, such as:

!ENTRY org.eclipse.jst.jsp.core 2 2 2012-02-07 18:04:47.686
!MESSAGE Taglib Index ZipException: /home/davide/.groovy/greclipse/global_dsld_support error in opening zip file

!ENTRY org.eclipse.jst.jsp.core 2 2 2012-02-07 18:04:47.687
!MESSAGE Taglib Index ZipException: /home/davide/opt/springsource/sts-2.8.1.RELEASE/plugins/org.codehaus.groovy_1.7.10.xx-20120118-1100-e37-M1/plugin_dsld_support/ error in opening zip file

The strange thing is that they refer to folders (and not to compressed archives), as you can see:

davide@ws-davide:~$ ls -la /home/davide/.groovy/greclipse/global_dsld_support /home/davide/opt/springsource/sts-2.8.1.RELEASE/plugins/org.codehaus.groovy_1.7.10.xx-20120118-1100-e37-M1/plugin_dsld_support/
/home/davide/.groovy/greclipse/global_dsld_support:
total 8
drwxr-xr-x 2 davide davide 4096 Dec 13 18:35 .
drwxr-xr-x 3 davide davide 4096 Dec 13 18:35 ..

/home/davide/opt/springsource/sts-2.8.1.RELEASE/plugins/org.codehaus.groovy_1.7.10.xx-20120118-1100-e37-M1/plugin_dsld_support/:
total 16
drwxr-xr-x 3 davide davide 4096 Feb  1 09:18 .
drwxr-xr-x 7 davide davide 4096 Feb  1 09:18 ..
drwxr-xr-x 2 davide davide 4096 Feb  1 09:18 dsld
-rw-r--r-- 1 davide davide  331 Jan 18 13:27 readme.txt

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Andrew Eisenberg added a comment -

Interesting...

Some questions:

  1. Do you have any stack traces for this? They might be included with the log entry.
  2. Do you know which project this is happening in? Is it a grails project? Or a Groovy project that uses JSPs in some way?
  3. Are you on Linux?
  4. Other than the stack trace, is this causing any noticeable problems?
  5. How often are the entries coming? Do you know what causes the exceptions to occur?
Show
Andrew Eisenberg added a comment - Interesting... Some questions:
  1. Do you have any stack traces for this? They might be included with the log entry.
  2. Do you know which project this is happening in? Is it a grails project? Or a Groovy project that uses JSPs in some way?
  3. Are you on Linux?
  4. Other than the stack trace, is this causing any noticeable problems?
  5. How often are the entries coming? Do you know what causes the exceptions to occur?
Hide
Permalink
Davide Cavestro added a comment -

1. Do you have any stack traces for this? They might be included with the log entry.

No, my log only contains the message I sent to you.

2. Do you know which project this is happening in? Is it a grails project? Or a Groovy project that uses JSPs in some way?

It's a gradle multiproject with some web applications (war overlay simulation).

3. Are you on Linux?

Yes, Debian GNU/Linux 6.0

Other than the stack trace, is this causing any noticeable problems?

Not at all

How often are the entries coming? Do you know what causes the exceptions to occur?

It happens only once or twice per day... but I don't know the cause.

Show
Davide Cavestro added a comment -
1. Do you have any stack traces for this? They might be included with the log entry.
No, my log only contains the message I sent to you.
2. Do you know which project this is happening in? Is it a grails project? Or a Groovy project that uses JSPs in some way?
It's a gradle multiproject with some web applications (war overlay simulation).
3. Are you on Linux?
Yes, Debian GNU/Linux 6.0
Other than the stack trace, is this causing any noticeable problems?
Not at all
How often are the entries coming? Do you know what causes the exceptions to occur?
It happens only once or twice per day... but I don't know the cause.
Hide
Permalink
Andrew Eisenberg added a comment -

I'm guessing that the problem is coming around because of an interaction with WTP and the Groovy DSL classpath containers. Do you have any groovy code in your gradle projects (besides the build files themselves)? If not, I'd recommend removing the Groovy DSL classpath container from your build path(s).

Show
Andrew Eisenberg added a comment - I'm guessing that the problem is coming around because of an interaction with WTP and the Groovy DSL classpath containers. Do you have any groovy code in your gradle projects (besides the build files themselves)? If not, I'd recommend removing the Groovy DSL classpath container from your build path(s).
Hide
Permalink
Davide Cavestro added a comment -

Some projects of the multi-project build contains several groovy files (they apply the groovy plugin)... so the question is: what happens if I remove Groovy DSL Support from their Java Build Path?
By the way it is interesting to notice that Groovy DSL Support is also enabled as an exported entry (I really didn't mean that).
Could it be the cause of such interaction with WTP and the Groovy DSL classpath containers?
I could also try to see if removing the export checkbox from Groovy DSL Support the error message still appears.

Show
Davide Cavestro added a comment - Some projects of the multi-project build contains several groovy files (they apply the groovy plugin)... so the question is: what happens if I remove Groovy DSL Support from their Java Build Path? By the way it is interesting to notice that Groovy DSL Support is also enabled as an exported entry (I really didn't mean that). Could it be the cause of such interaction with WTP and the Groovy DSL classpath containers? I could also try to see if removing the export checkbox from Groovy DSL Support the error message still appears.
Hide
Permalink
Andrew Eisenberg added a comment -

That's a good point about exporting the classpath container. It shouldn't be. I changed the code so that the DSL Support container will not be exported by default.

Let mw know if disabling export fixes the problem.

Show
Andrew Eisenberg added a comment - That's a good point about exporting the classpath container. It shouldn't be. I changed the code so that the DSL Support container will not be exported by default. Let mw know if disabling export fixes the problem.
Hide
Permalink
Mauro Molinari added a comment -

Today I reproduced the problem myself with GRECLIPSE 2.6.1.xx-20120118-1100-e37-M1.
I know it does not contain your latest change, but I'm quite sceptical the problem may reside in the fact that the DSL Support container is exported.
The log entries produced in my case are:

!ENTRY org.eclipse.jst.jsp.core 2 2 2012-02-17 10:02:00.179
!MESSAGE Taglib Index IOException: C:/Users/mauro/.groovy/greclipse/global_dsld_support C:\Users\mauro\.groovy\greclipse\global_dsld_support (Accesso negato)

!ENTRY org.eclipse.jst.jsp.core 2 2 2012-02-17 10:02:00.180
!MESSAGE Taglib Index IOException: D:/Eclipse37/plugins/org.codehaus.groovy_1.8.4.xx-20120118-1100-e37-M1/plugin_dsld_support/ D:\Eclipse37\plugins\org.codehaus.groovy_1.8.4.xx-20120118-1100-e37-M1\plugin_dsld_support (Accesso negato)

I'm pretty sure they were produced while the validation of the JSPs of my Dynamic Web Project was running.
The "export" flag of build path entries have nothing to do with Dynamic Web Project processing or JSP validation, this is why I don't think that is the source of the problem.

Isn't the fact that org.eclipse.jst.jsp.core is looking at the greclipse settings directory in my system home directory a clue of something?

Show
Mauro Molinari added a comment - Today I reproduced the problem myself with GRECLIPSE 2.6.1.xx-20120118-1100-e37-M1. I know it does not contain your latest change, but I'm quite sceptical the problem may reside in the fact that the DSL Support container is exported. The log entries produced in my case are:
!ENTRY org.eclipse.jst.jsp.core 2 2 2012-02-17 10:02:00.179 !MESSAGE Taglib Index IOException: C:/Users/mauro/.groovy/greclipse/global_dsld_support C:\Users\mauro\.groovy\greclipse\global_dsld_support (Accesso negato) !ENTRY org.eclipse.jst.jsp.core 2 2 2012-02-17 10:02:00.180 !MESSAGE Taglib Index IOException: D:/Eclipse37/plugins/org.codehaus.groovy_1.8.4.xx-20120118-1100-e37-M1/plugin_dsld_support/ D:\Eclipse37\plugins\org.codehaus.groovy_1.8.4.xx-20120118-1100-e37-M1\plugin_dsld_support (Accesso negato)
I'm pretty sure they were produced while the validation of the JSPs of my Dynamic Web Project was running. The "export" flag of build path entries have nothing to do with Dynamic Web Project processing or JSP validation, this is why I don't think that is the source of the problem. Isn't the fact that org.eclipse.jst.jsp.core is looking at the greclipse settings directory in my system home directory a clue of something?
Hide
Permalink
Andrew Eisenberg added a comment -

Thanks Mauro. Finally got a chance to look at this. It seems that I can reproduce the problem by having at least one jsp file in a Dynamic Web project. But I can only get the errors to occur at startup.

Show
Andrew Eisenberg added a comment - Thanks Mauro. Finally got a chance to look at this. It seems that I can reproduce the problem by having at least one jsp file in a Dynamic Web project. But I can only get the errors to occur at startup.
Hide
Permalink
Andrew Eisenberg added a comment -

This is a WTP bug. I raised this issue, which describes the full problem and how to reproduce without groovy-eclipse:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=372180

Feel free to comment on it if you would like the team to notice it faster.

Show
Andrew Eisenberg added a comment - This is a WTP bug. I raised this issue, which describes the full problem and how to reproduce without groovy-eclipse: https://bugs.eclipse.org/bugs/show_bug.cgi?id=372180 Feel free to comment on it if you would like the team to notice it faster.
Hide
Permalink
Andrew Eisenberg added a comment -

Closing as won't fix since the root cause is not in groovy-eclipse.

Show
Andrew Eisenberg added a comment - Closing as won't fix since the root cause is not in groovy-eclipse.
Hide
Permalink
Mauro Molinari added a comment -

Thank you Andrew, I will certainly follow the bug report.

Show
Mauro Molinari added a comment - Thank you Andrew, I will certainly follow the bug report.

People

  • Assignee:
    Andrew Eisenberg
    Reporter:
    Davide Cavestro
Vote (0)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved: