MQServer | PHP写的消息队列服务器，可以用来异步执行一些任务，比如发送邮件，短信之类的

Am I correct when I then assumed that this is a standalone Redis server

That's an incorrect conclusion, the Redis Server is a distributed in-memory data structure server which just like other distributed servers like an RDBMS or MQ Broker runs in its own isolated networked process.

All ServiceStack Redis Libraries connect to a Redis Server, Redis MQ is like all other distributed ServiceStack MQ providers which process messages sent to a broker, in this case Redis MQ uses the Redis Server as its broker. The statement:

Creates a Redis MQ Server that processes each message on its own background thread

Explains how Redis MQ processes the messages that it receives, where each different Message Type (i.e. Request DTO Type) processes messages in its own background thread.

Strange; this works fine for me...

The stuff after you source env.sh overrides many of the things it tried to initialize. If you don't want to replace the LD_LIBRARY_PATH it created etc, move the sourcing of env.sh to after the stuff in your .bash_profile.

The code in env.sh generally does a better job of preserving any earlier customizations. For example, it extends the existing value of LD_LIBRARY_PATH by adding stuff to the old value, rather than flat out replacing it with a static value.

You specify the channel name, host, and port in the MQCD which is referenced from the MQCNO. In C it is the MQCONNX call that allows this. If you specify things in the CCDT then you point to the CCDT with MQCHLLIB=/path/to/table and MQCHLTAB=table_filename.TAB, then you can issue a normal MQCONN (or MQCONNX) call and specify just the queue manager name. It will find this QMNAME in the CCDT and use the connection details provided in the CCDT. – JoshMc 21 mins ago

If you're using an explicit ReplyTo address any Errors will be sent to that ReplyTo address instead of the DLQ.

If your Response DTO has a ResponseStatus property the Exception will be populated in the ResponseStatus of the Response DTO, otherwise you can read the Exception Info using the generic ErrorResponse DTO, e.g:

The short answer is to remove the MQSERVER environment variable. For further details and references read below.

If you specify the MQSERVER environment variable MQ will only use this information and ignore the the CCDT environment variables (MQCHLLIB and MQCHLTAB).

This is referenced in the IBM MQ Knowledge Center page Configuring > Configuring connections between the server and clients > Using IBM MQ environment variables > MQSERVER > Using MQSERVER.

If you use the MQSERVER environment variable to define the channel between your IBM® MQ MQI client machine and a server machine, this is the only channel available to your application, and no reference is made to the client channel definition table (CCDT).

Further information on how MQ application will determine connection details is referenced in the IBM MQ Knowledge Center page Developing applications > Developing MQI applications with IBM MQ > Writing client procedural applications > Running applications in the IBM MQ MQI client environment > Connecting IBM MQ MQI client applications to queue managers

When an application running in an IBM MQ client environment issues an MQCONN or MQCONNX call, the client identifies how it is to make the connection. When an MQCONNX call is issued by an application on an IBM MQ client, the MQI client library searches for the client channel information in the following order:

1. Using the contents of the ClientConnOffset or ClientConnPtr fields of the MQCNO structure (if supplied). These fields identify the channel definition structure (MQCD) to be used as the definition of the client connection channel. Connection details can be overridden by using a pre-connect exit. For more information, see Referencing connection definitions using a pre-connect exit from a repository.
2. If the MQSERVER environment variable is set, the channel it defines is used.
3. If an mqclient.ini file is defined and contains a ServerConnectionParms, the channel that it defines is used. For more information, see Configuring a client using a configuration file and CHANNELS stanza of the client configuration file.
4. If the MQCHLLIB and MQCHLTAB environment variables are set, the client channel definition table they point to is used.
5. If an mqclient.ini file is defined and contains ChannelDefinitionDirectory and ChannelDefinitionFile attributes, these attributes are used to locate the client channel definition table. For more information, see Configuring a client using a configuration file and CHANNELS stanza of the client configuration file.

