At 08:54 PM 7/5/99 -0700, Mark Cassidy wrote:
>I have done simple tests using MQSeries from within a
>WebLogic deployed bean. -Seems to work fine putting a
>message on one queue, legacy app gets invoked and puts
>message on another queue, then code in the bean gets
>the message.
>
>I'm concerned that there may be some thread management
>that will rear its ugly head in the MQSeries code
>--EJB beans are not supposed to do thread management.
>Does anyone know if there are gotcha's here? I am not
>going to do anything fancy like subscribe to all new
>messages.
I have seen thread/JNI crashes when using MQSeries native java clients in
JVM 1.2.1 with WebLogic. We worked around this by using a client server MQ
config so that the app server was only invoking java code to callout to MQ.
This seems to work fine.
andy
---------------------------------------------------------------------------
" .sigs are like your face - rarely seen by you and uglier than you think"
Dr Andy Piper
mail: [EMAIL PROTECTED] web: http://www.xemacs.freeserve.co.uk/
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
