-
1. Re: Serialized call HELP!!!
adrian.brock Feb 22, 2003 4:03 AM (in response to milasx)Yes
Are you sure you aren't confusing an
MBean - Managed Bean with an
MDB - Message Driven Bean
Regards,
Adrian -
2. Re: Serialized call HELP!!!
milasx Feb 22, 2003 3:54 PM (in response to milasx)Hi,
Thanks for your reply!I use 3.2.0 RC1. I may miss something but what I am trying to do is I have an MBean (not Message Driven Bean) that manages and acts as controller for a pool of RMI servers that execute JNI commands. My idea is to have my client to call the EJB which in turn ask the MBean to execute the command to one of its RMI servers. Now I almost have one request per second and need to have parallel processing. If the MBean server soemehow serializes everything I am out of the game... Please could you confirm me that the MBean server serializes every request? If yes any better design idea?
Thanks very much!!!! -
3. Re: Serialized call HELP!!!
adrian.brock Feb 22, 2003 10:22 PM (in response to milasx)MBeanServer.invoke() performs the operation and
returns, there is no asynchronicity.
MDBs are designed for asynchronous processing.
Of course an MBean can hand off to a background thread
or thread pool to process asynchronously.
JBoss4 has an asynchronous NotificationBroadcaster
implementation that does just that.
Regards,
Adrian -
4. Re: Serialized call HELP!!!
milasx Feb 23, 2003 5:09 AM (in response to milasx)Hi,
I do not need to act asynchronously but syncronosly. My problem is that all the calls to MBeanServer.invoke() appers to be queed and served one by one. I need parallel synchrounous processing. Is this possible with the MBean? Thanks for your patience!!
Simone -
5. Re: Serialized call HELP!!!
adrian.brock Feb 23, 2003 6:32 PM (in response to milasx)I understand what you are talking about now.
Outside -> Stateless Session Bean -> MBean
can be run in parallel, there is no locking or queueing.
If it is not working in parallel, I suggest you take
a thread dump to find out where the threads are waiting.
Regards,
Adrian -
6. Re: Serialized call HELP!!!
milasx Feb 24, 2003 5:40 AM (in response to milasx)Thank you very much! Got the thread dump and it was the QueuedPessimisticEJBLock that was causing the serialization. I will now have to move to JDBCOptimisticLock. Thanks again for pointing me in the right direction.
Simone