We are using the Netscape Enterprise Server with MQ and have response times under a
second. Check your trigger status. It may be set to respond to only every 30 seconds
instead of upon receiving a queue? Also check the response time of the back-end
(mainframe?) system. The user-id on the back-end system may need to have it's
priority(class) set higher so that it will run before other scheduled jobs.
>>> Malcolm Hart <[EMAIL PROTECTED]> 09/27 5:26 AM >>>
Has anyone tried to make calls to MQ Series from a servlet running in WebSphere
?
I took a small piece of code from an MQ app. and put the calls into a servlet -
the response times are hideous !! Where a connect to the queue manager was
taking a second or two. it's now taking 20 to 30 seconds - it does complete
successfully though.
Has anyone seen this before ? Any pointer on where I can go and look ?
Thanks
Malcolm
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
