ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » Client vs. Server?

Post new topic  Reply to topic
 Client vs. Server? « View previous topic :: View next topic » 
Author Message
pichelma
PostPosted: Thu Apr 18, 2002 8:34 am    Post subject: Reply with quote

Apprentice

Joined: 11 Mar 2002
Posts: 25

Hi all,

Hoping someone could verify my findings on Server vs. Client.

I am told that the MQ client does not guarantee "assured" delivery of msgs, is this "all-together" true? If a queue is defined as persistent, can this help?
Any attributes for a channel definition that may guarantee delivery as well?
Is this soley up to the developer when coding MQI calls from the app?(EX.java)

On the server-side, I know the q-mgr/queues cache/save the msg. in case of TCP/IP(network), Machine/memory crash's or q-mgr problems...and have tested this already.

Any suggestions or solutions?

TIA!

Scott



Back to top
View user's profile Send private message
bower5932
PostPosted: Thu Apr 18, 2002 9:11 am    Post subject: Reply with quote

Jedi Knight

Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA

I wouldn't say that an MQ client does NOT give assured message delivery. The MQSeries client makes a synchronous network connection to the qmgr. If this connection is up and running, all is well. If this connection goes down, your application will get an error at message put time (probably a 2009) and you'll need to save your message. When you run in server (or bindings) mode, the application makes a direct (inter-process) connection to the qmgr so you don't have the possbility of a message not making it to the qmgr because of the network.

There aren't any parameters that you need to set to get this behavior. Marking a queue (or message) as persistent doesn't have any effect on the network connection.

As far as server-to-server communication is concerned, the channels on both ends use internal counters (CURLUWID, CURMSGS, CURSEQNO, LSTSEQNO) to verify which messages they have sent/received so that a message isn't lost or duplicately delivered.

Any suggestions or solutions?

TIA!

Scott
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger
EddieA
PostPosted: Thu Apr 18, 2002 9:41 am    Post subject: Reply with quote

Jedi

Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles

The 'window of doubt' on a Client is between the Get from the Queue until the application has processed the data.

You can protect this by doing the Get under Syncpoint.

Cheers,

_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0
Back to top
View user's profile Send private message
pichelma
PostPosted: Thu Apr 25, 2002 8:00 am    Post subject: Reply with quote

Apprentice

Joined: 11 Mar 2002
Posts: 25

Thanks again for clarifying guys!

Yes, more clear on this topic now.

I will utilize both suggestions...

thanks,

Scott
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » Client vs. Server?
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.