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 Discussion » WMQ Server/Client Applications

Post new topic  Reply to topic Goto page Previous  1, 2
 WMQ Server/Client Applications « View previous topic :: View next topic » 
Author Message
gunter
PostPosted: Wed Mar 04, 2009 12:20 pm    Post subject: Reply with quote

Partisan

Joined: 21 Jan 2004
Posts: 307
Location: Germany, Frankfurt

Vitor wrote:
So all the LIFO (Last in, First Out) systems are not really queues then? How would you describe them?

It's a stack, not a queue.

exerk wrote:
Computing a list of data items, commands, etc., stored so as to be retrievable in a definite order.


definite order - LIFO, exception are up to the user(programmer), get under cursor, get with correlation id, using different priorities, ..., but NOT changing the position in the queue because of using different routes or multithreading.

BTW, I believe, we are hi-jacking the thread, is's not the main subject.
_________________
Gunter Jeschawitz
IBM Certified System Administrator - Websphere MQ, 5.3
Back to top
View user's profile Send private message
mqjeff
PostPosted: Wed Mar 04, 2009 12:22 pm    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

The point is that messages are retrieved from a queue in First In, First Out order.

But they are not guaranteed to be placed on a queue in First Sent, First In order.
Back to top
View user's profile Send private message
bruce2359
PostPosted: Wed Mar 04, 2009 12:50 pm    Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 9475
Location: US: west coast, almost. Otherwise, enroute.

Quote:
A queue, by the Oxford English Dictionary definition, is:

...too broad to be a working definition for all things called queues.

You need to read the WMQ documentation (WMQ Application Programming Ref. and WMQ Application Programming Guide to begin to understand how, why and in what order, WMQ will deliver a message from a queue. It's not as simple as FIFO or LIFO.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live.
Back to top
View user's profile Send private message
PeterPotkay
PostPosted: Thu Mar 12, 2009 6:47 pm    Post subject: Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7722

mqjeff wrote:

You can't mix and match these two connections within the same application, even in Java.


Can't 1 thread of the Java app build a hash table for the MQEnvironment class and then connect in client mode while another thread doesn't do anything with MQEnvironment and connects in bindings mode?

I don't know, I'm asking.

Even if the answer is yes, I'm not saying this is a good idea anyway.
_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
mqjeff
PostPosted: Thu Mar 12, 2009 7:08 pm    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

PeterPotkay wrote:
mqjeff wrote:

You can't mix and match these two connections within the same application, even in Java.


Can't 1 thread of the Java app build a hash table for the MQEnvironment class and then connect in client mode while another thread doesn't do anything with MQEnvironment and connects in bindings mode?

I don't know, I'm asking.

Even if the answer is yes, I'm not saying this is a good idea anyway.


Despite the fact that this is easy enough for both of us to test, I suspect strongly that neither of us *will* test it. Left as an exercise, I guess.

No, this is not possible. The bindings connection uses the same dang MQ classes, which require a deep (umm) binding against the MQ dlls and the client connection requires a deep... binding against the TCP/IP pure Java classes that implement the MQI interface.

If the same Java app tries to do both, only one will end up being deeply bound, and thus only one of the connections will succeed.

If you try really hard, you can get the same Java app to make bindings connections to two separate local qmgrs. But it's going to take a little bit of extra effort. It's much easier to create many client connections to both remote or local qmgrs - that tends to "just work". But mixing them requires ridiculous games with classloaders and etc. etc. etc that are beyond the ken of mere mortals.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2 Page 2 of 2

MQSeries.net Forum Index » General Discussion » WMQ Server/Client Applications
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.