On Mon, Nov 4, 2019, 6:19 PM M. Manna wrote:
> I’m just trying to understand, is there really a plausible solution here ?
> Unless we have loadbalanced tomcat instances, can we truly ever stop such
> behaviour (or more importantly, does it make sense to do so)?
>
> For my use case, We do it in
Hello.
I'm doing something where I need to generate a password for a tomcat user
that is authenticated using org.apache.catalina.realm.UserDatabaseRealm
with "sha" digest, the user database is
produced by org.apache.catalina.users.MemoryUserDatabaseFactory from an xml
file (standard
Dear Christopher,
Really appreciate ur quick response! Sorry for late reply due to personal
affairs...
>>>I haven't read the code in detail, but I'm guessing that the thread pool
uses a queue and not a stack of threads, so each thread gets used,
repeatedly, in order of availability.
>>>Note that
I’m just trying to understand, is there really a plausible solution here ?
Unless we have loadbalanced tomcat instances, can we truly ever stop such
behaviour (or more importantly, does it make sense to do so)?
For my use case, We do it in production almost every other day for
patching, but we do
Sounds a lot like the issue I reported a few months ago
On Mon, Nov 4, 2019, 3:12 PM Tim K wrote:
> On Mon, Nov 4, 2019, 10:30 AM Mark Thomas wrote:
>
> >
> > Thanks. That helps as it means the issue should be reproducible on a
> > single, stand-alone instance.
> >
> > Mark
> >
>
> I was
On Mon, Nov 4, 2019, 10:30 AM Mark Thomas wrote:
>
> Thanks. That helps as it means the issue should be reproducible on a
> single, stand-alone instance.
>
> Mark
>
I was able to reproduce this behavior with a single server running a
vanilla 9.0.21 using the example hello.jsp file... I was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 11/4/19 11:56, Mark Thomas wrote:
> On 04/11/2019 15:30, Mark Thomas wrote:
>> On 04/11/2019 15:11, Tim K wrote:
>>> On Mon, Nov 4, 2019, 10:06 AM Mark Thomas
>>> wrote:
>>>
How are you distributing the updates to the JSP to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Alex,
On 11/4/19 10:09, Alexander Stöcker wrote:
> On Mon, Nov 4, 2019 at 2:55 PM Mark Thomas
> wrote:
>>
>> On 04/11/2019 12:59, Alexander Stöcker wrote:
>>> My code is basically just:
>>>
>>> Tomcat tomcat = new Tomcat();
On 04/11/2019 15:30, Mark Thomas wrote:
> On 04/11/2019 15:11, Tim K wrote:
>> On Mon, Nov 4, 2019, 10:06 AM Mark Thomas wrote:
>>
>>>
>>> How are you distributing the updates to the JSP to all 4 servers?
>>>
>>> Is there a shared file system involved? If yes, exactly what is shared
>>> between
On 04/11/2019 15:11, Tim K wrote:
> On Mon, Nov 4, 2019, 10:06 AM Mark Thomas wrote:
>
>>
>> How are you distributing the updates to the JSP to all 4 servers?
>>
>> Is there a shared file system involved? If yes, exactly what is shared
>> between the instances?
>>
>> Mark
>>
>
> Common NFS
On Mon, Nov 4, 2019, 10:06 AM Mark Thomas wrote:
>
> How are you distributing the updates to the JSP to all 4 servers?
>
> Is there a shared file system involved? If yes, exactly what is shared
> between the instances?
>
> Mark
>
Common NFS storage included via (DirResourceSet) within the
of
On Mon, Nov 4, 2019 at 2:55 PM Mark Thomas wrote:
>
> On 04/11/2019 12:59, Alexander Stöcker wrote:
> > My code is basically just:
> >
> > Tomcat tomcat = new Tomcat();
> > tomcat.getConnector();
> > tomcat.setPort(8080);
> >
> > Context context =
On 04/11/2019 13:55, Tim K wrote:
>>
>> In my tests when hitting it every second, I make a few changes and it
>> works fine (all within the same min). Then I'll let it go for a few mins,
>> make a change and more often than not, one or more of the servers gets
>> stuck on the previous jsp
>
> In my tests when hitting it every second, I make a few changes and it
> works fine (all within the same min). Then I'll let it go for a few mins,
> make a change and more often than not, one or more of the servers gets
> stuck on the previous jsp change... I'm pretty sure the class/java
>
On 04/11/2019 12:59, Alexander Stöcker wrote:
> My code is basically just:
>
> Tomcat tomcat = new Tomcat();
> tomcat.getConnector();
> tomcat.setPort(8080);
>
> Context context = tomcat.addContext("/context", new
> File(".").getAbsolutePath());
>
> //
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Alex,
On 11/4/19 07:59, Alexander Stöcker wrote:
> My code is basically just:
>
> Tomcat tomcat = new Tomcat(); tomcat.getConnector();
> tomcat.setPort(8080);
>
> Context context = tomcat.addContext("/context", new
>
My code is basically just:
Tomcat tomcat = new Tomcat();
tomcat.getConnector();
tomcat.setPort(8080);
Context context = tomcat.addContext("/context", new
File(".").getAbsolutePath());
// servlet
Tomcat.addServlet(context, "myServlet", new
17 matches
Mail list logo
