at least a changelog would help.

Probably the default xml file as well

marcf


|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Bill
|Burke
|Sent: Wednesday, September 19, 2001 2:16 PM
|To: [EMAIL PROTECTED]
|Subject: RE: [JBoss-dev] RequiresNew Locking Bug in JBoss 2.4.1
|
|
|Jim,
|
|I'm in total agreement here.  Serialized access is really only good for
|synchronized caching.
|
|Yes, for commit option 'B' and 'C' there is a way to duplicate instances of
|entity beans.  Unfortunately, this code has a major bug in it so you would
|have to go to CVS and get latest from Branch_2_4.
|
|How to enable it?
|
|1. In standardjboss.xml(or your own container-configuration), change
|<commit-option> to B or C.
|2. Also change the <locking-policy> from QueuedPessimisticEJBLock to
|MethodOnlyEJBLock.
|3. Also change EntityInstanceInterceptor to EntityMultiInstanceInterceptor.
|4. Also change EntitySynchronizationInterceptor to
|EntityMultiInstanceSynchronizationInterceptor.
|
|I'm sorry that this is not documented.
|
|Also, unfortunately, this stuff will not work with commit-option 'A' since
|no caching is done.  This can be improved later.
|
|Regards,
|
|Bill
|
|> -----Original Message-----
|> From: [EMAIL PROTECTED]
|> [mailto:[EMAIL PROTECTED]]On Behalf Of James
|> Cook
|> Sent: Wednesday, September 19, 2001 1:31 PM
|> To: [EMAIL PROTECTED]
|> Subject: RE: [JBoss-dev] RequiresNew Locking Bug in JBoss 2.4.1
|>
|>
|> Bill,
|>
|> Since there is little documentation regarding locking, can you clear up a
|> question?
|>
|> Don't take this as a slam. All of the major commercial vendors have
|> discovered that it is problematic to perform serialization of
|> client access
|> to EJB's in the container. [We can expound upon this, if you feel this is
|> not the case]. WebLogic was the last holdout and since 6.1, they
|too, have
|> removed serialized access from their container.
|>
|> Does jBoss currently support (in 2.4.1) the opportunity to duplicate
|> instances of entity beans in the container? If so, how do I
|enable it, and
|> do we run tests against the server in this mode? Also, if so,
|> shouldn't this
|> be enabled as the default...taking the queue from every other app server
|> vendor?
|>
|> thanks,
|> jim
|>
|>
|> _______________________________________________
|> Jboss-development mailing list
|> [EMAIL PROTECTED]
|> https://lists.sourceforge.net/lists/listinfo/jboss-development
|>
|
|
|
|_______________________________________________
|Jboss-development mailing list
|[EMAIL PROTECTED]
|https://lists.sourceforge.net/lists/listinfo/jboss-development


_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to