I just checked and it appears that this change is included in trunk (if
you have a recent enough version). Perhaps the objectname changed yet
again. I don't have a working version of trunk at the moment to check
and see if I get the same error or not. Can you check to see if you
have the fix included in your image. That should let us know if the
error is the old one or something new.
Check your version of
applications/console-standard/src/java/org/apache/geronimo/console/internaldb/DerbyConnectionUtil.java
and see if the objectname referenced is
geronimo.server:J2EEApplication=null,J2EEServer=geronimo,JCAResource=geronimo/system-database/1.0/car,j2eeType=JCAManagedConnectionFactory,name=SystemDatasource
Joe
Vamsavardhana Reddy wrote:
The version I am using is built from trunk.
-Vamsi
On 1/4/06, *Joe Bohn* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
What version of Geronimo are you using?
There was a problem with this that was fixed in 1.0 by Paul McMahan
http://issues.apache.org/jira/browse/GERONIMO-1373
<http://issues.apache.org/jira/browse/GERONIMO-1373>
Perhaps this patch didn't get applied to trunk.
Joe
Vamsavardhana Reddy wrote:
> I notice that the DB Info portlet in Geronimo Console is not
displaying
> any information. No error is logged to geronimo.log . Only
> java.sql.SQLException is output to the command window running
Geronimo.
> Has anybody else came across this?
--
Joe Bohn
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
"He is no fool who gives what he cannot keep, to gain what he cannot
lose." -- Jim Elliot
--
Joe Bohn
[EMAIL PROTECTED]
"He is no fool who gives what he cannot keep, to gain what he cannot
lose." -- Jim Elliot
