roller-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dave <snoopd...@gmail.com>
Subject Re: Some error happend
Date Thu, 09 Aug 2007 12:45:31 GMT
Hi Nike,

Looks like you have several possible problems in your configuration:


On 8/9/07, Nike Freeman <chageoni@yahoo.com> wrote:
> apache-tomcat-5.5.23\common\lib  : ojdbc14.jar  |  activation.jar  |
> mail.jar

Good. You've got an Oracle JDBC driver in the right place.


> <Context path="/roller" docBase="F:\roller31\build\webapp" debug="0">
> <Resource name="jdbc/rollerdb"
> auth="Container"
> type="javax.sql.DataSource"
> driverClassName="oracle.jdbc.driver.OracleDriver"
> url="jdbc:oracle:thin:@172.26.253.53:1521:MP"
> username="roller"
> password="roller"
> maxActive="20"
> maxIdle="3"
> removeAbandoned="false"
> maxWait="3000" />
> <Resource name="mail/Session"
> auth="Container"
> type="javax.mail.Session"
> mail.smtp.host="mail.strongit.com.cn" />
> </Context>

Good. You've got database connection parameters and they look OK.


> javax.naming.NameNotFoundException: Name RollerDataSource is not bound in
> this Context
>         at org.apache.naming.NamingContext.lookup(NamingContext.java:770)
>         at org.apache.naming.NamingContext.lookup(NamingContext.java:140)
>         at org.apache.naming.NamingContext.lookup(NamingContext.java:781)

That sounds bad.

Why is Tomcat looking for the name "RollerDataSource"? Your context
configuration file (above) uses the name "jdbc/rollerdb". That's
probably a problem. Did you change something in Roller's web.xml file?


> INFO  2007-08-09 12:55:42,888 Environment:<clinit> - Hibernate 3.1.3
> INFO  2007-08-09 12:55:42,903 Environment:<clinit> - hibernate.properties

Why Hibernate 3.1.3? The installation instructions specify Hibernate
3.1.2 and we only tested with 3.1.2. That's probably not the cause of
your current problem, but it could be a problem later.


> INFO  2007-08-09 12:55:43,763 DriverManagerConnectionProvider:configure -
> Using Hibernate built-in connection pool (not for production use!)

That looks wrong.

Why is Hibernate using it's own connection pool? What changes did you
make to the Hibernate configuration file? The only change you need to
make is to set the Oracle dialect; there is no need to set any
database connection parameters in hibernate.cfg.xml.


> INFO  2007-08-09 12:55:43,763 DriverManagerConnectionProvider:configure -
> Hibernate connection pool size: 20
> INFO  2007-08-09 12:55:43,763 DriverManagerConnectionProvider:configure -
> autocommit mode: false
> INFO  2007-08-09 12:55:43,779 DriverManagerConnectionProvider:configure -
> using driver: oracle.jdbc.driver.OracleDriver at URL:
> jdbc:oracle:thin:@172.26.253.52:1521:innis
> INFO  2007-08-09 12:55:43,779 DriverManagerConnectionProvider:configure -
> connection properties: {user=roller, password=****}
> WARN  2007-08-09 12:55:46,233 SettingsFactory:buildSettings - Could not
> obtain connection metadata
> java.sql.SQLException: Listener refused the connection with the following
> error:
> ORA-12505, TNS:listener does not currently know of SID given in connect
> descriptor
> The Connection descriptor used by the client was:
> 172.26.253.52:1521:innis

That error "ORA-12505, TNS:listener does not currently know of SID
given in connect descriptor" seems to indicate that your Oracle
connection URL is incorrect, but I don't know enough about Oracle to
tell.

- Dave

Mime
View raw message