| Author |
Message
|
| sarbajit |
 Posted: Mon Aug 11, 2003 8:15 am Post subject: MQ in Solaris |
 |
|
Acolyte
Joined: 22 May 2003
Posts: 53
|
Hi All,
I am starting the channels in Solaris using the following command "nohup runmqchl -c QM0.R1.SENDER -m UNXR1ISQM0$1 & ". It is woking fine. But the next day it is getting stopped automatically. I have to execute the command once again. The Channels are Sender, Receiver channels. Server Connection channels are working fine. Please let me know how to do this.
I am using mqm ID to do this and MQ version is 5.3 on Solaris.
Thanks.... |
|
| Back to top |
|
 |
| Leafar |
| Posted: Mon Aug 11, 2003 8:21 am Post subject: |
|
|
Acolyte
Joined: 03 Apr 2003
Posts: 74
Location: Buenos Aires
|
Is the DISCINT parameter set in the channel definition?
what can you see at the error log?
and in the nohup.out file??
Saludos
RAfael |
|
| Back to top |
|
|
| sarbajit |
| Posted: Mon Aug 11, 2003 8:59 am Post subject: |
|
|
Acolyte
Joined: 22 May 2003
Posts: 53
|
Hi,
No the DISCINT interval is not set. In the error log also it is not writing anything. In the nohup.out it is showing "Channel program started". Also,
it is working properly once I start it manually. Same thing is occuring for command server also. It is getting stopped everyday. |
|
| Back to top |
|
|
| mrlinux |
| Posted: Mon Aug 11, 2003 10:02 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
Are they any messages indicating the channel is comming down in the log files ????? is the box being rebooted daily ???? There is no reason for the command server to come down without a failure or someone stopping it
what info do you see in the /var/mqm/qmgrs/$QMGR_NAME/errors/AMQERR01.LOG file ??
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| sarbajit |
| Posted: Mon Aug 11, 2003 10:40 am Post subject: |
|
|
Acolyte
Joined: 22 May 2003
Posts: 53
|
Hi,
Following are the things we are getting in the log file.
08/11/03 10:41:25
AMQ9545: Disconnect interval expired.
EXPLANATION:
Channel 'QM0.R1.SENDER' closed because no messages arrived on the transmission
queue within the disconnect interval period.
ACTION:
None.
The box is not getting rebooted. The Queue Managers and the other channels like system.admin.svrconn are running all the time. |
|
| Back to top |
|
|
| Leafar |
| Posted: Mon Aug 11, 2003 10:46 am Post subject: |
|
|
Acolyte
Joined: 03 Apr 2003
Posts: 74
Location: Buenos Aires
|
As you can see the message
"Channel 'QM0.R1.SENDER' closed because no messages arrived on the transmission
queue within the disconnect interval period. "
is indicating that you have the DISCINT value different of 0
you must alter the channel sender definition DISCINT(0) to avoid this message or set the xmitq to start the channel every time a message is put in the xmitq
Saludos
Rafael |
|
| Back to top |
|
|
| tej |
| Posted: Mon Aug 11, 2003 5:11 pm Post subject: |
|
|
Novice
Joined: 18 Nov 2002
Posts: 20
|
Hi,
Two things are not clear for me.
1. Is it a cluster channel. If it is a cluster channel, then it is a know issue. In mqseries if the cluster channel went to inactive, some time it will not come up , even there is a message in xmitq.
2. what is the patch level r u using. This u can find by mqver command in command line.
It it is a cluster sender channel - U have to run a cronjob to start the channel. This is the only solution to my knowledge
Let me know if u have any other questions. |
|
| Back to top |
|
|
|
|
