Hey Roger,
try to upgrade to the current CVS. If I remember well, after 2.0 Final Ole
fixed a bug on the class server that can be related to what you see.
Let know if with the fresh CVS it happens again.
Simon
> Hi:
>
> We are running into some transaction/locking issues that may
> or may not be
> our fault - anyone's help would be appreciated!
>
> We have jboss 2.0 Final running in one VM, and 2 client
> applications (each
> in different VM's) attaching to it; all beans (and all methods) have
> transaction attribute set to "REQUIRED".
>
> - The first client app gets a stateless session bean, and
> calls a method
> on it.
>
> - While that bean's method is running, the 2nd client app
> tries to get
> the Home object of an entity bean by calling "new
> InitialContext()" and
> "context.lookup( ejbname )".
>
> The call to "lookup" hangs (locks) until the first app's bean method
> completes!! ?? !!
>
> Once the session bean method returns, the JNDI lookup completes
> successfully. I'm using a source level debugger in all 3
> VM's to see this
> behavior.
>
> Thus, everything works, I just don't understand why there's
> synchronization/locking on the JNDI call. Am I crazy? :-)
> If I'm right,
> this seems an exorbitant performance problem; surely I must
> have something
> set up inefficiently?
>
> Help!
> Thanks,
> Roger
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> List Help?: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
