Re: Jmxproxy causes datasources exceptions.

Problem was initialSize="0". Solution initialSize="1". -- Forwarded message - From: Oliva Date: mié., 21 feb. 2018 a las 12:47 Subject: Jmxproxy causes datasources exceptions. To: When I try

RE: Tomcat 8.5.23

Am 15. Februar 2018 19:25:24 MEZ schrieb Lawrence Lim : >Red Hat Enterprise Linux Server release 6.9 (Santiago) How did you install tomcat? Are you running tomcat with some kind of security manager enabled (Java or system wide)? Can the tomcat user (running the

Re: error creating connection pool

Am 13. Februar 2018 15:20:00 MEZ schrieb "Bruce L. Riddle" : >We are running a CDC Application PHIN MS that uses Tomcat 8.5.11. > >As the application starts, we are getting a message that says > >'error creating connection pool for dbid.' > > >Our assumption is

[SECURITY] CVE-2018-1304 Security constraints mapped to context root are ignored

CVE-2018-1304 Security constraints mapped to context root are ignored Severity: High Vendor: The Apache Software Foundation Versions Affected: Apache Tomcat 9.0.0.M1 to 9.0.4 Apache Tomcat 8.5.0 to 8.5.27 Apache Tomcat 8.0.0.RC1 to 8.0.49 Apache Tomcat 7.0.0 to 7.0.84 Description: The URL

[SECURITY] CVE-2018-1305 Security constraint annotations applied too late

CVE-2018-1305 Security constraint annotations applied too late Severity: High Vendor: The Apache Software Foundation Versions Affected: Apache Tomcat 9.0.0.M1 to 9.0.4 Apache Tomcat 8.5.0 to 8.5.27 Apache Tomcat 8.0.0.RC1 to 8.0.49 Apache Tomcat 7.0.0 to 7.0.84 Description: Security

Re: problems with tomcat 8.5.5

Can you please check the changelog for 8.5.x and see if this was fixed? Regards, On Thu, 22 Feb 2018 at 23:11, Lou DeGenaro wrote: > From catalina.out, NPE seems bad. Other log files have NPEs too. Need a > never version of tomcat? > > Thanks. > > Lou. > > - > >

problems with tomcat 8.5.5

>From catalina.out, NPE seems bad. Other log files have NPEs too. Need a never version of tomcat? Thanks. Lou. - 22-Feb-2018 16:37:28.599 SEVERE [http-nio-8080-exec-29] org.apache.coyote.http11.Http11Processor.endRequest Error finishing response java.lang.NullPointerException

Re: TomcatCon at ApacheCon?

On 22/02/18 16:21, David Cleary wrote: > Mark, > > Will there be a TomcatCon within ApacheCon this year? Yes. Both at the EU roadshow in Berlin (we are aiming for a one track of content for a day) and at the NA conference in Montreal. How much content there is at Montreal is TBD but it should be

TomcatCon at ApacheCon?

Mark, Will there be a TomcatCon within ApacheCon this year? Dave

Re: tomcat 8.5 gives RC 400 sometimes?

On 22/02/18 11:15, Lou DeGenaro wrote: > tomcat version = 8.5.5 > > Requests for same file sometimes get 200 and sometime 400. How come? The request is invalid in some way. Probably an illegal HTTP header value. Mark > > From log file: > > 192.168.1.1 - - [22/Feb/2018:05:48:57 -0500] "GET

Re: Http with client certificate authentication

On 22/02/18 03:23, Alex O'Ree wrote: > Howdy folks, > > If I setup a tomcat connector in server.xml with clientAuth="true" and have > the key store for tomcat and a trust store is the following true? > > - all public key certificates issued by CA's the trust store are allowed in? Yes. > - all

tomcat 8.5 gives RC 400 sometimes?

tomcat version = 8.5.5 Requests for same file sometimes get 200 and sometime 400. How come? >From log file: 192.168.1.1 - - [22/Feb/2018:05:48:57 -0500] "GET / whiteplainshistory.org//local/images/icons/Heritage_Trail.jpg HTTP/1.1" 400 - 192.168.1.1 - - [22/Feb/2018:05:49:05 -0500] "GET /

Re: Tomcat throwing 404 error after modifying context.xml

Have you read what resource definitions mean from - https://tomcat.apache.org/tomcat-8.5-doc/config/context.html ? On 22 February 2018 at 08:32, Howlader, Aakash [GTSUS Non-J] < ahowl...@its.jnj.com> wrote: > Hello, > > The jdbc url "url="jdbc:postgresql://itsusralsp06829:5432/spectra" > points

RE: Tomcat throwing 404 error after modifying context.xml

Hello, The jdbc url "url="jdbc:postgresql://itsusralsp06829:5432/spectra" points to a postgre db in another host. We tried to modify the maxActive parameter. The other parameters were left untouched. This is what the property was in the original context.xml > type="javax.sql.DataSource"