[Dspace-tech] tomcat bound to port 80

[Yongming Wang]

Hi,

I'm new to DSpace. My situation is: DSpace 5.2 on RH Enterprise Linux 7, using jspui.

I'm trying to change the default tomcat port 8080 to 80. I searched the Internet and dspace mailing-list and decided to use the following method:

Step one: modify [tomcat]/conf/server.xml, change connector port from 8080 to 80
Step two: install the AUTOBIND package. But instead my school IT department installed something called "jsvc" which they told me is newer and better than AUTHBIND.

Now I got some internal error message when trying to access the application homepage at port 80. I'll paste it below.

Does anyone have any suggestions and insight to this issue?

Or in general, how do you change the 8080 port to 80 so user won't need to type 8080 to access the application? What is the simplest way?



Thanks very much in advance!



Yongming

---------------------------------
Yongming Wang
Systems Librarian
The College of New Jersey Library
phone: 609-771-3337
email: wan...@tcnj.edu
---------------------------------

exception stack:

-- URL Was: http://xxxxxx.tcnj.edu/jspui/internal-error
-- Method: GET
-- Parameters were:


Exception:
org.apache.jasper.JasperException: javax.servlet.ServletException: org.dspace.plugin.PluginException: org.dspace.app.webui.components.RecentSubmissionsException: org.dspace.browse.BrowseException: org.dspace.discovery.SearchServiceException: Server refused connection at: http://localhost:8080/solr/search
at org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:549)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:455)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:390)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:334)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServletFilter.java:78)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1040)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:745)
Caused by: javax.servlet.ServletException: org.dspace.plugin.PluginException: org.dspace.app.webui.components.RecentSubmissionsException: org.dspace.browse.BrowseException: org.dspace.discovery.SearchServiceException: Server refused connection at: http://localhost:8080/solr/search
at org.apache.jsp.index_jsp._jspService(index_jsp.java:128)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432)
... 26 more
Caused by: org.dspace.plugin.PluginException: org.dspace.app.webui.components.RecentSubmissionsException: org.dspace.browse.BrowseException: org.dspace.discovery.SearchServiceException: Server refused connection at: http://localhost:8080/solr/search
at org.dspace.app.webui.components.RecentSiteSubmissions.process(RecentSiteSubmissions.java:53)
at org.apache.jsp.index_jsp._jspService(index_jsp.java:121)
... 29 more
Caused by: org.dspace.app.webui.components.RecentSubmissionsException: org.dspace.browse.BrowseException: org.dspace.discovery.SearchServiceException: Server refused connection at: http://localhost:8080/solr/search
at org.dspace.app.webui.components.RecentSubmissionsManager.getRecentSubmissions(RecentSubmissionsManager.java:105)
at org.dspace.app.webui.components.RecentSiteSubmissions.process(RecentSiteSubmissions.java:47)
... 30 more
Caused by: org.dspace.browse.BrowseException: org.dspace.discovery.SearchServiceException: Server refused connection at: http://localhost:8080/solr/search
at org.dspace.browse.SolrBrowseDAO.getSolrResponse(SolrBrowseDAO.java:195)
at org.dspace.browse.SolrBrowseDAO.doQuery(SolrBrowseDAO.java:289)
at org.dspace.browse.BrowseEngine.browseMini(BrowseEngine.java:164)
at org.dspace.app.webui.components.RecentSubmissionsManager.getRecentSubmissions(RecentSubmissionsManager.java:89)
... 31 more
Caused by: org.dspace.discovery.SearchServiceException: Server refused connection at: http://localhost:8080/solr/search
at org.dspace.discovery.SolrServiceImpl.search(SolrServiceImpl.java:1608)
at org.dspace.browse.SolrBrowseDAO.getSolrResponse(SolrBrowseDAO.java:190)
... 34 more
Caused by: org.apache.solr.client.solrj.SolrServerException: Server refused connection at: http://localhost:8080/solr/search
at org.apache.solr.client.solrj.impl.HttpSolrServer.executeMethod(HttpSolrServer.java:559)
at org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:210)
at org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:206)
at org.apache.solr.client.solrj.request.QueryRequest.process(QueryRequest.java:91)
at org.apache.solr.client.solrj.SolrServer.query(SolrServer.java:301)
at org.dspace.discovery.SolrServiceImpl.search(SolrServiceImpl.java:1603)
... 35 more
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:579)
at org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:117)
at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177)
at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:304)
at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)
at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)
at org.apache.solr.client.solrj.impl.HttpSolrServer.executeMethod(HttpSolrServer.java:448)
... 40 more

[Mark H. Wood]

