Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=dk20050327; d=earthlink.net;
  b=Qzc3R3NVR1znxSIeHT/GGPbMsZar6SDdVMg9gHvAt0vtMSmSGC9cJ4530HHgOOVI;
  h=Received:Message-ID:Date:From:User-Agent:X-Accept-Language:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Message-ID: <43262B4A.5040709@earthlink.net>
Date: Mon, 12 Sep 2005 21:28:42 -0400
From: Joe Bohn <joe.bohn@earthlink.net>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
MIME-Version: 1.0
To: dev@geronimo.apache.org
Subject: Re: Error locating GBean for JettyRequestLog
References: <4325F226.301@earthlink.net>
 <cf8bc05b3d697435dbb8b6f3f0bdb44b@yahoo.com> <4325F853.20704@earthlink.net>
In-Reply-To: <4325F853.20704@earthlink.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Well ... I knew of one place this was specified but it obviously isn't 
the only place. :-)  I made the change there and it didn't help the problem.

I did a grep from trunk of all *.java, *.xml, and *.properties files and 
found 312 matches for  "org/apach/geronimo/Server" in 122 different files.

Only 2 matches were in console modules ... the one I knew of and another 
one.   Even after making those changes the error still occurs.  So, it 
appears that this is something bigger than just the console.

I'll try to narrow this down to the offending file(s) ...  I'm sure most 
of these references or garbage left after the change in the name.  If 
anybody has any suggestions I'm all ears. :-)

Joe Bohn wrote:

> Thanks David ... that does help.
> I know where it is getting the name from (it's in a constants file in 
> the console).   I'll update that file and see how far it gets.
>
> Joe
>
> David Jencks wrote:
>
>>
>> On Sep 12, 2005, at 2:24 PM, Joe Bohn wrote:
>>
>>> With the most recent builds since late last week (maybe since we  
>>> started jointly building the image with Jetty and Tomcat) ....  
>>> I've  noticed a problem with the Jetty Web Server Log.
>>>
>>> First, we get this error during initialization of the server:
>>>
>>> [********>    ] 66%  31s Starting  
>>> ...che/geronimo/JettyRuntimeDeployer16:39:07,023 ERROR  
>>> [LocalAttributeManager] Unable to store attribute type  
>>> org.mortbay.http.RequestLog
>>
>>
>>
>> I don't think this is a problem.
>>
>>> [*************] 100%  37s Startup complete
>>>
>>> So it looks like something isn't right with the classloader, GBean  
>>> definition, or I don't know what .....
>>>
>>> This then results in the following exception when we attempt to 
>>> access  the content of the log from the console:
>>>
>>> org.apache.geronimo.kernel.GBeanNotFoundException:  
>>> geronimo.server:J2EEApplication=null,J2EEModule=org/apache/geronimo/ 
>>> Server,J2EEServer=geronimo,j2eeType=GBean,name=JettyRequestLog not  
>>> found
>>
>>
>>
>> I don't know where this name came from, but it is wrong.  J2EEModule  
>> should be o/a/g/Jetty.
>>
>>>
>> <snip>
>>
>>> When I look at the NCSARequestLog I notice that where it is setting  
>>> the GBeanInfoBuilder values there is no attribute for the 
>>> RequestLog   ... but when I look at older versions when the 
>>> attribute could be  found it is the same setting (or lack of 
>>> setting) for the RequestLog.
>>
>>
>> I don't know about this part, but I would try fixing the gbean name  
>> first.
>>
>> hope this helps,
>> david jencks
>>
>>
>>
>

-- 
Joe Bohn     
joe.bohn@earthlink.net

"He is no fool who gives what he cannot keep, to gain what he cannot lose."   -- Jim Elliot