I am working with a development team that is having problems receiving
messages from an upstream system. They have a fairly well proven receiving
component (in service for a couple of years), coded in java, and have just
started to use it to interface with a new counterparty.
In their code they
Hi all - posted for a colleague in the hope someone knows the answer off the top of their head:
...Has anybody actually gotten q to send very large messages?
If I try using various files it either splits it into lines or gets a Hconn error.
% ./q -oBLAST -m minbar -=999 -f q
MQSeries Q
Lizette - from the 5.2 Intercommunication manual, the section on
Sequential retrieval of messages
... If an application puts a sequence of messages to the same destination
queue, those messages can
be retrieved in sequence by a single application with a sequence of MQGET
operations, if the
Hi Rebecca - that's TCP return code 125:
egrep 125 /usr/include/sys/errno.h
#define EADDRINUSE 125 /* Address already in use */
Then once you have the symbolic macro name more explanation of the error
return is available via man -s 2 intro, which documents the syscall
interface.
...
Erik
AMQ6175: The system could not dynamically load the library
/opt/mqm/mwas/xatm/ora8swit. The error message was ld.so.1: amqzxma0:
fatal:
libucb.so.1: open failed: No such file or directory. The Queue Manager
will
continue without this module.
It looks as if the file
Even if you havn't had the problem, it would be great to get confirmed
that someone have succeeded to send 4MB messages using JMS to attach
to a Solaris queue manager - binding mode or tcpip mode.
Johan
I assume you have checked that the default 4Mb message size limits
have been
