On Feb 12, 2007, at 11:27 AM, Spotts, Joel ((ISS Atlanta)) wrote:
Kevan,
How do I turn off proxy generation? What do you mean by breaking
admin console? I wont be able to control that app from the admin
console? Are there other side effects?
Hi Yoel,
Disable proxy generation like this:
export JAVA_OPTS=-DXorg.apache.geronimo.gbean.NoProxy=true
./geronimo.sh run
Server startup will be a few seconds faster. You should see a log
entry like this:
14:28:05,885 WARN [AbstractGBeanReference] GBean reference proxies
has been disabled: This is an experimental and untested operating mode
Starting Geronimo Application Server v1.1.1
It's my understanding that there are some admin console functions
that won't work, with NoProxy. I must confess that I don't know what
specific features they are...
Generated GBean proxies give the admin console a common management
GBean interface to work with. Without proxies some GBean inspection/
management functions won't work. I ran a quick test with NoProxy --
starting stopping web apps, etc -- and didn't run into any errors.
Perhaps someone better versed in our console implementation can
explain what exactly won't work...
--kevan
Thanks,
Yoel
From: Kevan Miller [mailto:[EMAIL PROTECTED]
Sent: Saturday, February 10, 2007 12:56 PM
To: [email protected]
Subject: Re: Gbean within a signed jar
On Feb 6, 2007, at 2:54 PM, Spotts, Joel ((ISS Atlanta)) wrote:
I have a gbean packaged within a signed jar that is placed in my
EAR. Trouble is it seems that geronimo uses proxy classes on the
gbean class files, which results in the dreaded:
java.lang.SecurityException: class "..."'s signer information does
not match signer information of other classes in the same package
when geronimo attempts to start the gbean. Anyone have a solution
to this problem other than not signing the jar?
Hi Yoel,
Interesting. First I've heard of this problem, but it makes sense.
I don't really have a "solution" for you.
1) As you suggest, don't sign your jar... :-P
2) Turn off proxy generation in the server. This, however, has the
unfortunate side-effect of breaking the admin console. So, this
really isn't much of an option.
Perhaps somebody else can chime in...
--kevan
