Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Java databases as alternative to MySQL on OS X Server? (OT)
Date: Tue, 29 Nov 2005 09:28:40 -0600
Message-ID: 
 <AEF3D568DD1D9E428048C592AA16459703067FE4@USRV-EXCH4.na.uis.unisys.com>
Thread-Topic: Java databases as alternative to MySQL on OS X Server? (OT)
Thread-Index: AcX0w4DUXrzV7KWKS++TH3RZVfyingAM+xsg
From: "Caldarale, Charles R" <Chuck.Caldarale@unisys.com>
To: "Tomcat Users List" <users@tomcat.apache.org>

> From: Oded Arbel [mailto:oded@m-wise.com]=20
> Subject: Re: Java databases as alternative to MySQL on OS X=20
> Server? (OT)
>=20
> inter-thread communication in java is done through shared=20
> memory - shared variables, but the Java memory sharing model=20
> doesn't really share memory, Instead it uses thread local=20
> storage to store copies of shared variables and when you=20
> cross into or out of a synchronized block, the contents of=20
> the variables are copied.

That's one of the most bizarre and blatantly wrong descriptions of the
Java memory model that I've ever read.  All Java objects reside in the
Java heap, which is shared across all threads of the JVM process and
directly referenceable by all.  Local variables for a Java method exist
in each thread's Java stack, which is normally not shared across threads
other than for garbage collection operations.  Entering a synchronized
block in a HotSpot-based JVM normally does not require any context
switching, since the lock on an object is established via the platform's
compare-and-exchange instruction; only if a conflict exists are kernel
services required to suspend the conflicting thread.  (This is also true
of the JRockit and IBM JVMs, as well as several others.)  No copying of
local variable is ever performed; on some OS implementations, parameters
are copied when calling a kernel service that requires a context switch
but that occurs within the OS, not the JVM.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org