Below are Error Details

Hi Sandeep,

MQ Reason code 3155 means MQRCCF_SUBSCRIPTION_IN_USE. This may be all you need to know but in case it doesn't help, remember that you can use IBM MQ administrative commands to see which durable subscriptions currently have an active connection associated with them, i.e. are "in use".

You can issue MQSC commands like the ones below, with a tool such as runmqsc (or your favourite other MQSC tool if you have one).

DISPLAY SBSTATUS('your-sub-name') ACTCONN

Then using the value returned in the ACTCONN attribute, find the last 16 characters (substring starting at 33 for length 16) and issue this command

DISPLAY CONN(last-part-of-actconn) ALL

The APPLTAG attribute in this output will show you the application name, the USERID field will show you the user it is running under. If it is running over a network connection, the CHANNEL and CONNAME fields will also be relevant. If it is locally bound, the PID and TID will help to narrow it down to the actual process on the machine.

Cheers,
Morag

Below are Error Details

Hi Sandeep,

MQ Reason code 3155 means MQRCCF_SUBSCRIPTION_IN_USE. This may be all you need to know but in case it doesn't help, remember that you can use IBM MQ administrative commands to see which durable subscriptions currently have an active connection associated with them, i.e. are "in use".

You can issue MQSC commands like the ones below, with a tool such as runmqsc (or your favourite other MQSC tool if you have one).

DISPLAY SBSTATUS('your-sub-name') ACTCONN

Then using the value returned in the ACTCONN attribute, find the last 16 characters (substring starting at 33 for length 16) and issue this command

DISPLAY CONN(last-part-of-actconn) ALL

The APPLTAG attribute in this output will show you the application name, the USERID field will show you the user it is running under. If it is running over a network connection, the CHANNEL and CONNAME fields will also be relevant. If it is locally bound, the PID and TID will help to narrow it down to the actual process on the machine.

Cheers,
Morag

Below are Error Details

Hi Sandeep,

I don't know what sample code you want - it sounds like your problem is that there is already an instance of your application running using that subscription hence the MQRCCF_SUBSCRIPTION_IN_USE (3155). If that instance of the application is not supposed to be running, then perhaps you can stop it so that your instance can run instead.

If it's not another instance of your application, then perhaps you need to make sure that your subscription names are unique for each application?

Have you used the commands I suggested to discover where this extra instance of the application came from?

I don't know why using a different channel name allowed your application to start - but perhaps the channel name forms part of your subscription name? Without seeing any of your output from the commands I suggested, I would have no way of knowing and could only guess.

Cheers,
Morag

Hi Sandeep,

MQ Reason code 3155 means MQRCCF_SUBSCRIPTION_IN_USE. This may be all you need to know but in case it doesn't help, remember that you can use IBM MQ administrative commands to see which durable subscriptions currently have an active connection associated with them, i.e. are "in use".

You can issue MQSC commands like the ones below, with a tool such as runmqsc (or your favourite other MQSC tool if you have one).

DISPLAY SBSTATUS('your-sub-name') ACTCONN

Then using the value returned in the ACTCONN attribute, find the last 16 characters (substring starting at 33 for length 16) and issue this command

DISPLAY CONN(last-part-of-actconn) ALL

The APPLTAG attribute in this output will show you the application name, the USERID field will show you the user it is running under. If it is running over a network connection, the CHANNEL and CONNAME fields will also be relevant. If it is locally bound, the PID and TID will help to narrow it down to the actual process on the machine.

Cheers,
Morag

Below are Error Details

Hi Sandeep,

I don't know what sample code you want - it sounds like your problem is that there is already an instance of your application running using that subscription hence the MQRCCF_SUBSCRIPTION_IN_USE (3155). If that instance of the application is not supposed to be running, then perhaps you can stop it so that your instance can run instead.

If it's not another instance of your application, then perhaps you need to make sure that your subscription names are unique for each application?

Have you used the commands I suggested to discover where this extra instance of the application came from?

I don't know why using a different channel name allowed your application to start - but perhaps the channel name forms part of your subscription name? Without seeing any of your output from the commands I suggested, I would have no way of knowing and could only guess.

Cheers,
Morag

Hi Sandeep,

MQ Reason code 3155 means MQRCCF_SUBSCRIPTION_IN_USE. This may be all you need to know but in case it doesn't help, remember that you can use IBM MQ administrative commands to see which durable subscriptions currently have an active connection associated with them, i.e. are "in use".

You can issue MQSC commands like the ones below, with a tool such as runmqsc (or your favourite other MQSC tool if you have one).

DISPLAY SBSTATUS('your-sub-name') ACTCONN

Then using the value returned in the ACTCONN attribute, find the last 16 characters (substring starting at 33 for length 16) and issue this command

DISPLAY CONN(last-part-of-actconn) ALL

The APPLTAG attribute in this output will show you the application name, the USERID field will show you the user it is running under. If it is running over a network connection, the CHANNEL and CONNAME fields will also be relevant. If it is locally bound, the PID and TID will help to narrow it down to the actual process on the machine.

Cheers,
Morag

Below are Error Details

Hi Sandeep,

