You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@roller.apache.org by Simon Haslam <si...@yahoo.co.uk> on 2007/11/12 22:00:04 UTC
Roller 4.0 RC9 installation problem on OAS 10.1.3.3.0 (OC4J)
Hello
I'm new to Roller and am trying to install roller 4.0 RC9 on Oracle Application Server 10.1.3.3.0 (i.e. OC4J) and Oracle database 10.2.0.3 on OEL/RHEL R5 Linux.
I'm using a straight JDBC connection for now - my roller-custom.properties file is:
installation.type=auto
database.configurationType=jdbc
database.jdbc.driverClass=oracle.jdbc.pool.OracleDataSource
database.jdbc.connectionURL=jdbc:oracle:thin:@//localhost:1521/myservicename
database.jdbc.username=roller
database.jdbc.password=***
In roller.log I'm getting:
INFO 2007-11-12 20:06:45,654 DatabaseProvider:successMessage - SUCCESS: Got parameters. Using configuration type JDBC_PROPERTIES
INFO 2007-11-12 20:06:45,663 DatabaseProvider:successMessage - -- Using JDBC driver class: oracle.jdbc.pool.OracleDataSource
INFO 2007-11-12 20:06:45,749 DatabaseProvider:successMessage - -- Using JDBC connection URL: jdbc:oracle:thin:@//localhost:1521/***
INFO 2007-11-12 20:06:45,751 DatabaseProvider:successMessage - -- Using JDBC username: roller
INFO 2007-11-12 20:06:45,766 DatabaseProvider:successMessage - -- Using JDBC password: [hidden]
INFO 2007-11-12 20:06:45,781 DatabaseProvider:successMessage - SUCCESS: loaded JDBC driver class [oracle.jdbc.pool.OracleDataSource]
INFO 2007-11-12 20:06:48,073 RollerContext:contextInitialized -
--------------------------------------------------------------
Roller Weblogger startup INCOMPLETE, user interaction required
--------------------------------------------------------------
INFO 2007-11-12 20:06:48,079 RollerContext:initializeSecurityFeatures - Remember Me enabled: true
INFO 2007-11-12 20:06:48,082 RollerContext:initializeSecurityFeatures - Password Encryption Algorithm set to 'SHA'
INFO 2007-11-12 20:06:48,083 RollerContext:setupVelocity - Initializing Velocity
...
INFO 2007-11-12 20:08:59,286 RequestMappingFilter:init - Request mapping filter initialized, 1 mappers configured.
WARN 2007-11-12 20:09:00,064 Settings:getLocale - Settings: Could not parse struts.locale setting, substituting default VM locale
I can see that the tables haven't been created by the auto install which presumably is a symptom of another problem. When I ran the oracle/createdb.sql script manually as the roller user from sqlplus that worked fine (I dropped the tables again afterwards). Whenever I do http://myserver/roller/ I get a roller message box "Roller has encountered and logged an unexpected exception." (i.e. from the container).
I saw the change to add the "Roller Weblogger startup INCOMPLETE, user interaction required" message, just not sure where I go from here...
Any help gratefully received!
Simon
PS. I'll contribute to the OAS/OC4J instructions if I manage to get it working ;-)
---------------------------------
Yahoo! Answers - Get better answers from someone who knows. Tryit now.
RE: Roller 4.0 RC9 installation problem on OAS 10.1.3.3.0 (OC4J)
Posted by John Langan <la...@homes.com>.
Hi,
We are running Roller in Glassfish and connecting to an Oracle database.
The steps we took were:
1. Our DBA created the tablespace in our database.
2. The ojdbc14.jar is installed in Glassfish, in
glassfish\domains\domain1\lib\ext.
3. Our roller-custom.properties file is similar to yours except
database.jdbc.driverClass=oracle.jdbc.driver.OracleDriver
and database.jdbc.connectionURL connects to our database server and after
the @ there is no //
On the first it created the tables in the database as described in the docs.
Hope this helps.
John.
-----Original Message-----
From: Gaetano Raimondo [mailto:gaetano.raimondo@gmail.com]
Sent: Friday, December 14, 2007 5:55 AM
To: user@roller.apache.org
Subject: Re: Roller 4.0 RC9 installation problem on OAS 10.1.3.3.0 (OC4J)
Hi, I'm facing the same problem, whit roller 4.0 final release.
Have you resolved it?
Thank you for any help
Simon Haslam wrote:
>
> Hello
>
> I'm new to Roller and am trying to install roller 4.0 RC9 on Oracle
> Application Server 10.1.3.3.0 (i.e. OC4J) and Oracle database 10.2.0.3 on
> OEL/RHEL R5 Linux.
>
> I'm using a straight JDBC connection for now - my roller-custom.properties
> file is:
>
> installation.type=auto
> database.configurationType=jdbc
> database.jdbc.driverClass=oracle.jdbc.pool.OracleDataSource
>
database.jdbc.connectionURL=jdbc:oracle:thin:@//localhost:1521/myservicename
> database.jdbc.username=roller
> database.jdbc.password=***
>
> In roller.log I'm getting:
> INFO 2007-11-12 20:06:45,654 DatabaseProvider:successMessage - SUCCESS:
> Got parameters. Using configuration type JDBC_PROPERTIES
> INFO 2007-11-12 20:06:45,663 DatabaseProvider:successMessage - -- Using
> JDBC driver class: oracle.jdbc.pool.OracleDataSource
> INFO 2007-11-12 20:06:45,749 DatabaseProvider:successMessage - -- Using
> JDBC connection URL: jdbc:oracle:thin:@//localhost:1521/***
> INFO 2007-11-12 20:06:45,751 DatabaseProvider:successMessage - -- Using
> JDBC username: roller
> INFO 2007-11-12 20:06:45,766 DatabaseProvider:successMessage - -- Using
> JDBC password: [hidden]
> INFO 2007-11-12 20:06:45,781 DatabaseProvider:successMessage - SUCCESS:
> loaded JDBC driver class [oracle.jdbc.pool.OracleDataSource]
> INFO 2007-11-12 20:06:48,073 RollerContext:contextInitialized -
> --------------------------------------------------------------
> Roller Weblogger startup INCOMPLETE, user interaction required
> --------------------------------------------------------------
> INFO 2007-11-12 20:06:48,079 RollerContext:initializeSecurityFeatures -
> Remember Me enabled: true
> INFO 2007-11-12 20:06:48,082 RollerContext:initializeSecurityFeatures -
> Password Encryption Algorithm set to 'SHA'
> INFO 2007-11-12 20:06:48,083 RollerContext:setupVelocity - Initializing
> Velocity
> ...
> INFO 2007-11-12 20:08:59,286 RequestMappingFilter:init - Request mapping
> filter initialized, 1 mappers configured.
> WARN 2007-11-12 20:09:00,064 Settings:getLocale - Settings: Could not
> parse struts.locale setting, substituting default VM locale
>
> I can see that the tables haven't been created by the auto install which
> presumably is a symptom of another problem. When I ran the
> oracle/createdb.sql script manually as the roller user from sqlplus that
> worked fine (I dropped the tables again afterwards). Whenever I do
> http://myserver/roller/ I get a roller message box "Roller has encountered
> and logged an unexpected exception." (i.e. from the container).
>
> I saw the change to add the "Roller Weblogger startup INCOMPLETE, user
> interaction required" message, just not sure where I go from here...
>
> Any help gratefully received!
>
>
> Simon
> PS. I'll contribute to the OAS/OC4J instructions if I manage to get it
> working ;-)
>
>
> ---------------------------------
> Yahoo! Answers - Get better answers from someone who knows. Tryit now.
>
--
View this message in context:
http://www.nabble.com/Roller-4.0-RC9-installation-problem-on-OAS-10.1.3.3.0-
%28OC4J%29-tp13714430s12275p14333555.html
Sent from the Roller - User mailing list archive at Nabble.com.
Re: Roller 4.0 RC9 installation problem on OAS 10.1.3.3.0 (OC4J)
Posted by Gaetano Raimondo <ga...@gmail.com>.
Hi, I'm facing the same problem, whit roller 4.0 final release.
Have you resolved it?
Thank you for any help
Simon Haslam wrote:
>
> Hello
>
> I'm new to Roller and am trying to install roller 4.0 RC9 on Oracle
> Application Server 10.1.3.3.0 (i.e. OC4J) and Oracle database 10.2.0.3 on
> OEL/RHEL R5 Linux.
>
> I'm using a straight JDBC connection for now - my roller-custom.properties
> file is:
>
> installation.type=auto
> database.configurationType=jdbc
> database.jdbc.driverClass=oracle.jdbc.pool.OracleDataSource
> database.jdbc.connectionURL=jdbc:oracle:thin:@//localhost:1521/myservicename
> database.jdbc.username=roller
> database.jdbc.password=***
>
> In roller.log I'm getting:
> INFO 2007-11-12 20:06:45,654 DatabaseProvider:successMessage - SUCCESS:
> Got parameters. Using configuration type JDBC_PROPERTIES
> INFO 2007-11-12 20:06:45,663 DatabaseProvider:successMessage - -- Using
> JDBC driver class: oracle.jdbc.pool.OracleDataSource
> INFO 2007-11-12 20:06:45,749 DatabaseProvider:successMessage - -- Using
> JDBC connection URL: jdbc:oracle:thin:@//localhost:1521/***
> INFO 2007-11-12 20:06:45,751 DatabaseProvider:successMessage - -- Using
> JDBC username: roller
> INFO 2007-11-12 20:06:45,766 DatabaseProvider:successMessage - -- Using
> JDBC password: [hidden]
> INFO 2007-11-12 20:06:45,781 DatabaseProvider:successMessage - SUCCESS:
> loaded JDBC driver class [oracle.jdbc.pool.OracleDataSource]
> INFO 2007-11-12 20:06:48,073 RollerContext:contextInitialized -
> --------------------------------------------------------------
> Roller Weblogger startup INCOMPLETE, user interaction required
> --------------------------------------------------------------
> INFO 2007-11-12 20:06:48,079 RollerContext:initializeSecurityFeatures -
> Remember Me enabled: true
> INFO 2007-11-12 20:06:48,082 RollerContext:initializeSecurityFeatures -
> Password Encryption Algorithm set to 'SHA'
> INFO 2007-11-12 20:06:48,083 RollerContext:setupVelocity - Initializing
> Velocity
> ...
> INFO 2007-11-12 20:08:59,286 RequestMappingFilter:init - Request mapping
> filter initialized, 1 mappers configured.
> WARN 2007-11-12 20:09:00,064 Settings:getLocale - Settings: Could not
> parse struts.locale setting, substituting default VM locale
>
> I can see that the tables haven't been created by the auto install which
> presumably is a symptom of another problem. When I ran the
> oracle/createdb.sql script manually as the roller user from sqlplus that
> worked fine (I dropped the tables again afterwards). Whenever I do
> http://myserver/roller/ I get a roller message box "Roller has encountered
> and logged an unexpected exception." (i.e. from the container).
>
> I saw the change to add the "Roller Weblogger startup INCOMPLETE, user
> interaction required" message, just not sure where I go from here...
>
> Any help gratefully received!
>
>
> Simon
> PS. I'll contribute to the OAS/OC4J instructions if I manage to get it
> working ;-)
>
>
> ---------------------------------
> Yahoo! Answers - Get better answers from someone who knows. Tryit now.
>
--
View this message in context: http://www.nabble.com/Roller-4.0-RC9-installation-problem-on-OAS-10.1.3.3.0-%28OC4J%29-tp13714430s12275p14333555.html
Sent from the Roller - User mailing list archive at Nabble.com.
Re: Roller 4.0 RC9 installation problem on OAS 10.1.3.3.0 (OC4J)
Posted by Dave <sn...@gmail.com>.
On Jan 19, 2008 3:45 PM, Simon Haslam <si...@yahoo.co.uk> wrote:
>
> Success!!! (I think!) Thanks for the tip Gabe - your workaround got me over
> the 500 error! Thanks too to Dave and the others who have posted
> suggestions.
>
> So, let me recap what I had to do to install Roller 4.0 from scratch on
> Oracle Application Server 10.1.3.3 and an Oracle 10g database on Linux
> (hopefully I've not forgotten anything):
>
> 1) unzip Roller, e.g. into your Oracle account's home directory and create a
> WAR file
>
> 2) create a separate roller_data directory (again I put it in ~oracle), copy
> in the themes directory from Roller and also create empty directories called
> "resources" and "search-index".
>
> 3) create a roller-custom.properties file, preferably outside the roller
> deployment directory (at the moment I've got it my jdk classes directory but
> will look to put it somewhere more sensible). The file should contain at
> least the following:
> installation.type=manual
> database.configurationType=jdbc
> database.jdbc.driverClass=oracle.jdbc.driver.OracleDriver
> database.jdbc.connectionURL=jdbc:oracle:thin:@yourhost:yourport:yoursid
> database.jdbc.username=yourrolleruser
> database.jdbc.password=yourpassword
> mail.configurationType=properties
> mail.hostname=yoursmtphost
> uploads.dir=/home/oracle/roller_data/resources
> themes.dir=/home/oracle/roller_data/themes
> search.index.dir=/home/oracle/roller_data/search-index
> log4j.appender.roller.File=/home/oracle/roller_data/roller.log
>
> note: there's still work to be done here, e.g. I'd like use container
> managed JNDI connection pooling. The above settings got me running though.
>
> 4) create a user account on the Oracle database, e.g. sqlplus / as sysdba
> create user yourrolleruser
> identified by yourrollerpassword
> default tablespace users
> temporary tablespace temp
> quota unlimited on users;
> grant create session to yourrolleruser;
> grant create table to yourrolleruser;
>
> 5) log in to the database as your roller user and run the
> webapp/roller/WEB-INF/classes/dbscripts/oracle/createdb.sql script to create
> the schema objects - check there were no errors.
>
> 6) log in to the App Server Control console, create a new OC4J container for
> roller (optional but sensible)
>
> 7) download log4j and put the jar file into the classpath (e.g. cp
> log4j-1.2.15.jar $ORACLE_HOME/j2ee/roller/applib)
>
> 8) deploy the roller app using the default settings (upload the roller.war
> file you created earlier) except untick the Apache.commons.logging 1.0.4
> library. You shouldn't get any errors.
>
> Now the roller app should have deployed - at this point it would probably be
> sensible to plough through the log file and make sure roller connected to
> the database OK and that the bootstrapping worked.
>
> The final steps are:
> 9) (note: going to http://yourdomain/roller will give an error as per Gabe's
> ROL-1653). Go to http://yourdomain/roller/roller-ui/menu.rol which gives the
> login screen as well as a link to Register a new user (register.rol). Create
> your first user.
>
> 10) Now login with that user and create a first blog.
>
> 11) Click on the "Main Menu" (or maybe you'll already be there) and then the
> "Server Administration" link on the righthand side.
>
> 12) Scroll down the page and set "Handle of weblog to serve as frontpage
> blog" to the one you just created then click the Save button.
>
> Now when you click Front Page (or just enter the http://yourdomain/roller
> URL) you should go to your new blog.
>
> Enjoy!
>
>
> Simon
> PS. As Dave pointed out, there may still be issues with the way the Oracle
> JDBC driver handles nulls yet to be resolved when actually using roller.
> Note: this isn't a fault of the database (you wouldn't want it to store an
> empty field as spaces) but a "feature" of their JDBC driver implementation.
> I'll post anything I find as a new thread.
I'm glad to hear you had success and thank you very much for writing
this up. I'm sure other Oracle users will find this very useful.
If you would like to contribute patches or docs (wiki or otherwise) to
make Roller work better with Oracle, please file an Individual
Contributor License Agreement (ICLA) with Apache. Details are here:
http://www.apache.org/licenses/icla.txt
- Dave
Re: Roller 4.0 RC9 installation problem on OAS 10.1.3.3.0 (OC4J)
Posted by Simon Haslam <si...@yahoo.co.uk>.
Thanks for the suggestions Gabe - good timing!
I see that Roller does quite a few JDBC new sessions per page view (~8 I think) so getting
connection pooling working is a definite requirement if you're running an Oracle database.
Without a pooled connection I'm also finding that when I reload the page after it has been idle
for a while it doesn't refresh properly and I get this error:
WARN 2008-01-22 09:38:17,421 WebloggerRuntimeConfig:getProperty - Trouble accessing property:
site.frontpage.weblog.aggregated
<0.9.7-incubating nonfatal general error> org.apache.openjpa.persistence.PersistenceException:
Listener refused the connection with the following error:
ORA-12519, TNS:no appropriate service handler found
The Connection descriptor used by the client was:
localhost:1521:mysid
When you look in the listener log you see:
22-JAN-2008 09:38:17 * (CONNECT_DATA=(SID=mysid)(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))) *
(ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=14204)) * establish * mysid * 12519
TNS-12519: TNS:no appropriate service handler found
This is the database not having enough free processes and is usually symptomatic of something else
being wrong. In this case I'm guessing it is probably due to lots of JDBC connections left
dangling.
Anyway, there's not much point worrying about that until pooled connections are working.
Running OAS, rather than just a standalone OC4J, means that you can set up and test the connection
pool from ASC admin tool and it will set up the aplpication.xml etc when you deploy the WAR file.
I haven't yet got a clean deployment using a pooled connection but have managed to get it to work
by bludgeoning the config in application-deployments... it must just be a question of getting the
deployment descriptors right.
What I'd like to do is get an Oracle deployment plan delivered alongside the Roller release - then
admins would simply be able to edit their database credentials in that and then deploy the war
file. A bit more work to be done though...
__________________________________________________________
Sent from Yahoo! Mail - a smarter inbox http://uk.mail.yahoo.com
Re: Roller 4.0 RC9 installation problem on OAS 10.1.3.3.0 (OC4J)
Posted by Gabe Wong <ga...@ngasi.com>.
Simon Haslam wrote:
> Success!!! (I think!) Thanks for the tip Gabe - your workaround got me over
> the 500 error! Thanks too to Dave and the others who have posted
> suggestions.
>
> So, let me recap what I had to do to install Roller 4.0 from scratch on
> Oracle Application Server 10.1.3.3 and an Oracle 10g database on Linux
> (hopefully I've not forgotten anything):
>
> 1) unzip Roller, e.g. into your Oracle account's home directory and create a
> WAR file
>
> 2) create a separate roller_data directory (again I put it in ~oracle), copy
> in the themes directory from Roller and also create empty directories called
> "resources" and "search-index".
>
> 3) create a roller-custom.properties file, preferably outside the roller
> deployment directory (at the moment I've got it my jdk classes directory but
> will look to put it somewhere more sensible). The file should contain at
> least the following:
> installation.type=manual
> database.configurationType=jdbc
> database.jdbc.driverClass=oracle.jdbc.driver.OracleDriver
> database.jdbc.connectionURL=jdbc:oracle:thin:@yourhost:yourport:yoursid
> database.jdbc.username=yourrolleruser
> database.jdbc.password=yourpassword
> mail.configurationType=properties
> mail.hostname=yoursmtphost
> uploads.dir=/home/oracle/roller_data/resources
> themes.dir=/home/oracle/roller_data/themes
> search.index.dir=/home/oracle/roller_data/search-index
> log4j.appender.roller.File=/home/oracle/roller_data/roller.log
>
> note: there's still work to be done here, e.g. I'd like use container
> managed JNDI connection pooling. The above settings got me running though.
>
>
JNDI DataSource can be accomplished by deploying roller as an EAR on
Oracle-OC4J (10.x).
Place the following 3 files in the EAR META-INF directory. Edit accordingly:
application.xml:
<?xml version="1.0"?>
<!DOCTYPE application PUBLIC "-//Sun Microsystems, Inc.//DTD J2EE
Application 1.2//EN" "http://java.sun.com/j2ee/dtds/application_1_2.dtd">
<application>
<display-name>Oracle generated application roller</display-name>
<module>
<web>
<web-uri>roller.war</web-uri>
<context-root>/roller</context-root>
</web>
</module>
</application>
data-sources.xml:
<?xml version="1.0" standalone='yes'?>
<data-sources
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="http://xmlns.oracle.com/oracleas/schema/data-sources-10_1.xsd"
schema-major-version="10"
schema-minor-version="1"
>
<managed-data-source name="jdbc/rollerdb"
connection-pool-name="rollerdb Connection Pool"
jndi-name="jdbc/rollerdb" ejb-location="jdbc/rollerdb"/>
<connection-pool name="rollerdb Connection Pool">
<connection-factory factory-class="oracle.jdbc.pool.OracleDataSource"
user="scott"
password="coolgeek"
url="jdbc:oracle:thin:@localhost:1521:orcl">
</connection-factory>
</connection-pool>
</data-sources>
orion-application.xml:
<?xml version = '1.0' encoding = 'utf-8'?>
<orion-application
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="http://xmlns.oracle.com/oracleas/schema/orion-application-10_0.xsd"
schema-major-version="10"
schema-minor-version="0"
component-classification="internal">
<data-sources path="./data-sources.xml"/>
<mail-session location="mail/Session" ejb-location="mail/Session"
smtp-host="localhost"/>
</orion-application>
Before packaging the roller.war into the EAR, unpackage it and edit
roller-custom.properties like so:
installation.type=manual
hibernate.dialect=org.hibernate.dialect.OracleDialect
uploads.dir=~/appservers/private/roller_roller_data/uploads
search.index.dir=~/appservers/private/roller_roller_data/search-index
planet.aggregator.cache.dir=~/appservers/private/roller_roller_data/planetcache
database.configurationType=jndi
database.jndi.name=jdbc/rollerdb
mail.configurationType=jndi
mail.jndi.name=mail/Session
log4j.appender.roller.File=~/appservers/private/roller_roller.log
Hope this helps.
--
Regards
Gabe Wong
NGASI AppServer Manager
JAVA AUTOMATION and SaaS Enablement
<a href=http://www.ngasi.com>http://www.ngasi.com</a>
NEW! 8.0 - Centrally manage multiple physical servers
RE: Roller 4.0 RC9 installation problem on OAS 10.1.3.3.0 (OC4J)
Posted by Simon Haslam <si...@yahoo.co.uk>.
Success!!! (I think!) Thanks for the tip Gabe - your workaround got me over
the 500 error! Thanks too to Dave and the others who have posted
suggestions.
So, let me recap what I had to do to install Roller 4.0 from scratch on
Oracle Application Server 10.1.3.3 and an Oracle 10g database on Linux
(hopefully I've not forgotten anything):
1) unzip Roller, e.g. into your Oracle account's home directory and create a
WAR file
2) create a separate roller_data directory (again I put it in ~oracle), copy
in the themes directory from Roller and also create empty directories called
"resources" and "search-index".
3) create a roller-custom.properties file, preferably outside the roller
deployment directory (at the moment I've got it my jdk classes directory but
will look to put it somewhere more sensible). The file should contain at
least the following:
installation.type=manual
database.configurationType=jdbc
database.jdbc.driverClass=oracle.jdbc.driver.OracleDriver
database.jdbc.connectionURL=jdbc:oracle:thin:@yourhost:yourport:yoursid
database.jdbc.username=yourrolleruser
database.jdbc.password=yourpassword
mail.configurationType=properties
mail.hostname=yoursmtphost
uploads.dir=/home/oracle/roller_data/resources
themes.dir=/home/oracle/roller_data/themes
search.index.dir=/home/oracle/roller_data/search-index
log4j.appender.roller.File=/home/oracle/roller_data/roller.log
note: there's still work to be done here, e.g. I'd like use container
managed JNDI connection pooling. The above settings got me running though.
4) create a user account on the Oracle database, e.g. sqlplus / as sysdba
create user yourrolleruser
identified by yourrollerpassword
default tablespace users
temporary tablespace temp
quota unlimited on users;
grant create session to yourrolleruser;
grant create table to yourrolleruser;
5) log in to the database as your roller user and run the
webapp/roller/WEB-INF/classes/dbscripts/oracle/createdb.sql script to create
the schema objects - check there were no errors.
6) log in to the App Server Control console, create a new OC4J container for
roller (optional but sensible)
7) download log4j and put the jar file into the classpath (e.g. cp
log4j-1.2.15.jar $ORACLE_HOME/j2ee/roller/applib)
8) deploy the roller app using the default settings (upload the roller.war
file you created earlier) except untick the Apache.commons.logging 1.0.4
library. You shouldn't get any errors.
Now the roller app should have deployed - at this point it would probably be
sensible to plough through the log file and make sure roller connected to
the database OK and that the bootstrapping worked.
The final steps are:
9) (note: going to http://yourdomain/roller will give an error as per Gabe's
ROL-1653). Go to http://yourdomain/roller/roller-ui/menu.rol which gives the
login screen as well as a link to Register a new user (register.rol). Create
your first user.
10) Now login with that user and create a first blog.
11) Click on the "Main Menu" (or maybe you'll already be there) and then the
"Server Administration" link on the righthand side.
12) Scroll down the page and set "Handle of weblog to serve as frontpage
blog" to the one you just created then click the Save button.
Now when you click Front Page (or just enter the http://yourdomain/roller
URL) you should go to your new blog.
Enjoy!
Simon
PS. As Dave pointed out, there may still be issues with the way the Oracle
JDBC driver handles nulls yet to be resolved when actually using roller.
Note: this isn't a fault of the database (you wouldn't want it to store an
empty field as spaces) but a "feature" of their JDBC driver implementation.
I'll post anything I find as a new thread.
--
View this message in context: http://www.nabble.com/Roller-4.0-RC9-installation-problem-on-OAS-10.1.3.3.0-%28OC4J%29-tp13714430s12275p14975013.html
Sent from the Roller - User mailing list archive at Nabble.com.
RE: Roller 4.0 RC9 installation problem on OAS 10.1.3.3.0 (OC4J)
Posted by Gabe Wong <ga...@ngasi.com>.
>
> On Jan 18, 2008 1:39 AM, Simon Haslam <si...@yahoo.co.uk> wrote:
> > >
> > > Any chance you can use a better supported Servlet Container (e.g.
Tomcat
> > > or Glassfish)?
> > >
> >
> > Actually no - I had already resolved first of those two problems
and just
> > put the error messages in my post in case there were other people
trying to
>
> Glad to hear it. Your next hurdle may be the way that Oracle DB treats
> spaces as nulls.
>
> I think we worked some of those issues out in previous releases, but
> 4.0 may have re-introduced that problem in places -- and I'm pretty
> sure nobody tested on OC4J before we made the final 4.0 release.
>
> I'd like to get those and some other Planet-related fixed in 4.0.1
> release (but my time is pretty limited re: 4.0).
>
> - Dave
In case you encounter further adventures with Oracle, I have open a
related bug with workaround and patch:
http://opensource.atlassian.com/projects/roller/browse/ROL-1653
--
Regards
Gabe Wong
NGASI AppServer Manager
JAVA AUTOMATION and SaaS Enablement
<a href=http://www.ngasi.com>http://www.ngasi.com</a>
NEW! 8.0 - Centrally manage multiple physical servers
Re: Roller 4.0 RC9 installation problem on OAS 10.1.3.3.0 (OC4J)
Posted by Simon Haslam <si...@yahoo.co.uk>.
Progress!!!
Simon Haslam wrote:
>
> I've attempted to override the uploads.dir, themes.dir and
> search.index.dir in roller-custom.properties without success. However when
> I set debug-level logging I don't see any:
> WebloggerConfig:getProperty - Fetching property [themes.dir=...]
> messages before the failure so maybe it's not attempting to read them at
> that point.
>
Please ignore the getRealPath() comments - I think that might be a red
herring. Roller is definitely reading the properties and so, as they are not
set to "${webapp.context}", the null context should be irrelevant.
The problem appeared to be related to the auto setup of the database. I
couldn't work out why, but I think it was possibly failing in
DatabaseInstaller.isCreationRequired(). The workaround was to manually
install the schema objects (using dbscripts/oracle/createdb.sql in sqlplus)
and then set installation.type=manual in roller-custom.properties.
So far, so good. The next problem was related using the JDBC pooled driver
(oracle.jdbc.pool.OracleDataSource) where I got:
"org.apache.openjpa.persistence.PersistenceException: Invalid Oracle URL
specified: OracleDataSource.makeURL"
I've seen this before so will have to dig out my notes on it - in the
meantime I used oracle.jdbc.driver.OracleDriver with
database.jdbc.connectionURL=jdbc:oracle:thin:@<myhost>:<myport>:<mysid> and
that was OK.
So, it went through "Bootstrapping Roller Weblogger business tier" which
looked OK, it found my search-index dir and then my themes dir. After that
lots of "initializeMissingProps - Found uninitialized property site.name ...
setting value to [Roller Site]" type of messages... and so on. This all
looked quite healthy I think.
Anyway, the upshot is it still isn't quite there. When I go to the /roller
URL I get the "Roller has encountered and logged an unexpected exception."
500 error page. The logs show this (all DEBUG messages with timestamp
removed):
CharEncodingFilter:doFilter - Processing CharEncodingFilter
CharEncodingFilter:doFilter - Set request character encoding to UTF-8
BootstrapFilter:doFilter - Entered /roller/
PersistenceSessionFilter:doFilter - Entered /roller/
RequestMappingFilter:doFilter - entering
RequestMappingFilter:doFilter - trying mapper
org.apache.roller.weblogger.ui.rendering.WeblogRequestMapper
WeblogRequestMapper:handleRequest - evaluating [/roller/]
WeblogRequestMapper:handleRequest - potential weblog handle =
WeblogRequestMapper:isWeblog - checking weblog handle
WeblogRequestMapper:handleRequest - SKIPPED
RequestMappingFilter:doFilter - request not mapped
WebloggerRuntimeConfig:getProperty - fetched property
[site.frontpage.weblog.handle=null]
PersistenceSessionFilter:doFilter - Releasing Roller Session
WebloggerConfig:getProperty - Fetching property
[planet.aggregator.enabled=false]
CharEncodingFilter:doFilter - Processing CharEncodingFilter
CharEncodingFilter:doFilter - Set request character encoding to UTF-8
BootstrapFilter:doFilter - Entered /roller/roller-ui/styles/roller.css
PersistenceSessionFilter:doFilter - Entered
/roller/roller-ui/styles/roller.css
RequestMappingFilter:doFilter - entering
RequestMappingFilter:doFilter - trying mapper
org.apache.roller.weblogger.ui.rendering.WeblogRequestMapper
WeblogRequestMapper:handleRequest - evaluating
[/roller/roller-ui/styles/roller.css]
WeblogRequestMapper:handleRequest - potential weblog handle = roller-ui
WeblogRequestMapper:handleRequest - SKIPPED roller-ui
RequestMappingFilter:doFilter - request not mapped
RequestMappingFilter:doFilter - exiting
PersistenceSessionFilter:doFilter - Releasing Roller Session
WebloggerConfig:getProperty - Fetching property
[planet.aggregator.enabled=false]
PersistenceSessionFilter:doFilter - Exiting
/roller/roller-ui/styles/roller.css
BootstrapFilter:doFilter - Exiting /roller/roller-ui/styles/roller.css
...it doesn't feel that far away from working...
Simon
--
View this message in context: http://www.nabble.com/Roller-4.0-RC9-installation-problem-on-OAS-10.1.3.3.0-%28OC4J%29-tp13714430s12275p14949380.html
Sent from the Roller - User mailing list archive at Nabble.com.
Re: Roller 4.0 RC9 installation problem on OAS 10.1.3.3.0 (OC4J)
Posted by Simon Haslam <si...@yahoo.co.uk>.
Progress!!!
Simon Haslam wrote:
>
> I've attempted to override the uploads.dir, themes.dir and
> search.index.dir in roller-custom.properties without success. However when
> I set debug-level logging I don't see any:
> WebloggerConfig:getProperty - Fetching property [themes.dir=...]
> messages before the failure so maybe it's not attempting to read them at
> that point.
>
Please ignore the getRealPath() comments - I think that might be a red
herring. Roller is definitely reading the properties and so, as they are not
set to "${webapp.context}", the null context should be irrelevant.
The problem appeared to be related to the auto setup of the database. I
couldn't work out why, but I think it was possibly failing in
DatabaseInstaller.isCreationRequired(). The workaround was to manually
install the schema objects (using dbscripts/oracle/createdb.sql in sqlplus)
and then set installation.type=manual in roller-custom.properties.
So far, so good. The next problem was related using the JDBC pooled driver
(oracle.jdbc.pool.OracleDataSource) where I got:
"org.apache.openjpa.persistence.PersistenceException: Invalid Oracle URL
specified: OracleDataSource.makeURL"
I've seen this before so will have to dig out my notes on it - in the
meantime I used oracle.jdbc.driver.OracleDriver with
database.jdbc.connectionURL=jdbc:oracle:thin:@<myhost>:<myport>:<mysid> and
that was OK.
So, it went through "Bootstrapping Roller Weblogger business tier" which
looked OK, it found my search-index dir and then my themes dir. After that
lots of "initializeMissingProps - Found uninitialized property site.name ...
setting value to [Roller Site]" type of messages... and so on. This all
looked quite healthy I think.
Anyway, the upshot is it still isn't quite there. When I go to the /roller
URL I get the "Roller has encountered and logged an unexpected exception."
500 error page. The logs show this (all DEBUG messages with timestamp
removed):
CharEncodingFilter:doFilter - Processing CharEncodingFilter
CharEncodingFilter:doFilter - Set request character encoding to UTF-8
BootstrapFilter:doFilter - Entered /roller/
PersistenceSessionFilter:doFilter - Entered /roller/
RequestMappingFilter:doFilter - entering
RequestMappingFilter:doFilter - trying mapper
org.apache.roller.weblogger.ui.rendering.WeblogRequestMapper
WeblogRequestMapper:handleRequest - evaluating [/roller/]
WeblogRequestMapper:handleRequest - potential weblog handle =
WeblogRequestMapper:isWeblog - checking weblog handle
WeblogRequestMapper:handleRequest - SKIPPED
RequestMappingFilter:doFilter - request not mapped
WebloggerRuntimeConfig:getProperty - fetched property
[site.frontpage.weblog.handle=null]
PersistenceSessionFilter:doFilter - Releasing Roller Session
WebloggerConfig:getProperty - Fetching property
[planet.aggregator.enabled=false]
CharEncodingFilter:doFilter - Processing CharEncodingFilter
CharEncodingFilter:doFilter - Set request character encoding to UTF-8
BootstrapFilter:doFilter - Entered /roller/roller-ui/styles/roller.css
PersistenceSessionFilter:doFilter - Entered
/roller/roller-ui/styles/roller.css
RequestMappingFilter:doFilter - entering
RequestMappingFilter:doFilter - trying mapper
org.apache.roller.weblogger.ui.rendering.WeblogRequestMapper
WeblogRequestMapper:handleRequest - evaluating
[/roller/roller-ui/styles/roller.css]
WeblogRequestMapper:handleRequest - potential weblog handle = roller-ui
WeblogRequestMapper:handleRequest - SKIPPED roller-ui
RequestMappingFilter:doFilter - request not mapped
RequestMappingFilter:doFilter - exiting
PersistenceSessionFilter:doFilter - Releasing Roller Session
WebloggerConfig:getProperty - Fetching property
[planet.aggregator.enabled=false]
PersistenceSessionFilter:doFilter - Exiting
/roller/roller-ui/styles/roller.css
BootstrapFilter:doFilter - Exiting /roller/roller-ui/styles/roller.css
...it doesn't feel that far away from working...
Simon
--
View this message in context: http://www.nabble.com/Roller-4.0-RC9-installation-problem-on-OAS-10.1.3.3.0-%28OC4J%29-tp13714430s12275p14949380.html
Sent from the Roller - User mailing list archive at Nabble.com.
Re: Roller 4.0 RC9 installation problem on OAS 10.1.3.3.0 (OC4J)
Posted by Dave <sn...@gmail.com>.
On Jan 18, 2008 1:39 AM, Simon Haslam <si...@yahoo.co.uk> wrote:
> >
> > Any chance you can use a better supported Servlet Container (e.g. Tomcat
> > or Glassfish)?
> >
>
> Actually no - I had already resolved first of those two problems and just
> put the error messages in my post in case there were other people trying to
Glad to hear it. Your next hurdle may be the way that Oracle DB treats
spaces as nulls.
I think we worked some of those issues out in previous releases, but
4.0 may have re-introduced that problem in places -- and I'm pretty
sure nobody tested on OC4J before we made the final 4.0 release.
I'd like to get those and some other Planet-related fixed in 4.0.1
release (but my time is pretty limited re: 4.0).
- Dave
Re: Roller 4.0 RC9 installation problem on OAS 10.1.3.3.0 (OC4J)
Posted by Simon Haslam <si...@yahoo.co.uk>.
Dave Johnson-8 wrote:
>
> Sounds like you are experiencing multiple problems:
>
> Your database connection is not setup correctly
> ...
> Roller's Log4J is conflicting with the one in OC4J
> ...
> And you mentioned the getRealPath() problem.
>
> Any chance you can use a better supported Servlet Container (e.g. Tomcat
> or Glassfish)?
>
> - Dave
>
Actually no - I had already resolved first of those two problems and just
put the error messages in my post in case there were other people trying to
use OC4J. It doesn't seem to matter whether you use the pooled or "straight"
Oracle JDBC driver though I will probably ultimately use a pooled connection
from the container via JNDI anyway.
I'm increasingly convinced it's related to getRealPath(). What I don't
understand is how it can work from a war file on a J2EE compliant server as
the Sun spec says: "This method returns null if the servlet container cannot
translate the virtual path to a real path for any reason (such as when the
content is being made available from a .war archive)."
Does anyone deploy it from a war file, if so, on what app server? If so, is
admin tool exploding the war file as part of the deployment (if such a thing
happens?)?
I think Roller is expecting getRealPath to return the deployed context
directory so that it can then open files in the <context>/resources,
<context>/themes, etc. It looks as though there's a move to have these
outside the context root anyway (I guess you may want to preserve them
across releases).
I've attempted to override the uploads.dir, themes.dir and search.index.dir
in roller-custom.properties without success. However when I set debug-level
logging I don't see any:
WebloggerConfig:getProperty - Fetching property [themes.dir=...]
messages before the failure so maybe it's not attempting to read them at
that point.
I'll keep digging,
Simon
PS. as to using something else, yes I could try, but I'm quite keen to get
open source blogging software running on Oracle (and Roller looks the
best)... I might even write a magazine article on it if I ever get it
working.
--
View this message in context: http://www.nabble.com/Roller-4.0-RC9-installation-problem-on-OAS-10.1.3.3.0-%28OC4J%29-tp13714430s12275p14948040.html
Sent from the Roller - User mailing list archive at Nabble.com.
Re: Roller 4.0 RC9 installation problem on OAS 10.1.3.3.0 (OC4J)
Posted by Dave <sn...@gmail.com>.
On Jan 17, 2008 7:09 AM, Simon Haslam <si...@yahoo.co.uk> wrote:
> Simon Haslam wrote:
> >
> > I forgot to mention that I deployed roller by creating a WAR file ...
> > Perhaps my problem is somewhere around the servletContext.getRealPath("/")
> > call in RollerContext.contextInitialized?...
> >
>
> OK I *think* servletContext.getRealPath("/") is returning null - this is
> expected behaviour according to Sun's Javadoc as the application has been
> deployed as a war file. Even if it were returning a useful path presumably
> we wouldn't be able to open it (e.g. for a theme) as it is within the
> archive.
>
> It looks very similar to the WLS question Stefan Edwards raised on the
> roller-user list on 14 Dec 2007 and I see what looks like the same topic
> raised here: http://opensource.atlassian.com/projects/roller/browse/ROL-95
> quite a while back (I couldn't find the referenced posting from the dev mail
> archive for 2004).
>
> What confuses me is that the Roller 4.0 Install Doc (section 4.2 and later)
> suggests that you can deploy it as a war file. Is this issue something
> peculiar to OC4J (and perhaps WLS)? Is anyone else out there deploying
> Roller by a war file (to any app server)?
Sounds like you are experiencing multiple problems:
Your database connection is not setup correctly:
--- ROOT CAUSE ---
java.sql.SQLException: Io exception: Invalid connection string format, a
valid format is: "host:port:sid"
Roller's Log4J is conflicting with the one in OC4J
Unpublished Bug 5871305 : APACHE.COMMONS.LOGGING LIBRARY HAS DEPENDENCY ON
LOG4J CLASSES In the OC4J class loading framework
And you mentioned the getRealPath() problem.
Any chance you can use a better supported Servlet Container (e.g.
Tomcat or Glassfish)?
- Dave
Re: Roller 4.0 RC9 installation problem on OAS 10.1.3.3.0 (OC4J)
Posted by Simon Haslam <si...@yahoo.co.uk>.
Simon Haslam wrote:
>
> I forgot to mention that I deployed roller by creating a WAR file ...
> Perhaps my problem is somewhere around the servletContext.getRealPath("/")
> call in RollerContext.contextInitialized?...
>
OK I *think* servletContext.getRealPath("/") is returning null - this is
expected behaviour according to Sun's Javadoc as the application has been
deployed as a war file. Even if it were returning a useful path presumably
we wouldn't be able to open it (e.g. for a theme) as it is within the
archive.
It looks very similar to the WLS question Stefan Edwards raised on the
roller-user list on 14 Dec 2007 and I see what looks like the same topic
raised here: http://opensource.atlassian.com/projects/roller/browse/ROL-95
quite a while back (I couldn't find the referenced posting from the dev mail
archive for 2004).
What confuses me is that the Roller 4.0 Install Doc (section 4.2 and later)
suggests that you can deploy it as a war file. Is this issue something
peculiar to OC4J (and perhaps WLS)? Is anyone else out there deploying
Roller by a war file (to any app server)?
Anyway, sorry for the excessive posting.
--
View this message in context: http://www.nabble.com/Roller-4.0-RC9-installation-problem-on-OAS-10.1.3.3.0-%28OC4J%29-tp13714430s12275p14921166.html
Sent from the Roller - User mailing list archive at Nabble.com.
Re: Roller 4.0 RC9 installation problem on OAS 10.1.3.3.0 (OC4J)
Posted by Simon Haslam <si...@yahoo.co.uk>.
I forgot to mention that I deployed roller by creating a WAR file and then
uploading it through ASC (the OAS web UI). This might be different from
others who deploy it by pointing at the roller directory.
Perhaps my problem is somewhere around the servletContext.getRealPath("/")
call in RollerContext.contextInitialized? I found someone else trying to
deploy a war file to Weblogic and they were finding that this was returning
null (in fact Dave might have said something to that effect too).
By the way: I forgot to mention for other OAS users that you need to put
log4j-1.2.15.jar into the classpath (e.g. j2ee/roller/applib) and untick the
Apache.commons.logging 1.0.4 library when deploying (see Metalink note
460448.1 "java.lang.NoClassDefFoundError: org/apache/log4j/Category after
upgrading from 10.1.3.1 to 10.1.3.3"
Unpublished Bug 5871305 : APACHE.COMMONS.LOGGING LIBRARY HAS DEPENDENCY ON
LOG4J CLASSES In the OC4J class loading framework, by default, system level
shared library takes precedence to that of application defined shared
library. commons-logging.jar is defined as a system level shared library in
OC4J. This shared library has a dependency on log4j.x.jar file which has not
been properly declared. This bug is scheduled to be fixed in 10.1.3.4).
If I ever get this working I'll put together some instructions...
--
View this message in context: http://www.nabble.com/Roller-4.0-RC9-installation-problem-on-OAS-10.1.3.3.0-%28OC4J%29-tp13714430s12275p14916810.html
Sent from the Roller - User mailing list archive at Nabble.com.
Re: Roller 4.0 RC9 installation problem on OAS 10.1.3.3.0 (OC4J)
Posted by Simon Haslam <si...@yahoo.co.uk>.
Dave Johnson-8 wrote:
>
> Are there error messages in any other log files? OC4J should have it's
> own log file(s) -- do you see any messages there? Before Roller inits
> it's logging system, it logs to a file called roller-startup.log...
>
Firstly: Dave, Gaetano & John thank you for your responses - I do humbly
apologise for not replying sooner as I was only checking
mail-archives.apache.org and didn't notice them on there.
Anyway, I'm having another look at this issue now (I've downloaded 4.0 too).
This is what I've found so far:
* I have a roller-startup.log but this is empty. Possibly it was written to
before I added a line for log4j.appender.roller.File=/temp/roller.log in
roller-custom.properties though it seems to be recreated if I delete it and
restart the container.
* I think the database connection is happening OK - e.g. if you use an
invalid password or the wrong connection syntax you get a different error.
e.g.
DatabaseProvider:errorMessage - ERROR: unable to obtain database connection.
Likely problem: bad connection parameters or database unavailable.
--- ROOT CAUSE ---
java.sql.SQLException: Io exception: Invalid connection string format, a
valid format is: "host:port:sid"
* I have tried both my original pooled connection and John's "straight"
connection but still get the same "Weblogger startup INCOMPLETE, user
interaction required" error.
Further thoughts:
* I wonder if it's something to do with paths or environment variables -
that sort of thing could be different between Tomcat and OC4J. E.g.
log4j.appender.roller.File=${catalina.base} in roller.properties has to be
overridden.
* I had a bit of a dig in the source: RollerContext.ContextInitialized =>
WebLoggerStartup.prepare() => DatabaseInstaller.CreateDatabase... which has
an info message "Creating Roller Weblogger database tables" which I'm not
seeing so it's not getting that far. I'm also not seeing "Roller Weblogger
startup failed during app preparation" either.
Simon
--
View this message in context: http://www.nabble.com/Roller-4.0-RC9-installation-problem-on-OAS-10.1.3.3.0-%28OC4J%29-tp13714430s12275p14907554.html
Sent from the Roller - User mailing list archive at Nabble.com.
Re: Roller 4.0 RC9 installation problem on OAS 10.1.3.3.0 (OC4J)
Posted by Dave <sn...@gmail.com>.
Are there error messages in any other log files? OC4J should have it's
own log file(s) -- do you see any messages there? Before Roller inits
it's logging system, it logs to a file called roller-startup.log,
which is usually created in the app server's startup directory. There
may be some clues there as well.
- Dave
On Nov 12, 2007 4:00 PM, Simon Haslam <si...@yahoo.co.uk> wrote:
> I'm new to Roller and am trying to install roller 4.0 RC9 on Oracle Application Server 10.1.3.3.0 (i.e. OC4J) and Oracle database 10.2.0.3 on OEL/RHEL R5 Linux.
>
> I'm using a straight JDBC connection for now - my roller-custom.properties file is:
> installation.type=auto
> database.configurationType=jdbc
> database.jdbc.driverClass=oracle.jdbc.pool.OracleDataSource
> database.jdbc.connectionURL=jdbc:oracle:thin:@//localhost:1521/myservicename
> database.jdbc.username=roller
> database.jdbc.password=***
>
> In roller.log I'm getting:
> INFO 2007-11-12 20:06:45,654 DatabaseProvider:successMessage - SUCCESS: Got parameters. Using configuration type JDBC_PROPERTIES
> INFO 2007-11-12 20:06:45,663 DatabaseProvider:successMessage - -- Using JDBC driver class: oracle.jdbc.pool.OracleDataSource
> INFO 2007-11-12 20:06:45,749 DatabaseProvider:successMessage - -- Using JDBC connection URL: jdbc:oracle:thin:@//localhost:1521/***
> INFO 2007-11-12 20:06:45,751 DatabaseProvider:successMessage - -- Using JDBC username: roller
> INFO 2007-11-12 20:06:45,766 DatabaseProvider:successMessage - -- Using JDBC password: [hidden]
> INFO 2007-11-12 20:06:45,781 DatabaseProvider:successMessage - SUCCESS: loaded JDBC driver class [oracle.jdbc.pool.OracleDataSource]
> INFO 2007-11-12 20:06:48,073 RollerContext:contextInitialized -
> --------------------------------------------------------------
> Roller Weblogger startup INCOMPLETE, user interaction required
> --------------------------------------------------------------
>
> I can see that the tables haven't been created by the auto install which presumably is a symptom of another problem. When I ran the oracle/createdb.sql script manually as the roller user from sqlplus that worked fine (I dropped the tables again afterwards). Whenever I do http://myserver/roller/ I get a roller message box "Roller has encountered and logged an unexpected exception." (i.e. from the container).
>
> I saw the change to add the "Roller Weblogger startup INCOMPLETE, user interaction required" message, just not sure where I go from here...