On 3/19/2016 5:39 PM, Daniel Savard wrote:
André,
I was just trying to understand why this was a so hard requirement to
run on port 80. The provided answers didn't help to understand why
this was hardly needed. I was just questioning and sometimes, we, yes
I include myself, look at a problem wit
André,
I was just trying to understand why this was a so hard requirement to
run on port 80. The provided answers didn't help to understand why
this was hardly needed. I was just questioning and sometimes, we, yes
I include myself, look at a problem with a narrow view how to solve it
and it may be
On 19.03.2016 22:06, Lyallex wrote:
...
I have it working now, I'd be glad to advise if required
Yes, please describe your solution. With the increasing footprint of systemd, I am sure
that this information will be helpful to other tomcat users, when they search the list
archives.
It cou
On 19 March 2016 at 21:02, André Warnier (tomcat) wrote:
> Daniel,
>
> first of all, stop top-posting (this applies to both of you). This is not
> the style of posting desired on this list.
> See http://tomcat.apache.org/lists.html#tomcat-users, #6.
>
> Secondly,
> the original poster (lyallex) wa
Daniel,
first of all, stop top-posting (this applies to both of you). This is not the style of
posting desired on this list.
See http://tomcat.apache.org/lists.html#tomcat-users, #6.
Secondly,
the original poster (lyallex) wants to run Tomcat under Linux, without a front-end, as a
webserver,
I still don't see how the number of concurrent sessions is related to
the port number.
The default ports for Tomcat are 8080 and 8443.
For huge websites, usually you have a load balancer as a front-end
anyway. You then get the capability to distribute the workload on more
than one instance of Tom
On 19 March 2016 at 19:19, Daniel Savard wrote:
> I see what you were trying to achieve, however I don't see much
> interest in that.
Really, I've been running a successful commercial web site for the
last 4 years using Tomcat as a standalone web server
and servlet container using exactly this
I see what you were trying to achieve, however I don't see much
interest in that.
1) Obviously, if you were expecting systemd to solve that problem, you
were wrong and it is a sane behavior of systemd to not allow that
neither.
2) Your solution to your problem is lying on jsvc alone.
3) I believe
It's the simplest way to find out which port you have Tomcat listening on
*NIX based systems don't allow non root uses bind to ports < 1024
jsvc
http://commons.apache.org/proper/commons-daemon/jsvc.html
solves this problem, nobody seems to have grasped that this is what I
was asking about.
I kno
Why? What is the point? The server.xml has nothing to do with
integration with systemd.
-
Daniel Savard
2016-03-19 1:40 GMT-04:00 Lyallex :
> Would you mind posting your server.xml, here is the relevant bit from mine.
>
>
>
> connectionTimeout="2"
>
Would you mind posting your server.xml, here is the relevant bit from mine.
On 18 March 2016 at 23:35, Daniel Savard wrote:
> I believe all distros have over engineered the scripts to start
> Tomcat. Forget all the scripts
Or remove the Type=Forking and just execute catalina.sh run, as I had
suggested days ago. Then you can drop the ExecStop too.
On Fri, Mar 18, 2016 at 7:35 PM, Daniel Savard wrote:
> I believe all distros have over engineered the scripts to start
> Tomcat. Forget all the scripts from your distro,
I believe all distros have over engineered the scripts to start
Tomcat. Forget all the scripts from your distro, learn the
signification of the environment variables from the catalina.sh script
shipped with the default Tomcat version. Define your variables in a
file, this file is not a script, so y
13 matches
Mail list logo