Have you determined which application currently has your subscription in use? Your post here suggests you don't think that the subscription is in use - you ask how to reconnect to it. I believe you are getting reason code MQRCCF_SUBSCRIPTION_IN_USE (3155) because there is an application currently running that is connected to the subscription. When your instance of the application tries to connect to the subscription it is refused because it is not allowed to have more than one application connected to the subscription at a time.

Please can you review my original answer and discover the application that currently has hold of your subscription.

Your replies suggest you think that your application code can somehow be changed to allow you to reconnect to a subscription that is already being used by another application. What do you imagine should happen to the other application if this happened?

Cheers,
Morag

Hi Sandeep,

I don't know what sample code you want - it sounds like your problem is that there is already an instance of your application running using that subscription hence the MQRCCF_SUBSCRIPTION_IN_USE (3155). If that instance of the application is not supposed to be running, then perhaps you can stop it so that your instance can run instead.

If it's not another instance of your application, then perhaps you need to make sure that your subscription names are unique for each application?

Have you used the commands I suggested to discover where this extra instance of the application came from?

I don't know why using a different channel name allowed your application to start - but perhaps the channel name forms part of your subscription name? Without seeing any of your output from the commands I suggested, I would have no way of knowing and could only guess.

Cheers,
Morag

Hi Sandeep,

MQ Reason code 3155 means MQRCCF_SUBSCRIPTION_IN_USE. This may be all you need to know but in case it doesn't help, remember that you can use IBM MQ administrative commands to see which durable subscriptions currently have an active connection associated with them, i.e. are "in use".

You can issue MQSC commands like the ones below, with a tool such as runmqsc (or your favourite other MQSC tool if you have one).

DISPLAY SBSTATUS('your-sub-name') ACTCONN

Then using the value returned in the ACTCONN attribute, find the last 16 characters (substring starting at 33 for length 16) and issue this command

DISPLAY CONN(last-part-of-actconn) ALL

The APPLTAG attribute in this output will show you the application name, the USERID field will show you the user it is running under. If it is running over a network connection, the CHANNEL and CONNAME fields will also be relevant. If it is locally bound, the PID and TID will help to narrow it down to the actual process on the machine.

Cheers,
Morag

Below are Error Details

Hi Sandeep,

I don't know what sample code you want - it sounds like your problem is that there is already an instance of your application running using that subscription hence the MQRCCF_SUBSCRIPTION_IN_USE (3155). If that instance of the application is not supposed to be running, then perhaps you can stop it so that your instance can run instead.

If it's not another instance of your application, then perhaps you need to make sure that your subscription names are unique for each application?

Have you used the commands I suggested to discover where this extra instance of the application came from?

I don't know why using a different channel name allowed your application to start - but perhaps the channel name forms part of your subscription name? Without seeing any of your output from the commands I suggested, I would have no way of knowing and could only guess.

Cheers,
Morag

Hi Sandeep,

MQ Reason code 3155 means MQRCCF_SUBSCRIPTION_IN_USE. This may be all you need to know but in case it doesn't help, remember that you can use IBM MQ administrative commands to see which durable subscriptions currently have an active connection associated with them, i.e. are "in use".

You can issue MQSC commands like the ones below, with a tool such as runmqsc (or your favourite other MQSC tool if you have one).

DISPLAY SBSTATUS('your-sub-name') ACTCONN

Then using the value returned in the ACTCONN attribute, find the last 16 characters (substring starting at 33 for length 16) and issue this command

DISPLAY CONN(last-part-of-actconn) ALL

The APPLTAG attribute in this output will show you the application name, the USERID field will show you the user it is running under. If it is running over a network connection, the CHANNEL and CONNAME fields will also be relevant. If it is locally bound, the PID and TID will help to narrow it down to the actual process on the machine.

Cheers,
Morag

Below are Error Details

Hi Sandeep,

I don't know what sample code you want - it sounds like your problem is that there is already an instance of your application running using that subscription hence the MQRCCF_SUBSCRIPTION_IN_USE (3155). If that instance of the application is not supposed to be running, then perhaps you can stop it so that your instance can run instead.

If it's not another instance of your application, then perhaps you need to make sure that your subscription names are unique for each application?

Have you used the commands I suggested to discover where this extra instance of the application came from?

I don't know why using a different channel name allowed your application to start - but perhaps the channel name forms part of your subscription name? Without seeing any of your output from the commands I suggested, I would have no way of knowing and could only guess.

Cheers,
Morag

Hi Sandeep,

MQ Reason code 3155 means MQRCCF_SUBSCRIPTION_IN_USE. This may be all you need to know but in case it doesn't help, remember that you can use IBM MQ administrative commands to see which durable subscriptions currently have an active connection associated with them, i.e. are "in use".

You can issue MQSC commands like the ones below, with a tool such as runmqsc (or your favourite other MQSC tool if you have one).

DISPLAY SBSTATUS('your-sub-name') ACTCONN

Then using the value returned in the ACTCONN attribute, find the last 16 characters (substring starting at 33 for length 16) and issue this command

DISPLAY CONN(last-part-of-actconn) ALL

The APPLTAG attribute in this output will show you the application name, the USERID field will show you the user it is running under. If it is running over a network connection, the CHANNEL and CONNAME fields will also be relevant. If it is locally bound, the PID and TID will help to narrow it down to the actual process on the machine.

Cheers,
Morag

Below are Error Details