Hello!
I tried 8.0.17 (previously I had 8.0.15) and we still have the same
problem with same possible workaround.
I'll go through your examples, try them and compare what's the difference.
On Tue, Jan 20, 2015 at 11:52 AM, Mark Thomas ma...@apache.org wrote:
On 20/01/2015 08:10, Leonid
On 01/21/2015 11:26 AM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Matt,
On 1/21/15 11:13 AM, Matthew Mah wrote:
On 01/20/2015 10:08 AM, Christopher Schultz wrote: Matthew,
On 1/18/15 1:54 PM, Matthew Mah wrote:
I have setup a Tomcat server using spring-boot
Is it advisable to have the following JVM option set in Tomcat 7 (with
Java 7)?
-XX:+DisableExplicitGC
Or will this prevent Tomcat itself from calling System.gc() when it
needs to?
Mike
-
To unsubscribe, e-mail:
On 01/20/2015 10:08 AM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Matthew,
On 1/18/15 1:54 PM, Matthew Mah wrote:
I have setup a Tomcat server using spring-boot with SSL/TLS for
secure websockets.
Tomcat version? JVM version? Any relevant configuration?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Leo,
On 1/21/15 10:51 AM, Leo Donahue wrote:
On Wed, Jan 21, 2015 at 9:03 AM, Christopher Schultz
ch...@christopherschultz.net wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256
Leo,
On 1/20/15 10:29 PM, Leo Donahue wrote:
On Tue,
On Wed, Jan 21, 2015 at 9:03 AM, Christopher Schultz
ch...@christopherschultz.net wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Leo,
On 1/20/15 10:29 PM, Leo Donahue wrote:
On Tue, Jan 20, 2015 at 9:24 PM, Leo Donahue donahu...@gmail.com
wrote:
On Tue, Jan 20, 2015 at 5:09
You mean here maxThreads=150?
But is no respective log message for this. And, I didn't find much request
to the service. Currently there are no changed settings(firewall/network,
etc.).
On Wed, Jan 21, 2015 at 11:28 PM, Jeffrey Janner
jeffrey.jan...@polydyne.com wrote:
-Original
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Matt,
On 1/21/15 11:13 AM, Matthew Mah wrote:
On 01/20/2015 10:08 AM, Christopher Schultz wrote: Matthew,
On 1/18/15 1:54 PM, Matthew Mah wrote:
I have setup a Tomcat server using spring-boot with SSL/TLS
for secure websockets.
Tomcat
-Original Message-
From: Jason Y [mailto:day...@gmail.com]
Sent: Wednesday, January 21, 2015 12:44 AM
To: Tomcat Users List
Subject: Re: SSL issue in tomcat
Got another issue...Tomcat is working fine after restart but it cannot
last
long.
Now I cannot access https pages with any
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
André,
On 1/21/15 3:13 PM, André Warnier wrote:
Mike Seda wrote:
Is it advisable to have the following JVM option set in Tomcat 7
(with Java 7)? -XX:+DisableExplicitGC
Or will this prevent Tomcat itself from calling System.gc() when
it needs
On 21/01/2015 19:59, Mike Seda wrote:
Is it advisable to have the following JVM option set in Tomcat 7 (with
Java 7)?
-XX:+DisableExplicitGC
That should be fine. Apps really should not be calling that.
Or will this prevent Tomcat itself from calling System.gc() when it
needs to?
Tomcat
Sorry no, it happens on both connectors, 8080(HTTP) and 8443(HTTPS).
The 8080 connector is the default out of the installation. I try to stick to
defaults for trouble shooting purposes.
Shaun Morton
Legal Files Software
217-726-6000 Ext. 341
sh...@legalfiles.com
www.legalfiles.com
Mike Seda wrote:
Is it advisable to have the following JVM option set in Tomcat 7 (with
Java 7)?
-XX:+DisableExplicitGC
Or will this prevent Tomcat itself from calling System.gc() when it
needs to?
Tomcat is probably not doing that anyway (I'll let someone else answer that part), but
there
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Matt,
On 1/21/15 2:16 PM, Matthew Mah wrote:
On 01/21/2015 11:26 AM, Christopher Schultz wrote: Matt,
On 1/21/15 11:13 AM, Matthew Mah wrote:
On 01/20/2015 10:08 AM, Christopher Schultz wrote: Matthew,
On 1/18/15 1:54 PM, Matthew Mah wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Daniel,
On 1/21/15 3:16 PM, Daniel Mikusa wrote:
On Wed, Jan 21, 2015 at 2:59 PM, Mike Seda
mike.s...@lillegroup.com wrote:
Is it advisable to have the following JVM option set in Tomcat 7
(with Java 7)? -XX:+DisableExplicitGC
It may or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Shaun,
On 1/21/15 4:23 PM, Shaun Morton wrote:
After upgrading from Tomcat 8.0.15 to Tomcat 8.017 our web software
was not loading completely in the end users web browser. The
server side was processing everything but never fully getting to
Just so you know we are only using class Http11Protocol not Http11NioProtocol
or Http11AprProtocol.
This is our connector port which is also the default:
Connector port=8080 protocol=HTTP/1.1
connectionTimeout=2
redirectPort=8443 /
Shaun Morton
Legal Files
On Wed, Jan 21, 2015 at 2:59 PM, Mike Seda mike.s...@lillegroup.com wrote:
Is it advisable to have the following JVM option set in Tomcat 7 (with
Java 7)?
-XX:+DisableExplicitGC
It may or may not make a difference. Some questions like these come to
mind...
- How would you feel if one of
Thank you. That worked. Should i open a ticket in bugzilla to fix the doc?
On 1/21/2015 1:43 PM, Mark Thomas wrote:
On 21/01/2015 20:27, George Sexton wrote:
I'm having a problem configuring log4j with Apache Tomcat 8.0.17. I'm
using OpenSUSE 13.2 with OpenJDK 8.0:
linux:java -version
On Wed, Jan 21, 2015 at 3:51 PM, Christopher Schultz
ch...@christopherschultz.net wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Daniel,
On 1/21/15 3:16 PM, Daniel Mikusa wrote:
On Wed, Jan 21, 2015 at 2:59 PM, Mike Seda
mike.s...@lillegroup.com wrote:
Is it advisable to
On 21/01/2015 21:04, George Sexton wrote:
Thank you. That worked. Should i open a ticket in bugzilla to fix the doc?
Please.
Mark
On 1/21/2015 1:43 PM, Mark Thomas wrote:
On 21/01/2015 20:27, George Sexton wrote:
I'm having a problem configuring log4j with Apache Tomcat 8.0.17. I'm
On 21/01/2015 20:27, George Sexton wrote:
I'm having a problem configuring log4j with Apache Tomcat 8.0.17. I'm
using OpenSUSE 13.2 with OpenJDK 8.0:
linux:java -version
openjdk version 1.8.0_40
OpenJDK Runtime Environment (build 1.8.0_40-b10)
OpenJDK 64-Bit Server VM (build 25.40-b14,
After upgrading from Tomcat 8.0.15 to Tomcat 8.017 our web software was not
loading completely in the end users web browser. The server side was
processing everything but never fully getting to end user. We see that the
response is not complete via Developer mode in IE.
After much research
On 21/01/2015 21:51, Shaun Morton wrote:
Sorry no, it happens on both connectors, 8080(HTTP) and 8443(HTTPS).
The 8080 connector is the default out of the installation. I try to stick to
defaults for trouble shooting purposes.
I must confess I suspected the two were related as well when I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 1/21/15 4:59 PM, Mark Thomas wrote:
On 21/01/2015 21:51, Shaun Morton wrote:
Sorry no, it happens on both connectors, 8080(HTTP) and
8443(HTTPS).
The 8080 connector is the default out of the installation. I try
to stick to defaults
We will be creating a .jsp and putting it in a .war for you. Should be
tomorrow.
Shaun Morton
Legal Files Software
217-726-6000 Ext. 341
sh...@legalfiles.com
www.legalfiles.com
-Original Message-
From: Mark Thomas [mailto:ma...@apache.org]
Sent: Wednesday, January 21, 2015 4:00 PM
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Shaun,
On 1/21/15 5:27 PM, Shaun Morton wrote:
Just so you know we are only using class Http11Protocol not
Http11NioProtocol or Http11AprProtocol.
This is our connector port which is also the default: Connector
port=8080 protocol=HTTP/1.1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chris,
On 1/21/15 5:56 PM, Chris Arnold wrote:
When i look at the apache log for that request, i dont see
where the request is even making it to apache or tomcat.
Try to request a static file from DocumentRoot directory.
If you cannot,
+1
And also, could you specify again what URL you are requesting in the browser,
which you
would expect to be proxied to Tomcat ?
https://share2.domain.tld
Looking at the log you just showed, it seemed that the only requests ever
passed through
mod_jk for evaluation, where things like
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Shaun,
On 1/21/15 6:04 PM, Shaun Morton wrote:
Chris,
I apologize, I thought I had to specify the other classes. I do not
have the Tomcat native library installed and it looks to be
http-nio, here are the log entries:
21-Jan-2015
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chris,
On 1/21/15 5:56 PM, Chris Arnold wrote:
When i look at the apache log for that request, i dont see
where the request is even making it to apache or tomcat.
Try to request a static file from DocumentRoot
Chris,
I apologize, I thought I had to specify the other classes.
I do not have the Tomcat native library installed and it looks to be http-nio,
here are the log entries:
21-Jan-2015 15:44:17.118 INFO [main] org.apache.coyote.AbstractProtocol.start
Starting ProtocolHandler [http-nio-8080]
On 01/21/2015 03:24 PM, Christopher Schultz wrote:
Have you tried a plain-old HTTPS connection? No Websocket?
I just tried HTTPS using
HttpsURLConnection urlConnection = (HttpsURLConnection)
url.openConnection();
try {
try {
InputStream in = new
Both have the same problem.
Shaun Morton
On Jan 21, 2015, at 5:09 PM, Christopher Schultz
ch...@christopherschultz.net wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Shaun,
On 1/21/15 6:04 PM, Shaun Morton wrote:
Chris,
I apologize, I thought I had to specify the other
Greetings,I have inherited code that calls:
org.apache.catalina.startup.Catalina.process(args). I now need to upgrade this
code to Tomcat 8. Currently, we are using Tomcat 6. I have previously
upgraded with no problems, but both Tomcat 7 and 8 do not have the .process
method. I can not
Chris,
On 1/21/15 5:56 PM, Chris wrote:
You must have changed something since your original configuration. Do
you have JkMount ajp13 somewhere? You need to use the worker name
and not the protocol name.
Can you post your updated workers.properties file, and related
httpd.conf configurations?
When i look at the apache log for that request, i dont see where the request
is even making it to apache or tomcat.
Try to request a static file from DocumentRoot directory.
If you cannot, then your HTTPS is not configured correctly. Get that
working first.
Yeah, I overlooked that in my
2015-01-22 0:23 GMT+03:00 Shaun Morton sh...@legalfiles.com:
After upgrading from Tomcat 8.0.15 to Tomcat 8.017 our web software was not
loading completely in the end users web browser. The server side was
processing everything but never fully getting to end user. We see that the
response
What I changed in server.xml is adding
sslEnabledProtocols=TLSv1.2,TLSv1.1,TLSv1.
BUT I noticed that I am using JSSE instead of APR, so I remoeved the
listener Listener
className=org.apache.catalina.core.AprLifecycleListener SSLEngine=on /
is this causing my error?
On Wed, Jan 21, 2015 at 11:39
Am 22.01.2015 um 01:03 schrieb Chris Arnold:
+1
And also, could you specify again what URL you are requesting in the browser,
which you
would expect to be proxied to Tomcat ?
https://share2.domain.tld
Looking at the log you just showed, it seemed that the only requests ever
passed through
I'm having a problem configuring log4j with Apache Tomcat 8.0.17. I'm
using OpenSUSE 13.2 with OpenJDK 8.0:
linux:java -version
openjdk version 1.8.0_40
OpenJDK Runtime Environment (build 1.8.0_40-b10)
OpenJDK 64-Bit Server VM (build 25.40-b14, mixed mode)
I'm following the instructions in the
On 2015-01-21 00:15, Christopher Schultz wrote:
Can you build with an updated patch[1], re-break your directory
permissions and re-run Tomcat? Let me know if the log output you get
would have led you to a solution more quickly.
- -chris
I did. Here is the warning I obtained:
21-Jan-2015
That sounds possible. (I haven't looked at the code to check the theory
though.)
Please open a Bugzilla issue for this so it doesn't get lost.
thanks for your reply. I filed a bug for Tomcat 8:
https://issues.apache.org/bugzilla/show_bug.cgi?id=57472
I assume your web application is loading
then may be its not the issue of tomcat.you can check you firewall? may be
your firewall dropping the correction after some time.
try to connect the server from localhost using openssl s_client -connect
hostname:8443 -debug may be you will found something use full.
On Wed, Jan 21, 2015 at
Here is what I get with openssl s_client command:
Loading 'screen' into random state - done
CONNECTED(01E8)
write to 0x2103650 [0x2103698] (124 bytes = 124 (0x7C))
- 80 7a 01 03 01 00 51 00-00 00 20 00 00 39 00 00 .zQ... ..9..
0010 - 38 00 00 35 00 00 16 00-00 13 00 00 0a 07 00 c0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jason,
On 1/20/15 8:53 PM, Jason Y wrote:
Thank you all. Now it is working fine.
Connector port=8443
protocol=org.apache.coyote.http11.Http11Protocol maxThreads=150
SSLEnabled=true scheme=https secure=true clientAuth=false
sslProtocol=TLS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jason,
On 1/21/15 4:29 AM, Jason Y wrote:
Here is what I get with openssl s_client command:
Loading 'screen' into random state - done CONNECTED(01E8) write
to 0x2103650 [0x2103698] (124 bytes = 124 (0x7C)) - 80 7a 01
03 01 00 51
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Leo,
On 1/20/15 10:29 PM, Leo Donahue wrote:
On Tue, Jan 20, 2015 at 9:24 PM, Leo Donahue donahu...@gmail.com
wrote:
On Tue, Jan 20, 2015 at 5:09 PM, Mark Thomas ma...@apache.org
wrote:
The Apache Tomcat team announces the immediate
48 matches
Mail list logo
