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 IndexIBM MQ Installation/Configuration SupportWhat kind situation the listener would be down?

Post new topicReply to topic
What kind situation the listener would be down? View previous topic :: View next topic
Author Message
jackysu
PostPosted: Tue Dec 11, 2001 4:21 am Post subject: Reply with quote

Novice

Joined: 10 Dec 2001
Posts: 13

Dear Support,
We have two queue managers and two channels(send and reciver) in the same machine(AIX) and after we start both queue managers and then start both channels running a period.
But channel after running a few minutes that
both channel service was down and use ping command appear failed.so would you give me
right direction to find out the rootcause?
Regards!

Jacky Su
Pershing Systems Corporation
RS/6000 Service Provider
Back to top
View user's profile Send private message Visit poster's website MSN Messenger
StefanSievert
PostPosted: Tue Dec 11, 2001 11:45 am Post subject: Reply with quote

Partisan

Joined: 28 Oct 2001
Posts: 333
Location: San Francisco

Jacky,
what does your configuration look like? Can you post the MQSeries-related contents of the following files/command output:

1) /etc/inetd.conf (The lines containing MQ)
2) /etc/services (The lines containing MQ)
3) DISPLAY CHL(*sender*) ALL on both QM's
4) DISPLAY CHL(*rcvr*) ALL on both QM's
5) The AMQERR01.LOG lines form the time the channels started/stopped

Have you used two different IP ports for your two queue managers?

Please provide some more details about your setup so we can help you.

Cheers,
Stefan


_________________
Stefan Sievert
IBM Certified * WebSphere MQ
Back to top
View user's profile Send private message
jackysu
PostPosted: Thu Dec 13, 2001 4:37 am Post subject: Reply with quote

Novice

Joined: 10 Dec 2001
Posts: 13

Dear Stefan,
First appreciate your support and after I collate some MQ information that you can see folloqing explain our environment.
1. Operation System: AIX 4.3.3
2. MQ Series Version: 5.2.0.2
3. Hosname: labg40
Source Side(in the labg40)
1. First Queue Manager :source.queue.manager
2. Channel Name: source.to.target
3. Local Queue: target.queue.manager
4. XMITQ: target.queue.manager
Target Side(in the labg40 machine too)
1. Second Queue Manager:target.queue.manager
2. Channel Name:target.to.source
3. Local queue: source.queue.manager
4. XMITQ: source.queue.manager


The folllowing setting is detail information:
Source side channel definition:
Sender Side:
CHANNEL(source.to.target) CHLTYPE(SDR)
TRPTYPE(TCP) DESCR( )
XMITQ(target.queue.manager) MCANAME( )
MODENAME( ) TPNAME( )
BATCHSZ(50) DISCINT(6000)
SHORTRTY(10) SHORTTMR(60)
LONGRTY(999999999) LONGTMR(1200)
SCYEXIT( ) SEQWRAP(999999999)
MAXMSGL(4194304) CONVERT(NO)
SCYDATA( ) USERID( )
PASSWORD( ) MCATYPE(PROCESS)
CONNAME(LABG40) HBINT(300)
BATCHINT(0) NPMSPEED(FAST)
MCAUSER( ) ALTDATE(2001-12-13)
ALTTIME(11.28.51)
MSGEXIT( )
SENDEXIT( )
RCVEXIT( )
MSGDATA( )
SENDDATA( )
RCVDATA( )

Receiver Side:
CHANNEL(target.to.source) CHLTYPE(RCVR)
TRPTYPE(TCP) DESCR( )
BATCHSZ(50) SCYEXIT( )
SEQWRAP(999999999) MAXMSGL(4194304)
PUTAUT(DEF) SCYDATA( )
MREXIT( ) MRDATA( )
MRRTY(10) MRTMR(1000)
HBINT(300) NPMSPEED(FAST)
MCAUSER( ) ALTDATE(2001-12-13)
ALTTIME(11.29.11)
MSGEXIT( )
SENDEXIT( )
RCVEXIT( )
MSGDATA( )
SENDDATA( )
RCVDATA( )

