Chris,
Thank you for your quick response. We are planning to use the combination of
one of these below in production. Our application is a high volume application
with transactions per second of about 20. Just wondering for the recommended
value for validationInterval.
Option1:
testOnBorrow =
On 11/04/18 09:22, Richard Tearle wrote:
> I've built tomcat from source using the link you provided, and rebuilt the
> containers with this tomcat, and can still reproduce the issue. I've uploaded
> the logs (30s before the connection closed error), to dropbox:
>
> https://www.dropbox.com/s/qe
Thanks Christopher
On Mon, Apr 16, 2018 at 11:29 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Loai,
>
> Unfortunately, there really isn't enough information in your question
> to help you out.
>
> But it's fairly clear this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Loai,
Unfortunately, there really isn't enough information in your question
to help you out.
But it's fairly clear this is a problem with your application's use of
Grails and/or Spring. Someone here might be able to help, but you are
likely better
Having trouble starting up the application on a new dev AWS server.
Tomcat says….
SEVERE: Error initializing static Resources
java.lang.IllegalArgumentException: Document base
/home/testuser/resources/Raptor
does not exist or is not a readable directory
But if you see below folder/permissi
Also this error occurred in the same file ( catalina.out)
java.io.IOException: Did not receive successful HTTP response: status code
= 500, status message = [Internal Server Error]
at org.springframework.remoting.httpinvoker.
SimpleHttpInvokerRequestExecutor.validateResponse(
SimpleHttpIn
Hello every one
I have deployed Core app in worker 0 and got the following error
Receive call from the ESB.
consumerKey SC-serviceName RemotePersonService-methodName getPerson
---
serviceName
RemotePersonService-methodNamegetPerson-Error-METHOD_NOT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Steve,
On 4/16/18 12:23 PM, Steve Willett wrote:
> Has anyone else had this problem? When I download the
> apache-tomcat-8.5.30-windows-x64.zip Windows 10 binaries, and try
> to unzip them, WinZip reports that they are corrupt. I am using
> WinZi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Rémy,
On 4/16/18 11:05 AM, Rémy Maucherat wrote:
> On Mon, Apr 16, 2018 at 4:51 PM, Igor
> wrote:
>
>> If this is really such a simple problem then how can I get rid of
>> its output into error log?
>>
>
> You can always configure the logging if
Has anyone else had this problem? When I download the
apache-tomcat-8.5.30-windows-x64.zip Windows 10 binaries, and try to
unzip them, WinZip reports that they are corrupt. I am using WinZip
20.5 running under Windows 10 Home (ver. 1709).
-- *
Steve Willett*
YourSportsLeague.com
(510) 435-05
On Mon, Apr 16, 2018 at 4:51 PM, Igor wrote:
> If this is really such a simple problem then how can I get rid of its
> output
> into error log?
>
You can always configure the logging if you'd like to filter this one out,
but this looks like a serious error during accept. I'd think you should try
If this is really such a simple problem then how can I get rid of its output
into error log?
--
Sent from: http://tomcat.10.x6.nabble.com/Tomcat-User-f1968778.html
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
F
The Apache Tomcat team announces the immediate availability of Apache
Tomcat 7.0.86.
Apache Tomcat is an open source software implementation of the Java
Servlet, JavaServer Pages, Java Expression Language and Java
WebSocket technologies.
This release contains a number of bug fixes and improvement
The Apache Tomcat team announces the immediate availability of Apache
Tomcat 8.0.51.
Please note that Apache Tomcat 8.x users should normally be using 8.5.x
releases in preference to 8.0.x releases. The Apache Tomcat team
announced that support for Apache Tomcat 8.0.x will end on
30 June 2018.
Ap
On Sun, Apr 15, 2018 at 1:32 PM, Igor T wrote:
> I'm experiencing many "Socket accept failed: The specified network
> name is no longer available." exceptions in the Tomcat error log.
>
> These exceptions happen both on port 80 and 443. Both connectors are
> using Http11Nio2Protocol.
>
> I can't
15 matches
Mail list logo