This page contains information, on some report analysis scripts contained in the JK distribution. We apologise for any inconvenience. This release contains mainly bug fixes Download the JK 1. Reference Guide. This page contains detailed description of all workers. Status Worker The status worker is a builtin management worker. Common HowTo. Quick Start This page describes the configuration files used by JK on the web server side for the 'impatients'. All about workers This page contains an overview about the various aspects of defining and using workers.
Timeouts This page describes the possible timeout settings you can use. Load Balancing This page contains an introduction on load balancing with JK. Reverse Proxy This page contains an introduction to reverse proxies, how JK handles this situation and how you can influence the JK proxying behaviour.
Webserver HowTo. AJP Protocol Reference. Miscellaneous documentation. This is configured using the domain attribute. All workers with the same domain are assumed to share the sessions.
For maintenance purposes you can tell the load balancer to not allow any new sessions on some members, or even not use them at all. This is controlled by the member attribute activation. The value Active allows normal use of a member, disabled will not create new sessions on it, but still allow sticky requests, and stopped will no longer send any requests to the member.
Switching the activation from "active" to "disabled" some time before maintenance will drain the sessions on the worker and minimize disruption. Depending on the usage pattern of the application, draining will take from minutes to hours. Finally you can also configure hot spare workers by using activation set to disabled in combination with the attribute redirect added to the other workers:. The redirect flag on worker1 tells the load balancer to redirect the requests to worker2 in case that worker1 has a problem.
In all other cases worker2 will not receive any requests, thus acting like a hot standby. When using bookmarks or browsers that are running since a long time, it is possible to send a request carrying an old and invalid session id pointing at a disabled member.
Since the load balancer does not have a list of valid sessions, it will forward the request to the disabled member.
Thus draining takes longer than expected. If you detect "DIS" and the session for the request is no longer active, delete the session cookie and redirect using a self-referential URL.
The redirected request will then no longer carry session information and thus the load balancer will not send it to the disabled worker. The status worker does not communicate with Tomcat.
Instead it is responsible for the worker management. Besides JK Status Manager , is there other way to monitor the status of workers in real time? I mean if one server is down, I'd like to know immediately.
Is it default "A"? After 60 seconds it should turn into Err state. You can check its availability i. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Asked 6 years, 7 months ago.
Active 6 years, 7 months ago. Viewed 3k times. Improve this question. Add a comment. Active Oldest Votes.
0コメント