Re: [Wrapper-user] IllegalAccessException

[Leif M. <le...@ta...>]

Alan,
Is there any reason why you are placing your personal jar files into the
jre/lib/ext directory? Normally that is not a good idea. Jars in that
directory are considered to be privileged / trusted jars that always have
full security permissions.
The problem is that you have placed the wrapper.jar file into a non
privileged directory "../lib/wrapper.jar" I believe that is what is happing
is that the Wrapper, which is unprivileged code is attempting to create
a class that is privileged. Depending on the security manager this may
be causing the problems you are seeing.
Normally you should place your custom classes / jar files into an
application lib directory as you have done with the wrapper.jar file. All
of the jars in that directory are then included in the classpath. The
Wrapper makes this easy by allowing you to specify a wild card:

wrapper.java.classpath.1=../lib/*.jar

If this does not work, then please explain a little more about your
application and why you have set things up the way you have. Also
let me know if you are setting a SecurityManager someplace in your
code.

Cheers,
Leif

Parry, Alan wrote:

> Hi,
>
> I'm using the WrapperSimpleApp method of starting my java service and
> when running the Console batch file I receive the following error
> message (see below). I receive the same error when attempting to start
> as a NT service.
>
> I have declared the class public (also attached below), see below and
> am unsure of what else could be stopping the Wrapper from accessing my
> class, which runs comfortably when called by its own main method.
>
> Does anyone have any experience with this error message and a possible
> fix? I have jar'ed the classes in my application and placed them in
> jre/lib/ext and am wondering if more needs to be done before this
> mechanism will function correctly.
>
> Many Thanks,
>
> Alan Parry
>