Re: Long shot on a IllegalAccessError

[Pete Helgren <Pete@xxxxxxxxxx>]

I had looked up the Javadoc on it and saw the same rationale.  I just 
can't quite figure out what this application wouldn't have access to.  I 
don't think permissions on the jars would be an issue so the Javadoc 
seems to only indicate an issue with a method or field that may be 
flagged private or something

I have done that since I posted.  I removed the jars, logged off the 
system and then logged back in and replaced the jars (assuming that 
maybe something in the job was holding the jars in cache).

Any idea where the cached jars might reside? This is driving me a little 
crazy, knowing that I am on a deadline, I have seen the error and fixed 
it (in Windows) and can't find any other explanation for the error.

Thanks!

Pete


On 5/1/2010 4:08 PM, Thorbjoern Ravn Andersen wrote:
> Den 01/05/10 22.16, Pete Helgren skrev:
>    
> > I DID see this once, even in my Windows environment, but it seemed to
> > stem from a mismatch in Birt versions.  I have checked and rechecked the
> > jars and both environments seem to match.  Unless the jars are cached
> > somewhere on the i, I don't think a version mismatch is the issue.
> >
> >
> >      
>    From the javadoc:
> ===
>
> Thrown if an application attempts to access or modify a field, or to
> call a method that it does not have access to.
>
> Normally, this error is caught by the compiler; this error can only
> occur at run time if the definition of a class has incompatibly changed.
>
> ====
>
> In your situation that _could_ make sense as the i JVM caches some of
> the work hidden with the jar file in the IFS.  I have seen that
> overwriting the contents of a jar file did not remove that work.  I
> would start with removing the birt jar completely from the ifs and copy
> it in again.
>
> On second thought.  Do it with all your jars :)
>    
> > I could use *any* ideas you might have.  I don't quite understand what
> > is being accessed illegally here.  Not much in the Birt method
> > ExtensionManager.initialize() to go on.
> >
> >      
> I've also seen it happen with reflection I think.  Nasty one there.
>
>