These resources (xsd or dtd) should all be referenced locally. If you
determine there's a remote reference, it should get fixed.
On 6/27/19 1:28 PM, Williams, David A. wrote:
Dave,
Thanks for the help.
I turned this over to someone else here who will have more
details I expect on Monday. This is my secondhand understanding:
It appears that the issue is some xsd or dtd files set to be
checked remotely. Or production servers are generally not allowed outbound
connections. As we’re migrating from version 4, the “normal” pages, which all
use custom templates, didn’t have that dependency. And our development systems
are not locked down as tightly and can make outbound connections.
Again, thank you for your response,
-David
From: Dave <[email protected]>
Sent: Wednesday, June 26, 2019 7:32 PM
To: Roller User <[email protected]>
Cc: Williams, David A. <[email protected]>
Subject: Re: Roller 5.2.2 login hanging with
If there is a 500 error maybe there is a stack trace in the logs? Take a look
at roller.log and catalina.out. If the system is able to connect to the
database, you should see evidence of that in roller.log.
What versions of Java, Tomcat and MySQL are you using?
Dave
On Tue, Jun 18, 2019 at 3:43 PM Williams, David A.
<[email protected]<mailto:[email protected]>> wrote:
Hi,
We have several environments with instances of Roller running. Our
production instance is still 4.1 but we're preparing 5.2.2 to replace it.
The homepage loads fine (so it seems the DB connection is fine) but
login.rol times out, eventually with a 500 error.
Roller-custom.properties says:
installation.type=manual
mediafiles.storage.dir=/usr/share/tomcat/rollerdata/mediafiles
search.index.dir=/usr/share/tomcat/rollerdata/searchindex
database.configurationType=jdbc
database.jdbc.driverClass=com.mysql.jdbc.Driver
database.jdbc.connectionURL=jdbc:mysql://<our DB
host>:3306/rollerdb522?useUnicode=true&useFastDateParsing=false&characterEncoding=UTF-8
database.jdbc.username=<our user name>
database.jdbc.password=<our password>
database.jdbc.removeAbandoned="true"
database.jdbc.removeAbandonedTimeout="60"
database.jdbc.logAbandoned="true"
database.jdbc.testOnBorrow="true"
database.jdbc.validationQuery="SELECT 1"
mail.configurationType=properties
mail.hostName=localhost
comment.throttle.enabled=true
We're using the roller db for authentication rather than OAUTH or
LDAP. The only intentional differnce between the environment where this works
and where login is timing out is in the working environment, MySQL is running
locally; in the timing out environment, MySQL is on a separate host (as noted,
the db connection seems fine as the main page loads). One rabbit hole I tried
was TCPDump between tomcat server and db host: in both working and non-working
cases, I see DB query when the main page is loaded and no DB query when
login.rol is called from the command line.
I welcome any troubleshooting pointers,
-David
--------------------------------------------
David Williams
Chief, Website Management Branch
Information Management Services
U.S. Patent & Trademark Office
U.S. Department of Commerce
Madison West, 4D35
Alexandria, VA 22314
1-571-272-3877
[email protected]<mailto:[email protected]>
