Title: [JBoss-dev] jboss container calls query
Hi Scott
Thanks for your response.
I had this doubt because i added this line to the StatelessSessionContainer.java
 protected double randomNumber=1000*Math.random();
and when i run the server i always get the same number for a particular deployed EJB
example. If i have a SSB OrderSessionBean , whenever any method is invoked by any client on any instance of OrderSessionBean the value of randomNumber is always the same, even when multiple clients are accessing multiple instances simultaneously.  To me it seemed that this scenario is very unlikely unless the container object is the same for all instances.
 
Raghu
-----Original Message-----
From: Scott M Stark [mailto:[EMAIL PROTECTED]On Behalf Of Scott M Stark
Sent: Tuesday, December 23, 2003 8:08 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-dev] jboss container calls query

The calls will not be serialized as different instances of the stateless session bean will be used to
handle a() and b().
 
xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx


From: [EMAIL PROTECTED] on behalf of Raghuram
Sent: Mon 12/22/2003 6:04 PM
To: [EMAIL PROTECTED]
Subject: [JBoss-dev] jboss container calls query

Hi,
I had posted this query on the jboss forum but did not get a response so I
thought I'll try here.
Am not sure if my question is clear.
I wanted to know if jboss serializes all calls to an ejb container. Consider
an EJB x with methods a() and b() and two clients c1 and c2.
x could be a deployed stateless session bean or an entity bean.

c1 calls x.a() and c2 calls x.b() at the same time.
will the two calls be serialized ?
As i understand, all the ejb calls are invoked through jmx and every
container is an MBean. However, if there is only one MBean for every
deployed EJB does it not imply that ALL calls to any instance of that EJB
will be serialized ?
If my understanding is wrong, please do correct me. However, if it is
serialized as i understand, i wanted to know if that is a spec requirement.
thanks
raghu

<<attachment: winmail.dat>>

Reply via email to