Hi Mark, thank you for providing those steps. I downloaded a "YourKit"
trial and did execute them.
I am blocked at the "Figure out what is creating those reference chains"
step. The documentation [
https://tomcat.apache.org/tomcat-9.0-doc/api/org/apache/catalina/loader/WebappClassLoaderBase.html
]
Hello,
When I upgraded to tomcat 11.0.5 and Java 24,
Tomcat log gives this warning..
WARNING: A terminally deprecated method in sun.misc.Unsafe has been called
WARNING: sun.misc.Unsafe::invokeCleaner has been called by
org.apache.tomcat.util.buf.ByteBufferUtilsUnsafe
(file:/home/web/ser
Good afternoon
Our HR and Payroll functions are being outsources to a HUB in Manila.
The employees who will be dealing with the these functions require access to be
able to submit the ROE and any claims, however they do not have a South African
Identity Number, is there another way that we will
Good afternoon
Our letter of Good Standing expires on 31 April 2025, however the system to
submit ROE applications only opens for renewal on 1 May 2025.
Could you please advise an alternative way that we can submit the application
for ROE?
Kind regards,
Christa Olivier
HR Specialist
Human Re
Hi Mark,
By duplicate session I mean that we get a duplicate session id created
by one of the nodes which then hijacks an existing session and we have
two users with a single session. We thought using JDBC based sessions
would avoid this but that doesn't seem to be the case. It could be how
o
On 24/04/2025 02:02, Zoran Avtarovski wrote:
We have a cluster of tomcat servers on AWS EC2 which operate behind an
AWS load balancer with sticky sessions.
We have our session storage on a DB using a JDBC store which for the
most part is working well, but we occasionally see duplicate session
On 23/04/2025 16:10, Simon Arame wrote:
What java method call should I be searching for in libraries source code ?
It isn't going to be that simple. You'll need to do something like.
1. Deploy the application
2. Undeploy the application
3. Force GC (with a profiler)
4. Take a memory snap
Thanks Chuck,
I missed that and will implement. Bigger problem is that
PersistentManager is incompatible with Clusters so we have to migrate
back to memory based sessions and use clusters to share sessions.
I would have thought that cluster would be easier to support with DB
based sessions.