The target side channel definition:
Sender side:
CHANNEL(target.to.source) CHLTYPE(SDR)
TRPTYPE(TCP) DESCR( )
XMITQ(source.queue.manager) MCANAME( )
MODENAME( ) TPNAME( )
BATCHSZ(50) DISCINT(6000)
SHORTRTY(10) SHORTTMR(60)
LONGRTY(999999999) LONGTMR(1200)
SCYEXIT( ) SEQWRAP(999999999)
MAXMSGL(4194304) CONVERT(NO)
SCYDATA( ) USERID( )
PASSWORD( ) MCATYPE(PROCESS)
CONNAME(LABG40) HBINT(300)
BATCHINT(0) NPMSPEED(FAST)
MCAUSER( ) ALTDATE(2001-12-13)
ALTTIME(11.30.07)
MSGEXIT( )
SENDEXIT( )
RCVEXIT( )
MSGDATA( )
SENDDATA( )
RCVDATA( )

Receiver Side:
CHANNEL(source.to.target) CHLTYPE(RCVR)
TRPTYPE(TCP) DESCR( )
BATCHSZ(50) SCYEXIT( )
SEQWRAP(999999999) MAXMSGL(4194304)
PUTAUT(DEF) SCYDATA( )
MREXIT( ) MRDATA( )
MRRTY(10) MRTMR(1000)
HBINT(300) NPMSPEED(FAST)
MCAUSER( ) ALTDATE(2001-12-13)
ALTTIME(11.30.26)
MSGEXIT( )
SENDEXIT( )
RCVEXIT( )
MSGDATA( )
SENDDATA( )
RCVDATA( )

After we issued the "runmqlsr" and "runmqchl" command that MQ appear the following message " $ 12/13/01 19:14:10 AMQ9218: The TCP/IP listener program could not bind to por
t number 1414.
12/13/01 19:14:10 AMQ9218: The TCP/IP listener program could not bind to port
number 1414."

The following is MQ related file description:
/etc/inetd.conf file description:
MQSeries stream tcp nowait mqm /usr/mqm/bin/amqcrsta ampcrsta
/etc/services file description:
MQSeries 1414/tcp #MQSeries
AMQERR01.LOG file description:


12/13/01 11:54:02
AMQ6209: An unexpected asynchronous signal (2) has been received and ignored.

EXPLANATION:
Process 18776 received an unexpected asynchronous signal and ignored it. This
has not caused an error but the source of the signal should be determined as it
is likely that the signal has been generated externally to MQSeries. Use the
UNIX system command kill with option -l to determine the symbolic name for
signal 2.
ACTION:
Determine the source of the signal and prevent it from re-occurring.
-------------------------------------------------------------------------------
12/13/01 11:54:02
AMQ6183: An internal MQSeries error has occurred.

EXPLANATION:
An error has been detected, and the MQSeries error recording routine has been
called. The failing process is process 18776.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.

PS: The both Queue Manager was the same machine so please give me a hand to solve this problem Thanks!

Thanks your support!




Jacky Su
Back to top
View user's profile Send private message Visit poster's website MSN Messenger
StefanSievert
PostPosted: Thu Dec 13, 2001 12:23 pm Post subject: Reply with quote

Partisan

Joined: 28 Oct 2001
Posts: 333
Location: San Francisco

Jacky,
it is pretty clear why you see the behavior on your machine.
You need to have a dedicated port for every queue manager (and listener) on a single machine because a listener will exclusively bind to that port.
Here's what you need to update. I removed all the attributes that don't need to be changed. If using your hostname in the CONNAME doesn't work, try using CONNAME('loacalhost(port)').
--------------------------
Sender Side:
CHANNEL(source.to.target) CHLTYPE(SDR)
TRPTYPE(TCP)
CONNAME('LABG40(1414)')

