retry=60
route=dl360x3806.8030
Regards,
Adhavan.M
On Thu, May 11, 2017 at 9:06 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Adhavan,
>
> On 5/11/17 11:32 AM, Adhavan Mathiyalagan wrote:
> &
Hi,
8030 is the port where the application is running.
Regards,
Adhavan.M
On Thu, May 11, 2017 at 8:53 PM, André Warnier (tomcat)
wrote:
> On 11.05.2017 16:57, Adhavan Mathiyalagan wrote:
>
>> Hi Chris,
>>
>> *Tomcat Configuration*
---BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Adhavan,
>
> On 5/11/17 9:30 AM, Adhavan Mathiyalagan wrote:
> > The connections in the CLOSE_WAIT are owned by the Application
> > /Tomcat process.
>
> Okay. Can you please post your configuration on both h
cer IP
Regards,
Adhavan.M
On Thu, May 11, 2017 at 7:06 PM, André Warnier (tomcat)
wrote:
> On 11.05.2017 15:30, Adhavan Mathiyalagan wrote:
>
>> Hi Chris,
>>
>> The connections in the CLOSE_WAIT are owned by the Application /Tomcat
>> process.
>>
>
> C
> On 5/10/17 12:32 PM, Adhavan Mathiyalagan wrote:
> > Team,
> >
> > Tomcat version : 8.0.18
> >
> > Apache HTTPD version : 2.2
> >
> >
> > There are lot of CLOSE_WAIT connections being created at the
> > Application(tomcat) ,when the traffic is
> your LB and the server, you also have to take a look on this.
>
>
> Said that, one more cent about the protocol between the LB and the Tomcat:
> I don’t know about HTTP, but if you use AJP (with mod_jk) you may configure
> it to keep and reuse connections to the Tomcat backend(
Team,
Tomcat version : 8.0.18
Apache HTTPD version : 2.2
There are lot of CLOSE_WAIT connections being created at the
Application(tomcat) ,when the traffic is routed through the Apache HTTPD
load balancer to the Application running over tomcat container. This leads
to slowness of the port wher
Thanks for your answer Konstantin !.
I will re-verify the code.
Adhavan.M
On Sat, Jan 30, 2016 at 5:56 PM, Konstantin Kolinko
wrote:
> 2016-01-20 1:47 GMT+03:00 Mark Thomas :
> > On 19/01/2016 16:37, Adhavan Mathiyalagan wrote:
> >> Thanks Mark ! Please find my answer
&g
Hi Mark,
Kindly let me know if any further information required apart from the
information that i have provided in the above mail.
Thanks & Regards,
Adhavan.M
On Wed, Jan 27, 2016 at 4:09 PM, Adhavan Mathiyalagan
wrote:
> Hi Mark,
>
> Kindly find my answer for your query
&g
ag version : displaytag 1.1
Tomcat Version : tomcat 8.0.30
Kindly suggest me the path forward for the issue.
Thanks in Advance.
Adhavan.M
On Fri, Jan 22, 2016 at 6:46 PM, Mark Thomas wrote:
> On 22/01/2016 13:01, Adhavan Mathiyalagan wrote:
> > Hi Mark,
> >
> > Kindly let me
at 4:17 AM, Mark Thomas wrote:
> On 19/01/2016 16:37, Adhavan Mathiyalagan wrote:
> > Thanks Mark ! Please find my answer
> >
> > Figure out what is inserting something other than String[] as the value
> > into a Map instance.
> >
> > There are lot of pla
ix all the client code.
Is there any other way or path forward to fix this ? (Like upgrading the
displaytag version
which is currently 1.1) Or Is the modifying the Client Code is the only
path forward ?
Thanks Again !
On Tue, Jan 19, 2016 at 8:12 PM, Mark Thomas wrote:
> On 19/01/2016 1
Hi ,
While upgrading from tomcat 8.0.18 to tomcat 8.0.30 version ,we are facing
the below issue .The displaytag version used by the application is
DisplayTag 1.1
Caused by: javax.servlet.ServletException: javax.servlet.jsp.JspException:
java.lang.ClassCastException: java.lang.Integer cannot be c
13 matches
Mail list logo