On Mon, Aug 03, 2015 at 11:09:49AM -0400, Yongming Wang wrote:
> I'm new to DSpace. My situation is: DSpace 5.2 on RH Enterprise Linux 7, using jspui.
>
> I'm trying to change the default tomcat port 8080 to 80. I searched the Internet and dspace mailing-list and decided to use the following method:
>
> Step one: modify [tomcat]/conf/server.xml, change connector port from 8080 to 80
> Step two: install the AUTOBIND package. But instead my school IT department installed something called "jsvc" which they told me is newer and better than AUTHBIND.

jsvc is what I would choose. It is used to start Java-based processes
in a similar fashion to traditional Unix daemons: begin as root, open
access to privileged resources (such as low-numbered ports), then
setuid() to a nonprivileged user and begin service. Tomcat is one
Java application which is designed to be used this way.

> Now I got some internal error message when trying to access the application homepage at port 80. I'll paste it below.
>
> Does anyone have any suggestions and insight to this issue?

See below. Your DSpace configuration still contains some references
to port 8080. I would check:

o search.server in config/modules/discovery.cfg

o server in config/modules/solr-statistics.cfg

o solr.url in config/modules/oai.cfg

> Or in general, how do you change the 8080 port to 80 so user won't need to type 8080 to access the application? What is the simplest way?

Probably the way you are doing it. It is made less simple because
there are three URLs in build.properties which, as delivered, select
port 8080 and these are copied into various other configuration files
as part of the installation process. If you start with dspace.url,
dspace.baseUrl, and solr.server all set to port 80 and then build
DSpace ("mvn clean install") then you should wind up with an
installation package that will use port 80 throughout. If you built
your DSpace for port 8080 and then changed the built configuration,
you have to find all of the places where these build.properties values
are used and change them accordingly.

> Thanks very much in advance!
>
>
>
> Yongming
>
> ---------------------------------
> Yongming Wang
> Systems Librarian
> The College of New Jersey Library
> phone: 609-771-3337
> email: wan...@tcnj.edu
> ---------------------------------
>
> exception stack:
>
> -- URL Was: http://xxxxxx.tcnj.edu/jspui/internal-error
> -- Method: GET
> -- Parameters were:
>
>
> Exception:
> org.apache.jasper.JasperException: javax.servlet.ServletException: org.dspace.plugin.PluginException: org.dspace.app.webui.components.RecentSubmissionsException: org.dspace.browse.BrowseException: org.dspace.discovery.SearchServiceException: Server refused connection at: http://localhost:8080/solr/search

^^^^
DSpace made an internal reference to port 8080 here.

> ------------------------------------------------------------------------------
> _______________________________________________
> DSpace-tech mailing list
> DSpac...@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
> List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>

--
Mark H. Wood
Lead Technology Analyst

University Library
Indiana University - Purdue University Indianapolis
755 W. Michigan Street
Indianapolis, IN 46202
317-274-0749
www.ulib.iupui.edu

[Graham Triggs]

Hi,

The error that you have received is because the main DSpace application can't communicate with the secondary Solr application - which by default it expects to be in the same Tomcat, and on the default port of 8080.

Note that the circumstances of this error point to a very good reason why you should NOT relocate the Tomcat port.

By putting the main Tomcat connector on port 80, you are - by default - exposing(*) all of the applications hosted in that Tomcat to the internet. This includes the "internal" support applications like Solr, which may be a security risk.

(* this may very depending on other firewalls that you may be running).

If you instead use something like Apache HTTPd with mod_proxy / mod_jk, you can be more explicit about what applications you mount through HTTPd, limiting what is exposed to potential attacks. Also, it gives you a place to more easily add other security modules / features.

Plus, if it is ever necessary, it gives you a means to disable general access to the underlying application, whilst you still have direct access to the Tomcat application.

Regards,

Graham

[Yongming Wang]

Hi Mark,

You are right. I searched through the system and changed all 8080 to 80. It's working now!

Thank you so much for your help!

Yongming

---------------------------------
Yongming Wang
Systems Librarian
The College of New Jersey Library
phone: 609-771-3337
email: wan...@tcnj.edu
---------------------------------

[Yongming Wang]

Hi Graham,

Thanks very much for your advice, especially on the security front. I don't have any experience with the Apache HTTPd with mod_proxy / mod_jk. I don't want to bother the college IT department again. So I'll stay with the current solution they provide, the jsvc.

Thanks again.

Yongming

---------------------------------
Yongming Wang
Systems Librarian
The College of New Jersey Library
phone: 609-771-3337
email: wan...@tcnj.edu
---------------------------------

----- Original Message -----
From: "Graham Triggs" <graham...@gmail.com>
To: "Yongming Wang" <wan...@tcnj.edu>
Cc: dspac...@lists.sourceforge.net
Sent: Monday, August 3, 2015 4:53:35 PM
Subject: Re: [Dspace-tech] tomcat bound to port 80