Are you sure you have jdbc/rollerdb datasource defined? Did you try
running the dstest.jsp?
If you are running tomcat 5.5.X, copy the jtds-1.2.jar (or your jdbc
driver) to $TOMCAT_HOME\common\lib
Then on your conf\server.xml inside the "<host> ... </host>" section
Add the following
<Context path="/roller" docBase="roller" debug="1"
reloadable="true">
<Resource name="jdbc/rollerdb"
auth="Container"
type="javax.sql.DataSource"
factory="org.apache.tomcat.dbcp.dbcp.BasicDataSourceFactory"
maxActive="20"
maxIdle="5"
maxWait="10000"
username="%SOMEUSER%"
password="%SOMEPASS%"
driverClassName="net.sourceforge.jtds.jdbc.Driver"
url="jdbc:jtds:sqlserver://%DBHOST.FQDN%:1433/%DBNAME%;selectMethod=curs
or"
removeAbandoned="true"
removeAbandonedTimeout="60"
logAbandoned="true" />
</Context>
Change the SOMEUSER,SOMEPASS,DBHOST.FQDN,DBNAME to their proper values.
Restart tomcat and make sure the dstest.jsp works correctly.
George
-----Original Message-----
From: Steele, Aaron [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 28, 2006 3:37 PM
To: [email protected]
Subject: RE: Roller MS SQL Server
Sorry to bother you all again, but I keep getting this error in the
roller.log file
FATAL 2006-03-28 17:33:16,041 PropertiesManagerImpl:init - Failed to
initialize runtime configuration properties.Please check that the
database has been upgraded!
java.lang.UnsupportedOperationException
at
org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSourc
e.java:116)
Do you have any thoughts on why this would be happening? Thanks.
Thank You,
Aaron Steele
YRI Enterprise Solutions
https://ris.yumnet.com
w: 972.338.6862
c: 817.401.0831
-----Original Message-----
From: George Daswani [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 28, 2006 4:34 PM
To: [email protected]
Subject: RE: Roller MS SQL Server
Sorry, wrong link. JTDS = http://jtds.sourceforge.net/
G
-----Original Message-----
From: George Daswani [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 28, 2006 2:32 PM
To: [email protected]
Subject: RE: Roller MS SQL Server
I was the one that submitted the patch.
I've tested it on both the JTDS 1.2 (http://www.jtds.org) along with
Microsoft's new SQL Server 2005 Driver (which also works with SQL Server
2K).
Make sure your hibernate config file (WEB-INF/classes/hibernate.cfg.xml)
is set to use the SQLServer Dialect, instead of the default (MySQL
dialect)
>From this
<property
name="dialect">org.hibernate.dialect.MySQLDialect</property>
To this
<property
name="dialect">org.hibernate.dialect.SQLServerDialect</property>
George
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 28, 2006 2:24 PM
To: [email protected]
Subject: Re: Roller MS SQL Server
You might want to test the latest Roller 2.2 release candidate and see
how that works. We accepted a patch that added MS SQL Server support.
There are database create scripts for MS SQL Server. However, we don't
have upgrade scripts so you might have to create those yourself based on
the other database ones.
Whatever you do, don't mess with your old database until you've complete
verified that you can upgrade safely. Make a copy of your old database
and use that to test.
> You can get the new RC here:
> http://people.apache.org/~snoopdave/roller-2.2-rc/
- Dave
- Dave
On Mar 28, 2006, at 1:07 PM, Steele, Aaron wrote:
> Can anyone point me in the right direction to get Roller working with
> MS SQL Server? Thanks.
>
> Thank You,
>
> Aaron Steele
> YRI Enterprise Solutions
> https://ris.yumnet.com
> w: 972.338.6862
> c: 817.401.0831
>
>
>
>
> This communication is confidential and may be legally privileged.
> If you are not the intended recipient, (i) please do not read or
> disclose to others, (ii) please notify the sender by reply mail,
> and (iii) please delete this communication from your system.
> Failure to follow this process may be unlawful. Thank you for your
> cooperation.
This communication is confidential and may be legally privileged. If
you are not the intended recipient, (i) please do not read or disclose
to others, (ii) please notify the sender by reply mail, and (iii) please
delete this communication from your system. Failure to follow this
process may be unlawful. Thank you for your cooperation.