The target side channel definition:
Sender side:
CHANNEL(target.to.source) CHLTYPE(SDR)
TRPTYPE(TCP)
CONNAME('LABG40(1415)')
--------------------------
/etc/inetd.conf file description should look like:
MQSeries_01 stream tcp nowait mqm /usr/mqm/bin/amqcrsta amqcrsta -m target.queue.manager
MQSeries_02 stream tcp nowait mqm /usr/mqm/bin/amqcrsta amqcrsta -m source.queue.manager

(I don't know if it was just a typo but you had ampcrsta at the end of the line, instead of amqcrsta)

/etc/services file description should look like:
MQSeries_01 1414/tcp #MQSeries service for target.queue.manager
MQSeries_02 1415/tcp #MQSeries service for source.queue.manager

Don't forget to refresh inetd after you've done the changes.
Hopefully, this should solve your problem.
Good luck!
Stefan

_________________
Stefan Sievert
IBM Certified * MQSeries

[ This Message was edited by: StefanSievert on 2001-12-13 12:24 ]

[ This Message was edited by: StefanSievert on 2001-12-13 15:07 ]
Back to top
View user's profile Send private message
jackysu
PostPosted: Mon Dec 17, 2001 2:40 am Post subject: Reply with quote

Novice

Joined: 10 Dec 2001
Posts: 13

Dear Support,

Marry X'mas,wish you have a new year!
After I modified these files but MQ still occured errors,so could you analysis folowing error? I think maybe is naming error? right?
PS:
After I modified that restart listener and channel service and command as below:

From Sender side:
runmqlsr -t TCP -m source.queue.manager
runmqchl -c source.to.target -m source.queue.manager

From Receiver Side:
runmqlsr -t TCP -m target.queue.manager
runmqchl -c target.to.source -m target.queue.manager
12/17/01 17:13:14
AMQ9547: Type of remote channel not suitable for action requested.

EXPLANATION:
The operation requested cannot be performed because channel 'source.to.target'
on the remote machine is not of a suitable type. For example, if the local
channel is defined as a sender the remote machine must define its channel as
either a receiver or requester.
ACTION:
Check that the channel name is specified correctly. If it is, check that the
remote channel has been defined correctly.
-------------------------------------------------------------------------------
12/17/01 17:13:14
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'source.to.target' ended abnormally.
ACTION:
Look at previous error messages for channel program 'source.to.target' in the
error files to determine the cause of the failure.


Regard !


Marry X'mas


Jacky Su
Back to top
View user's profile Send private message Visit poster's website MSN Messenger
StefanSievert
PostPosted: Mon Dec 17, 2001 11:42 am Post subject: Reply with quote

Partisan

Joined: 28 Oct 2001
Posts: 333
Location: San Francisco

Jacky,
first of all, you wrote:

>From Sender side:
>runmqlsr -t TCP -m source.queue.manager

I thought you were running on AIX!? If you have configured your inetd correctly (/etc/services & /etc/inetd.conf), it will start up your listener automagically. So, don't use the runmqlsr command line listener.

>The operation requested cannot be performed
>because channel 'source.to.target'
>on the remote machine is not of a suitable
>type.

It looks like your definitions of the channel 'source.to.target' are inconsistent or your port assignement for the queue managers is not correct. Can you do the following:
On both queue managers, start runmqsc (be sure to specify the queue manager name if you have two qmgrs on one box) and issue the following commands:
DIS CHL('source*') ALL
and
DIS CHL('target*') ALL
and post the output stating which output is from what queue manager. Please also cut and paste the two lines from /etc/services and /etc/inetd.conf that contain your MQ settings.
If you want to read a bit and find out yourself what's going wrong, check the Intercommunication guide. It contains step by step instructions on how to establish two way communications between two queue managers.
Cheers,
Stefan

_________________
Stefan Sievert
IBM Certified * WebSphere MQ
Back to top
View user's profile Send private message
Display posts from previous:
Post new topicReply to topic Page 1 of 1

MQSeries.net Forum IndexIBM MQ Installation/Configuration SupportWhat kind situation the listener would be down?
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.