----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
My desire is to track transaction failures/excess latency. The will be
computationally expensive, but what it cost in hardware will be made up in
the ability to validate service level compliance. Maybe calling it
"transaction management" was a mistake since it implies so much more then I
think is needed.
- Dustin -
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Jean-Luc
Rochat
Sent: Monday, October 18, 1999 6:47 AM
To: Java Apache Users
Subject: Re: managing at the transaction level.
----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
Dustin Goodwin wrote:
>
> Has anyone thought about adding transaction management to jserv? All the
> most recent load balancing stuff is great. But does not address
managability
> at the transaction level. I am trying to just figure out a way to do basic
> monitoring in apache of requests sent to jserv. Has anyone else tried to
> address this?
>
> - Dustin -
Yep, I did already think of keeping count of requests sent to every
JServ.
The choice I had to do was between :
- synchronize all the shared memory accesses, protecting critical
sections with mutexes/monitor
vs
- NO synchronization at all (performance), understanding the possible
impact (I really can live with it, we are on a distributed system, and
even a moniitor could not solve all the possible problems).
What could be cool : offer customers the choice. But, definitively, the
rigth tool for that iis RSE's mm library, which will be part of
Apache2.0 AFAIK.
This "synchronized" shared memory could then be used to implement more
clever load-balancing algorithms.
But OTOH, if you need it, OK to discuss on the subject, and design
something.
Transaction management, IMO, are another point.
Jean-Luc
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
