You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@roller.apache.org by "Williams, David A." <da...@USPTO.GOV> on 2019/06/18 19:43:07 UTC
Roller 5.2.2 login hanging with
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
david.williams@uspto.gov
RE: Roller 5.2.2 login hanging with
Posted by "Gilvary, Joseph" <Jo...@USPTO.GOV>.
Good morning, and Happy Monday (at least it's a Monday morning on the east coast of the U.S. of A right now),
I work on David's staff and did some of the digging into this. We believe we found the issue with our installation, though maybe not the root cause.
We had the tiles.xml in WEB-INF referencing the tiles-config_2_0.dtd, but our upgraded blog was using the 3.07 version of several tiles JAR files (core, api, servlet, freemarker, etc). When I fetched a copy of the 3.0 dtd to the WEB-INF/lib directory & updated the tiles.xml to point to it locally, it seemed to resolve this issue after restarting Tomcat.
I'm not sure how we got the version mismatch, but that's a story and a task for another time.
Thanks for all the pointers!
Joe
-----Original Message-----
From: Anil Gangolli <an...@busybuddha.org>
Sent: Friday, June 28, 2019 10:58 AM
To: user@roller.apache.org
Subject: Re: Roller 5.2.2 login hanging with
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 <sn...@gmail.com>
> Sent: Wednesday, June 26, 2019 7:32 PM
> To: Roller User <us...@roller.apache.org>
> Cc: Williams, David A. <da...@USPTO.GOV>
> 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. <da...@uspto.gov>> 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
> david.williams@uspto.gov<ma...@uspto.gov>
>
Re: Roller 5.2.2 login hanging with
Posted by Anil Gangolli <an...@busybuddha.org>.
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 <sn...@gmail.com>
> Sent: Wednesday, June 26, 2019 7:32 PM
> To: Roller User <us...@roller.apache.org>
> Cc: Williams, David A. <da...@USPTO.GOV>
> 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. <da...@uspto.gov>> 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
> david.williams@uspto.gov<ma...@uspto.gov>
>
RE: Roller 5.2.2 login hanging with
Posted by "Williams, David A." <da...@USPTO.GOV>.
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 <sn...@gmail.com>
Sent: Wednesday, June 26, 2019 7:32 PM
To: Roller User <us...@roller.apache.org>
Cc: Williams, David A. <da...@USPTO.GOV>
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. <da...@uspto.gov>> 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
david.williams@uspto.gov<ma...@uspto.gov>
Re: Roller 5.2.2 login hanging with
Posted by Dave <sn...@gmail.com>.
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. <da...@uspto.gov>
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
> david.williams@uspto.gov
>
>
>