• Post Reply Bookmark Topic Watch Topic
  • New Topic

JMS Delay  RSS feed

 
andreas krohn
Greenhorn
Posts: 18
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
We are using SwiftMQ's JMS server and have an annoying problem that only occure a couple of times a day with a heavy load. It seems like the messages (nonpersistant) gets stuck somewhere in SwiftMQ. Messages go in, but not out. Then after a couple of minutes everything comes at once. So nothing is lost, just delayed (which is problem enough right now).
Does anyone have an idea why this happens?
 
Ram Dhan Yadav K
Ranch Hand
Posts: 321
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Must be a product problem, better you consult the technical support of Swift MQ
 
Ruilin Yang
Ranch Hand
Posts: 150
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
One strategy might works for you is to throttle, or limit, the amount of work any given server instance can process at any one time. A machine can only guarantee a response time for the clients it serves and be reliable if it isn't using up every last bit of hardware resources it has at its disposal.
This might be what happen to you since the problem occurs when heaver loading occures.
Please elaborate/correct my point.
Thanks
Ruilin
[ February 07, 2002: Message edited by: Rulin Yang ]
 
Shubhrajit Chatterjee
Ranch Hand
Posts: 356
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
Correct me if I am wrong, but message oriented systems are architected mainly for asynchronous processing. So the time delay is a thing that one might have to live along with.
I understand that SwiftMQ is probably a middleware product like IBM MQSeries, and probably you are using it to talk to some legacy system, perhaps an OS/390 system. In that case you will probably have a problem.
I have never worked with SwiftMQ. However I have worked with IBM MQSeries, where in case you want to have synchronous processing, your client will have to wait for a reply message after putting in a request. There is a property by which you can set how much you want to wait befor the request times out. There is probably something similar in SwiftMQ and you would probably like to configure it.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!