THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
"Supported" might be the wrong word because we don't really offer support, but we can tell you what platforms are known to work.
Roller 4 worked on Tomcat 5 , Tomcat 6, Sun Web Server, Glassfish 2, MySQL, Derby and PostgreSQL. Some users we able to run on Oracle and DB2 with tweaks to the database creation scripts.Roller 5 will work on Tomcat 6 and 7 (it has not been tested on Roller 8 but should work there also), Glassfish 3.0 and 3.1, JBoss AS 6 and WebSphere 8. It should also work with MySQL, Derby, Oracle and DB2 databases.
Roller 5.1 requires minimum JDK 7 and Tomcat 7 or 8 (as it uses Servlet 3.0), it has also been shown to run successfully with recent versions of GlassFish and JBoss. We've tested with MySQL, Derby and PostSQL databases; scripts are also available for Oracle, DB2, and Microsoft SQL Server databases but we have not tested with them.
Tomcat is probably the safest platform for Roller because that's what most people use.
...
The very first user you create will be an admin user. That initial user can then grant and revoke admin rights from any other user.
| Anchor |
|---|
...
...
If Roller fails to start and you see a message like the one below in your log files (such as the Tomcat catalina.out log file), then you may not have MySQL set up for networking. See this page for more information http://dev.mysql.com/doc/mysql/en/Access_denied.html.
| No Format |
|---|
MESSAGE: Data source rejected establishment of connection,
message from server: "Host 'localhost.example.com'
is not allowed to connect to this MySQL server"
MESSAGE: Attempted reconnect 3 times. Giving up.
MESSAGE: java.sql.SQLException
|
|
You probably missed the instructions in the Roller Install Guide to set up UTF-8 as the default character encoding. Check out these instructions.
...
It's a long story. Read it here.
...
, check that guide for precise database creation scripts to use. The MySQL Reference Manual has more information.
| Anchor | ||||
|---|---|---|---|---|
|
This appears to be due to a MySQL and Connector/J bug that occurs if you use the MySQL 4.1.X server with Connector/J 3.1.X drivers. We recommend that you use the Connector/J 3.0.16 (or later 3.0.X series) drivers with MySQL 4.1.X to avoid this. You can download them from the MySQL site. Drop the jar in your CATALINA_HOME/common/lib and remove any 3.1.X drivers that you have there.
An alternate workaround that will allow you to keep the Connector/J 3.1.X drivers is to disable use of server-side prepared statements by setting the additional property useServerPrepStmts=false in both of the MySQL JDBC URLs in the context configuration.
Roller user Lee Gwun Wai has reported on the roller-user mailing list that this can also occur in the typical ISP-hosted situation where one's database is using UTF-8 but the overall server character set is something other than UTF-8. He suggests dropping the useUnicode=true from all JDBC URLs. We have still only seen this reported with the Connector/J 3.1.X drivers.
...
This warning appears if the ping queue processor task runs before there have been any requests made to the server and you have not set an explicit site URL in the configuration.
...
You don't have to do anything about it; things should be fine as soon as your server starts to see any activity. However, you can avoid the message by setting your absolute site url explicitly in "Absolute URL to Site" field in the configuration under "Admin | Configuration".
...
This has been reported on some Linux installations. Koji Lin suggested the gist of the following solution on the roller-user mailing list. The is caused by the java.security.SecureRandom class. On Linux environments it is often set up to use /dev/random as a source of entropy. Reading from the /dev/random device will block when there is not enough entropy available to satisfy a read request. Most linux systems now have /dev/urandom, which will not block and provides adequate security for most sites.
You can set your JRE to use /dev/urandom for all applications by editing the JAVA_HOME/jre/lib/security/java.security file. You can use it for Tomcat only by adding the following Java system property definition on the command line in the Tomcat startup script that invokes Java
| No Format |
|---|
-Djava.security.egd=file:/dev/urandom
|
or setting this in the JAVA_OPTS environment variable before invoking the Tomcat startup script. You may also want to refer to the Sun bug on this issue
...
If you're using PostgreSQL, and you see a stack trace starting like the one below, then this is due to a (well-known) bug in older PostgreSQL JDBC Drivers.
| No Format |
|---|
java.lang.StringIndexOutOfBoundsException: String index out of range: 23
java.lang.String.charAt(String.java:444)
org.postgresql.jdbc2.ResultSet.toTimestamp(ResultSet.java:1653)
org.postgresql.jdbc2.ResultSet.getTimestamp(ResultSet.java:398)
org.postgresql.jdbc2.ResultSet.getTimestamp(ResultSet.java:617)
...
|
You need to upgrade to the latest compatible JDBC drivers.
...
It is possible to setup roller to use LDAP Authentication for users created in roller DB. Please check LDAP and SSP FAQ page for more information.
...
Check these things:
...