6. Finally, if the environment variables are not set, the client searches for a client channel definition table with a path and name that are established from the DefaultPrefix in the mqs.ini file. If the search for a client definition table fails, the client uses the following paths:

   • UNIX and Linux systems: /var/mqm/AMQCLCHL.TAB
   • Windows: C:\Program Files\IBM\WebSphere MQ\amqclchl.tab
   • IBM i: /QIBM/UserData/mqm/@ipcc
   • IBM MQ Appliance: _AMQCLCHL.TAB. They appear under the mqbackup:// URI.

You cannot specify Cipherspec using the MQSERVER environment variable. This is referenced in the IBM MQ Knowledge Center page Configuring > Configuring connections between the server and clients > Using IBM MQ environment variables > MQSERVER

MQSERVER environment variable is used to define a minimal channel. MQSERVER specifies the location of the IBM® MQ server and the communication method to be used.

You cannot use MQSERVER to define an SSL channel or a channel with channel exits. For details of how to define an SSL channel, see Protecting channels with SSL.

The same Request Context instance can't be resolved from the IOC. The Request Context instance is created in the MQ's RegisterHandler() where you can add custom data in the IRequest.Items property, e.g:

I found information from a few sources on this topic that when put together paint the whole picture (unfortunately IBM's MQ KC does not document this very well to say the least).

1. At Capitalware's MQ Technical Conference v2.0.1.3 Morag Hughson gave a presentation WebSphere MQ V7 Enhanced Application Programming which has some useful information.

   On page six it states:

   • Your message consumer can also be called with CallType set to MQCBCT_EVENT_CALL (this is also the only way an Event handler can be called). The message consumer will be given events that are pertinent to the queue it is consuming from, for example, MQRC_GET_INHIBITED whereas the event handler gets connection wide events.

2. In the IBM MQ v8 KC page MQCBC - Callback context > Fields for MQCBC > Hobj (MQHOBJ) it states:

   For an event handler, this value is MQHO_NONE

3. The IBM provided sample amqscbf0.c also demonstrates checking the pContext->CallType in the MessageConsumer, if it is type MQCBCT_EVENT_CALL it prints the Reason, if it is type MQCBCT_MSG_REMOVED it prints the message.

Based on the above information it appears the behavior you see is the expected behavior.

A suggested work around would be to set the CallbackArea field of each queue's MQCBD with a unique value that you can use to determine the which queue the event refers to.

On page four of Morag's presentation "WebSphere MQ V7 Enhanced Application Programming" it states the following:

• MQGMO_WAIT with MQGMO.WaitInterval = 0 operates just like MQGMO_NO_WAIT when one uses on an MQGET, but in the case of asynchronous consumers we wish to avoid the consumer from polling in a busy loop in this case, so it operates more like a backstop marker to show when the end of a batch of messages has been reached.

In the table on the same page it under the Asynchronous Consume column for MQGMO_WAIT with MQGMO.WaitInterval = 0 it states:

Only called with MQRC_NO_MSGS_AVAILABLE if just started or has had a message since last 2033

Your consumer will not continuously get events notifying it that no messages are on the queue. An event is only generated if there are no messages when the call back is first started and/or after each time ALL messages have been read (GET) from the queue. Essentially it lets you know that currently no more messages are available after it had read at least one message. This may be useful if you expect batches of messages and want to perform some action after all messages in a batch have been read off the queue.

• Note that MQGMO_NO_WAIT, and MQGMO_WAIT with a WaitInterval of MQWI_UNLIMITED are quite different when passed to MQGET but with the MQCB call their behaviour is the same. The consumer will only be passed messages and events, it will never be passed the reason code indicating no messages. Effectively MQGMO_NO_WAIT will be treated as an indefinite wait. This is to prevent the consumer from endlessly being called with the no messages reason code.

If you really do not need the MQRC_NO_MSG_AVAILABLE event messages, then MQGMO_NO_WAIT is probably the way to go.

The output you provide indicates you are executing amqsget not amqsbcgc.

I note that your question mentions amqsbcg not amqsbcgc. The c at the end of the sample name indicates it is the client version of the program.