One more related changes :
https://bz.apache.org/bugzilla/show_bug.cgi?id=63041
Please suggest the probable fix to make this smooth.
On Sat, Jul 25, 2020 at 11:03 AM Kushagra Bindal
wrote:
> Thanks Martin,
>
> By looking at the change log I found few relevant items.
>
If possible, please help in understanding the behavior and possible way to
handle this.
Thanks in advance for helping me so far.
On Fri, Jul 24, 2020 at 1:08 AM Martin Grigorov
wrote:
> On Thu, Jul 23, 2020, 15:52 Kushagra Bindal
> wrote:
>
> > Thanks Martin.
> >
> &g
Thanks Martin.
But with the old version i.e. 8.5.24 it is working smoothly. So, what could
be the problem? Or some specific property/configuration changes that need
to be made around this?
On Thu, Jul 23, 2020 at 6:00 PM Martin Grigorov
wrote:
> On Thu, Jul 23, 2020 at 3:10 PM Kushagra Bin
clarity.
I have shared the server.xml and command which we are using in stopping the
tomcat.
On Thu, Jul 23, 2020 at 2:49 AM Martin Grigorov
wrote:
> On Wed, Jul 22, 2020, 15:55 Kushagra Bindal
> wrote:
>
> > Hi Christopher,
> >
> > Did you get a chance to look int
Hi Christopher,
Did you get a chance to look into this?
Please help us in resolving this issue.
On Sat, Jul 18, 2020 at 11:26 AM Kushagra Bindal
wrote:
> Hi Chris,
>
> Additionally when trying to stop running application, we are getting below
> error.
>
> Sat Jul 18
and when we stop the same
it is throwing below error.
On Sat, Jul 18, 2020 at 10:17 AM Kushagra Bindal
wrote:
> Hi Chris,
>
> To stop tomcat we are using the below command.
>
> bin/shutdown.sh -$sleeptime -force
>
> Where in our case sleeptime is set to 30.
>
&g
what needs to be done to resolve this issue.
On Sat, Jul 18, 2020 at 12:47 AM Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Kushagra,
>
> On 7/17/20 11:47, Kushagra Bindal wrote:
> > Similar is
Similar issues we are also facing in our environment. What could be the
problem?
On Fri, Jul 17, 2020 at 6:04 PM om tiwari wrote:
> Hi,
>
> We have upgraded our tomcat version from 8.5.24 to 8.5.53 in
> application. After upgrading we are facing issue while stopping
> tomcat.
> Below is the
t 7:38 PM Kushagra Bindal >
> wrote:
>
> > Hi,
> >
> > We are planning to upgrade from apache tomcat from 8.5.24 to 8.5.53
> > version. During this process I found that in catalina.sh file below line
> > which was commented in 8.5.24 version
> >
> > # U
Hi,
We are planning to upgrade from apache tomcat from 8.5.24 to 8.5.53
version. During this process I found that in catalina.sh file below line
which was commented in 8.5.24 version
# Uncomment the following line to make the umask available when using the
#
Thanks Marks. It helps in solving the problem.
On Thu, Apr 9, 2020, 5:44 PM Mark Thomas wrote:
> On April 9, 2020 8:49:05 AM UTC, Kushagra Bindal <
> bindal.kusha...@gmail.com> wrote:
> >Yes Mark. :) This discussion is also going on.
> >
> >But is there anything
Yes Mark. :) This discussion is also going on.
But is there anything configuration changes which I can try at my end as
well.
On Thu, Apr 9, 2020 at 2:14 PM Mark Thomas wrote:
> On 09/04/2020 09:35, Kushagra Bindal wrote:
> > Thanks Luis. But we have different vulnerabilities ti
10/concepts/supported-platforms.html
>
>
>
>
>
>
> El jue., 9 abr. 2020 a las 9:53, Kushagra Bindal (<
> bindal.kusha...@gmail.com>)
> escribió:
>
> > Hi,
> >
> > We are currently using Alfresco APS 1.10.0 version. It is working
> smoothly
> &g
Hi,
We are currently using Alfresco APS 1.10.0 version. It is working smoothly
with 8.5.24 version.
But while upgrading this to Tomcat 8.5.53 we are encountering below error.
08-Apr-2020 08:46:07.951 WARNING [localhost-startStop-1]
org.apache.catalina.startup.SetContextPropertiesRule.begin
Thanks Olaf.. It worked..
On Fri, Dec 20, 2019 at 6:51 PM Olaf Kock wrote:
>
> On 20.12.19 13:28, Kushagra Bindal wrote:
> > Hi,
> >
> > We are working on upgrading our tomcat version from 8.5.24 to 9.0.29. In
> > this process, while starting one of our services we
ver.xml file details.
--
--
Please help in resolving the issue.
--
Regards,
Kushagra Bindal
k and Kushagra,
>
> On 12/5/19 13:11, Mark Thomas wrote:
> > On 05/12/2019 17:10, Kushagra Bindal wrote:
> >> Thanks Mark for your response.
> >>
> >> In which version tomcat has introduced these restrictions
> >
> > Check the changelog. Look for
gt;
> Sorry, no. Requests with invalid host names are always rejected.
>
> Mark
>
>
> >
> > On Wed, Dec 4, 2019, 4:23 PM Mark Thomas wrote:
> >
> >> On 04/12/2019 05:19, Kushagra Bindal wrote:
> >>> Hi,
> >>>
> >>
could
result into regression in application.
So is there a way by which I can apply some setting like escape character
or something which could help me in resolving this issue?
On Wed, Dec 4, 2019, 4:23 PM Mark Thomas wrote:
> On 04/12/2019 05:19, Kushagra Bindal wrote:
> > Hi,
> &
> a path element (which just happens to be empty).
> > https://tools.ietf.org/html/rfc3986#section-3.3 does not seem to
> > forbid consecutive slashes either.
> >
> > But I would suppose that if the Tomcat developers decided to
> > collapse multiple consecutive slashes, they
Thanks
On Wed, Dec 4, 2019, 5:20 PM Mark Thomas wrote:
> On 04/12/2019 11:32, Kushagra Bindal wrote:
> > Hi Mark,
> >
> > I am not saying that this is a tomcat issue, I am just asking if there
> is a
> > way by which we can handle this. As maybe in later version o
; issue we can take a look.
>
> Mark
>
>
> >
> > On Tue, Dec 3, 2019 at 5:46 AM Kushagra Bindal <
> bindal.kusha...@gmail.com>
> > wrote:
> >
> >> Chris,
> >>
> >> If you will check in my early email then you will find that with // it
(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:745)
Can someone please help in identifying the actual root cause of the failure.
--
Regards,
Kushagra Bindal
Hi Mark/Manna/Chris,
Do we have any way out to handle this type of behavior?
On Tue, Dec 3, 2019 at 5:46 AM Kushagra Bindal
wrote:
> Chris,
>
> If you will check in my early email then you will find that with // it is
> throwing 404. But as soon as I removed it manually then it st
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Kushagra,
>
> On 12/2/19 11:29, Kushagra Bindal wrote:
> > I think it should be.
> >
> >
> > DanglingSessionInvalidateFilter
> > DanglingS
help & support in resolving this issue.
Regards
Kushagra
On Mon, Dec 2, 2019 at 9:00 PM Mark Thomas wrote:
> On 02/12/2019 10:59, Kushagra Bindal wrote:
> > Hi Mark,
> >
> > These are Rest Endpoints, and so will be processed through Filter.
>
> That is unusual.
>
Hi Mark/Manna
Please let me know if I need to provide some additional information about
the deployments so that it can be helpful in resolving the issue.
Regards
Kushagra
On Mon, Dec 2, 2019, 4:29 PM Kushagra Bindal
wrote:
> Hi Mark,
>
> These are Rest Endpoints, and so will be
Hi Mark,
These are Rest Endpoints, and so will be processed through Filter. Do, you
think Servlet mapping will play any role here?
On Mon, Dec 2, 2019 at 2:33 PM Mark Thomas wrote:
> On 02/12/2019 04:53, Kushagra Bindal wrote:
> > Hi Mark,
> >
> > Please find the snippet f
Mark Thomas wrote:
> On 01/12/2019 07:11, Kushagra Bindal wrote:
> > Hi Manna/Mark,
> >
> > Below are the sample URL which we are passing to Tomcat.
> >
> > http://backend_tomcat:8080//sdm/restcall)(.*)/file_uploads
> > http://backend_tomcat:808
a probable solution to handle such situation, then please
do let me know.
Looking forward to hearing from you.
Regards
Kushagra
On Fri, Nov 29, 2019 at 6:23 PM M. Manna wrote:
> Kushagra,
>
> On Fri, 29 Nov 2019 at 12:29, Kushagra Bindal
> wrote:
>
> > Hi Mark,
> >
&
, Nov 29, 2019 at 5:52 PM M. Manna wrote:
> Hi
>
> On Fri, 29 Nov 2019 at 11:43, Kushagra Bindal
> wrote:
>
> > Hi Mark,
> >
> > We tried to put the changes as suggested by you. Below are the changes
> that
> > we have made in context.
- [29/Nov/2019:11:27:46 +] "GET
/sdm/restcall/v1/platform//healthCheck HTTP/1.0" 404 -
Please help me in correcting the syntax.
Regards
Kushagra
On Fri, Nov 29, 2019 at 4:02 PM Kushagra Bindal
wrote:
> Hi Mark,
>
> Thanks for providing the response.
>
> Yes, you ar
.
On Fri, Nov 29, 2019 at 2:56 PM M. Manna wrote:
> HI,
>
>
> On Fri, 29 Nov 2019 at 09:00, Kushagra Bindal
> wrote:
>
> > Hi,
> >
> > We are working on upgrading our enterprise application from 8.5.24 to
> > 9.0.27 version.
> >
> > What we have obs
e same url which
was working earlier it is now throwing 404 status code.
Now, the problem is that we can not remove these double slash (//) manually
as it is used widely.
So, can someone please provide a possible solution of this issue?
--
Regards,
Kushagra Bindal
+91-9013792807
34 matches
Mail list logo
