[ http://issues.apache.org/jira/browse/GERONIMO-1073?page=all ]
     
Matt Hogstrom closed GERONIMO-1073:
-----------------------------------

    Resolution: Fixed

Same as GERONIMO-512...resolved there

> TradeDirect:init error on JNDI lookups of DataSource when TradeDataSource is 
> already running
> --------------------------------------------------------------------------------------------
>
>          Key: GERONIMO-1073
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1073
>      Project: Geronimo
>         Type: Bug
>     Versions: 1.0-M5
>  Environment: Windows
>     Reporter: Lin Sun
>     Priority: Minor

>
>  I had thought this issue is same as JIRA 512 
> (http://issues.apache.org/jira/browse/GERONIMO-512), but I did the following 
> practice to force the JDBC resource available before I deployed daytrader:
> I broke the jdbc resource portion of the plan to a seperate plan
> and deployed the jdbc resource first.
> 11:10:36,399 DEBUG [GBeanInstanceState] GBeanInstanceState for:
> geronimo.server:J2EEApplication=null,J2EEServer=geronimo,Resource
> Adapter=TradeDataSource,j2eeType=JCAResource,name=TradeDataSource
> State changed from stopped to starting
> 11:10:36,399 DEBUG [GBeanInstanceState] GBeanInstanceState for:
> geronimo.server:J2EEApplication=null,J2EEServer=geronimo,Resource
> Adapter=TradeDataSource,j2eeType=JCAResource,name=TradeDataSource
> State changed from starting to running
> Then I deployed the daytrader plan, still got the error on JNDI
> lookups:
> 11:13:57,077 DEBUG [WebappClassLoader]   Loading class from
> parent
> TradeLog:Fri Oct 14 11:13:57 EDT 2005------
>                 
> Error: TradeDirect:init -- error on JNDI lookups of DataSource
> -- TradeDirect will not work
>                javax.naming.NameNotFoundException:
> comp/env/jdbc/TradeDataSource
> javax.naming.NameNotFoundException:
> comp/env/jdbc/TradeDataSource
>                at 
> org.apache.geronimo.naming.java.RootContext.lookup(RootContex
> t.java:45)
> TradeDirect is working even with the exception, but I could not understand 
> why I would get this error in the console.  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to