Re: Newbie question - MQSeries on Linux rh9 - MQCONN failed (Reason = 2059)
Hi T.Rob,
Thanks for the reply. This is a local
connection.Here are snippets form both Perl modules that are generating
theerrors. I can see that the first bit has no error handling at all. I
need to find out if the problem is in the code or with the install of
MQSeries.
/usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/MQSeries/Queue.pm
72 # We'll need a Queue Manager, one way or
another. 73
# 74 # NOTE: if nothing is
given, then the MQSeries::QueueManager
75 # constructor will assume you want the "default"
QM. 76
# 77 if ( ref
$args{QueueManager} ) {
78 if (
$args{QueueManager}-isa("MQSeries::QueueManager") )
{
79
$self-{QueueManager} = $args{QueueManager};
80 } else
{
81
$self-{Carp}-("Invalid argument: 'QueueManager' must be an
MQSeries::QueueManager object");
82
return;
83 }
84 } else {
85 $self-{QueueManager} =
MQSeries::QueueManager-new
86
(
87
QueueManager
= $args{QueueManager},
88
Carp
= $self-{Carp},
89
) or return;
90 } 91
92
#
/usr/lib/perl5/site_perl/5.8.0/JEFCO/MQ.pm
218 sub open
{ 219 my $self =
shift(); 220 my $l =
$self-logger(); 221 my $osubheader =
$l-subheader(); 222
$l-subheader(ref($self) . "::open()"); 223
224 my $qn =
$self-q(); 225 unless (defined($qn))
{ 226 $qn =
MQSeries::Queue-new("QueueManager" =
$self-QueueManagerName(),
227
"Queue" =
$self-QueueName(),
228
"CloseOptions" = MQSeries::MQCO_NONE,
229
"NoAutoOpen" = 1);
230 unless (defined($qn)) {
231 $l-error("Unable to instantiate
MQSeries::Queue object.\n");
232 die("Unable to instantiate
MQSeries::Queue object."); 233
} 234 unless
($qn-Open("Options" =
$self-OpenOptions(),
235
"RetryCount" =
$self-OpenRetryCount(),
236
"RetrySleep" = $self-OpenRetrySleep()))
{ 237 my $reason =
$self-reasons($qn);
238 $l-error("Unable to open to queue: "
..
239
$self-QueueName(), "$reason");
240 } else {
241 $self-q($qn);
242 $l-info(1, "Opened",
$self-QueueName(), "on", $self-QueueManagerName(),
243
",", $self-QueueServerName(), "as a",
$self-Mode()); 244
} 245 } 246
247
$l-subheader($osubheader); 248
return($self); 249 }
From: MQSeries List
[mailto:[EMAIL PROTECTED] On Behalf Of Wyatt, T
RobSent: Thursday, October 21, 2004 4:14 PMTo:
[EMAIL PROTECTED]Subject: Re: Newbie question - MQSeries on
Linux rh9 - MQCONN failed (Reason = 2059)
Tad,
Would
help greatly to know whether this is a local connection or a client
connection. Can you provide the relevant code snippets just prior to line
232? We need to see what values are passed to the
MQSeries::QueueManager-new routine. If the hash uses variables instead
of hard-coded values, you may need to add a few lines (temporarily, at least) to
dump the values.
Can't
believe the code keeps going after it can't instantiate the QMgr. You'd
expect something more like...
$QMgr
= MQSeries::QueueManager-new (
QueueManager = $QMName,
ClientConn = { 'ChannelName' =
$Channel,
'TransportType' =
'TCP',
'ConnectionName' =
"$IPAddress($Port)",
},
AutoConnect = 0, ) or
die("!-- Unable to instantiate QMgr object for $QMName
--\n");
$QMgr-Connect() or die("Unable
to connect to $QMName at $IPAddress($Port) on $Channel: ",
MQReasonToText($QMgr-Reason()), "\n");}
Notice
in the code snippet above, instantiating the QMgr object and connecting to the
QMgr are separated into two different calls for better error handling.
Then if the connect fails, it displays what parameters were used for the
connect.
--
T.Rob
-Original Message-From: MQSeries List
[mailto:[EMAIL PROTECTED]On Behalf Of Tad
PerilloSent: Thursday, October 21, 2004 3:39 PMTo:
[EMAIL PROTECTED]Subject: Newbie question - MQSeries on Linux
rh9 - MQCONN failed (Reason = 2059)
I just started a
new job and one of the first things I have to do is migrate MQSeries running
on Solaris 8 to a Linux redhat 9 box. I finally got MQ to allow me to create a
queue but when I execute my program I get the following
errors:
= Starting
get_prices.pl, release 1.1, pid 18992, 10/21/2004 15:02:41
=
Log
file:
/usr/home/harbor/logs/get_prices.pl.1021Exit
time: 22:00Poll
rate: 0
secondsRevision: 1.1, 10/25/01
14:05:37Paging:
yesLog Level: 2Quote Frequency
(secs):
5Echo:
0Mqsc Cmd: rsh hspapp03
/opt/mqm/bin/runmqsc
qm.hspprod01Mode:
read/write (2 processes)MQCONN failed (Reason = 2059) (Queue manager not
available for connection.) at
/usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/MQSeries/Queue.pm line
85Unable to instantiate MQSeries::Queue object. at
/usr/lib/perl5/site_perl/5.8.0/JEFCO/MQ.pm line 232.
- Clear input
Q APP.ILX.INT1.IN failed, reading til empty
- Entering
ReadTilEmpty, pid 18992, input Q APP.ILX.INT1.IN
- Making
JEFCO::MQ::Reader: Server:
APP.HSPPROD01/TC
Re: Newbie question - MQSeries on Linux rh9 - MQCONN failed (Reason = 2059)
Does the MQ Explorer connect to this qmgr? Try
connecting with the MQ Client, to see if your qmgr is
good. Maybe from a remote machine.
--- Tad Perillo [EMAIL PROTECTED] wrote:
Hi T.Rob,
Thanks for the reply. This is a local connection.
Here are snippets form
both Perl modules that are generating the errors. I
can see that the
first bit has no error handling at all. I need to
find out if the
problem is in the code or with the install of
MQSeries.
/usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/MQSeries/Queue.pm
72 # We'll need a Queue Manager, one way or
another.
73 #
74 # NOTE: if nothing is given, then the
MQSeries::QueueManager
75 # constructor will assume you want the
default QM.
76 #
77 if ( ref $args{QueueManager} ) {
78 if (
$args{QueueManager}-isa(MQSeries::QueueManager)
) {
79 $self-{QueueManager} =
$args{QueueManager};
80 } else {
81 $self-{Carp}-(Invalid
argument: 'QueueManager'
must be an MQSeries::QueueManager object);
82 return;
83 }
84 } else {
85 $self-{QueueManager} =
MQSeries::QueueManager-new
86 (
87QueueManager =
$args{QueueManager},
88Carp =
$self-{Carp},
89 ) or return;
90 }
91
92 #
/usr/lib/perl5/site_perl/5.8.0/JEFCO/MQ.pm
218 sub open {
219 my $self = shift();
220 my $l = $self-logger();
221 my $osubheader = $l-subheader();
222 $l-subheader(ref($self) . ::open());
223
224 my $qn = $self-q();
225 unless (defined($qn)) {
226 $qn =
MQSeries::Queue-new(QueueManager =
$self-QueueManagerName(),
227Queue
=
$self-QueueName(),
228
CloseOptions =
MQSeries::MQCO_NONE,
229NoAutoOpen
= 1);
230 unless (defined($qn)) {
231 $l-error(Unable to instantiate
MQSeries::Queue
object.\n);
232 die(Unable to instantiate
MQSeries::Queue object.);
233 }
234 unless ($qn-Open(Options =
$self-OpenOptions(),
235 RetryCount =
$self-OpenRetryCount(),
236 RetrySleep =
$self-OpenRetrySleep())) {
237 my $reason = $self-reasons($qn);
238 $l-error(Unable to open to queue:
.
239 $self-QueueName(),
$reason);
240 } else {
241 $self-q($qn);
242 $l-info(1, Opened,
$self-QueueName(), on,
$self-QueueManagerName(),
243,,
$self-QueueServerName(), as a,
$self-Mode());
244 }
245 }
246
247 $l-subheader($osubheader);
248 return($self);
249 }
From: MQSeries List [mailto:[EMAIL PROTECTED]
On Behalf Of Wyatt,
T Rob
Sent: Thursday, October 21, 2004 4:14 PM
To: [EMAIL PROTECTED]
Subject: Re: Newbie question - MQSeries on Linux rh9
- MQCONN failed
(Reason = 2059)
Tad,
Would help greatly to know whether this is a local
connection or a
client connection. Can you provide the relevant
code snippets just
prior to line 232? We need to see what values are
passed to the
MQSeries::QueueManager-new routine. If the hash
uses variables instead
of hard-coded values, you may need to add a few
lines (temporarily, at
least) to dump the values.
Can't believe the code keeps going after it can't
instantiate the QMgr.
You'd expect something more like...
$QMgr = MQSeries::QueueManager-new (
QueueManager = $QMName,
ClientConn = { 'ChannelName'=
$Channel,
'TransportType' = 'TCP',
'ConnectionName' =
$IPAddress($Port),
},
AutoConnect = 0,
) or die(!-- Unable to instantiate QMgr object
for $QMName
--\n);
$QMgr-Connect()
or die(Unable to connect to $QMName at
$IPAddress($Port) on
$Channel: , MQReasonToText($QMgr-Reason()), \n);
}
Notice in the code snippet above, instantiating the
QMgr object and
connecting to the QMgr are separated into two
different calls for better
error handling. Then if the connect fails, it
displays what parameters
were used for the connect.
-- T.Rob
-Original Message-
From: MQSeries List
[mailto:[EMAIL PROTECTED] Behalf Of
Tad Perillo
Sent: Thursday, October 21, 2004 3:39 PM
To: [EMAIL PROTECTED]
Subject: Newbie question - MQSeries on Linux
rh9 - MQCONN failed
(Reason = 2059)
I just started a new job and one of the
first things I have to
do is migrate MQSeries running on Solaris 8 to a
Linux redhat 9 box. I
finally got MQ to allow me to create a queue but
when I execute my
program I
Re: Newbie question - MQSeries on Linux rh9 - MQCONN failed (Reason = 2059)
Make sure that you have thread compatibility
sorted out.
Also want to make sure that you have
the correct assume kernel level.
See this link:
http://www-1.ibm.com/support/docview.wss?uid=swg21110096
http://www-106.ibm.com/developerworks/forums/dw_expandTree.jsp?thread=47783forum=160cat=5message=3166155
http://www-6.ibm.com/jp/software/websphere/developer/tecflash/data/19/readme.txt
Rex Ballard - Certified IT Architect
908-578-6803, [EMAIL PROTECTED]
Christopher Warneke [EMAIL PROTECTED]
Sent by: MQSeries List [EMAIL PROTECTED]
10/22/2004 11:13 AM
Please respond to
MQSeries List
To
[EMAIL PROTECTED]
cc
Subject
Re: Newbie question - MQSeries
on Linux rh9 - MQCONN failed
(Reason = 2059)
Does the MQ Explorer connect to this qmgr? Try
connecting with the MQ Client, to see if your qmgr is
good. Maybe from a remote machine.
--- Tad Perillo [EMAIL PROTECTED]
wrote:
Hi T.Rob,
Thanks for the reply. This is a local connection.
Here are snippets form
both Perl modules that are generating the errors. I
can see that the
first bit has no error handling at all. I need to
find out if the
problem is in the code or with the install of
MQSeries.
/usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/MQSeries/Queue.pm
72 # We'll need a Queue Manager,
one way or
another.
73 #
74 # NOTE: if nothing is given,
then the
MQSeries::QueueManager
75 # constructor will assume you
want the
default QM.
76 #
77 if ( ref $args{QueueManager}
) {
78 if (
$args{QueueManager}-isa(MQSeries::QueueManager)
) {
79 $self-{QueueManager}
=
$args{QueueManager};
80 } else {
81 $self-{Carp}-(Invalid
argument: 'QueueManager'
must be an MQSeries::QueueManager object);
82 return;
83 }
84 } else {
85 $self-{QueueManager}
=
MQSeries::QueueManager-new
86 (
87 QueueManager
=
$args{QueueManager},
88 Carp
=
$self-{Carp},
89 )
or return;
90 }
91
92 #
/usr/lib/perl5/site_perl/5.8.0/JEFCO/MQ.pm
218 sub open {
219 my $self = shift();
220 my $l = $self-logger();
221 my $osubheader = $l-subheader();
222 $l-subheader(ref($self) . ::open());
223
224 my $qn = $self-q();
225 unless (defined($qn)) {
226 $qn =
MQSeries::Queue-new(QueueManager =
$self-QueueManagerName(),
227
Queue
=
$self-QueueName(),
228
CloseOptions =
MQSeries::MQCO_NONE,
229
NoAutoOpen
= 1);
230 unless (defined($qn)) {
231$l-error(Unable to
instantiate
MQSeries::Queue
object.\n);
232die(Unable to instantiate
MQSeries::Queue object.);
233 }
234 unless ($qn-Open(Options
=
$self-OpenOptions(),
235
RetryCount =
$self-OpenRetryCount(),
236
RetrySleep =
$self-OpenRetrySleep())) {
237my $reason = $self-reasons($qn);
238$l-error(Unable to
open to queue:
.
239
$self-QueueName(),
$reason);
240 } else {
241$self-q($qn);
242$l-info(1, Opened,
$self-QueueName(), on,
$self-QueueManagerName(),
243
,,
$self-QueueServerName(), as a,
$self-Mode());
244 }
245 }
246
247 $l-subheader($osubheader);
248 return($self);
249 }
From: MQSeries List [mailto:[EMAIL PROTECTED]
On Behalf Of Wyatt,
T Rob
Sent: Thursday, October 21, 2004 4:14 PM
To: [EMAIL PROTECTED]
Subject: Re: Newbie question - MQSeries on Linux rh9
- MQCONN failed
(Reason = 2059)
Tad,
Would help greatly to know whether this is a local
connection or a
client connection. Can you provide the relevant
code snippets just
prior to line 232? We need to see what values are
passed to the
MQSeries::QueueManager-new routine. If the hash
uses variables instead
of hard-coded values, you may need to add a few
lines (temporarily, at
least) to dump the values.
Can't believe the code keeps going after it can't
instantiate the QMgr.
You'd expect something more like...
$QMgr = MQSeries::QueueManager-new (
QueueManager = $QMName,
ClientConn = { 'ChannelName'
=
$Channel,
'TransportType' = 'TCP',
'ConnectionName' =
$IPAddress($Port),
},
AutoConnect = 0,
) or die(!-- Unable to instantiate QMgr object
for $QMName
--\n);
$QMgr-Connect()
or die(Unable to connect to $QMName
at
$IPAddress($Port) on
$Channel: , MQReasonToText($QMgr-Reason()), \n);
}
Notice in the code snippet above, instantiating the
QMgr object and
connecting to the QMgr are separated into two
different calls for better
error handling. Then if the connect fails, it
displays what parameters
were used for the connect.
-- T.Rob
-Original Message-
From: MQSeries List
[mailto:[EMAIL PROTECTED] Behalf Of
Tad Perillo
Sent: Thursday, October 21, 2004 3:39
PM
To: [EMAIL PROTECTED]
Subject
Re: Newbie question - MQSeries on Linux rh9 - MQCONN failed (Reason = 2059)
Tad, The module codedoesn't help diagnose this. Would need to see the relevant code from the get_prices.pl program - including the parms passed to the module. Interesting thing here is that, even though you say it's a local connection, the error log shows a server, QMgr name, channel and port like it is trying to use a client connection. Do you have a listener running on 1414? Is the SVRCONN channel 'APP.HSPPROD01'defined and enabled? It also appears from the log that get_prices.pl is remote shelling to hspapp03 to run an MQSC command on qm.hspprod01. Hard to say from the error log whether the error reported is happening locally or over at hspapp03. As others have suggested, a good approach here would be to see if a known-good program can access the QMgr. You might try amqsgetc using the same parameters that get_price.pl uses: 'APP.HSPPROD01/TCP/hspapp03(1414)'. -- T.Rob -Original Message-From: MQSeries List [mailto:[EMAIL PROTECTED]On Behalf Of Tad PerilloSent: Thursday, October 21, 2004 3:39 PMTo: [EMAIL PROTECTED]Subject: Newbie question - MQSeries on Linux rh9 - MQCONN failed (Reason = 2059) I just started a new job and one of the first things I have to do is migrate MQSeries running on Solaris 8 to a Linux redhat 9 box. I finally got MQ to allow me to create a queue but when I execute my program I get the following errors: = Starting get_prices.pl, release 1.1, pid 18992, 10/21/2004 15:02:41 = Log file: /usr/home/harbor/logs/get_prices.pl.1021Exit time: 22:00Poll rate: 0 secondsRevision: 1.1, 10/25/01 14:05:37Paging: yesLog Level: 2Quote Frequency (secs): 5Echo: 0Mqsc Cmd: rsh hspapp03 /opt/mqm/bin/runmqsc qm.hspprod01Mode: read/write (2 processes)MQCONN failed (Reason = 2059) (Queue manager not available for connection.) at /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/MQSeries/Queue.pm line 85Unable to instantiate MQSeries::Queue object. at /usr/lib/perl5/site_perl/5.8.0/JEFCO/MQ.pm line 232. - Clear input Q APP.ILX.INT1.IN failed, reading til empty - Entering ReadTilEmpty, pid 18992, input Q APP.ILX.INT1.IN - Making JEFCO::MQ::Reader: Server: APP.HSPPROD01/TCP/hspapp03(1414) Manager: qm.hspprod01 TimeOut: 0 Queue: APP.ILX.INT1.IN Logger: Log=HASH(0x804d1e0) * Unable to instantiate MQSeries::Queue object. ! Queue not open. Any ideas? Thanks in advance. Tad *** DISCLAIMER: All email(s) sent to and from Harborside Plus are recorded and archived, monitored, and/or disclosed to someone other than the recipient.. The information contained in this e-mail is, unless otherwise indicated, confidential and is intended solely for the use of the named addressee. Access, copying or re-use of the e-mail or any information contained therein by any other person is not authorized. If you are not the intended recipient please notify Harborside Plus immediately by returning the e-mail to Tad Perillo *** DISCLAIMER: All email(s) sent to and from Harborside Plus are recorded and archived, monitored, and/or disclosed to someone other than the recipient.. The information contained in this e-mail is, unless otherwise indicated, confidential and is intended solely for the use of the named addressee. Access, copying or re-use of the e-mail or any information contained therein by any other person is not authorized. If you are not the intended recipient please notify Harborside Plus immediately by returning the e-mail to Tad Perillo
Newbie question - MQSeries on Linux rh9 - MQCONN failed (Reason = 2059)
I just started a new job and one of the first things I have to do is migrate MQSeries running on Solaris 8 to a Linux redhat 9 box. I finally got MQ to allow me to create a queue but when I execute my program I get the following errors: = Starting get_prices.pl, release 1.1, pid 18992, 10/21/2004 15:02:41 = Log file: /usr/home/harbor/logs/get_prices.pl.1021Exit time: 22:00Poll rate: 0 secondsRevision: 1.1, 10/25/01 14:05:37Paging: yesLog Level: 2Quote Frequency (secs): 5Echo: 0Mqsc Cmd: rsh hspapp03 /opt/mqm/bin/runmqsc qm.hspprod01Mode: read/write (2 processes)MQCONN failed (Reason = 2059) (Queue manager not available for connection.) at /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/MQSeries/Queue.pm line 85Unable to instantiate MQSeries::Queue object. at /usr/lib/perl5/site_perl/5.8.0/JEFCO/MQ.pm line 232. - Clear input Q APP.ILX.INT1.IN failed, reading til empty - Entering ReadTilEmpty, pid 18992, input Q APP.ILX.INT1.IN - Making JEFCO::MQ::Reader: Server: APP.HSPPROD01/TCP/hspapp03(1414) Manager: qm.hspprod01 TimeOut: 0 Queue: APP.ILX.INT1.IN Logger: Log=HASH(0x804d1e0) * Unable to instantiate MQSeries::Queue object. ! Queue not open. Any ideas? Thanks in advance. Tad *** DISCLAIMER: All email(s) sent to and from Harborside Plus are recorded and archived, monitored, and/or disclosed to someone other than the recipient.. The information contained in this e-mail is, unless otherwise indicated, confidential and is intended solely for the use of the named addressee. Access, copying or re-use of the e-mail or any information contained therein by any other person is not authorized. If you are not the intended recipient please notify Harborside Plus immediately by returning the e-mail to Tad Perillo
Re: MQCONN FAILED
Title: RE: MQCONN FAILED Thanks everybody for the feedback. This one really get to me. I have checked all 3 logs, and 2 of them is empty since the last time the QMGR was sterted. The one under SYSTEM shows a channel going inactive at 18:00 the previous day because of disconnect interval, and active again on the day in question at 09:00. There is nothing inbetween at 06:10 when the error occured. On the sollution to retry the connect because the QMGR might still be coming up, doesn't help. The QMGR has been running since May 18 and this happened on June 25. Thank you Pieter Voges MQ Support Nedcor Limited Tel: (011) 881 4410 Sel: 083 6455 300 E-mail: [EMAIL PROTECTED] http://dotweb.it.nednet.co.za/link.asp?names=Voges,%20Pieter -Original Message- From: Robert Broderick [mailto:[EMAIL PROTECTED]] Sent: 08 July 2003 04:24 To: [EMAIL PROTECTED] Subject: Re: MQCONN FAILED With an extension on Peter's comments there are three error logs you need to look at. One in /errors and two in /qmgrs one under @SYSTEM/error and one under YOUR_QMGR/error. bobbee From: Potkay, Peter M (PLC, IT) [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: MQCONN FAILED Date: Tue, 8 Jul 2003 08:23:52 -0400 Did you check both the server level MQ error logs as well as the queue manager specific error logs? -Original Message- From: Voges, P. (Pieter) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 08, 2003 2:36 AM To: [EMAIL PROTECTED] Subject: MQCONN FAILED We ran into an interesting problem and if anybody can explain it or supply me with any info in this regard I will really appreciate it. We got a QMGR (5.1 - I know I must upgrade to 5.3) running on a AIX box(4.3). On the box there is an application running as a process that starts up in the morning and then firstly does a connect to the QMGR. Last week the app started and tried to connect. It got a 2059 (QMGR not available) return code. Later in the day the app was restarted and connected fine. My problem is that the QMGR had been running for a month when this happened. It was up and running on the first connect attempt. There was no intervention between the 2 attempts. There are no errors in the logs. It is a very low volume box so no default maximums was reached. Can anybody provide me with any possible causes or direct me to whatever else I can check. Thank you Pieter Voges MQ Support Nedcor Limited Tel: (011) 881 4410 Sel: 083 6455 300 E-mail: [EMAIL PROTECTED] http://dotweb.it.nednet.co.za/link.asp?names=Voges,%20Pieter http://dotweb.it.nednet.co.za/link.asp?names=Voges,%20Pieter _ This email and any accompanying attachments may contain confidential and proprietary information. This information is private and protected by law and, accordingly, if you are not the intended recipient, you are requested to delete this entire communication immediately and are notified that any disclosure, copying or distribution of or taking any action based on this information is prohibited. Emails cannot be guaranteed to be secure or free of errors or viruses. The sender does not accept any liability or responsibility for any interception, corruption, destruction, loss, late arrival or incompleteness of or tampering or interference with any of the information contained in this email or for its incorrect delivery or non-delivery for whatsoever reason or for its effect on any electronic device of the recipient. If verification of this email or any attachment is required, please request a hard-copy version. _ This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. _ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive This email and any accompanying attachments may contain confidential and proprietary information. This information is private and protected by law and, accordingly, if you are not the intended recipient, you are requested to delete this entire communication immediately and are notified that any disclosure, copying or distribution of or taking any action based on this information is prohibited. Emails cannot be guaranteed to be secure or free of errors or viruses. The sender does not accept any liability or responsibility for any interception, corruption, destruction, loss, late arrival
Re: MQCONN FAILED
Title: RE: MQCONN FAILED I have periodically seen similar symptoms on MQ v5.2.0, where MQ does NOT log incidents or outages consistently or the timestamps appear to be wrong. Upgrade to the latest CSD levels at v5.1 to seek resolution. This may not resolve your MQCONN problem but should restore a more consistent MQ logging picture for you. In turn, a more reliable logging environment may lead you to the answer to resolving your MQCONN problem. -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED]On Behalf Of Voges, P. (Pieter) Sent: Wednesday, July 09, 2003 4:14 AM To: [EMAIL PROTECTED] Subject: Re: MQCONN FAILED Thanks everybody for the feedback. This one really get to me. I have checked all 3 logs, and 2 of them is empty since the last time the QMGR was sterted. The one under SYSTEM shows a channel going inactive at 18:00 the previous day because of disconnect interval, and active again on the day in question at 09:00. There is nothing inbetween at 06:10 when the error occured. On the sollution to retry the connect because the QMGR might still be coming up, doesn't help. The QMGR has been running since May 18 and this happened on June 25. Thank you Pieter Voges MQ Support Nedcor Limited Tel: (011) 881 4410 Sel: 083 6455 300 E-mail: [EMAIL PROTECTED] http://dotweb.it.nednet.co.za/link.asp?names=Voges,%20Pieter -Original Message- From: Robert Broderick [mailto:[EMAIL PROTECTED]] Sent: 08 July 2003 04:24 To: [EMAIL PROTECTED] Subject: Re: MQCONN FAILED With an extension on Peter's comments there are three error logs you need to look at. One in /errors and two in /qmgrs one under @SYSTEM/error and one under YOUR_QMGR/error. bobbee From: Potkay, Peter M (PLC, IT) [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: MQCONN FAILED Date: Tue, 8 Jul 2003 08:23:52 -0400 Did you check both the server level MQ error logs as well as the queue manager specific error logs? -Original Message- From: Voges, P. (Pieter) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 08, 2003 2:36 AM To: [EMAIL PROTECTED] Subject: MQCONN FAILED We ran into an interesting problem and if anybody can explain it or supply me with any info in this regard I will really appreciate it. We got a QMGR (5.1 - I know I must upgrade to 5.3) running on a AIX box(4.3). On the box there is an application running as a process that starts up in the morning and then firstly does a connect to the QMGR. Last week the app started and tried to connect. It got a 2059 (QMGR not available) return code. Later in the day the app was restarted and connected fine. My problem is that the QMGR had been running for a month when this happened. It was up and running on the first connect attempt. There was no intervention between the 2 attempts. There are no errors in the logs. It is a very low volume box so no default maximums was reached. Can anybody provide me with any possible causes or direct me to whatever else I can check. Thank you Pieter Voges MQ Support Nedcor Limited Tel: (011) 881 4410 Sel: 083 6455 300 E-mail: [EMAIL PROTECTED] http://dotweb.it.nednet.co.za/link.asp?names=Voges,%20Pieter http://dotweb.it.nednet.co.za/link.asp?names=Voges,%20Pieter _ This email and any accompanying attachments may contain confidential and proprietary information. This information is private and protected by law and, accordingly, if you are not the intended recipient, you are requested to delete this entire communication immediately and are notified that any disclosure, copying or distribution of or taking any action based on this information is prohibited. Emails cannot be guaranteed to be secure or free of errors or viruses. The sender does not accept any liability or responsibility for any interception, corruption, destruction, loss, late arrival or incompleteness of or tampering or interference with any of the information contained in this email or for its incorrect delivery or non-delivery for whatsoever reason or for its effect on any electronic device of the recipient. If verification of this email or any attachment is required, please request a hard-copy version. _ This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. _ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail Instructions for managing your mailing list subscription are provided
MQCONN FAILED
Title: MQCONN FAILED We ran into an interesting problem and if anybody can explain it or supply me with any info in this regard I will really appreciate it. We got a QMGR (5.1 - I know I must upgrade to 5.3) running on a AIX box(4.3). On the box there is an application running as a process that starts up in the morning and then firstly does a connect to the QMGR. Last week the app started and tried to connect. It got a 2059 (QMGR not available) return code. Later in the day the app was restarted and connected fine. My problem is that the QMGR had been running for a month when this happened. It was up and running on the first connect attempt. There was no intervention between the 2 attempts. There are no errors in the logs. It is a very low volume box so no default maximums was reached. Can anybody provide me with any possible causes or direct me to whatever else I can check. Thank you Pieter Voges MQ Support Nedcor Limited Tel: (011) 881 4410 Sel: 083 6455 300 E-mail: [EMAIL PROTECTED] http://dotweb.it.nednet.co.za/link.asp?names=Voges,%20Pieter This email and any accompanying attachments may contain confidential and proprietary information. This information is private and protected by law and, accordingly, if you are not the intended recipient, you are requested to delete this entire communication immediately and are notified that any disclosure, copying or distribution of or taking any action based on this information is prohibited. Emails cannot be guaranteed to be secure or free of errors or viruses. The sender does not accept any liability or responsibility for any interception, corruption, destruction, loss, late arrival or incompleteness of or tampering or interference with any of the information contained in this email or for its incorrect delivery or non-delivery for whatsoever reason or for its effect on any electronic device of the recipient. If verification of this email or any attachment is required, please request a hard-copy version.
Re: MQCONN FAILED
Title: MQCONN FAILED Were there any netweork / TCP problems at that stage -Original Message-From: Voges, P. (Pieter) [mailto:[EMAIL PROTECTED]Sent: 08 July 2003 08:36To: [EMAIL PROTECTED]Subject: MQCONN FAILED We ran into an interesting problem and if anybody can explain it or supply me with any info in this regard I will really appreciate it. We got a QMGR (5.1 - I know I must upgrade to 5.3) running on a AIX box(4.3). On the box there is an application running as a process that starts up in the morning and then firstly does a connect to the QMGR. Last week the app started and tried to connect. It got a 2059 (QMGR not available) return code. Later in the day the app was restarted and connected fine. My problem is that the QMGR had been running for a month when this happened. It was up and running on the first connect attempt. There was no intervention between the 2 attempts. There are no errors in the logs. It is a very low volume box so no default maximums was reached. Can anybody provide me with any possible causes or direct me to whatever else I can check. Thank you Pieter Voges MQ Support Nedcor Limited Tel: (011) 881 4410 Sel: 083 6455 300 E-mail: [EMAIL PROTECTED] http://dotweb.it.nednet.co.za/link.asp?names=Voges,%20Pieter This email and any accompanying attachments may contain confidential and proprietary information. This information is private and protected by law and, accordingly, if you are not the intended recipient, you are requested to delete this entire communication immediately and are notified that any disclosure, copying or distribution of or taking any action based on this information is prohibited. Emails cannot be guaranteed to be secure or free of errors or viruses. The sender does not accept any liability or responsibility for any interception, corruption, destruction, loss, late arrival or incompleteness of or tampering or interference with any of the information contained in this email or for its incorrect delivery or non-delivery for whatsoever reason or for its effect on any electronic device of the recipient. If verification of this email or any attachment is required, please request a hard-copy version. For information about the Standard Bank group visit our web site www.standardbank.co.za Disclaimer and confidentiality note Everything in this e-mail and any attachments relating to the official business of the Standard Bank Group Limited is proprietary to the group. It is confidential, legally privileged and protected by law. Standard Bank does not own and endorse any other content. Views and opinions are those of the sender unless clearly stated as being that of the group.The person addressed in the e-mail is the sole authorised recipient. Please notify the sender immediately if it has unintentionally reached you and do not read, disclose or use the content in any way. Standard Bank can not assure that the integrity of this communication has been maintained nor that it is free of errors, virus, interception or interference. I
Re: MQCONN FAILED
Title: MQCONN FAILED That was my initial thought as well, but the app and the qmgr runs on the same AIX server Thank you Pieter VogesMQ SupportNedcor LimitedTel: (011) 881 4410Sel: 083 6455 300E-mail: [EMAIL PROTECTED] http://dotweb.it.nednet.co.za/link.asp?names=Voges,%20Pieter -Original Message-From: Kearns, Emile E [mailto:[EMAIL PROTECTED]Sent: 08 July 2003 09:05To: [EMAIL PROTECTED]Subject: Re: MQCONN FAILEDImportance: High Were there any netweork / TCP problems at that stage -Original Message-From: Voges, P. (Pieter) [mailto:[EMAIL PROTECTED]Sent: 08 July 2003 08:36To: [EMAIL PROTECTED]Subject: MQCONN FAILED We ran into an interesting problem and if anybody can explain it or supply me with any info in this regard I will really appreciate it. We got a QMGR (5.1 - I know I must upgrade to 5.3) running on a AIX box(4.3). On the box there is an application running as a process that starts up in the morning and then firstly does a connect to the QMGR. Last week the app started and tried to connect. It got a 2059 (QMGR not available) return code. Later in the day the app was restarted and connected fine. My problem is that the QMGR had been running for a month when this happened. It was up and running on the first connect attempt. There was no intervention between the 2 attempts. There are no errors in the logs. It is a very low volume box so no default maximums was reached. Can anybody provide me with any possible causes or direct me to whatever else I can check. Thank you Pieter Voges MQ Support Nedcor Limited Tel: (011) 881 4410 Sel: 083 6455 300 E-mail: [EMAIL PROTECTED] http://dotweb.it.nednet.co.za/link.asp?names=Voges,%20Pieter This email and any accompanying attachments may contain confidential and proprietary information. This information is private and protected by law and, accordingly, if you are not the intended recipient, you are requested to delete this entire communication immediately and are notified that any disclosure, copying or distribution of or taking any action based on this information is prohibited. Emails cannot be guaranteed to be secure or free of errors or viruses. The sender does not accept any liability or responsibility for any interception, corruption, destruction, loss, late arrival or incompleteness of or tampering or interference with any of the information contained in this email or for its incorrect delivery or non-delivery for whatsoever reason or for its effect on any electronic device of the recipient. If verification of this email or any attachment is required, please request a hard-copy version. For information about the Standard Bank group visit our web site www.standardbank.co.za Disclaimer and confidentiality note Everything in this e-mail and any attachments relating to the official business of the Standard Bank Group Limited is proprietary to the group. It is confidential, legally privileged and protected by law. Standard Bank does not own and endorse any other content. Views and opinions are those of the sender unless clearly stated as being that of the group.The person addressed in the e-mail is the sole authorised recipient. Please notify the sender immediately if it has unintentionally reached you and do not read, disclose or use the content in any way. Standard Bank can not assure that the integrity of this communication has been maintained nor that it is free of errors, virus, interception or interference. I This email and any accompanying attachments may contain confidential and proprietary information. This information is private and protected by law and, accordingly, if you are not the intended recipient, you are requested to delete this entire communication immediately and are notified that any disclosure, copying or distribution of or taking any action based on this information is prohibited. Emails cannot be guaranteed to be secure or free of errors or viruses. The sender does not accept any liability or responsibility for any interception, corruption, destruction, loss, late arrival or incompleteness of or tampering or interference with any of the information contained in this email or for its incorrect delivery or non-delivery for whatsoever reason or for its effect on any electronic device of the recipient. If verification of this email or any attachment is required, please request a hard-copy version.
Re: MQCONN FAILED
Title: MQCONN FAILED Did you check both the server level MQ error logs as well as the queue manager specific error logs? -Original Message-From: Voges, P. (Pieter) [mailto:[EMAIL PROTECTED]Sent: Tuesday, July 08, 2003 2:36 AMTo: [EMAIL PROTECTED]Subject: MQCONN FAILED We ran into an interesting problem and if anybody can explain it or supply me with any info in this regard I will really appreciate it. We got a QMGR (5.1 - I know I must upgrade to 5.3) running on a AIX box(4.3). On the box there is an application running as a process that starts up in the morning and then firstly does a connect to the QMGR. Last week the app started and tried to connect. It got a 2059 (QMGR not available) return code. Later in the day the app was restarted and connected fine. My problem is that the QMGR had been running for a month when this happened. It was up and running on the first connect attempt. There was no intervention between the 2 attempts. There are no errors in the logs. It is a very low volume box so no default maximums was reached. Can anybody provide me with any possible causes or direct me to whatever else I can check. Thank you Pieter Voges MQ Support Nedcor Limited Tel: (011) 881 4410 Sel: 083 6455 300 E-mail: [EMAIL PROTECTED] http://dotweb.it.nednet.co.za/link.asp?names=Voges,%20Pieter This email and any accompanying attachments may contain confidential and proprietary information. This information is private and protected by law and, accordingly, if you are not the intended recipient, you are requested to delete this entire communication immediately and are notified that any disclosure, copying or distribution of or taking any action based on this information is prohibited. Emails cannot be guaranteed to be secure or free of errors or viruses. The sender does not accept any liability or responsibility for any interception, corruption, destruction, loss, late arrival or incompleteness of or tampering or interference with any of the information contained in this email or for its incorrect delivery or non-delivery for whatsoever reason or for its effect on any electronic device of the recipient. If verification of this email or any attachment is required, please request a hard-copy version. This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies.
Re: MQCONN FAILED
Title: MQCONN FAILED Hi Pieter, I've seen a similar problem once or twice before. We too have MQ applications that start up when the system starts. The MQ services also start at this time (they start first). On very rare occasions, it may take longer than usual for the QMgr processes to start and be ready to accept requests from applications. When this occurs, the application will get a 2059. I suggest changing the application to monitor for a 2059, wait a minute and then try to connect again; maybe try this 3 or 4 times before executing any error handling or ending the application. This happened to us on an AS/400. There happened to be a test queuecontaining alarge number of persistent messages, andon startup, MQ did its media recovery thing, which on the AS/400 involves journal receivers. My theory was that this extra processing took time, which caused the QMgr to not be ready as quickly as usual. This is one possible explanation. Lynn -Original Message-From: MQSeries List [mailto:[EMAIL PROTECTED]On Behalf Of Voges, P. (Pieter)Sent: Tuesday, July 08, 2003 2:36 AMTo: [EMAIL PROTECTED]Subject: MQCONN FAILED We ran into an interesting problem and if anybody can explain it or supply me with any info in this regard I will really appreciate it. We got a QMGR (5.1 - I know I must upgrade to 5.3) running on a AIX box(4.3). On the box there is an application running as a process that starts up in the morning and then firstly does a connect to the QMGR. Last week the app started and tried to connect. It got a 2059 (QMGR not available) return code. Later in the day the app was restarted and connected fine. My problem is that the QMGR had been running for a month when this happened. It was up and running on the first connect attempt. There was no intervention between the 2 attempts. There are no errors in the logs. It is a very low volume box so no default maximums was reached. Can anybody provide me with any possible causes or direct me to whatever else I can check. Thank you Pieter Voges MQ Support Nedcor Limited Tel: (011) 881 4410 Sel: 083 6455 300 E-mail: [EMAIL PROTECTED] http://dotweb.it.nednet.co.za/link.asp?names=Voges,%20Pieter This email and any accompanying attachments may contain confidential and proprietary information. This information is private and protected by law and, accordingly, if you are not the intended recipient, you are requested to delete this entire communication immediately and are notified that any disclosure, copying or distribution of or taking any action based on this information is prohibited. Emails cannot be guaranteed to be secure or free of errors or viruses. The sender does not accept any liability or responsibility for any interception, corruption, destruction, loss, late arrival or incompleteness of or tampering or interference with any of the information contained in this email or for its incorrect delivery or non-delivery for whatsoever reason or for its effect on any electronic device of the recipient. If verification of this email or any attachment is required, please request a hard-copy version.
Re: MQCONN FAILED
With an extension on Peter's comments there are three error logs you need to look at. One in /errors and two in /qmgrs one under @SYSTEM/error and one under YOUR_QMGR/error. bobbee From: Potkay, Peter M (PLC, IT) [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: MQCONN FAILED Date: Tue, 8 Jul 2003 08:23:52 -0400 Did you check both the server level MQ error logs as well as the queue manager specific error logs? -Original Message- From: Voges, P. (Pieter) [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 08, 2003 2:36 AM To: [EMAIL PROTECTED] Subject: MQCONN FAILED We ran into an interesting problem and if anybody can explain it or supply me with any info in this regard I will really appreciate it. We got a QMGR (5.1 - I know I must upgrade to 5.3) running on a AIX box(4.3). On the box there is an application running as a process that starts up in the morning and then firstly does a connect to the QMGR. Last week the app started and tried to connect. It got a 2059 (QMGR not available) return code. Later in the day the app was restarted and connected fine. My problem is that the QMGR had been running for a month when this happened. It was up and running on the first connect attempt. There was no intervention between the 2 attempts. There are no errors in the logs. It is a very low volume box so no default maximums was reached. Can anybody provide me with any possible causes or direct me to whatever else I can check. Thank you Pieter Voges MQ Support Nedcor Limited Tel: (011) 881 4410 Sel: 083 6455 300 E-mail: [EMAIL PROTECTED] http://dotweb.it.nednet.co.za/link.asp?names=Voges,%20Pieter http://dotweb.it.nednet.co.za/link.asp?names=Voges,%20Pieter _ This email and any accompanying attachments may contain confidential and proprietary information. This information is private and protected by law and, accordingly, if you are not the intended recipient, you are requested to delete this entire communication immediately and are notified that any disclosure, copying or distribution of or taking any action based on this information is prohibited. Emails cannot be guaranteed to be secure or free of errors or viruses. The sender does not accept any liability or responsibility for any interception, corruption, destruction, loss, late arrival or incompleteness of or tampering or interference with any of the information contained in this email or for its incorrect delivery or non-delivery for whatsoever reason or for its effect on any electronic device of the recipient. If verification of this email or any attachment is required, please request a hard-copy version. _ This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. _ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: MQCONN FAILED
Check for another possibility, whichmight look very silly, but its bound to happen. Your app shouldtake in an argument which is the QM name along with host of other things. You did NOT specify the QMname and the app tried to connect to the default QM, since none was specified.You have a default QM defined, but not started. You would get a 2059. I know this is specifics, but since you did not mention any of the above supportive information, i amassuming this one scenario to be a possibility. Cheers Kumar ---Original Message--- From: MQSeries List Date: Tuesday, July 08, 2003 10:26:47 AM To: [EMAIL PROTECTED] Subject: Re: MQCONN FAILED With an extension on Peter's comments there are three error logs you need to look at. One in /errors and two in /qmgrs one under @SYSTEM/error and one under YOUR_QMGR/error. bobbee From: "Potkay, Peter M (PLC, IT)" [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: MQCONN FAILED Date: Tue, 8 Jul 2003 08:23:52 -0400 Did you check both the server level MQ error logs as well as the queue manager specific error logs? -Original Message- From: Voges, P. (Pieter) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 08, 2003 2:36 AM To: [EMAIL PROTECTED] Subject: MQCONN FAILED We ran into an interesting problem and if anybody can explain it or supply me with any info in this regard I will really appreciate it. We got a QMGR (5.1 - I know I must upgrade to 5.3) running on a AIX box(4.3). On the box there is an application running as a process that starts up in the morning and then firstly does a connect to the QMGR. Last week the app started and tried to connect. It got a 2059 (QMGR not available) return code. Later in the day the app was restarted and connected fine. My problem is that the QMGR had been running for a month when this happened. It was up and running on the first connect attempt. There was no intervention between the 2 attempts. There are no errors in the logs. It is a very low volume box so no default maximums was reached. Can anybody provide me with any possible causes or direct me to whatever else I can check. Thank you Pieter Voges MQ Support Nedcor Limited Tel: (011) 881 4410 Sel: 083 6455 300 E-mail: [EMAIL PROTECTED] http://dotweb.it.nednet.co.za/link.asp?names=Voges,%20Pieter http://dotweb.it.nednet.co.za/link.asp?names=Voges,%20Pieter _ This email and any accompanying attachments may contain confidential and proprietary information. This information is private and protected by law and, accordingly, if you are not the intended recipient, you are requested to delete this entire communication immediately and are notified that any disclosure, copying or distribution of or taking any action based on this information is prohibited. Emails cannot be guaranteed to be secure or free of errors or viruses. The sender does not accept any liability or responsibility for any interception, corruption, destruction, loss, late arrival or incompleteness of or tampering or interference with any of the information contained in this email or for its incorrect delivery or non-delivery for whatsoever reason or for its effect on any electronic device of the recipient. If verification of this email or any attachment is required, please request a hard-copy version. _ This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. _ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive . IncrediMail - Email has finally evolved - Click Here
