MQSeries.net :: View topic - Activation Spec & Listener Port-- Conflict?

SAFraser · Posted: Fri Nov 25, 2011 8:32 am Post subject:

I'm not even sure how to ask this question...

Application server: WAS 7.0.1.9 on Solaris 10
MQ server: MQ 7.0.1.3 on Solaris 10

We have a working application that uses a WAS listener port connecting to MQ.

When a new application recently began development, we advised "let's use an activation spec instead of a listener port--the listener port has been stabilized by IBM".

(And, we have an application on a different server that uses an activation spec successfully in production.)

The new code has been bundled into existing application code. This particular Enterprise Application already uses a listener port in WAS. Now is added a function that uses an activation spec.

After the enhanced application is deployed, it appears that both the listener port and the activation spec are running ('green' in Admin Console). However, there are no IPPROCS on the queue associated with the listener port.

I stopped and started the listener port manually; there was no activity in the SystemOut.log at all, even though the port turned 'red' and then 'green' as expected.

I cannot see this as an MQ problem at all, but the development teams do look to us for help with client connection problems.

Could this be an application code problem? Is it impossible to run both a listener port and an activation spec in the same application? Am I doomed to open a PMR?

Thanks.